Last updated 27 July 2026
Cookie policy
Airrow uses only the cookies the service needs to function. There are no advertising or tracking cookies, and nothing is shared with third parties for profiling.
We do measure how many people visit the site, and we do it without cookies — see how we count visits below. That is why there is still no banner asking you to accept anything: strictly necessary cookies do not require consent, and measurement that stores nothing on your device does not either.
What is set
| Name | Purpose | Lifetime |
|---|---|---|
airrow-theme | Remembers whether you chose the dark or light theme, so the first paint is already correct. Holds one of two values and nothing else. | One year |
sb-* | Authentication cookies set by our auth provider, Supabase. They keep you signed in and let the session refresh. Without them you cannot use an account. | Session, refreshed while you stay signed in |
How we count visits
We use Vercel Web Analytics, which is cookieless. It sets no cookie, writes nothing to your browser's storage, and reads nothing that is already there. It records that a page was viewed — the page, the referring site, and coarse details like country, browser and device type — and aggregates it. It does not build a profile of you, does not follow you to other sites, and is never joined to an account, a workspace or a project.
We also use PostHog to see where people get stuck: that an interview was started, which question it was abandoned at, that a foundation was generated or downloaded. It is configured to keep nothing on your device either — no cookie, no local storage — which means it cannot recognise you when you come back, and we accept a less precise count rather than ask you for a cookie. It never receives your name, your email address, your interview answers or anything Airrow generated for you.
This is why you are not asked to consent to it. The rule that makes consent banners necessary is about storing or reading information on your device; measurement that does neither does not trigger it. We rely on our legitimate interest in knowing whether people can find the service at all, and we have chosen a tool that buys that answer at the lowest cost to you.
Both run only on the public pages. Nothing you do while signed in to your workspace is measured this way.
If you would rather not be counted at all, any content blocker will stop the script, and the site works exactly the same without it.
Browser storage
If you start the interview before creating an account, your draft answers are held in your browser's local storage under airrow-guest-interview until you sign in and claim them. Nothing is written to our servers before that. Clearing your browser data removes the draft.
Controlling cookies
Your browser can block or delete cookies for this site. Blocking the theme cookie only means the site forgets your theme. Blocking the authentication cookies means you cannot stay signed in, so the signed-out interview is all that remains usable.
More
What we store beyond cookies, and who processes it, is in the privacy policy. Questions go to hello@airrow.app.
Airrow is in early access. These pages describe how the service actually works today. The operating entity, registered address and governing law are published here before general availability, and the date above changes whenever anything on this page does.