Privacy Policy

Last updated October 24, 2026

This Privacy Policy explains how Atlaso Labs Inc. ("Atlaso", "we", "us", "our") collects, uses, shares, and protects personal data when you use the Atlaso memory layer: our dashboard, brain/API, Connectors, and CLI (together, the "Service"). In plain English: when you sign up we hold your account details with our authentication provider; when you connect a tool, the Memories you create or that our Connectors capture are stored on Atlaso's servers so they can sync across your sessions and devices, with a copy also kept on your own machine for some tools that run there (Section 3); we use specialist sub-processors (listed below) to run the Service; we run no advertising pixels or advertising cookies (the one advertising pixel we previously used was removed on September 22, 2026, and Google Analytics, which loads only if you press Accept all, has Google signals switched on, as Section 4 explains); we measure how our website and dashboard are used with Google Analytics and PostHog, which store nothing in your browser unless you press Accept all in our cookie banner, never record a session replay on the dashboard, and do not load in the browser for anyone whose browser sends a Global Privacy Control signal; we also count page views and measure page speed with tools from Vercel and Cloudflare that set no cookies and store nothing in your browser (Section 4); we do not sell your personal data, we do not operate a training endpoint, and we do not train any AI models on your Memory; Atlaso's own AI features run on open models hosted by Fireworks AI with zero data retention (Section 6 lists every feature that uses it; the Ask Atlaso product assistant on our website uses OpenRouter instead); and you have rights to access, correct, and delete your data, and can delete your Account yourself in the dashboard. On every plan, including Free, Atlaso sends selected Memory text to Fireworks AI's zero-retention open models to write your dashboard greeting and Ambient Memory summaries; our earlier policy wrongly said Free Memory was never sent to an AI model. Two dashboard settings, Use my memories and usage data to improve Atlaso and Use my approximate location, are on unless you turn them off, and when Claude Code, Codex or Antigravity search your Memories, we keep the search text for about 30 days without removing secrets from it (Section 4). Please read the full policy for the details, including the important explanation of where your Memories actually live.

1. Who We Are and How to Contact Us

Data controller: Atlaso Labs Inc., a Delaware C-Corporation.

Postal address: 131 Continental Dr, Suite 305, Newark, DE 19713, United States

Contact (all enquiries: privacy and data-rights requests, general and legal notices, support and billing): support@atlaso.ai

EU / UK data subjects: You can direct any question or request about your personal data to support@atlaso.ai. We have not appointed a representative in the EU or the UK under Article 27 of the GDPR or the UK GDPR.

India (Digital Personal Data Protection Act, 2023): You can raise any privacy question or grievance with our Grievance Officer, Ashish Khandelwal, at support@atlaso.ai.

If you have questions about this policy or how we handle your personal data, contact us at support@atlaso.ai.

2. Scope

This policy applies to personal data we process about:

  • Visitors to atlaso.ai and users of the dashboard at app.atlaso.ai;
  • Visitors to our documentation at docs.atlaso.ai, which is hosted by Mintlify (Section 8);
  • Users of the Atlaso Connectors (Claude Code, Codex and ChatGPT, Cursor, Antigravity, OpenCode, Claude Desktop, and any other app connected through our MCP connector at mcp.atlaso.ai) and the Atlaso CLI; and
  • Account holders on the Free and Pro tiers.

It does not cover third-party websites, tools, or AI models you choose to use alongside Atlaso, which are governed by their own privacy policies.

3. How Your Memories Are Stored (Please Read This)

We want to be precise about where your data lives, because it matters.

When you connect a tool, your Memories are stored on Atlaso's servers so they can sync across your sessions and devices. Tools that run on your computer also keep data locally, in most cases a local copy of your Memories.

What is kept locally depends on the tool. Claude Code, Codex and Antigravity keep a full copy of your Memories in the ~/.atlaso folder on each computer where you use them. Cursor and OpenCode keep only captures that have not been sent to our servers yet. Apps connected through our MCP connector, such as Claude Desktop, keep nothing in that folder. The local files, including the sign-in tokens our Connectors use, are protected by your computer's own file permissions, not by encryption from us, and they stay there until you delete them, including after you disconnect that computer or delete your Account.

Your Memory is only purely local in these situations:

  • before you connect any tool to Atlaso;
  • when a tool is not your active/entitled tool; or
  • while you are offline (in which case it syncs to our servers when connectivity is restored).

On the Free tier, your single active tool is cloud-linked, so its Memory syncs to and persists on Atlaso's servers as normal operation. Memory persists on our servers on both Free and Pro. The dashboard greeting and Ambient Memory summaries may use selected Memory text on every plan, including Free. Automatic enrichment, "Ask your memory", and Ambient Memory in connected tools are Pro features. Section 6 explains which features send text to an AI model.

In short: Atlaso is cloud-synced memory, with a local mirror in some tools that run on your computer, not a purely local-only product. We have written this policy to reflect that accurately.

4. Categories of Personal Data We Collect

