Last updated: November 4, 2026
This Cookie Policy explains how ColorArchive uses cookies and similar technologies when you visit colorarchive.org.
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.
ColorArchive uses a minimal set of cookies, limited to what is strictly necessary for the service to function:
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.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.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.
In addition to cookies, ColorArchive uses your browser's localStorage to store non-sensitive preferences locally on your device:
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.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).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.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.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.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.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.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.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.The following third-party services may set their own cookies or collect data when you interact with them:
NRBA_SESSION) rather than setting a cookie, records no session replay, and is not told who you are. See New Relic's Privacy Notice.You can control and manage cookies through your browser settings. Most browsers allow you to:
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.
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.
If you have questions about our use of cookies, please contact us at support@colorarchive.org.