Privacy Policy

What we collect

Almost nothing.

When you sign in with Google, we receive your name and email address to authenticate your session. That is it.

We do not collect:

• Your writing
• Your brainstorming sessions
• Your journal entries
• Your highlights or notes
• Your reading activity
• Your AI conversations
• Analytics or usage tracking
• Cookies beyond session authentication

Where your data lives

Wretify is a client-side application. Your browser talks directly to the Google Drive API using your own OAuth token. Your writing is stored and synced without passing through our servers. The one exception is the AI: when you ask it something, the text you send it passes through our server on its way to the provider you chose (see below).

If you delete Wretify today, your files remain exactly where they are. No export needed. No migration tool. No rescue operation.

There is one database, and your writing is not in it. We are specific about this rather than sweeping, because a promise you have to trust is worth less than one you can check. It holds exactly these things about you, and only if they apply:

• Your email address, if you joined the waitlist. You typed it in to be told when Wretify launches. That is the only thing it is used for, and asking us to remove it is enough.
• A record of your access, from the first time you sign in. It is keyed to the anonymous account id Google gives us, and holds when your free months began and end, and — if you subscribe — what you paid for and until when. Beside it we keep the email address you signed in with, for one purpose only: to tell you before your free months end, and when they have. A short log records that those two messages were sent. Nothing about what you write, when you write, or how much.

That database also holds this website: the articles, the pages, the words you are reading now. Those are ours, not yours.

AI and API keys

Wretify uses a BYOK model (Bring Your Own Key). When you connect an AI thinking partner (Claude, Gemini or DeepSeek), you provide your own API key. Your key is saved in your browser and in a file in your own Google Drive (Wretify/_keys.json), so it follows you to your other devices. To remove it completely, disconnect the key in Wretify and delete that file.

When you use the AI, your key travels with the request through our server to the provider. We do not log or store your key or the content of these requests. They pass through and are gone.

We do not train any model on your data. We cannot: your writing is in your Drive, not ours.

Cookies and tracking

We use a single session cookie for authentication. That is the only cookie.

We do not use:

• Google Analytics
• Facebook Pixel
• Hotjar, Mixpanel, Amplitude, or any analytics tool
• Advertising trackers of any kind
• Fingerprinting

There is no cookie banner because there is nothing to consent to.

Third-party services

The only third-party services involved are:

• Google OAuth — for sign-in
• Google Drive API — for storing your files in your own Drive
• Vercel — for hosting the application
• AI providers (your choice) — Anthropic, Google or DeepSeek, using your own key
• Polar — for payments, if you subscribe (we never see your card)
• Neon — hosts the one database described above
• Resend — sends the two emails about your free months

We do not sell, share, or transfer your information to anyone. There is no information to sell.

Your rights

You have the right to:

• Access — your data is already in your Drive, in plain text
• Delete — delete the Wretify folder from your Drive, and your writing is gone. To have your access record and email removed from our database as well, write to us through the contact page and we will delete them.
• Export — your files are already Markdown, the universal format
• Leave — sign out and never come back, nothing is left behind

We designed it so that your writing never needs us: it is already in your hands. The only things we hold — the access record and an email address — are removed when you ask.

Changes to this policy

If we ever change this policy, we will update the date at the top and notify users in the app. But honestly, this policy is unlikely to change because the architecture makes it almost impossible to collect data even if we wanted to.