Cookie policy

A cookie is a small string of text your browser stores when a site asks it to. The site reads it back on the next visit to remember something useful — who you are, what you clicked, whether you already answered a question. Cookies are not programs. They cannot run code on your device.

Local storage does the same job with a different mechanism, and we treat it under the same rules: if it tracks you, it needs your consent.

Amplitude, configured to record only page views and sessions. No clicks, no form input tracking, no session replays, no web vitals. That is the entire list. No ad networks, no social pixels, no third-party fonts phoning home. When you load a page on this site and you have not yet consented, no tracking cookies are set. The consent decision itself is stored in a cookie and in local storage so we do not ask you twice — that one is functional, not tracking, and it does not need consent.

Amplitude’s browser SDK sets first-party cookies on this domain to recognize your device and stitch a session together. They load only after you allow analytics. The exact names can shift between SDK versions, so the table names the purpose rather than a brittle string.

Amplitude may also write to local storage for the same purposes. Clearing your browser data removes all of it.

The only cookie that loads before you decide is antagosoft_consent, and it exists solely to remember what you chose. No analytics, no fingerprinting, no marketing. The site is fully usable with every other cookie blocked.

The first time you visit, a banner asks whether to allow analytics. Skip it and nothing tracks you. Allow it and Amplitude loads.

You can also clear the antagosoft_consent cookie in your browser settings, which re-shows the banner. Withdrawing consent stops new data from being collected. Existing analytics data already sent to Amplitude follows the retention period in our privacy policy.

Questions about this cookie policy go to [email protected].