Privacy Policy

Files you convert are uploaded over an encrypted (HTTPS) connection and processed on our servers. File contents are handled in memory to perform the conversion and are not stored after your converted result is produced. We keep metadata about each conversion — file names, sizes, detected formats, conversion warnings, and timing — to operate quotas, debug failures, and understand which converters matter.

Without an account:a randomly generated anonymous identifier stored in your browser, a coarse first-touch attribution record (referring site, landing page, UTM parameters, browser language region, and timezone), and the conversion metadata above. Conversions made through our MCP/API endpoint are metered by a one-way hash of the caller's IP address; the IP itself is not stored.

With an account: additionally your email address, name, and sign-in method (email/password or Google), and your plan and usage balances.

We do not use third-party advertising or cross-site tracking.

Billing runs through Autumn and Stripe. Your payment card details go directly to Stripe and never touch our servers; we see your plan, purchase history, and billing status. Stripe's handling of your data is covered by the Stripe Privacy Policy.

We use a small set of infrastructure providers to run the service: Convex (backend and database), Fly.io (hosting), Stripe and Autumn (billing), Resend (transactional email, such as password resets), and Google (optional sign-in). Each receives only what it needs to perform its function. We do not sell your data or share it with anyone for marketing.

Conversion metadata and account data are retained while the service operates or your account exists. To delete your account and its associated data, email us and we'll handle it promptly.

Questions, deletion requests, or anything unclear: [email protected]. More about who runs CutConvert is on the About page.