Archify

Privacy

What we keep.

The short version: we keep what we need to run the archive, nothing else. No third-party ad tracking, no data sales.

Last updated 2026-05-15

01

Waitlist

If you submitted your email to the waitlist before launch, we still store:

  • The email address you entered.
  • A source label (which page you signed up from — e.g. home or browse).
  • The timestamp of submission.

We used it once: to email you when the archive opened. Write to hi@archify.ai to be removed at any time.

02

Site analytics

We count visits to the public pages so we can understand interest. The only thing we store per visit is:

  • The path visited (e.g. /, /browse, /about).
  • An anonymous viewer ID — a random UUID kept in a first-party cookie. It is not derived from your email, IP, or any personal identifier.
  • The timestamp.

No third-party analytics, no advertising trackers, no cross- site tracking. All data lives on our own database.

03

What we collect later (when the archive opens)

  • Account email and a magic-link token (signs you in for seven days).
  • Seller verification: government-ID metadata, payout details handled by Stripe.
  • Order records: which listing, which buyer, license key, downloads consumed.
  • Standard server logs (IP, user-agent) kept for 30 days.
04

What we don’t collect

We don’t use third-party advertising trackers or analytics that share data outside Archify. We don’t sell your data. We don’t train models on your code or messages.

05

Cookies in use today

  • archify_v_id — anonymous viewer ID for our internal page-view counter. First- party, httpOnly, expires in one year.
  • archify_deck — set only when someone unlocks the private pitch deck with a token. First-party, httpOnly, expires in thirty days, scoped to /deck.
  • archify_gate — set only if you enter a password to view a gated area of the site. First-party, httpOnly.
  • Supabase session cookies — set only if you sign in to an Archify account (admin / future seller area). They keep you signed in. First-party, httpOnly.
06

Where it lives

The site runs on Vercel, our hosting provider. Application data is hosted on Supabase (EU region). Email magic links (when login is open) are sent via Resend. Payments and KYC data will be processed by Stripe once the archive opens. None of these vendors receive data outside what is strictly required to do their job.

07

Your controls

  • Ask us to delete your waitlist email — write to hi@archify.ai.
  • Clear the analytics cookie at any time via your browser settings.
  • Once the archive opens: export every record we hold about you in JSON, delete your account (orders are kept anonymised for tax-compliance reasons), update or correct any field in your profile.
08

Contact

For privacy requests, write to hi@archify.ai. We answer within one to five business days.

Back to home

Questions? hi@archify.ai