Cookie Policy

Cookies are small text files stored in your browser that let a website recognize your device across requests — most commonly used to keep you signed in between page visits.

Atlas sets an essential session cookie, issued by our authentication provider, Supabase, when you sign in. It stores your encrypted session so you stay signed in as you move between pages, and it's required for the product to function — there's no way to opt out of it short of signing out.

We use Google Analytics 4 across the site, but only once you've accepted it (see section 6). It then sets first-party cookies named _ga and _ga_ followed by a container ID, which let it tell one visitor apart from another and group page views into a single visit. These are analytics cookies, and unlike the session cookie above, the product works without them.

What we send it: page views, and three events — creating an account, starting a trial, and a subscription payment. Those events carry the plan and the amount, not your name, your email, or your Etsy shop's data. We use them to see which channels bring people who actually sign up. Our Google Ads account can use some of these events as well, to measure our ads — see section 4.

We also use Vercel's cookieless Web Analytics for aggregate traffic patterns; it sets no cookies and stores no personal identifiers.

We don't sell cookie data to data brokers.

Atlas includes the Meta Pixel, which lets us measure whether people who arrive from a Facebook or Instagram ad go on to create an account or start a trial. It is an advertising and cross-site tracking technology: it sets cookies such as _fbp, and it reports to Meta.

What we send it: a page view, and two events — creating an account, and starting a trial. The trial event carries the plan's recurring amount and currency. Neither carries your name, your email, or your Etsy shop's data.

It only loads if you accept it, and there is a second switch behind that: we enable the Pixel per environment, so on any deployment where it isn't enabled, accepting still loads nothing.

Atlas also uses Google Ads conversion measurement, which lets us see whether people who arrive from a Google ad go on to create an account. It is an advertising technology, and it reports to Google. While it is on, Google's tag may set cookies in your browser to connect an ad click with a later sign-up (these commonly have names starting with _gcl_). Which cookies it sets, and for how long, is Google's decision, so please don't read that as a complete list.

What we send it on purpose: one event, when an account is created. It doesn't carry your name, your email, or your Etsy shop's data. Like any tag your browser loads, Google's tag also receives the technical details your browser sends with every request, such as your IP address and the address of the page, and, depending on how our Google Ads account is set up, it may receive information about the pages you visit. If you arrived from an ad, it also reads the identifier of that ad click.

It runs through the same Google tag as the analytics in section 3, and it only loads if you accept it. As with the Pixel, there is a second switch behind that: we enable it per environment, so on any deployment where it isn't enabled, accepting still loads nothing for it.

Atlas includes Tolt, which credits partners who refer new customers to us. If you arrive through a partner's referral link, it records which partner sent you, so that if you later subscribe they're paid their commission for it.

What it stores: a referral identifier in your browser, and only if you arrived through a partner link. If you didn't, it stores nothing at all — no cookie, no local storage entry. When you subscribe, we pass that same identifier to our payment provider, Paddle, alongside the subscription you're buying, and Tolt reads it from there to attribute the sale. It doesn't carry your name, your email, or your Etsy shop's data.

Unlike sections 3 and 4, this one isn't behind the consent banner, and it loads on every page. It isn't there to measure you or to advertise to you — it's how we know a partner earned a commission on a sale they actually made, and switching it off would mean withholding someone's payment for work they did.

The first time you visit, a banner asks whether the non-essential cookies in sections 3 and 4 are allowed. Nothing in either section loads until you choose “Accept” — not Google Analytics, not Google Ads conversion measurement, not the Meta Pixel. Choosing “Essential only” keeps them off, and so does ignoring the banner entirely: no answer means no consent, and we treat that the same as a no.

The banner does not cover section 5, and we'd rather say so plainly than leave it to be inferred: affiliate referral tracking loads either way, for the reason given there.

We ask everyone the same question, wherever you are. There is no location lookup deciding who sees the banner.

Your answer is stored in your browser's local storage under cookie_consent, not in a cookie, and never leaves your device. Clearing your browser data resets it and we'll ask again. You can change it here at any time:

Most browsers let you block or delete cookies through their settings, and browser-level or extension-level blocking of the analytics and advertising cookies above works — the product is unaffected by losing them.

The session cookie in section 2 is the exception: blocking it will sign you out and prevent you from accessing your dashboard until you sign in again.

When what we use changes, we'll update this page and reflect the change in the “Last updated” date above. See our Privacy Policy for more on how we handle data generally.

Questions about cookies on Atlas? Reach us at support@atlasgrowth.app.