Last updated October 6, 2026
In plain English: Atlaso uses a small number of cookies. Most are the essential ones needed to keep you securely signed in and to make the dashboard work. On our website, we ask before using anything else. The first time you visit, a small card asks you to choose Accept all or Necessary only. Until you choose, and if you choose Necessary only, our website does not load Google Analytics at all, and our other analytics tool, PostHog, sets no cookie, writes nothing to your browser's storage, and records no session replay: it still counts page views, clicks and the other interactions described in Section 4.3, with no identifier that survives the tab, and it works out an approximate location from your IP address before discarding the address. If you choose Accept all, Google Analytics loads (with Google signals switched on, see Section 4.3), PostHog sets a first-party cookie and may record a replay of how you moved through the page, and we keep a note of the campaign that brought you. You can change your answer at any time from the round cookie button in the bottom-left corner of any page, or from Cookie settings in our footer. If your browser sends a Global Privacy Control (GPC) signal, we treat it as Necessary only and PostHog does not load at all. The dashboard at app.atlaso.ai, which you use after signing in to an Account, follows the same answer: it loads Google Analytics, and lets PostHog store an identifier in your browser, only after you press Accept all, and loads neither if your browser sends GPC. Unless your browser sends GPC, the dashboard also sends PostHog a limited set of pseudonymous product-usage events, which never contain your memories or anything you type; without Accept all, nothing for them is stored in your browser (see Section 4.3). We run no advertising pixels or advertising cookies: the single Reddit advertising pixel we previously used was removed on September 22, 2026. Session replay never records anything you type into our contact form or our Ask Atlaso box, and every other input is masked. We do not sell your personal data. We also keep a few small settings in your browser's storage, such as your light/dark theme and, on the dashboard, choices like your preferred export format (see Section 4.2). This policy explains what each item is, why it exists, and how you can control it.
This Cookie Policy explains how Atlaso Labs Inc., a Delaware C-Corporation ("Atlaso", "we", "us", or "our"), uses cookies and similar technologies (such as browser local storage) on our website at atlaso.ai and our dashboard at app.atlaso.ai (together, the "Service").
Our documentation site, docs.atlaso.ai, is hosted for us by Mintlify, Inc. (see our Sub-processors List). It does not load the Google Analytics or PostHog set-up described in this policy, and the tables below do not cover it; any cookies or browser storage Mintlify uses there are described in Mintlify's own notices.
It should be read together with our Privacy Policy, which describes in full how we handle your personal data, and our Terms of Service, which govern your use of the Service. Capitalized terms not defined here have the meaning given to them in those documents.
This policy covers only cookies and similar technologies set in your web browser when you visit our website and dashboard. It does not cover the Atlaso Connectors (Claude Code, Codex, Cursor, Antigravity, OpenCode, Claude Desktop, and MCP) or the Atlaso CLI, which are software you install on your own machine and which do not use browser cookies; those are addressed in the Privacy Policy.
Cookies are small text files that a website places on your device (computer, phone, or tablet) when you visit. They are widely used to make websites work, to remember your settings, and to keep you signed in between pages and visits.
Cookies can be described in a few ways:
Similar technologies include local storage and session storage, which let a website store small amounts of data in your browser. These are not technically "cookies," but we disclose them here for transparency because they serve a comparable purpose. Atlaso uses local and session storage for a few functional settings, none of them used for tracking (see Section 4.2).
Another similar technology is a pixel (also called a tag or beacon): a small piece of code a website loads from another company, which tells that company you visited the page and lets it set its own cookies in your browser. Atlaso loads no advertising pixel of any kind. We previously ran a single Reddit advertising pixel on our marketing website; it was removed on September 22, 2026.
A third is session replay: a recording of how a visitor moved through a page (scrolling, clicking, and navigating), reconstructed afterwards so we can see where a page confused people. It is not a video of your screen and it does not use your camera. We use it only if you press Accept all in our cookie banner, and in a limited way, described in Section 4.3.
Cookies are commonly grouped into the categories below. We tell you plainly which categories apply to Atlaso.
| Category | Used by Atlaso? | What it means |
|---|---|---|
| Strictly necessary | Yes | Required for the Service to function: for example, to keep you securely authenticated and signed in. These cannot be switched off through a consent banner without breaking core functionality. |
| Functional | Yes (browser storage only) | Remember choices you make to improve your experience, such as your light/dark theme preference or your preferred export format. |
| Analytics / performance | Yes | Measure how visitors use a site. Atlaso uses Google Analytics 4 and PostHog, and also Vercel Web Analytics, Vercel Speed Insights and Cloudflare Web Analytics, which set no cookies and store nothing in your browser. On our website and dashboard, Google Analytics loads, and PostHog stores anything in your browser, only after you press Accept all; until then Google Analytics does not load and PostHog stores nothing in your browser (see Sections 4.3 and 7). |
| Advertising / targeting | No | Track users across sites to serve and measure ads. Atlaso runs none of this. The single Reddit advertising pixel we previously used on the marketing website was removed on September 22, 2026. No advertising or social-media pixel of any kind now runs on our website or our dashboard. (Google Analytics, an analytics tool that loads only after you press Accept all, has Google signals switched on: see Section 4.3.) |
In short: Atlaso uses strictly-necessary authentication cookies, a few functional settings kept in browser storage, and two analytics tools, Google Analytics 4 and PostHog, for aggregate usage measurement, plus cookieless page counting and page-speed measurement from Vercel and Cloudflare that stores nothing in your browser. On our website and dashboard, analytics cookies are set only after you press Accept all. We run no advertising pixels or advertising cookies anywhere (Google Analytics has Google signals switched on: see Section 4.3), and we do not sell your personal data. We also set two first-party cookies of our own: one remembers your cookie choice, and, only if you accept, one records the campaign you arrived from.
The table below lists the cookies and similar technologies present on our Service. Cookie names and exact durations are set by our authentication provider and may change as that provider updates its software; we will keep this list reasonably current.
| Name | Provider | Purpose | Type | Duration |
|---|---|---|---|---|
__session | Clerk (our authentication provider) | Maintains your authenticated session so you stay securely signed in to the dashboard and your requests are recognized. | First-party, HTTP cookie | Session / short-lived; refreshed while you are active |
__client_uat | Clerk | A signal used by Clerk to determine your signed-in state and manage session validity. | First-party, HTTP cookie | Persistent (set by Clerk; typically until sign-out or expiry) |
Other Clerk authentication cookies (e.g. __clerk_*) | Clerk | Support secure sign-in, session handling, and protection against session-related abuse. | First-party | Session or short-lived, as set by Clerk |
atl_consent | Atlaso | Remembers your answer to our cookie banner (Accept all or Necessary only), so we do not ask on every page and so our analytics follow your choice. See Section 4.5. | First-party cookie, set on .atlaso.ai | 6 months, then we ask again |
These cookies are strictly necessary: without them we cannot keep you signed in, operate the dashboard securely, or honour the choice you made in our cookie banner. Because they are essential to providing a service you have requested, they do not require consent under EU/UK rules, but we disclose them here for transparency.
For details on how Clerk processes data on our behalf, see our Sub-processors List and Privacy Policy.
| Name | Provider | Purpose | Type | Duration |
|---|---|---|---|---|
theme | Atlaso (via the next-themes library) | Remembers your light/dark mode preference so the interface matches your choice on your next visit. | First-party, browser local storage (not a cookie), website and dashboard | Persists in your browser until you clear it |
atlaso.exportFormat | Atlaso | Remembers the export format you last chose on the dashboard. | First-party, browser local storage | Persists in your browser until you clear it |
atlaso.proWelcome.pending, atlaso.proWelcome.shownAt | Atlaso | Timestamps that make the Pro welcome message show once after checkout. | First-party, browser local storage | Persists in your browser until you clear it |
atlaso:claude-skill-offer:... | Atlaso | Remembers, for your account, that you skipped the Claude skill offer on the dashboard. The name includes your pseudonymous Atlaso user id. | First-party, browser local storage | Persists in your browser until you clear it |
atlaso:dash-counted, atlaso:memory-entered, atlaso:connections-entered | Atlaso | Stop the dashboard's entrance animations from replaying on every page. | First-party, browser session storage | Until the browser session ends |
atl_internal | Atlaso | Set only when a page is opened with ?atl_internal=1, which our own team uses. It labels that browser's analytics events as internal so they are left out of our reports. It contains no identifier. | First-party, browser local storage, website and dashboard | Until you clear it, or a page is opened with ?atl_internal=0 |
These items stay in your browser and are not sent to our servers as cookies. They are not used for analytics or advertising, except that atl_internal adds an "internal" label to our own team's analytics events.
We use two analytics tools that can set cookies. Google Analytics 4 has been in place the longest and gives us aggregate visit numbers. PostHog was added on September 22, 2026 and tells us how people actually move through a page: how far they scroll, which questions they open, whether a form worked. Both are described below. We also use cookieless measurement from Vercel and Cloudflare and, on the dashboard, error reports to Sentry, both described at the end of this section.
We use Google Analytics 4 (provided by Google LLC) to understand how visitors use our website and dashboard so we can improve the Service. Google Analytics is loaded via Google's gtag.js and sets the following first-party cookies.
On our website, Google Analytics loads only after you press Accept all in our cookie banner. Until then the script is not requested at all, so no Google Analytics cookie is set and nothing about your visit is sent to Google. On the dashboard at app.atlaso.ai, which you use after signing in to an Account, Google Analytics follows the same rule: it loads only if you pressed Accept all on our website and your browser does not send GPC. When it loads, it links that usage to your Account's identifier and plan so we can see which features are used (see Section 7).
| Name | Provider | Purpose | Type | Duration |
|---|---|---|---|---|
_ga | Google LLC (Google Analytics) | Distinguishes unique users/browsers | First-party, set on the .atlaso.ai domain (shared across atlaso.ai and app.atlaso.ai) | Persistent, ~2 years |
_ga_9NX4EF249D | Google LLC (Google Analytics) | Persists GA4 session state for this property | First-party, .atlaso.ai | Persistent, ~2 years |
These are analytics cookies and are not strictly necessary. The data they generate is processed by Google LLC in the United States under the Standard Contractual Clauses and the EU–US Data Privacy Framework (Google is DPF-certified). Google Analytics 4 does not store IP addresses by default.
Settings we have chosen in Google Analytics. Once Google Analytics loads, these settings apply:
On our website and dashboard, choosing Necessary only keeps Google Analytics switched off. Anywhere, you can also opt out by installing the Google Analytics Opt-out Browser Add-on, or by blocking or deleting these cookies through your browser settings (see Section 8).
We use PostHog (provided by PostHog, Inc.) on our marketing website to measure how pages are actually used: how far down a page visitors read, which questions they open, which buttons they press, and whether a form succeeded or failed. We also use it on the dashboard to understand the sign-up, setup and upgrade steps, in the narrower way described under "PostHog on the dashboard" below. PostHog acts as our service provider (sub-processor): it processes this data on our instructions and does not use it for its own purposes, and it is listed in our Sub-processors List. Data is processed on PostHog's US Cloud. PostHog keeps events for one year and session replays for 30 days. Our PostHog project, used for both the website and the dashboard, is set to discard IP addresses: PostHog uses the address at most to work out an approximate location for an event, and then discards it.
On our website, PostHog runs in one of two modes, and the difference is significant:
| If you have... | What PostHog does |
|---|---|
| Not answered our cookie banner yet, or chosen Necessary only | Runs in memory-only mode: it sets no cookie, writes nothing to local storage, and keeps no identifier that survives the browser tab. Session replay is switched off entirely. It still sends an event for each page view, click and the other interactions described above, and PostHog works out an approximate location (such as country and city) from your IP address before discarding the address. Each visit is unlinked to any other. |
| Chosen Accept all | Sets the first-party cookie and local-storage entry in the table below, and may record a session replay of how you moved through the page. If you accept part-way through a visit, this starts from that moment on the same page. |
| A browser that sends a Global Privacy Control signal | PostHog does not load at all. No cookie, no storage, no replay, no event of any kind. |
Whichever of these applies, PostHog records it with each event (as "all", "necessary" or "unset"), so that our reports can tell the groups apart. It is a label on the event, not an identifier.
| Name | Provider | Purpose | Type | Duration |
|---|---|---|---|---|
ph_<project>_posthog | PostHog, Inc. | Holds a randomly generated visitor identifier and session state, so a series of page views can be recognised as one visit. Contains no name or email address. On the dashboard, once you are signed in, it also holds your pseudonymous Atlaso user id. Set only after you press Accept all, and never where GPC is present. | First-party cookie and local-storage entry, set on the site you are visiting, plus session-storage entries that tell your browser windows apart | Persistent, up to 1 year (session-storage entries end with the browser session) |
Where PostHog's data is sent. Requests go to a path on our own domains (atlaso.ai/ingest on the website, app.atlaso.ai/ingest on the dashboard), which forwards them to PostHog. On the dashboard, that path removes your cookies and sign-in credentials from each request before forwarding it. We do this so that content blockers (which drop requests by hostname) do not silently delete part of our measurement and leave us with numbers we would wrongly treat as complete. The practical effect for you is that your browser makes no request to a third-party address for PostHog.
What session replay does and does not record. Where replay is active, it reconstructs how a page was used: scrolling, clicking, and navigation. It is not a recording of your screen, your camera, or any other tab. It records no text you type: every input field on the site is masked, and our contact form and our Ask Atlaso box are excluded from recording altogether, so nothing written into them is ever captured. We record no passwords or payment details anywhere, and no session replay runs on the dashboard at app.atlaso.ai.
On the dashboard at app.atlaso.ai, PostHog is limited to named product-usage events about the sign-up, setup and upgrade steps. It runs no session replay and no automatic click capture, and a filter in the dashboard drops any other event or property before it leaves your browser. Events are identified by your internal Atlaso user id, which is pseudonymous, and never by your name or email address. Each event carries only: the event type; the page path, with any ids removed; the tool you connected; your plan and billing interval; the number of tools you have connected; the date you signed up; a count of your Memories; which setup step, screen or button the event came from; your cookie-banner answer; and the standard technical details PostHog's software adds (random session and device identifiers, the browser's user-agent string, browser and version, operating system and version, device type and model, screen and window size, language, time zone, and the referring page, reduced the same way as the page path). Events never include the content of your Memories, your searches, your questions, or anything you type.
| If you have... | What PostHog does on the dashboard |
|---|---|
| Not answered our cookie banner, or chosen Necessary only | Keeps its identifier in memory only: it sets no cookie and writes nothing to local storage. It still sends the events above, and the dashboard tells PostHog not to use your IP address to work out your location. |
| Chosen Accept all | Sets the first-party cookie and local-storage entry in the table above, on .atlaso.ai. PostHog may work out an approximate location from your IP address. The random visitor id from your earlier visits to our website in the same browser is linked to your Account, so those earlier visits (including any website session replay) become associated with it. |
| A browser that sends a Global Privacy Control signal | PostHog does not load in the dashboard at all, and neither does Google Analytics. Your browser sends no analytics event. |
One event is sent from our servers, not your browser. When a Pro subscription starts, our payment provider notifies our server, which sends PostHog a single "subscription started" event with your user id, the plan and the billing interval, and tells PostHog not to work out a location for it. Because it does not come from your browser, it is sent regardless of your cookie choice or Global Privacy Control setting. It involves no cookie or browser storage.
On our website and dashboard we also use Vercel Web Analytics (Vercel Inc., which hosts both) to count page views and visits, and Cloudflare Web Analytics (Cloudflare, Inc.) to count visits and measure how fast pages load. On our website we also use Vercel Speed Insights to measure page speed. Depending on the tool, each page view sends the page address, the referring page, your browser, operating system and device type, page-load timings, and an approximate location worked out from your request. None of these tools sets a cookie or stores anything in your browser, which is why none appears in the tables above. Vercel Web Analytics identifies a visitor by a hash created from the incoming request and discards that visitor session after 24 hours; Cloudflare states that its tool does not fingerprint visitors and does not log query strings. Because nothing is read from or stored on your device, these tools run for every visitor, whatever you answer in our cookie banner and whether or not your browser sends Global Privacy Control. Cloudflare's script loads from static.cloudflareinsights.com and reports to cloudflareinsights.com; the Vercel tools report to a path on our own domain. Vercel and Cloudflare are listed in our Sub-processors List.
Error reports (dashboard only). If something breaks on the dashboard, the page sends an error report to Sentry (Functional Software, Inc., United States). A report holds the error, the page route without its query string, and browser and device details, never your account id, email address, Memory content or anything you type. Sentry stores nothing in your browser, so it runs whatever your cookie answer and whether or not your browser sends GPC. Sentry is listed in our Sub-processors List.
We do not set or use:
Aside from the analytics described in Section 4.3, we do not use cookies to build advertising profiles or to track you across other websites. If this changes, we will update this policy.
These cookies are set by us, read only by us, and never sent to any advertising network. Neither is used to track you across other websites.
| Name | Provider | Purpose | Type | Duration |
|---|---|---|---|---|
atl_consent | Atlaso | Records your answer to our cookie banner: all or necessary. It is what our website and dashboard read, each time a page loads, to decide whether Google Analytics may load, which mode PostHog runs in, and (on the website) whether atl_attr may be set. It contains nothing else. | First-party, set on .atlaso.ai (shared with app.atlaso.ai) | 6 months, then we ask again |
atl_attr | Atlaso | Records how you arrived: the campaign parameters in the link you clicked (utm_source, utm_medium, utm_campaign, utm_content, utm_term), an advertising click identifier if the link carried one, the website that referred you, the page you landed on, and a timestamp. If you later create an Account, this lets us attribute that signup to the campaign that brought you. It is set only after you press Accept all, and only if you arrived with campaign evidence (a UTM-tagged link, an ad click identifier, or a referral from another website). A direct visit sets nothing. Once set it is never overwritten, so it always reflects your first visit. | First-party, set on .atlaso.ai | Persistent, 90 days |
atl_consent is strictly necessary: it is the record of your choice, and without it we could not honour that choice. atl_attr is not, which is why it waits for your consent. If you arrive from a campaign and accept on a later page of the same visit, we still record the campaign you arrived from; if you never accept, nothing is written.
What happens at signup. If you create an Atlaso Account while the atl_attr cookie is present, we store the campaign details it contains against your Account on our own servers, so we can measure how many signups (and later, subscriptions) a campaign produced. We do not share that record with an advertising network. See our Privacy Policy for what we store and for how long.
Changing your mind. If you choose Necessary only after previously accepting, we delete atl_attr and the Google Analytics and PostHog cookies and storage from your browser, and reload the page so nothing keeps running. The dashboard also deletes any Google Analytics and PostHog cookies and PostHog storage the next time one of its pages loads.
Retired: atl_geo. Until September 23, 2026 we also set a cookie called atl_geo, which recorded a coarse region (eu or row) derived from country-level IP geolocation, and decided which PostHog mode applied to you. Your answer in the cookie banner has replaced it. We no longer set it, and our website deletes any copy left in your browser.
Until September 22, 2026 this section also described a Reddit advertising pixel. That pixel has been removed.
Some of the cookies described above are set by Clerk, the third-party provider we use for authentication and session management. Clerk acts as our service provider (sub-processor) and these cookies are used solely to deliver the Atlaso sign-in and session experience, not for advertising or independent tracking.
PostHog is also a service provider. The cookie and local-storage entry described in Section 4.3 are set on our instructions, for our analytics only, and PostHog does not use that data for its own purposes or share it with anyone. It appears in our Sub-processors List.
Some vendors may set their own cookies when you visit a page they host directly: for example, Stripe on its hosted checkout and billing-portal pages. Our other service providers, such as Render (backend hosting), Neon (database) and Fireworks AI (AI features), work behind the scenes and set no cookies in your browser. Where a vendor does set its own cookies, those technologies are governed by the respective provider's own cookie and privacy notices. A complete list of our service providers, with links, is available in our Sub-processors List.
We no longer have an advertising relationship of any kind. Earlier versions of this policy described Reddit, Inc. as an advertising partner and independent controller in respect of a pixel on our marketing website. That pixel was removed on September 22, 2026, and no advertising pixel now runs on our website or dashboard. Google Analytics, which loads only after you press Accept all, has Google signals switched on, and Google may use some of its data for its own purposes under its own policies (Section 4.3).
We use the limited cookies and storage described above only to:
We do not use cookies to build advertising profiles or to track you across other websites, we run no advertising pixels, and we do not sell your personal information. Google Analytics, which loads only after you press Accept all, has Google signals switched on (Section 4.3).
Atlaso's authentication cookies, the atl_consent cookie that records your choice, and the functional settings in Section 4.2 are strictly necessary or functional and are exempt from consent because they are essential to providing a service you have actively requested.
Everything else on our website that stores anything in your browser waits for your consent. On your first visit to atlaso.ai, a card in the bottom-left corner of the page asks you to choose:
atl_attr records the campaign you arrived from.atl_attr is not set.Both buttons are the same size and the same style, and both are on the first screen, so declining is as easy as agreeing. There are no pre-ticked boxes. Until you choose, we behave exactly as if you had chosen Necessary only. We ask the same question wherever you are.
What is measured before you choose. Before you answer, and after Necessary only, PostHog stores nothing on your device and keeps no identifier that outlives the browser tab. It still sends an event for each page view, click and the other interactions described in Section 4.3, with browser details its script reads to describe the visit (such as browser type, screen size and language). PostHog works out an approximate location for these events from your IP address and then discards the address. On the dashboard these events are tied to your pseudonymous Atlaso user id, and no location is worked out (Section 4.3). Because this measurement stores nothing on your device and keeps no lasting identifier, we run it without asking first. Vercel and Cloudflare's cookieless measurement and dashboard error reports to Sentry (Section 4.3) also run before you choose. If you would prefer that PostHog and Google Analytics send no event about your visit at all, a Global Privacy Control signal does that (see Section 9).
Changing your mind. You can change your answer at any time: press the round cookie button in the bottom-left corner of any page of our website, or Cookie settings in the "Legal & policies" menu in our footer. Withdrawing takes effect immediately: we delete the analytics cookies and storage from your browser and reload the page. We ask again after six months.
The dashboard. Your answer is saved on .atlaso.ai, so the dashboard at app.atlaso.ai reads it too and follows it; the dashboard has no banner of its own. With Accept all, the dashboard loads Google Analytics, and PostHog keeps its identifier in a first-party cookie and local storage. With Necessary only, or no answer, Google Analytics does not load and PostHog keeps its identifier in memory only, storing nothing in your browser; the dashboard still sends PostHog the pseudonymous product-usage events described in Section 4.3, which store nothing on your device. No session replay runs on the dashboard in any case. If you change your answer on our website, the dashboard follows it the next time one of its pages loads.
Global Privacy Control overrides everything. If your browser sends a GPC signal, anywhere in the world, we treat it as your answer: our cookie banner does not ask, Google Analytics does not load on our website or dashboard, and PostHog is not loaded in your browser at all, so there is no analytics cookie, no storage, no replay, and no PostHog or Google Analytics event from your browser (see Section 9). Vercel and Cloudflare's cookieless measurement, which stores nothing in your browser, still runs (Section 4.3). The one exception is the single "subscription started" event our server sends when a Pro subscription starts, described in Section 4.3.
No advertising pixels anywhere. Previous versions of this policy set out the conditions under which an advertising pixel would load. That pixel was removed on September 22, 2026, and the question no longer arises: no advertising pixel runs on our website or dashboard, in any region, and we run no advertising or cross-site tracking technology of our own. Google Analytics, which loads only after you press Accept all and never where GPC is present, has Google signals switched on (Section 4.3).
If we introduce additional non-essential cookies or similar technologies in the future, we will update this Cookie Policy to describe them and ask for your consent before using them where the law requires it.
The simplest control for our website is our own cookie banner: press the round cookie button in the bottom-left corner of any page, or Cookie settings in our footer, and choose Accept all or Necessary only. You can change your answer as often as you like.
You are also always in control of cookies through your browser settings. You can:
Most major browsers provide instructions here:
Please note: Atlaso's authentication cookies are strictly necessary. If you block or delete them, you will be signed out and may be unable to sign in to or use the dashboard at app.atlaso.ai. Blocking strictly-necessary cookies does not stop the Service from functioning by design; it simply prevents the parts that require a logged-in session from working.
Clearing your browser's local storage will reset these settings to their defaults (for example your theme) but will not otherwise affect your Account or your Memories.
Some browsers offer a "Do Not Track" (DNT) setting or send a Global Privacy Control (GPC) signal. There is no industry-wide standard for how DNT signals should be interpreted.
We honor Global Privacy Control (GPC) as a valid opt-out signal, and we act on it concretely: when your browser sends GPC, neither Google Analytics nor PostHog loads on our website or dashboard. No analytics cookie is set, no session replay is recorded, and your browser sends no PostHog event. Vercel and Cloudflare's cookieless page counting and page-speed measurement, which stores nothing in your browser, is not affected (Section 4.3). Dashboard error reports to Sentry (Section 4.3) are not affected either. The only analytics event sent regardless is the single "subscription started" event our server sends when a Pro subscription starts (plan and billing interval), because it does not come from your browser. This applies wherever you are and whether or not you have an Account with us.
We do not sell your personal data, and we run no advertising pixels or advertising cookies. As of September 22, 2026 we run no advertising pixel of any kind, on the marketing website or the dashboard, in any region. Earlier versions of this policy disclosed that page-visit data went to Reddit for advertising measurement, and treated that as "sharing" for cross-context behavioral advertising as the California Consumer Privacy Act (CCPA/CPRA) uses that term. That pixel has been removed, so that sharing has stopped. We do not track you across other websites for our own purposes. Google Analytics, which loads only after you press Accept all and never where GPC is present, has Google signals switched on, as explained in Section 4.3.
For more on your privacy rights, including under the CCPA/CPRA and other laws, please see our Privacy Policy.
We may update this Cookie Policy from time to time: for example, if we add new functionality, change service providers, or are required to do so by law. When we make material changes, we will update the "Last updated" date at the top of this page and give advance notice before they take effect, on our website and dashboard or by email where available; if you have an Account, you may cancel before they take effect, and where the law requires it we will ask for your consent again. We encourage you to review this page periodically.
If you have questions about this Cookie Policy or our use of cookies, please contact us:
Atlaso Labs Inc., a Delaware C-Corporation.
For more on how we handle your personal data, see our Privacy Policy. For the full list of our service providers, see our Sub-processors List.