Archify

Cookies

The short list.

A handful of first-party cookies, no third-party trackers. Here’s every one, what it does, and how to be rid of it.

Last updated 2026-06-08

01

No trackers, no ads

We don’t use third-party analytics, advertising pixels, or cross-site trackers. Every cookie below is first-party and set by Archify alone.

02

Strictly necessary

  • Supabase session — set only when you sign in; keeps you signed in. First-party, httpOnly.
  • archify_gate — set only if you enter a password to view a gated area of the site. First-party, httpOnly.
03

Analytics — first-party only

archify_v_id is a random, anonymous ID for our own page-view counter. It isn’t derived from your email, IP, or any personal detail, it never leaves our database, and the site works fine without it. First-party, httpOnly, expires in a year.

04

The deck cookie

archify_deck is set only if you unlock the private pitch deck with a token. It’s scoped to /deck and expires in thirty days. If you never open the deck, you never get it.

05

Turning them off

Clear cookies anytime in your browser settings. Signing out clears the session cookie; the analytics cookie can be blocked without breaking anything. The necessary cookies are the only ones the site needs to function.

06

The longer version

Cookies are part of the wider picture on the Privacy page, which covers everything else we store and why.

Back to home

Questions? hi@archify.ai