Cookie policy
Last updated: 12 October 2026. Contact: anubhab7105@gmail.com
No cookies, no analytics
Assembly sets zero cookies: no login cookies (there are no accounts), no consent-tracking cookies, and no third-party advertising or analytics cookies. There is no Google Analytics, no Meta Pixel, no Hotjar, and no social-media trackers on this site. Fonts are self-hosted, so loading a page does not call Google Fonts servers. Because there are no non-essential cookies, there is nothing for a consent banner to switch off; the banner on this site is informational and dismisses without recording anything about you beyond its own dismissal.
What is stored instead
| Storage | Purpose | Control |
|---|---|---|
| _none by Assembly_ | No cookies are set by this site. | Not applicable. There is nothing to accept or reject. |
| assembly (IndexedDB) | Your keys, run history, settings, usage counters, privacy acknowledgment. Stays on your device. | Delete via History and Settings, or clear browser site data. |
| assembly:* (localStorage) | Fallback mirror used only when IndexedDB is unavailable, plus the cookie-banner dismissal. | Clear browser site data. Runs still work; saved data may not persist. |
| Host logs (Vercel, Render) | IP addresses and request metadata in platform operational logs under their policies. | Platform-controlled. See their policies. |
Do-not-track and consent
With no analytics or advertising, there is no behavioral tracking to opt out of. The one consent that matters is the in-app privacy notice: a run cannot start until you tick the acknowledgment checkbox confirming your question goes to your chosen providers. Withdrawing that consent is the same as stopping use: remove your keys and clear site data.