Cookies

Logging in needs cookies, so those are always set. Google Analytics is the only optional one, it only runs on the public pages (the homepage, signup, login and pages like this one), and only if you pressed Accept. It never runs inside the app once you're logged in.

Declining doesn't change anything about how GT Vault works, and you won't be asked again unless you ask to be.

Supabase sign-in

Keeps you logged in. GT Vault can't work without these.

gtv_seen

Only set when you're logged in. It holds a date and nothing else, and it's used to count you as active at most once a day.

_ga

Tells one browser apart from another, so a returning visit isn't counted as a new person. Expires after 2 years.

_ga_<id>

Keeps track of the current visit. Expires after 2 years.

Both are set by Google Analytics. Neither carries your name, email or account, and GT Vault never sends any of those to Google. Google keeps the data for 14 months.

I look at how people find GT Vault and which public pages they read, so I can work out what's worth improving. It isn't connected to any advertising, and I don't retarget anyone. There are no advertising pixels on GT Vault.

Your answer is kept in your browser's local storage, not in a cookie, so it's never sent to my server, and it doesn't follow you to another device or browser.

Worth knowing: clearing your browsing data clears the answer too, and the question comes back. That's the storage working properly, not your choice being ignored.

Use the switch at the top of this page. Withdrawing is as easy as agreeing was, one press, no form and no reason needed. It clears the cookies Google set and stops the tag sending anything.

You can also block or delete cookies in your browser settings, which works regardless of anything on this page. Blocking the sign-in cookies will log you out though.

The privacy policy covers everything else: what GT Vault collects, who processes it, how long it's kept and how to get it deleted. For anything it doesn't answer, email james@gtvault.app.