Summary. No HTTP cookies. No analytics. No advertising. No third-party embeds. Three localStorage keys, all non-sensitive, described below.
1. Cookies versus local storage
A cookie is a small piece of data sent by a server and stored by the browser, then automatically attached to subsequent requests to that domain. Local storage is a browser-side key/value store that is never sent automatically over the network; it is only readable by scripts running on the same origin.
PromptScrubber sets no cookies. Everything it remembers is written to local storage and stays on your device.
2. Cookies used by this site
None. The application code does not call document.cookie and does not create session cookies. No consent banner is displayed, because there is no optional technology that would require consent.
The hosting provider may set strictly technical cookies at the network edge for security or load balancing. Those are outside the application code; if the deployment’s provider does so, their own documentation applies and the list below must be updated accordingly before publication.
3. Local storage keys
| Key | Type | Purpose | Lifetime |
|---|---|---|---|
ps-theme |
localStorage | Remembers whether you chose the light or dark theme. | Until you clear it. |
ps-settings-v1 |
localStorage | Stores which detection categories are enabled. | Until you clear it. |
ps-consent-v1 |
localStorage | Stores your consent choice and the moment you made it. | Until you clear it or withdraw consent. |
Session storage and IndexedDB: not used. Cached documents: none — the text you paste is never written to any persistent browser storage.
4. Third-party technologies
The pages load no third-party scripts, fonts, stylesheets, images or frames. The PDF and DOCX readers are bundled in the vendor folder of this site; they are served from the same origin and make no external request. There is no Google Analytics, no advertising tag, no social plugin, no session recorder and no A/B testing tool.
5. Consent management
A consent manager is present in the code and reachable through Cookie Settings in the footer. It is built to gate any future optional category:
- Necessary technologies are always active and explained.
- Analytics, Advertising and Third-party services are listed as Not in use because no provider is configured.
- If a provider is configured in
site-config.js, its toggle becomes active, a banner appears with Accept All, Reject Optional and Customize at equal prominence, and nothing loads before a choice is stored.
There is no dark pattern: rejecting is as easy as accepting, no category is pre-selected, and no consent is inferred from continued browsing.
6. How to remove stored data
- In the app: press “Wipe all data” to clear the current session from memory. To remove the three keys, use “Cookie Settings” and reject the optional categories, then clear site data in your browser.
- In your browser: open the site settings (padlock icon in the address bar) and delete the site data, or clear browsing data for all sites.
Deleting site data removes your theme choice and detection preferences. Nothing else is lost, because nothing else is stored.
7. Changes
If a cookie or an optional technology is ever added, this page will list it — name, provider, purpose, duration — before it is activated. The current text reflects the shipped code, which contains none.
8. Contact
Questions: [CONTACT_EMAIL] · contact page.