✎ PROWRIT privacy

Privacy

Last updated 2026-07-26 · written to be read, not scrolled past

Prowrit is built by one person, funds itself with nothing (it's free), and wants exactly as little of your data as the product needs. Here is the complete picture.

What we store, and for how long

What your brief is used for

One thing: engineering your workflow. Your brief is sent to Anthropic's Claude via AWS Bedrock — under AWS's terms, Bedrock does not use your inputs to train models. We don't sell, share, or mine anything you paste. Generated cards are unlisted — only people you give the link to can see them, and search engines are told not to index them.

What we don't have

No ad trackers, no analytics cookies, no fingerprinting, no third-party pixels. The site sets no cookies at all; your signed-in session lives in your own browser's storage.

What we count

Four anonymous counters, so the product improves on evidence instead of guesswork. They are tallies, not records — no identifier is attached to any of them, which also means we cannot reconstruct your session, and neither can anyone else:

Never sent: your brief, the generated workflow, your answers, your email, or any id that could link two of these together. The server accepts only a fixed list of event names and a fixed list of values for each, so even a bug in our own code cannot smuggle your text into a counter. They become numbers in our own AWS metrics — no third party, nothing stored per person, and no cookie involved.

Erasing everything

Signed in → My studio → Account → Delete my account. This permanently erases your saved workflows, revision memories, cards, MCP key, and the sign-in itself — immediately, no email dance, no retention period. Anonymous runs erase themselves within 30 days regardless.

Questions

Write to privacy@prowrit.com. A human (the human) answers.