Privacy Policy
This describes how the application actually handles your data today, not a legal template.
What happens to an uploaded file
Your browser uploads files directly to our private object storage (Cloudflare R2) using a short-lived, single-use signed link - file bytes never sit in an email, log, or database row. Files are stored under a random, unguessable path, never under your original filename. When a workflow runs, the server downloads the file into a temporary working directory, runs the tools you requested, and uploads the result back to storage; the temporary copy is deleted as soon as the job finishes. You then download the result via another short-lived signed link straight from storage - results never sit at a permanent public URL.
How long files are kept
Files from an anonymous (signed-out) session are deleted within 2 hours. Files from a signed-in account are deleted within 24 hours. Deletion happens two ways: a scheduled job that removes expired files on a short interval, and a storage-level lifecycle rule as a second, independent backstop in case that job is ever delayed. Neither your original file nor the tool's output is kept beyond that window.
The AI Agent and AI-powered tools
The AI Agent's planning step reads your typed instruction and your files' names, types, and sizes - never file contents - to decide which deterministic tools to run. Deterministic tools (the vast majority of what this site offers) never call any AI provider and never send your data anywhere outside our own infrastructure. If you connect your own AI provider key (BYOK) for an AI-powered feature, requests for that feature go directly to the provider you chose, under that provider's own terms; we store that key encrypted (AES-256-GCM) and never display it again after you save it, never log it, and never send it to your browser.
Account data
If you create an account, we store your email, an encrypted password (handled entirely by Supabase Auth - we never see or store your plaintext password), and the usage/plan/AI-credit records needed to run the product. Signing in with Google shares only the profile fields Google discloses in its consent screen. You can delete your account at any time from Account → Security, which removes your profile, subscription record, AI credits, connected AI provider keys, saved workflows, and any files not already expired.
Payments
Paid plans are billed through Dodo Payments. Card and payment details are entered on Dodo's own checkout page and processed by Dodo - we never receive or store your full card number. We keep a record of the plan you purchased, its status, and billing events for support and accounting purposes.
Cookies
Signed-in sessions use a standard authentication cookie. If you use tools while signed out, we set one cookie holding a random, signed anonymous identifier so free usage limits can be enforced without an account - it identifies a browser session, not you personally, and carries no tracking or advertising purpose.
What we don't claim
We don't describe this as end-to-end encrypted, zero-knowledge, or unhackable. Files are decrypted-at-rest in storage and temporarily written to server disk while a workflow actually runs, which is a normal and necessary part of running the tools you request. If you're handling highly sensitive documents, weigh that against any tool that processes files on infrastructure you don't control, including this one.