1. At a glance
- We use one necessary first-party cookie to remember your analytics choice.
- PostHog product analytics is optional and only starts after you opt in.
- Cloudflare Web Analytics is cookie-free and does not use browser storage for its measurement.
2. Necessary preference cookie
We need to remember whether you accepted or rejected optional analytics. This preference cookie is not used for advertising or to identify you directly.
- Name
atotoi_consent- Purpose
- Stores a versioned choice: analytics accepted or rejected.
- Provider and type
- Ātotoi; first-party, necessary preference cookie.
- Scope
- Path
/;SameSite=Lax; markedSecureon HTTPS. - Retention
- Up to 180 days, unless you change or clear your choice.
3. Optional PostHog analytics
PostHog is not loaded until you choose analytics. When it is enabled, it may set first-party cookies and use local or session storage to operate product analytics. We use an EU cloud project and record only a landing-page view and Etsy CTA click, including the CTA location.
The exact PostHog cookie and storage key names are generated by its SDK and can change. They commonly begin withph_orposthog. We do not enable autocapture, session recording, error tracking or device-model collection.
4. Cloudflare Web Analytics
Cloudflare Web Analytics helps us understand high-level traffic and site performance. It is designed to be cookieless: it does not set cookies or access local or session storage for this measurement.
It is therefore separate from the optional PostHog setting. We use Cloudflare's aggregated reports to operate, protect and improve the site.
5. Changing or withdrawing your choice
You can change your optional analytics choice at any time. If you reject analytics after accepting it, we stop future PostHog collection and clear PostHog cookies and browser storage created by this site where possible. Withdrawal does not retrospectively remove events already held in PostHog.
You can also clear browser data through your browser settings. For a privacy request, contact privacy@atotoi.me.
6. Production verification checklist
Before each production release, verify the deployed site in a real browser: before consent, PostHog does not send requests; after acceptance, configured events can be sent; after withdrawal, later PostHog requests are blocked and its browser data is cleared.
Check the deployed site's browser storage and network panel against the necessary-cookie details above. This keeps the notice accurate if an integration or browser behaviour changes.