Cookie & Storage Policy

AuditOwl · Last updated 14 August 2026

This policy explains the cookies and similar technologies (such as browser localStorage) that AuditOwl uses. The short version: we do not track you. Everything we store is strictly necessary to run the service you asked for, so under UK rules (PECR and the UK GDPR) there is nothing here that requires your consent — only that we tell you about it, which is what this page does.

1. We do not set tracking cookies

AuditOwl uses no analytics, advertising or tracking cookies. We embed no third-party marketing pixels, no session recording and no A/B testing tools. Sign-in uses browser localStorage (listed below) rather than cookies.

This is also why you are not asked to accept anything when you arrive. A banner asking for consent to tracking we do not do would be noise, not transparency. If we ever add a non-essential tool, this page changes and a genuine choice comes back with it.

2. What we store in your browser

Name	Purpose	Category
auditai.accessToken	Keeps you signed in (short-lived session token).	Strictly necessary
auditai.refreshToken	Renews your session without re-entering your password.	Strictly necessary
auditai.theme	Remembers your light/dark theme.	Strictly necessary
auditai.currency	Remembers your preferred currency for amounts.	Strictly necessary
auditai.notifLastSeenAt	Tracks which notifications you have already seen.	Strictly necessary
auditai.activeClientId	Remembers which client you last worked on, so the sidebar can take you back to it.	Strictly necessary

All of it stays in your own browser. None of it is a cookie, so none of it is sent to us automatically with each request, and none of it is readable by another site.

None of it is written just because you looked. Visiting our public pages without signing in stores nothing at all: the theme entry appears only once you actually pick a theme, and the rest only once you have an account to keep.

3. Third-party services

Google Sign-In — loads on the sign-in and registration pages, and nowhere else on this site. It loads when one of those pages opens, not only if you choose Google, because Google's own script is what draws the button. That script may store a cookie named g_state on this domain, which Google uses to remember the state of its sign-in prompt; because it sits on our domain your browser sends it to our servers with each request, and we ignore it. Google may also set cookies on its own domains as part of signing you in.
Stripe — when you go to pay, Stripe may set cookies needed for secure payment and fraud prevention on its own hosted checkout and billing portal. No Stripe code runs on this site; paying takes you to a page Stripe hosts.

Neither is used to profile you and neither runs on our marketing pages. Both exist for something you set out to do — signing in, or paying.

4. Clearing what we store

Signing out removes the session entries. To clear everything, use your browser's "clear site data" or cookies-and-site-data settings for this site. The strictly necessary items cannot be switched off while you use the app, because the app cannot work without them — signing out or clearing site data is how you remove them.

5. Contact

Questions about this policy? Email supportauditai@gmail.com.