CategoryWhat it includesWhen collectedWhere it is stored
Account dataEmail address and a user idAt signupClerk
Profile dataYour first name (needed to finish signing up), and optionally your last name, an avatar you pick from our set, and what best describes your work (a role from a list, or up to 80 characters you type)At signup and in Settings > GeneralClerk
Sign-in dataOne-time sign-in codes sent to your email (we use no passwords), passkeys if you add one, and your sign-in sessions: device type, browser, last active time, and an approximate city and country estimated from your IP address. You can see and end sessions under Settings > General > Active sessions.At each sign-in; passkeys when you add oneClerk
Plan & billing identifiersYour plan (free/paid) and your Stripe customer idWhen you subscribeClerk metadata and Neon (user_plan)
Device dataA server-minted device_id; a device label, which is your computer's name (hostname) when you connect with the CLI, or the name an app registers when it connects through our MCP connector; when it was connected and last seen; which tools are connected on it, which one is active, and which version of Atlaso each tool is running; and content-free results of install checksWhen you run atlaso connect or approve an app on our connect page; the version is updated when a connected tool sends a request to AtlasoNeon (device_registry). A disconnected Device's record is kept, marked as disconnected, until you delete your Account. We do not perform any hardware fingerprinting.
Local files{ server, token, user_id, device_id } in ~/.atlaso/auth.json, and a sign-in token for each connected tool in ~/.atlaso/tools/. Claude Code, Codex and Antigravity also keep a full copy of your Memories in ~/.atlaso/cache.db; Cursor and OpenCode keep captures that have not been sent yet in the same folder.On connect, and as you use a ConnectorOn your own machine, protected by your computer's file permissions, not by encryption from us. These files stay until you delete them, including after you disconnect that computer or delete your Account.
Payment dataCard details, billing address, and subscription stateAt checkoutStripe. Full card numbers and security codes are handled by Stripe only and never touch Atlaso systems; we receive your card brand, last four digits and expiry date from Stripe to show them in Settings and in our billing emails, such as receipts and card-expiry reminders.
Memory / ContentFacts, decisions, preferences, gotchas, and auto-captured conversation snippets (your message plus up to 400 characters of the assistant's reply); may contain code or project facts. Each Memory is labelled with the project it came from (your git remote address, such as github.com/you/app, or a folder name with a short code) and the tool and Device that saved it.When you deposit a Memory or a Connector captures oneServer-side per-user database (the canonical copy); a full copy in ~/.atlaso/cache.db on each computer where you use Claude Code, Codex or Antigravity; transiently in the Neon enrichment queue (cleared after processing); and in Neon, the text of your latest dashboard greeting and Ambient summary, which are made from your Memories and kept until replaced or until the Memories they came from are deleted
Search textWhen Claude Code, Codex or Antigravity search your Memories, the Connector sends the text of the message you just wrote as the search text, and we keep it with a list of the Memories offered so we can measure whether recall helped. Recognized secrets are not removed from this search text before it is sent or stored. Cursor and OpenCode remove recognized secrets from their search text before sending it, and OpenCode's search text, with those secrets removed, is kept in the same way. Hosted connectors such as Claude Desktop also send search text without removing secrets; it is used for the search and is not kept.Each time you send a message in a connected toolYour server-side Memory store, for about 30 days (longer if the search was rated for usefulness). Because the search text travels in the web address of the request, it may also appear in the server request logs kept by us and our hosting providers.
Contact, support and waitlist dataYour name, email address and message when you use our contact form; your email address and the plan when you press Notify me for a plan that is not open yet; from the dashboard, your support messages, feature requests and ratings (sent with your user id, email, name and plan), and your name and email when you join a waitlist thereWhen you send a form or message or join a waitlistOur support inbox (hosted by Google Workspace), delivered there by Resend. Waitlist addresses, and for waitlists joined in the dashboard your name, are kept on that plan's contact list in Resend. A note that you contacted us, and any star rating you gave, is kept with your account in Clerk.
Privacy settings and approximate locationYour choices for Use my memories and usage data to improve Atlaso and Use my approximate location, which are both on unless you turn them off in Settings > Privacy; and, while the location setting is on, the city and region estimated from your IP address when you open the dashboard. Never GPS, your device's location services or your exact address. We keep only the most recent city and region.When you change a setting; location on dashboard visits while that setting is on. This setting is separate from the cookie banner and Global Privacy Control.Clerk (account metadata). Turning the location setting off deletes the stored city and region.
Usage dataContent-free activity counters used to measure daily/monthly active usageOn activityNeon (usage_event, daily_active). These never contain prompt or code content.
Dashboard usage eventsSign-up, setup and upgrade steps in the dashboard, identified by your pseudonymous user id, with the limited properties listed in the note below. Never Memory content, searches, questions or anything you type.While you use the dashboard at app.atlaso.ai, and once from our servers when a Pro subscription startsPostHog (US Cloud)
IP addressYour network IPPer requestUsed to limit abuse. Our brain/API holds it only in memory for rate-limiting and does not store it in our application database. Our website's forms and Ask Atlaso keep a one-way code made from your IP address and the date (not the address itself) for up to 48 hours in Upstash. Clerk records it with each sign-in session (see Sign-in data), and while Use my approximate location is on, we keep a city and region estimated from it (see above). IPs are inevitably present in the operational logs of our infrastructure providers (Render, Vercel, Cloudflare, Neon, Clerk, Stripe).
Campaign attribution dataThe campaign parameters in the link you arrived on (utm_source, utm_medium, utm_campaign, utm_content, utm_term), an advertising click identifier if the link carried one, the referring website, the landing page, and a first-touch timestamp. Without Accept all, only one word naming where your visit came from, from a fixed list (for example chatgpt, google or reddit)When you arrive at atlaso.ai from a tagged link, an ad, or another website, only if you press Accept all in our cookie banner (a direct visit collects nothing), and again at signup if you create an Account. The one word is added to a Get Started link at the moment you click it, and is kept only if you create an Account from that linkThe atl_attr first-party cookie in your browser (90 days), and, if you sign up, one row against your user id in Neon (user_attribution). The one word goes only into that same row and the sign-up event, never into your browser
Your cookie choiceWhether you pressed Accept all or Necessary only in our cookie bannerWhen you answer the banner, or change your answerThe atl_consent first-party cookie in your browser (6 months), shared across atlaso.ai and app.atlaso.ai. It holds only that one word. Until September 23, 2026 we instead set an atl_geo cookie holding a coarse region (eu or row); it is no longer set, and our website deletes any remaining copy.

A note on website and dashboard measurement, and campaign attribution

We run no advertising pixels or advertising cookies. Until September 22, 2026 our marketing website loaded a single Reddit advertising pixel for visitors outside the EU/EEA/UK/Switzerland. It has been removed, and no advertising pixel now runs on our website or dashboard. Google Analytics, described below, has Google signals switched on. On our marketing website at atlaso.ai, two things remain:

  • Website analytics, via Google Analytics and PostHog. These measure how pages are used: which pages are viewed, how far down them people read, which questions they open, and whether a form succeeded. On our website, both depend on your answer to our cookie banner, and we ask everyone the same question. Until you answer, and if you choose Necessary only, Google Analytics does not load, and PostHog stores nothing in your browser, keeps no identifier that outlives the tab, and records no session replay. PostHog does still run before you answer, and after you choose Necessary only: it counts page views, visits and clicks, and it may record an approximate location (such as country and city) worked out from your IP address. Our PostHog setting to discard IP addresses is on, so PostHog does not keep the address itself. If you choose Accept all, Google Analytics loads, and PostHog sets a first-party identifier and may record a session replay of how a page was used. In our Google Analytics account, Google signals is on, so Google may associate your visits with your Google account if you are signed in to Google and have allowed Google to do this; the collection of granular location and device data (such as city and device model) is also on. Session replay records no text you type: every input is masked, and our contact form and Ask Atlaso box are excluded from recording entirely. For any visitor whose browser sends a Global Privacy Control (GPC) signal, anywhere in the world, we treat it as Necessary only and PostHog does not load at all. You can change your answer at any time from the cookie button in the bottom-left corner of our website or Cookie settings in its footer. PostHog is our sub-processor and is listed as one.
  • Our own first-party attribution record. The atl_attr cookie above is set by us only after you press Accept all, and read only by us. If you create an Account while it is present, we store the campaign details against your user id so we can measure how many signups (and later, subscriptions) a campaign produced. We do not share that record with any third party, and it is not used to track you across other websites.

Dashboard analytics at app.atlaso.ai. The dashboard sends product-usage events to PostHog (US Cloud) so we can understand the sign-up, setup and upgrade steps: for example, that an Account was created, a setup step was viewed, a tool was connected, the upgrade dialog was opened, or a checkout was started. These 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 (not the time) you signed up; a count of your Memories; which setup step, screen or button the event came from; your cookie-banner answer; on the sign-up event only, the one-word source of your visit described under Campaign attribution data; 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. There is no session replay and no automatic click capture on the dashboard: only the events described here are sent, and a filter in the dashboard drops anything else before it leaves your browser. Requests go through our own address, app.atlaso.ai/ingest, which removes your cookies and sign-in credentials before passing them to PostHog.

  • Unless you pressed Accept all in our website's cookie banner (the dashboard has no banner of its own and follows the answer you gave there), PostHog keeps its identifier in memory only, nothing for analytics is stored in your browser, Google Analytics does not load, and the dashboard tells PostHog not to use your IP address to work out your location.
  • If you pressed Accept all, PostHog stores its identifier in a first-party cookie and local storage, PostHog may work out an approximate location from your IP address, and Google Analytics loads. The random visitor id from your earlier visits to our website in the same browser is then linked to your Account, so those earlier visits (including any website session replay) become associated with it.
  • If your browser sends a Global Privacy Control signal, neither PostHog nor Google Analytics loads in the dashboard at all, whatever you chose in the banner.
  • 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.

The dashboard also reads our own atl_attr attribution cookie once, at signup. When there is no such cookie, it reads the one-word source a Get Started link carried instead (from a fixed list, such as chatgpt or google; anything else is dropped) and stores it with your new Account and on the sign-up event. It is not an identifier, and it applies only to Accounts created from October 26, 2026.

Cookieless page counting and page-speed measurement, on both. On our website and our dashboard we also use Vercel Web Analytics and Cloudflare Web Analytics, and on our website Vercel Speed Insights. They count page views and visits and measure how fast pages load. 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. They set no cookies and store nothing in your browser. 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 choose in our cookie banner and whether or not your browser sends Global Privacy Control. Vercel (which hosts our website and dashboard) and Cloudflare are our sub-processors and are listed as such.

Full detail on both, including how to block them, is in our Cookie Policy.

A note on secrets in captured text

Connectors may capture text that inadvertently contains secrets (API keys, tokens, passwords). Our system assumes this can happen and scrubs detected secrets from Memories before they are stored: Connectors that run on your computer scrub on your device, our servers scrub again on every ingress, and enriched output is scrubbed too, using a fail-closed redaction process. This means secret material may be transiently present in transit before it is redacted. The search text that Claude Code, Codex and Antigravity send is not scrubbed: it is kept as written for about 30 days and may appear in server request logs (see Search text in the table above). Hosted connectors such as Claude Desktop also send unscrubbed search text, which is used for the search and not kept. Please do not rely on this scrubbing as a guarantee, and do not use Atlaso to store regulated or highly sensitive data (see Section 11 and our Acceptable Use Policy).

We do not knowingly collect special categories of data (e.g., health, biometric, or government-ID data) and ask that you do not store such data in your Memories.

A note on error reporting

We use Sentry to find and fix errors in the dashboard and our brain/API. Error events can include a stack trace, the page or API route, and technical details about the browser, device, or service. We configure Sentry not to store IP addresses in these events (Sentry's setting that prevents storing IP addresses is on) and not to attach your account id, email address, or name. We do not intentionally send Memory content or request bodies in error reports.

5. How We Use Your Data and Our Lawful Bases

Our role. For the Memory and account data of individual Free and Pro users, Atlaso is the data controller: we determine the purposes and means of processing, and this Privacy Policy governs that relationship. The processor/controller framing in our Data Processing Addendum (and its Standard Contractual Clauses) applies only where we process personal data on behalf of a business customer; it does not apply to individual users, whose safeguards are described here.

The legal ground we rely on for a given purpose depends on where you are. We describe the same processing activities below, region by region, because the applicable law differs.

5.1 EU / EEA and UK (GDPR / UK GDPR)

Where the GDPR or UK GDPR applies, we rely on the following lawful bases:

PurposeWhat we doLawful basis (GDPR Art. 6)
Provide the ServiceCreate and manage your Account; store, sync, retrieve, and inject your Memories; register and manage your DevicesPerformance of a contract (Art. 6(1)(b))
Authentication & securityVerify your identity, manage sessions and passkeys, prevent abuse and fraud, enforce rate limits, and keep encrypted backups so we can recover from an outage or data lossPerformance of a contract; legitimate interests in securing the Service (Art. 6(1)(f))
Billing & subscriptionsProcess payments, manage your Pro subscription, calculate taxesPerformance of a contract; compliance with legal/tax obligations (Art. 6(1)(c))
AI features provided as part of the ServiceProcess selected stored Memory text to generate the dashboard greeting and Ambient Memory summaries on every plan, including Free; on Pro, also provide enrichment (including of Memories saved on Free, after you upgrade) and "Ask your memory". An Ask question is sent with recalled Memory when you use Ask.Performance of a contract (Art. 6(1)(b)); see Sections 6 and 7
Measuring recall qualityKeep the search text that Claude Code, Codex, Antigravity and OpenCode send, with the list of Memories offered, for about 30 days to check whether recall helped (Section 4)Legitimate interests in making recall work well (Art. 6(1)(f))
Understanding where Atlaso is usedWhile Use my approximate location is on, record the city and region estimated from your IP address so we can understand, in aggregate, where Atlaso is usedLegitimate interests (Art. 6(1)(f)). You can turn it off at any time in Settings > Privacy.
Improving the ServiceWhile Use my memories and usage data to improve Atlaso is on, include your Memories and usage in automated evaluations of recall and headlines. No such evaluation runs yet (Section 7).Legitimate interests (Art. 6(1)(f)). You can turn it off at any time in Settings > Privacy.
Product analyticsCount content-free daily/monthly active usage, and measure website and dashboard usage via Google Analytics and PostHogConsent (Art. 6(1)(a)) for Google Analytics, for analytics cookies and browser storage, and for session replay on our website, all of which run only after you press Accept all; legitimate interests (Art. 6(1)(f)) for content-free usage counts, cookieless page counting on our website before or without consent (including the approximate location PostHog works out from your IP address), cookieless page counting and page-speed measurement by Vercel and Cloudflare on our website and dashboard, pseudonymous dashboard usage events that store nothing in your browser, and the single subscription-started event sent from our servers
Error reportingReceive technical error reports from the dashboard and brain/API to diagnose and fix faultsLegitimate interests in securing and repairing the Service (Art. 6(1)(f)). You may object at any time by emailing support@atlaso.ai.
Campaign measurementRecord in a first-party cookie which campaign you arrived from and, if you sign up, store it against your Account so we can tell which campaigns workConsent (Art. 6(1)(a)) for setting the cookie, which happens only after you press Accept all; legitimate interests in measuring the effectiveness of our own marketing (Art. 6(1)(f)) for the record kept with your Account
CommunicationsRespond to contact and support requests and email you to confirm we received them; send account, service and billing emails; email you when a plan whose waitlist you joined opens; send product-update emails, each with an unsubscribe link. We send these emails through Resend (Section 8).Performance of a contract; legitimate interests; for a waitlist, your request (consent, Art. 6(1)(a)), which you can withdraw by replying to any waitlist email; for product-update emails, legitimate interests where the law allows, otherwise your consent, and you can unsubscribe from any of them at any time
Legal complianceComply with applicable law and respond to lawful requestsLegal obligation (Art. 6(1)(c)); legitimate interests

No advertising pixels or advertising cookies are used in these regions, or anywhere. As of September 22, 2026 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); it runs only with your consent, as the Product analytics row above says. The campaign-measurement row above covers only our own first-party attribution record.

Analytics storage and your consent. On our website and dashboard, nothing for analytics is stored on your device until you press Accept all in our cookie banner. Before that, and if you choose Necessary only, PostHog's script still reads basic browser details (such as browser type, screen size and language) to describe each event, but stores nothing on the device; Google Analytics does not load, and no session replay is recorded (Section 4 and Section 7 of our Cookie Policy). You can withdraw consent at any time, as easily as you gave it, from the cookie button on any page of our website; we then delete the analytics cookies and storage from your browser, and the dashboard does the same the next time one of its pages loads.

Where we rely on legitimate interests, we have balanced those interests against your rights and freedoms. You may object to such processing as described in Section 12. Where we rely on consent (for example, certain optional features), you may withdraw it at any time without affecting prior processing.

5.2 India (Digital Personal Data Protection Act, 2023)

For data principals in India, the DPDP Act recognizes consent and a set of enumerated legitimate uses as the grounds for processing; it does not recognize performance-of-contract or legitimate-interests as separate bases. Accordingly, for Indian users we process your personal data on the basis of your consent, which you give when you continue at sign-in (the sign-in page links to this Privacy Policy, which is our notice of the personal data we process and why), and on the DPDP-enumerated legitimate uses where they apply (for example, where you have voluntarily provided data for a specified purpose, or to comply with law). You may withdraw your consent at any time (see Sections 12.3 and 12.1), which does not affect processing carried out before withdrawal. See Section 12.3 for our Data Fiduciary duties and grievance-redressal contact.

5.3 United States and other regions

Where US state privacy laws or the laws of other jurisdictions apply, we process your personal data as permitted under those laws to provide, secure, bill for, and improve the Service, to communicate with you, and to comply with legal obligations, as described above. See Section 12.2 for US state-specific rights.

6. The Three AI Processing Paths

Atlaso involves AI processing in three ways.

(a) Your own model, at your direction. When you use a Connector, your Content is routed through the AI model you have chosen to use, such as Claude or GPT, as part of how that tool works. That processing is governed by your relationship with that model provider.

(b) Atlaso's model provider, Fireworks AI. Atlaso's AI features run on open models hosted on Fireworks AI's serverless platform, with zero data retention. Fireworks does not log or store the text we send or the results it returns: the text exists only in memory while the request runs and is discarded when it finishes. Where prompt caching is used, some of it may stay in that temporary memory for a few minutes before it is cleared. Fireworks keeps only technical metadata, such as the number of tokens in a request. It does not use this text to train or improve its models, because that requires an explicit opt-in, which Atlaso has not given. Fireworks runs its service on servers in the United States.

Atlaso sends selected stored Memory text to Fireworks for the dashboard greeting and Ambient Memory summaries on every plan, including Free. On Pro, Fireworks also powers background Memory enrichment and "Ask your memory". Ambient Memory in your connected tools is currently put together without an AI model. One-line Memory headlines and Memory labelling, where we switch them on, also use Fireworks on every plan, including Free, and send the full text of one Memory per request, with recognized secrets removed.

The greeting uses selected stored Memory text. Ambient dashboard summaries use short, memory-derived candidates. Enrichment and Ask can use stored captures and related or recalled Memories. When you upgrade from Free to Pro, Memories you saved while on Free are queued for enrichment too, so their text is sent to Fireworks at that point. When you use Ask, your question is also sent to Fireworks and processed the same way, under the same zero-retention terms. Recognized secrets are removed from Memory when it is captured.

Fireworks describes these terms in its data-handling documentation and its privacy policy. We use chat completions, not Fireworks' stored Responses API, for these features.

The previous Privacy Policy wrongly said Free-plan Memory was never sent to a language model. This corrects the description of a practice already in place; it does not announce a new use of Free-plan Memory.

(c) Ask Atlaso on our website. The Ask Atlaso box on atlaso.ai answers product questions. Your question, and up to three earlier questions and answers from the same conversation, are sent through OpenRouter to the MiniMax M3 model, which may be run only by Together AI, CoreWeave or ModelRun. Requests specify zero-data-retention routing and deny provider data collection. No account data or Memories are attached. We do not log the questions or answers ourselves; our analytics record only a question's length and its position in the conversation, the type of answer given (or that it failed), and how long the answer took. Please do not type personal or sensitive information into it.

AI output can be wrong. The dashboard greeting, Ambient Memory summaries, enriched Memories, answers from "Ask your memory" and answers from Ask Atlaso on our website are generated by AI models. They may be inaccurate, incomplete or out of date, so please check anything important before you rely on it.

7. We Do Not Train AI Models on Your Memories

We do not operate a training endpoint and we do not train Atlaso models on your Memory. On every plan, selected Memory text is sent to Fireworks AI for the features described in Section 6, where it is processed on open models with zero data retention. We use that processing to generate your results, not to train AI models. Fireworks does not use this text to train or improve its models, because that requires an explicit opt-in, which Atlaso has not given.

We believe this is a meaningful difference from some competitors that take broad licenses to train on user content. We do not.

Improving Atlaso. Settings > Privacy in the dashboard has a switch, Use my memories and usage data to improve Atlaso, which is on unless you turn it off. It lets us include your Memories and how you use Atlaso in automated evaluations that test and tune how Atlaso recalls Memories and writes headlines. No model is trained on your Memories, and anything that looks like a credential is removed before an evaluation runs. No such evaluation runs today. When one starts, it will include only Memories saved after its start date, and we will update this policy first. Turning the switch off stops your Memories and usage being included from then on; it does not affect recall in your tools or delete anything in your Account.

8. Sub-processors

We use the service providers below to operate the Service. We rely on each provider's data-processing terms; for example, we accepted Google's Data Processing Terms for Google Analytics on July 21, 2026. Our current list:

Sub-processorPurposeData sharedLocation
ClerkAuthentication, session, and profileEmail, user id, name, profile choices (avatar and role), passkeys, sign-in sessions with IP address and approximate location, plan and Stripe customer id, your privacy settings, your approximate city and region while that setting is on, and records of support requests, ratings and waitlists you joinedUSA
StripePayment processing and subscription billingEmail, card/payment data, billing address, subscription stateUSA
NeonBrain metadata database and transient enrichment queueToken hashes, device registry (including device names), plan, content-free usage counters, campaign attribution records, OAuth state and registered apps, the text of your latest dashboard greeting and Ambient summary (made from your Memories), transient raw capture text, and a deletion receipt containing a one-way code made from a deleted user's id. Neon keeps a 7-day recovery history.USA (AWS US East)
Fireworks AIOpen-model processing with zero data retention for the dashboard greeting and Ambient Memory summaries on every plan; enrichment and Ask on Pro; headlines and labelling on every plan where we switch them onSelected stored Memory text, including captures and recalled Memories, and your Ask question. Recognized secrets are removed from Memory when it is captured. Fireworks does not log or store this text: it exists only in memory while the request runs, prompt caching may keep some of it for a few minutes, and Fireworks keeps only technical metadata such as token counts.United States (Fireworks servers)
OpenRouter, routing to MiniMax M3Optional Ask Atlaso product-question assistant on atlaso.aiA visitor's question and recent conversation turns. Atlaso does not attach account records, dashboard data or stored Memories. Text a visitor types may itself contain personal data. Requests specify zero-data-retention routing, deny provider data collection, and may be served only by Together AI, CoreWeave or ModelRun.Processing location not verified
RenderHosting the brain (all server-side Memory and metadata)All server-side data at rest, and every request to the brain/API, which Render routes through Cloudflare's networkUSA (Virginia)
Backblaze (Backblaze, Inc.)Encrypted off-site backupsEncrypted copies of our account database, which may also include copies of your server-side Memory store. We encrypt them before upload, and Backblaze does not hold the key. Kept for the periods in Section 10.USA (US East)
VercelHosting the website and dashboard; cookieless page counting (Vercel Web Analytics) on both, and page-speed measurement (Vercel Speed Insights) on the websiteRequest data and served content, including Memory text passing through the dashboard when you view, search, ask about or export your Memories. For measurement: the page address, referring page, browser, operating system, device type, approximate location and page-load timings, with nothing stored in your browser.Requests are received at Vercel's nearest network location, which may be outside the USA (for example in India), and processed in the USA (US East)
Cloudflare, Inc.Cookieless page counting and page-speed measurement (Cloudflare Web Analytics) on the website and dashboardThe page address, referring page, browser and device details, and page-load timings, with nothing stored in your browser. Cloudflare does not log query strings.USA
Google LLC (Google Analytics)Website and product analytics (aggregate usage measurement)Online identifiers (cookie IDs), device/browser info, pages viewed, approximate (city-level) location, and, for signed-in dashboard users, a pseudonymous user id and plan tier. Google signals and the collection of granular location and device data are on, so Google may associate visits with the Google account of a signed-in visitor who has allowed this. Loaded on the website and the dashboard only after you press Accept all, and never where GPC is present.USA
PostHog, Inc.Product analytics for the marketing website and the dashboard; heatmaps and session replay on the marketing website onlyOnline identifiers (a random visitor id; on the dashboard, your pseudonymous user id), device/browser info, pages viewed, and measured interactions. On the dashboard, only the usage events described in Section 4: never Memory content, searches, questions or anything you type, and no session replay. With your consent (Accept all), on the website only, this may include a session replay of movement through a page, with every input masked and the contact form and Ask Atlaso box excluded entirely. Without it, nothing is stored on the device and no replay is recorded, but PostHog still counts page views, visits and clicks on the website and may record an approximate location worked out from your IP address; our PostHog setting discards the IP address itself. Never loaded in the browser where GPC is present; one server-side event when a Pro subscription starts (plan and billing interval) is sent regardless.USA
Sentry (Functional Software, Inc.)Error and crash monitoring for the dashboard and brain/APIError events, stack traces, page or API routes, and technical browser, device and service details. Atlaso configures Sentry not to store IP addresses in these events and does not attach an account id, email address or name. Memory content and request bodies are not intentionally sent.United States
Resend (Resend, Inc.)Transactional email delivery: contact-form, support and waitlist confirmations, waitlist updates, account and billing emails (including payment receipts), product-update emails, and delivery of contact-form, support and waitlist messages to our support inbox. It may also deliver Clerk's sign-in code and account security emails.Email address, name, and the message content of the emails we send (a confirmation can quote the message you wrote to us). Waitlist addresses are kept on that plan's contact list until you ask to leave it.USA
Upstash (Upstash, Inc.)Rate limiting and abuse prevention for our website's forms and Ask AtlasoOne-way codes made from IP addresses and dates (kept up to 48 hours); one-way codes made from an email address and a plan, used to allow one waitlist sign-up a day; and, if an email sign-up is waiting for confirmation, the email address itself for up to 24 hoursIndia (AWS Mumbai)
Google LLC (Google Workspace)Hosts our email, including the support@atlaso.ai inbox, which only our founder can accessEmails you send us and our replies, including contact-form and dashboard support messages and data-rights requestsUSA and other countries where Google operates
MintlifyHosting our documentation site, docs.atlaso.ai, and its AI assistantRequest data from visits to docs.atlaso.ai, and any question you type into its AI assistantUSA (HQ in San Francisco); pages are served through Cloudflare's global network from a US East origin; where the docs AI assistant processes questions: not verified

For the maintained, dated list and how we tell you about changes, see our Sub-processors List. We use Google Analytics and PostHog for usage analytics, Vercel and Cloudflare for the page and speed measurements described above, and Sentry for error reporting. Ask Atlaso uses OpenRouter and a routed MiniMax model as described above. Resend delivers the emails we send you: the reply confirming we received your message, waitlist confirmations and updates, account and billing emails, and product updates. Our own mailbox, including support@atlaso.ai, is hosted by Google Workspace, so messages you send us (including contact-form messages and data-rights requests) are stored there. Apart from Clerk, which may send sign-in code and account security emails itself, and Google Workspace, which hosts our mailbox and sends our replies to you, we do not use any other email vendor. Our emails load their fonts from Google Fonts, so if your email app loads remote content when you open one of our emails, Google receives your IP address and browser details.

We have no advertising partner. Earlier versions of this policy disclosed 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. We now use no advertising vendor of any kind. Some of our providers may act as independent controllers for some data under their own terms: for example, Stripe processes payment data for its own legal and fraud-prevention purposes under its own privacy policy, and Google may use some Google Analytics data for its own purposes, such as Google signals and aggregated modelling, under its own policies. Otherwise, the service providers listed above process data to provide their services to us under the arrangements described on our Sub-processors List.

9. International Data Transfers

Atlaso is a US company with operations and personnel in India. Our infrastructure and service providers may process personal data in the United States, India, and other locations where they operate. Fireworks states its servers are in the United States. Our encrypted backups are stored with Backblaze in the United States, and the short-lived rate-limit codes for our website's forms and Ask Atlaso are stored with Upstash in India. An Ask Atlaso request may be served only by Together AI, CoreWeave or ModelRun through OpenRouter, and we have not verified where those hosts process it. Our documentation site's pages are served by Mintlify through Cloudflare's global network from a US East origin; we have not verified where its AI assistant processes questions. The location column in Section 8 distinguishes known locations from those still to be confirmed.

Transfers from the EEA and UK require a valid transfer mechanism where the destination lacks an adequacy decision. We are finalizing the applicable Standard Contractual Clauses, UK Addendum, assessments and related instruments for the relevant transfers. We do not represent that every instrument is already executed. For information about the safeguards applicable to your data, contact support@atlaso.ai.

10. Data Retention

We retain personal data for as long as needed to provide the Service and for the purposes described in this policy.

  • Memory content: retained for the life of your Account. There is no automated expiry of Memory content. On a verified deletion request (see Section 12) we delete it from our live systems without undue delay and within the statutory timeframes that apply to you, and in any event within 30 days. Copies in our encrypted backups expire on the schedule described under Backups below.
  • Account, profile, device, and plan data: retained for the life of your Account and deleted in line with a verified deletion request.
  • Transient raw capture text in the enrichment queue: cleared (set to empty) once processed.
  • Search text: the search text kept with a recall (Section 4) is deleted after about 30 days, or later if the search was rated for usefulness, and in any case when your Account is deleted. Content-free recall statistics are deleted after 90 days.
  • Tokens: access and device tokens expire after 90 days and app refresh tokens after 1 year, or earlier if you disconnect that Device or app; one-time authorization codes expire within minutes; duplicate-request keys are deleted after 7 days.
  • Campaign attribution data: the atl_attr cookie expires from your browser after 90 days; where a signup was attributed to a campaign, that single row is retained for the life of the Account and deleted with it on a verified deletion request.
  • Waitlist sign-ups: your email address stays on the Resend contact list for that plan until you ask to leave it, by replying to any waitlist email or writing to support@atlaso.ai.
  • Billing records: retained by Stripe and by us as required for tax, accounting, and legal-compliance purposes.
  • Usage counters, Device records and deletion markers: kept for the life of your Account and deleted with it.
  • Approximate location: only the most recent city and region is kept; it is deleted when you turn the setting off or delete your Account.
  • Analytics events: PostHog keeps events for 1 year and website session replays for 30 days; Google Analytics keeps event and user data for 14 months.
  • Error reports: Sentry keeps error events for its standard retention period. They contain no account id, email address or name.
  • Provider logs: our hosting and infrastructure providers keep operational logs, which can include IP addresses, your user id and the search text described in Section 4, for their standard periods.

Deletion and retraction paths:

  • Forget a Memory: erases the Memory's text from our server-side store and its search index, clears any greeting or summary made from it, and records a deletion marker (a tombstone) so your other Devices delete their copy the next time they sync. Text that was already given to an AI tool in a past conversation stays in that tool. Memories forgotten through older versions of the Service may keep their text in our store until your Account is deleted. Copies in backups expire as described under Backups below.
  • Revoke / disconnect a Device: revokes its tokens immediately and marks its registry entry as disconnected; the entry is kept so you can reconnect, and is deleted with your Account. It does not delete your Memories or the local files on that computer.
  • Downgrade (Pro → Free): arms an approximately 5-day grace period; expensive AI features turn off immediately; at expiry we keep your most-recent Device and disconnect the rest. Your Memories are not deleted on downgrade.
  • Account deletion: you can delete your Account yourself in the dashboard under Settings > Privacy > Delete my account (we ask you to confirm it is you first), or ask us at support@atlaso.ai. Deletion disconnects every Device and app, permanently deletes your server-side Memory store and the records linked to your Account in our database, removes you from any waitlist you joined in the dashboard, and deletes your sign-in account at Clerk. To leave a waitlist you joined on our website, reply to any waitlist email or write to support@atlaso.ai. If you are on Pro, deleting your Account ends Pro immediately, with no refund for the unused part of your billing period; this does not affect the 14-day withdrawal right of consumers in the EU and UK described in our Refund & Cancellation Policy. We remove your data from our live systems within 30 days of your request. We keep your Stripe customer record and invoices, marked as deleted, for tax and accounting; a deletion receipt containing a one-way code made from your user id (never your email or Memories), so a deleted Account cannot be restored by mistake; and the emails you sent us. Copies in our backups expire on their own schedule (see Backups below). Pseudonymous analytics events linked to your former user id may remain until the analytics provider's retention period ends (1 year in PostHog, 14 months in Google Analytics). Deleting your Account does not remove the Atlaso folder (~/.atlaso) from your own computers; you can delete it yourself.

Backups. We keep encrypted backups so we can recover from an outage or data loss. Each night we copy our account database, which includes Memory-derived text such as your latest dashboard greeting and captures waiting to be processed, and our backups may also include copies of your server-side Memory store (and so the search text kept in it). Each copy is encrypted on our own servers before it is uploaded to Backblaze in the United States, and Backblaze does not hold the key. Each backup is locked so that no one, including us, can change or delete it early: daily copies are kept for 14 days, weekly copies for 35 days and monthly copies for 93 days, and they are then deleted automatically. This means data you delete, including a deleted Account, can remain in backup copies for up to about 94 days. Our database provider, Neon, also keeps a 7-day recovery history, and our hosting provider may keep short-term disk snapshots. If we ever restore a backup, data deleted after that backup was taken could come back.

Erasure and Fireworks. A feature in Section 6 sends text to Fireworks when it runs. Fireworks does not log or store that text: it exists only in memory while the request runs, and prompt caching may keep some of it for a few minutes before it is cleared. Atlaso does not use Fireworks as a store for your Memory, so deleting a Memory removes it from Atlaso's canonical store under the process above. The technical metadata Fireworks keeps, such as token counts, is not affected by deleting a Memory.

Legal-hold and preservation carve-out. Where we are legally required to preserve data, for example to comply with a legal hold, a law-enforcement preservation request, a subpoena or court order, our obligations to report and preserve suspected illegal content (including the preservation duties under 18 U.S.C. §2258A), or to establish, exercise, or defend legal claims, we may suspend deletion of the affected data for as long as the preservation obligation lasts, even if you have asked us to delete it. We delete the data once the obligation ends.

11. Security

We take reasonable and appropriate technical and organizational measures to protect personal data. These measures, implemented among others, currently include:

  • Token handling: tokens stored only as SHA-256 hashes; OAuth codes/refresh tokens hashed; plaintext device tokens held only briefly during the approve-then-consume flow. The client secrets issued to apps when they register with our MCP connector are currently stored unhashed.
  • Secret scrubbing: redaction of detected secrets (private keys; sk-, GitHub, AWS, Google, and Slack tokens; JWTs; bearer tokens; credentials embedded in URIs; high-entropy blobs) from Memories on every ingress and on enriched output. The search text described in Section 4 is not scrubbed. The redaction process is designed to fail closed: if a check cannot complete, the content is treated as if it contained a secret rather than passed through. As noted in Section 4, secret material may be transiently present in transit before it is redacted, so this is not a guarantee.
  • Authenticated connect flows: PKCE with loopback device connect (RFC 7636 / RFC 8252); an OAuth 2.1 authorization server with our own consent page, dynamic client registration, and revocation.
  • Service-to-service gating: constant-time secret comparison for web-to-brain calls.
  • Tenant isolation: per-tenant isolation by authenticated user_id; per-project visibility is designed to fail closed; cross-user access attempts return a 404.
  • Abuse controls: rate limiting, denial-of-service guards (a 64 KB text cap, a batch cap of 100, and device caps), and a data directory locked to owner-only permissions.

Encryption. Data is encrypted in transit (HTTPS everywhere; Neon connections require SSL). At rest, data relies on our infrastructure providers' disk encryption (Neon, Render). We do not add our own application-level encryption to Memory content in our live systems. Our backups are encrypted by us (AES-256-GCM) before they leave our servers.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security. Do not store regulated data (such as health information or payment-card data) in your Memories unless separately contracted with us.

Breach notification. In the event of a personal-data breach, we will assess and notify as required by applicable law, in-product and/or by email where available. In particular:

  • EU / UK (GDPR): where the breach is likely to result in a risk to individuals' rights, we will notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it (Art. 33), and where the breach is likely to result in a high risk, we will notify affected individuals without undue delay (Art. 34).
  • India (DPDP Act, 2023): we will notify the Data Protection Board of India and affected data principals of a personal-data breach in the manner and timeframe required by the Act and its rules.
  • United States and other regions: we will provide any notifications required under applicable state or national breach-notification laws.

12. Your Rights

Tools in the dashboard. On every plan you can see and forget individual Memories, change your privacy settings, and delete your Account (Settings > Privacy). Export is a Pro feature: on Pro you can download your Memories from the dashboard (Settings > Privacy) as JSON, Markdown, AI context or CSV files, or print them or save them as a PDF. On any plan, you can request a copy of your data under your legal rights at support@atlaso.ai.

12.1 GDPR / UK GDPR (EEA and UK users)

You have the right to: access your data; rectify inaccurate data; erase your data ("right to be forgotten"); restrict or object to processing; data portability; and to withdraw consent where processing is based on consent. You also have the right to lodge a complaint with a supervisory authority in your country of residence or work.

To exercise these rights, contact support@atlaso.ai. We will respond within the timeframes required by law (generally one month under the GDPR).

12.2 CCPA / CPRA (California residents)

We provide notice at collection through this policy. California residents have the right to know/access, delete, and correct personal information, and to limit the use of sensitive personal information.

We do not sell your personal information, as that term is defined under the CCPA/CPRA, and we have not done so in the preceding 12 months.

"Sharing" for cross-context behavioral advertising. We run no advertising pixels or advertising cookies, and we have no advertising partner. Google Analytics, which loads only after you press Accept all and never where GPC is present, has Google signals switched on, so Google may associate visits with the Google accounts of signed-in visitors who have allowed this, and Google may use some Google Analytics data for its own purposes under its own policies (Sections 4 and 8). Between August 1, 2026 and September 22, 2026, our marketing website loaded a Reddit advertising pixel for visitors outside the EU/EEA/UK/Switzerland whose browsers were not sending an opt-out signal. Through that pixel Reddit received online identifiers and the fact of a visit, and used them for advertising measurement and to build advertising audiences. We treated that as "sharing" under the CCPA/CPRA and said so plainly. That pixel was removed on September 22, 2026, and no advertising pixel now runs. We did not share personal information through an advertising pixel before August 1, 2026 either, and the dashboard at app.atlaso.ai has never carried an advertising pixel in any region.

How to opt out. We treat the Global Privacy Control (GPC) signal as a valid opt-out request and act on it directly: when your browser sends GPC, our analytics provider PostHog is not loaded at all on our website or dashboard, so your browser stores no identifier, records no session replay and sends no event, and Google Analytics does not load on our website or dashboard. The one exception is the single "subscription started" event our server sends when a Pro subscription starts (plan and billing interval), which does not come from your browser and so is sent regardless of GPC (Section 4). GPC does not switch off the cookieless page counting and page-speed measurement by Vercel and Cloudflare (Section 4), which stores nothing in your browser. You can also choose Necessary only in our website's cookie banner, or opt out by emailing support@atlaso.ai.

We will not discriminate against you for exercising your rights. To make a request, contact support@atlaso.ai.

Other US states. Comprehensive privacy laws in states including Virginia, Colorado, Connecticut, Texas, and Oregon (among others) give residents comparable rights: to access, correct, delete, and obtain a portable copy of their personal data, to opt out of sale/targeted advertising/certain profiling, and, in several states, to appeal a decision on a rights request. Some of these laws apply regardless of a business's size or revenue (for example, Texas and Oregon have no such thresholds). If you are a resident of one of these states, you may exercise your rights by contacting support@atlaso.ai, and we will honor them as required by your state's law. Your browser's Global Privacy Control signal is honored in every region, not only California: where it is present, neither PostHog nor Google Analytics loads in your browser on our website or dashboard.

12.3 India: Digital Personal Data Protection Act, 2023

For data principals in India, Atlaso acts as a Data Fiduciary and processes your personal data on a consent-based model (with the enumerated legitimate uses where they apply), as described in Section 5.2. In that role we take on the Data Fiduciary duties under the Act, including maintaining the accuracy and security of your data, using it only for the notified purpose, and erasing it when the purpose is served or you withdraw consent (subject to Section 10's legal-hold carve-out).

If you are in India, you have the right to access a summary of your personal data and our processing, to correction and erasure, to grievance redressal, and to nominate another individual to exercise your rights in the event of death or incapacity. Because our processing is based on your consent, you may withdraw that consent at any time by contacting support@atlaso.ai; withdrawal does not affect processing carried out before it.

Children. Atlaso is not intended for anyone under 18 in India. Sign-up does not ask your age; if we learn that an Account belongs to someone under 18 in India, we will delete it (see Section 13). We do not track, profile, or serve targeted advertising to children.

Grievance redressal. You can raise any privacy grievance with our Grievance Officer, Ashish Khandelwal, at support@atlaso.ai, and we will work to resolve it. If your grievance is not resolved, you may complain to the Data Protection Board of India.

12.4 Verifying your request

To protect your data, we may need to verify your identity before fulfilling a request. We will only use information provided in a request to verify and respond to it.

13. Children's Data

The Service is not directed to children, and you must meet the minimum age set out in Section 3 of our Terms of Service to use it: at least 13 years old, and at least 18 years old in India. Where local law sets a higher age for consenting to the processing of personal data (16 in parts of the EU/EEA), you must meet that age or have the consent of a parent or guardian. Sign-up does not ask your age. We do not knowingly collect personal data from anyone who does not meet these requirements, and if we learn that an Account belongs to such a person, we will delete it. If you believe a child has provided us with personal data without meeting these requirements, contact support@atlaso.ai and we will delete it.

14. Cookies

We use essential authentication cookies (set by Clerk); small functional preferences in your browser's local storage (your theme, your chosen export format, and whether you have dismissed certain dashboard messages); a flag in local storage that our own team sets to keep our visits out of analytics; and Google Analytics 4 cookies for aggregate usage analytics, with Google signals and granular location and device data turned on (Section 4). On our marketing website, we ask first: a cookie banner offers Accept all or Necessary only, and Google Analytics, PostHog's cookies and session replay, and our atl_attr attribution cookie are used only after you press Accept all. We store your answer in our own atl_consent cookie. Before you answer, PostHog still counts visits on our website without storing anything in your browser (Section 4). We load no advertising pixel and no third-party advertising cookies anywhere. The dashboard at app.atlaso.ai follows the same answer: it runs no session replay, loads Google Analytics and lets PostHog store an identifier in your browser only after you press Accept all, loads neither where GPC is present, and reads our own atl_attr cookie once at signup, which is shared across atlaso.ai and app.atlaso.ai. Without Accept all, the dashboard still sends PostHog the pseudonymous usage events described in Section 4, with nothing stored in your browser. On both our website and dashboard, the page counting and page-speed measurement we use from Vercel and Cloudflare sets no cookies and stores nothing in your browser. For the full detail, including how to change your answer or block each of these, see our Cookie Policy.

15. What We Never Do

  • We do not sell your personal data.
  • We run no advertising pixels or advertising cookies, anywhere: not on the marketing website, not on the dashboard, in no region. The one advertising pixel we previously used was removed on September 22, 2026. Google Analytics, which loads only after you press Accept all, has Google signals switched on (Section 4).
  • We never share your Memory content, your account details, or your email address with an advertising network. We have no advertising network.
  • We never record a session replay on the dashboard (app.atlaso.ai), for any website visitor who has not pressed Accept all in our cookie banner, or for any visitor whose browser sends a Global Privacy Control signal. Where replay does run, it captures no text you type: every input is masked and our contact form and Ask Atlaso box are excluded entirely.
  • We do not operate a training endpoint and do not train AI models on your Memory. Selected Memory text is sent to Fireworks AI for the features listed in Section 6 on every plan, including Free. Fireworks runs these features on open models with zero data retention, and it does not use this text to train or improve its models, because that requires an explicit opt-in, which Atlaso has not given.
  • We use Sentry for error monitoring in the dashboard and brain/API. We configure Sentry not to store IP addresses in error events and do not attach your account id, email address or name. We also use Google Analytics and PostHog for usage measurement, and Vercel and Cloudflare for page and speed measurement, as listed in Section 8. Dashboard analytics do not intentionally include Memory content, searches or Ask questions. We use no advertising pixels or advertising cookies.

16. Business Transfers

If Atlaso is involved in a merger, acquisition, financing, reorganization, sale of assets, or bankruptcy, personal data (including your Memories and account data) may be transferred or disclosed as part of that transaction or diligence, as a business asset. Any acquirer or successor will remain bound by the commitments in this Privacy Policy, or we will require it to honor equivalent protections, and we will notify you (in-product and/or by email where available) of any change in ownership or use of your personal data, and of any choices you may have, as required by applicable law.

17. Changes to This Policy

We may update this Privacy Policy from time to time. When we make a material change, we update the date above and tell you in advance, in the product or by email, so that you can stop using the Service or delete your Account before the change takes effect. When we make a material correction, we update the date above and give appropriate direct notice. The date and substance of a correction do not make earlier processing newly authorized.

Change log

  • October 24, 2026: Device data now includes which version of Atlaso each connected tool is running, so we can see which versions are in use and remind people on an old version to update.
  • October 6, 2026: We described our encrypted backups and how long they keep data, and the real deletion timelines; added Backblaze, Upstash, Google Workspace and Mintlify to our sub-processors and named the hosts OpenRouter may use for Ask Atlaso; described self-serve account deletion and what it keeps; disclosed that the search text Claude Code, Codex and Antigravity send is kept for about 30 days without secret scrubbing and may appear in server request logs; described the approximate-location and improve-Atlaso settings, which are on unless you turn them off; disclosed that PostHog counts visits to our website before you answer the cookie banner, and that Google signals is on in Google Analytics; corrected which Pro features use Fireworks and disclosed that Memories saved on Free are enriched after you upgrade; named our India Grievance Officer; and updated the age rules, export and product-update email sections.
  • September 27, 2026: We corrected an inaccurate statement that Free-plan Memory was never sent to a language model. Selected Memory text has been sent to Fireworks AI for the dashboard greeting and Ambient Memory summaries on every plan, including Free. We clarified Fireworks' data-handling terms, Ask question handling, the separate website assistant, error reporting and international transfers. We added Resend, which delivers the emails we send, including the reply confirming we received a contact-form message and waitlist confirmations.

Questions about this policy? Contact us at support@atlaso.ai.