Cookie Policy

This page explains the cookies and similar local-storage technologies that agntly uses, why they exist, and how you can control them. It supplements our Privacy Policy.

We keep this list short. agntly works without third-party advertising trackers.

Strictly necessary — authentication

• Clerk session cookies (e.g. __session, __client_uat). Set by our identity provider Clerk to keep you signed in across pages and to protect against session hijacking. Without these, signing in is not possible.
• cookie-consent(localStorage). Stores your banner choice (“accepted” or “declined”) so we don’t ask again on this device.

Analytics

• Vercel Analytics. Aggregate page-view counts, navigation patterns, and performance metrics. No cross-site identifiers are set; the data is stored in aggregate by our hosting provider Vercel.
• Error and performance logs. Anonymous logs that help us diagnose bugs and slowdowns. These are kept for up to 90 days.

What we do NOT use

• Third-party advertising or retargeting cookies.
• Cross-site tracking cookies for behavioural profiling.
• Session-replay tooling that records keystrokes or screen content.

You have several ways to control cookies on agntly:

• Click Decline on the cookie banner the first time you visit. Strictly necessary authentication cookies will still be set when you sign in (they are required for the service to work), but analytics will be disabled.
• Use your browser settings to block or delete cookies from agntly.app and its subdomains. If you block authentication cookies you will not be able to sign in.
• Clear thecookie-consentkey from your browser’s local storage to see the banner again.
• Send a Global Privacy Control or Do Not Track signal — we honour these by treating the visit as “declined” for analytics purposes.

If we add or remove a category of cookie, we will update this page, refresh the “Last updated” date, and re-prompt users via the consent banner where appropriate.

Questions about how we use cookies? Email hello@agntly.app.