Privacy Policy

• Account info. When you sign up we collect your email address and username through our auth provider (Clerk). We do not collect or store passwords ourselves.
• Text you humanize. The text you submit is sent to our backend and passed to a third-party AI rewriting provider to produce the result. We do not store the text you submit or the rewrite. We keep only the number of words you used.
• Question content (Extension). When you double-click a question with the Extension, the visible text of that question (and any answer choices on the page) is sent to our backend so we can generate a hint or answer. We do not store it. We do not collect screenshots, browsing history, or any other page content, and the Extension reads nothing until you double-click.
• Usage counts. We record how many words you humanize per month and how many solver requests you make per day, so we can enforce plan limits.
• Billing info. If you buy a plan or a word pack, payment details are handled entirely by Stripe, which is the merchant of record for the purchase. We never see your card number; we store a customer ID, your current plan and a record of each word pack (words, amount, date).
• Sign-up checks. When an account is created we record the country and a one-way hash of the IP address it was created from, and a normalised form of the email address. We use these only to stop one person from collecting the free trial many times over; the raw IP address is not kept.
• Error logs. When something breaks on our side we log the request path, time and error message so we can fix it. These logs do not include the text you submitted.
• Page views. We count visits with a cookieless analytics tool. It does not identify you or follow you across other sites.

• To produce the rewrites, answers and explanations you ask for.
• To track usage against your plan’s monthly or daily limits.
• To send you essential account and billing email (e.g. receipts, plan changes).
• To debug, prevent abuse, and improve the Service.

We do not sell your personal data, and we do not use your text or question content to train AI models.

• AI rewriting provider — the text you submit for humanizing is sent to a third-party AI rewriting service to generate the result. That provider processes it under its own terms and privacy policy. We send the text only, not your name, email or account ID.
• OpenRouter and Google— question text from the Extension is sent through OpenRouter to Google’s Gemini API to generate the hint or answer. We send the question and its answer choices only, never your name, email or account ID. Both providers process it under their own terms; on the paid API tier Google does not use it to train models.
• Clerk — handles authentication and stores your email, username and session.
• Stripe — the merchant of record: processes every payment, stores your billing details, collects sales tax, issues receipts (via Link) and may contact you about a refund or dispute.
• Neon (Postgres host) — stores our database (account, plan, usage counts).
• Vercel — hosts the Site, runs our backend and provides the cookieless page-view analytics.

We do not share your data with anyone else.

• Account data is kept while your account exists. You can delete your account from Settings in the dashboard at any time; doing so cancels any subscription and removes your usage records within minutes. Stripe keeps payment records for as long as the law requires.
• Text you humanize and question content are processed to produce a result and are not retained by us after the response is returned.
• Usage counts are retained for billing and abuse prevention.

• The Extension only sends data to this Site’s servers. It does not contact any other server.
• DripWrite runs entirely in your browser: the text you type out never leaves it. Google Docs mode uses Chrome’s debugger permission only to send keystrokes to the document while a run is active; it reads nothing from the page.
• The Extension only reads page content when you actively double-click a question.
• The Extension stores your preferences (mode, enabled state) and a connection token for your account locally in your browser via chrome.storage.local. You can revoke that token from the Extension page in your dashboard or by clicking Disconnect in the Extension.

We use a session cookie set by Clerk to keep you signed in, and so that the Extension can identify you when it calls our API. We do not use third-party tracking or advertising cookies.

The Service is not directed to children under 13. If you believe a child has signed up, contact us and we will delete the account.

We may update this policy. Material changes will be announced on the Site. Continued use of the Service after changes means you accept the updated policy.

Questions or deletion requests: zapplayz1@gmail.com.