Privacy

We process the names, memories, facts, tone choices, and optional email address you submit. Please use only information you have permission to share and avoid unnecessary sensitive details.

Stripe processes payment details. DraftedFor receives the checkout status, amount, product, customer contact details supplied at checkout, and a compressed copy of the form input stored in Stripe Checkout metadata so a paid draft can still be delivered if the browser closes.

Your browser keeps a working copy in session storage until that browser session is cleared. The server uses deterministic templates to build the draft. When an optional model-assisted rewrite is configured, paid draft text and the details needed to revise it may also be sent to Groq or OpenRouter. The deterministic version remains the fallback.

A paid draft may be shown in the browser and sent by email through Resend or the operator's delivery service. Those processors handle the information needed to provide their service under their own policies.

DraftedFor uses a self-hosted Umami analytics script for aggregate visits and funnel events. It is configured as privacy-friendly analytics without advertising cookies. Technical server logs may also record request time, route, and error information; form answers are not intentionally written to application logs.

DraftedFor does not maintain a separate customer-profile database. Stripe, email providers, hosting logs, and browser storage retain data according to their policies and account settings. Payment and transaction records may be retained where required for accounting, fraud prevention, or law.

You can clear browser session storage at any time. To request access, correction, or deletion of information controlled by DraftedFor, email hello@toledotechnologies.com. Some payment or accounting records may need to be retained.