Your privacy is our product.

For implemented local PDF and image tools, selected file bytes are read and processed in the browser. ZANCTA does not receive those bytes for processing. Background removal is deferred rather than sending an image to an undisclosed cloud fallback.

This boundary does not control browser extensions, malware, operating-system backups, device sharing, or future features that are explicitly offered as optional cloud services.

If you create an account, the application stores information needed for authentication and entitlements, such as email address, optional name, password hash, sessions, verification tokens, and password-reset tokens. Passwords are not stored in plain text.

Authentication uses session mechanisms needed to keep an account signed in. Local tool results are held in the browser session for preview, copy, or download. Closing or clearing the workspace releases the active local result state.

When enabled and configured, a payment provider handles checkout and billing, and an email provider delivers verification or password-reset messages. Those providers receive only the information needed for their service. Live provider configuration and delivery verification are not claimed here unless they have been completed.

No live advertising provider is enabled in the current application. If an analytics function is explicitly configured, the product may send a coarse completion event without filenames or file contents. Any future analytics or advertising provider must be disclosed, must not receive file content, and must stay outside the active tool workflow.

ZANCTA does not retain selected file bytes for implemented local processing. Authenticated account deletion removes associated application account records through the account flow. Provider retention, user-rights requests, and jurisdiction-specific retention language require legal review before launch.