Privacy by design.
Any File Type is designed to minimize unnecessary data collection while still supporting accounts, usage limits, subscriptions and site reliability.
File processing
Current conversion and file-utility tools process the selected file content in your browser. Some formats load supporting conversion software into the browser, but the file itself is not sent to the Any File Type backend just to perform the conversion. The backend can receive usage-completion events and ordinary web requests without receiving the selected file contents.
Accounts
Account sign-in is provided through Clerk. If you create an account, Any File Type stores the email address associated with the account along with plan status, daily usage and subscription-related identifiers needed to operate the service. Clerk may process the account information required for authentication. Any File Type does not display profile photos.
Payments
Paid subscriptions and self-service billing are handled by Stripe. Any File Type does not store raw card numbers. We store only the Stripe customer/subscription identifiers and subscription status needed to activate or remove Pro access.
Analytics
Any File Type uses Google Analytics to measure site visits and interactions so we can understand which pages and tools are useful and improve the service. Google Analytics can receive information such as page URL, referrer, browser/device information and general location derived from network information. Analytics is not used to send the contents or filenames of files selected for conversion.
Usage and site counters
The service uses a first-party browser identifier for guest daily limits and to count a browser at most once per UTC day for the public visitor counter. Signed-in daily limits are tied to the account instead. Standard hosting and security logs may also include information such as IP address, request time, user agent and requested URL.
Service providers
Clerk provides authentication, Stripe provides subscription billing, and Cloudflare provides site delivery and backend infrastructure. Unsplash currently hosts limited visual imagery used by the Ivy avatar and seasonal promotional artwork; loading those images can create a direct browser request to Unsplash. Remote images are requested with a no-referrer policy to avoid sending the Any File Type page URL. These providers may process limited information needed to deliver their respective services under their own privacy terms.
Local storage
Browser storage is used for local conveniences such as up to 6 recent tools, up to 12 saved favorites for a signed-in account on that browser, and remembering whether a seasonal offer has already been shown. Clearing browser storage can remove those local conveniences even if the account still exists.
Questions
For help with conversions, account limits, billing controls or file handling, visit the Help Center or email support@anyfiletype.com. Do not send passwords, full payment-card numbers or private file contents by email. This policy will be updated when data practices materially change.
Optional temporary encrypted sharing
When you choose to create a share link, your browser encrypts a copy of the file and its name before upload. The service stores ciphertext and expiry information. The decryption key is carried in the link fragment and is not included in the server request. Anyone with the complete link can decrypt the file. Access expires after 15 minutes; scheduled cleanup removes expired encrypted copies. Revoke a link early from its result card. This feature requires sign-in and has size and daily limits.
Workspace settings and local engines
Saved presets stay in this browser and exclude file contents and verification keys. Files stay in memory while a local workspace is open. Explicitly choosing Continue in workspace creates a short-lived device-local handoff that is removed when received or cleared. Model and processing-engine downloads may contact their asset providers; your input files are processed locally. Clearing a workspace releases its file references; this does not guarantee immediate physical overwriting of device memory.
Developer API
API requests send the selected text to the service for processing. API keys are stored as hashes. Daily per-user call counts are stored for quotas. The API does not store submitted text as a file or conversion history. Do not submit passwords or private tokens to an unrelated conversion operation.