A small browser footprint.
This notice describes the cookies and browser storage used by the current WishCodes web app. Last updated September 1, 2026.
At a glance
No ad pixels. No browser replay.
The current app does not load a browser PostHog SDK, run autocapture, record sessions, capture DOM text or send full tokenized URLs to analytics. It uses a small number of first-party mechanisms for session security and the accountless management link.
Browser storage
Private management-link convenience
After a profile is created, the recipient may have the private management link saved in first-party local storage on that device. It is a convenience for an accountless product; it contains the link itself, so treat the device as private. Clearing browser storage removes the convenience copy, not the profile.
No persistent analytics identifier
The client creates an in-memory pseudonymous event identifier when explicit analytics are sent. It is not saved in a cookie or local storage, and it is not a name, answer, profile or capability.
No advertising storage
The current implementation does not use advertising cookies, third-party tracking pixels or cross-site ad identifiers.
Questions
For the broader data boundary, vendors and rights information, read Privacy or How we use data. Contact work@atharv.me with a privacy question.