We're live on Product Hunt!Support us
ColorArchive

A curated color library with 5,446 algorithmically generated colors. Browse, search, save favorites, and export palette tokens — no account required.

CollectionsFamiliesBrandsRegionsJournalNotesGuidesFree ResourcesEmbed widgetConvertColorblindAboutSupportUpdatesiOS app
Privacy·Terms·Refunds·Cookies·Commerce Disclosure
colorarchive.org · © 2026 ColorArchive
Skip to content
ColorArchive
ProLog in
ArchiveAll ColorsCollections
Legal

Cookie Policy

Last updated: November 4, 2026

This Cookie Policy explains how ColorArchive uses cookies and similar technologies when you visit colorarchive.org.

1. What Are Cookies

Cookies are small text files stored on your device by your web browser when you visit a website. They are widely used to make websites work efficiently and to provide information to site operators.

2. Cookies We Use

ColorArchive uses a minimal set of cookies, limited to what is strictly necessary for the service to function:

  • Session cookie (colorarchive_session): The authentication cookie that keeps you logged in after signing in via magic link or Google OAuth. Type: first-party, httpOnly. Duration: up to 30 days. It is renewed while you use the site (whenever it has less than 15 days left), so you stay signed in as long as you visit at least every 15 days, for at most one year after you sign in. Your browser may keep it for less. Signing out deletes it. This cookie is essential for account features such as favorites sync, purchase history, and API key management.
  • Google sign-in cookie (colorarchive_google_state): Signing in with Google also sets this cookie for 10 minutes to protect the sign-in. Type: first-party, httpOnly. It is cleared when Google sends you back to the site.
  • No advertising or tracking cookies of ours: colorarchive.org sets no advertising cookies and no analytics cookies that identify individual users, and runs no advertising tag.
The cookies we set are limited to what is strictly necessary. We do not display a cookie consent banner.

To be accurate rather than convenient about why: the ePrivacy Directive's Article 5(3) is technology-neutral — it covers storing or reading information in your device generally, not cookies specifically — so localStorage and sessionStorage are not exempt from it just because they are not cookies. Our position rests on the analytics storage described in section 3 being first-party, holding no name, email address or account id, setting no advertising identifier, and involving no session recording, not on a technicality about the word "cookie". If you would rather not have it, clearing site data removes all of it and the site continues to work.

3. Local Storage

In addition to cookies, ColorArchive uses your browser's localStorage to store non-sensitive preferences locally on your device:

  • Favorites: Colors you mark as favorites (if not logged in, these are stored only in your browser).
  • Recent colors: A list of recently viewed colors for quick access.
  • UI preferences: Theme preference and other display settings.
  • Analytics identifier: PostHog stores a random id here instead of setting a cookie. It is sent with product-analytics events so we can tell whether people come back. It is not linked to your account. Until 14 October 2026, signing in also told PostHog your numeric account id, which then took the place of this random id; since then we do not tell PostHog who you are when you sign in, and a browser that had been linked gets a new random id on its next visit. Clearing localStorage also resets it.
  • First-touch source (ca_attr_v1): how you first arrived — the referring URL, the first page you landed on, any campaign parameters in the link, and the date. Stored once and kept, so that if you later subscribe or buy we can tell which channel earned it rather than crediting whatever page you happened to be on. Sent with analytics events.
  • Analytics session id (ca_sid): a random per-tab id kept in sessionStorage (not localStorage), sent with analytics events so we can count *visits* instead of clicks — one person scrolling past the same card ten times should count once. It is discarded when you close the tab and cannot by itself connect one visit to another. If you are signed in, the events it is sent with are stored with your account id (see the Privacy Policy, section 1).
  • Undelivered-event count (ca_ev_dropped): a number, kept only after an analytics event could not be delivered. It is sent with the next event that gets through, and then removed.
  • Page read flags (ca_read: followed by the page address): the single character 1 in sessionStorage, one per page, set once you have stayed on a page for a few seconds and scrolled, moved the pointer, pressed a key or touched the screen, so that page is counted as read once per visit. Discarded when you close the tab.
  • Guide card visit flag (ca_w1_seen_v1): the single character 1 in sessionStorage, set the first time a tab opens a guide page, so the guide colour card is counted once per visit rather than once per page. Discarded when you close the tab.
  • Layout test group (ca_w1_v1) — retired: from 31 August to 14 October 2026 this held the single word control or card, decided by a coin flip the first time you opened a guide page, to test whether an extra colour card in guide articles helps readers. The test has ended and every reader now sees the card, so the value is no longer set, and it is deleted from your browser the next time you open a guide page. It never contained any information about you; while the test ran it was sent with analytics events.
  • Export-limit notice flags (ca_lock_seen_v1: followed by the page address): the single character 1 in sessionStorage, one per page, set the first time that page shows you that today's free exports are used up, so the notice is counted once per page per visit instead of once per button. Discarded when you close the tab.
  • Free export counter (colorarchive_export_count, colorarchive_export_date): how many of today's free exports this browser has used, and the date (in UTC) that count belongs to, so the daily free allowance works without an account. Both stay on your device.
  • Internal-traffic flag (ca_internal): the single character 1, set only when a page is opened with ?ca_internal=1 in its address. We use it on our own devices and test browsers so our visits aren't counted. While it is set, this browser sends no analytics events and no page views, to us or to PostHog, and a page opened while it is set does not start PostHog at all; error reporting (Sentry) and performance monitoring (New Relic) still run. Opening a page with ?ca_internal=0, or clearing site data, removes it.
