Writes a ready-to-send GDPR access, GDPR erasure or CCPA deletion letter, cites the correct article, and puts the real statutory deadline in writing.
Most people never send these letters, not because the right is unclear but because the wording feels like a legal exam. It is not. A valid request only has to identify you, say what you want, and name the right the law gives you.
The generator also does the part people forget: stating the date you expect an answer by. That turns a vague ask into a dated obligation, and it is the evidence you would need if you later complained to a supervisory authority.
| Request | Legal basis | Deadline to answer |
|---|---|---|
| See what they hold | GDPR Article 15 | One month, extendable by two further months |
| Have it erased | GDPR Article 17 | One month, extendable by two further months |
| Deletion (California) | CCPA | 45 days, extendable by another 45 |
The GDPR deadline is Article 12(3): the controller must respond "without undue delay and in any event within one month of receipt of the request", and "that period may be extended by two further months where necessary, taking into account the complexity and number of the requests". The California Attorney General states businesses must respond within 45 calendar days, extendable by another 45 if they notify you.
The erasure letter also asks for confirmation under Article 19, that recipients of the data have been told about the erasure. That is the clause people leave out, and it is the one that propagates.
Everything runs in the browser. No server, no analytics, no storage, no network request once the page has loaded. Your name and email never leave the tab.
This reproduces rights that exist in published law and nothing more. Whether a given company is covered, and what it may lawfully refuse, depends on your situation.
No build step, no dependencies. Open index.html, or serve the directory:
python3 -m http.server 8000
MIT.