Favorites, recent colors and UI preferences stay on your device unless you are logged in, in which case favorites are synced to your account on our server. The analytics identifier, first-touch source, analytics session id and undelivered-event count above are the exception: they are sent with analytics events by design. The flags and the export counter stay in your browser.

4. Third-Party Services

The following third-party services may set their own cookies or collect data when you interact with them:

  • Google OAuth: If you sign in with Google, Google may set cookies as part of the authentication flow. See Google's Privacy Policy.
  • Vercel: Our hosting provider may collect anonymous performance metrics. See Vercel's Privacy Policy.
  • Lemon Squeezy: When you are redirected to the checkout page for a purchase, our payment processor may set cookies for fraud prevention and payment processing. See Lemon Squeezy's Privacy Policy. (This entry previously named Stripe, which we no longer use.)
  • PostHog: Product analytics. Configured to be cookieless — it uses the localStorage identifier described in section 3 rather than setting a cookie. It is not told your email address, and since 14 October 2026 it is not told your account id either. See PostHog's Privacy Policy.
  • New Relic: Website performance monitoring — how quickly pages load and respond, and the JavaScript errors they hit. It keeps a session record in localStorage (keys beginning NRBA_SESSION) rather than setting a cookie, records no session replay, and is not told who you are. See New Relic's Privacy Notice.
  • Pinterest: The Pin buttons on colour and collection pages open Pinterest's own Save page in a new tab. Pinterest may set its own cookies there, on pinterest.com; ColorArchive sets no Pinterest cookie and stores no Pinterest data in your browser. See Pinterest's Privacy Policy.
We do not control the cookies set by third-party services. Please refer to their respective privacy policies for more information.

5. Managing Cookies

You can control and manage cookies through your browser settings. Most browsers allow you to:

  • View what cookies are stored and delete them individually.
  • Block third-party cookies.
  • Block all cookies from specific sites.
  • Clear all cookies when you close the browser.
Please note that disabling the session cookie will prevent you from staying logged in, and clearing localStorage will remove your locally saved favorites and preferences.

6. Do Not Track (DNT)

ColorArchive does not currently respond to Do Not Track (DNT) browser signals, as there is no industry-standard implementation. However, we serve no advertisements, run no advertising tag and do no cross-site tracking of our own, so the practical effect is the same regardless of your DNT setting.

7. Changes to This Policy

We may update this Cookie Policy from time to time to reflect changes in our practices or for legal or regulatory reasons. The updated policy will be posted on this page with a revised date.

8. Contact

If you have questions about our use of cookies, please contact us at support@colorarchive.org.