Privacy Policy

Version 1.9 · Effective 28 October 2026

Atlas Red is built so that your content stays yours: map content is encrypted at rest, nothing you write is used for advertising or AI training, and the product analytics we collect can never contain your content. This policy explains exactly what we process, why, and what control you have.

Who is responsible

Atlas Red (app.atlas-red.com) is operated by Sinisa Dukic, trading as Electra Apps Studio, 8 Ljubljana Str., 1618, Sofia, Bulgaria (the “operator”, “we”) — see our Legal Notice. Sinisa Dukic is the data controller for the personal data described here. For any privacy question or request, contact hello@atlas-red.com.

What we store, and how

Account data

Your name, email address, a salted hash of your password (never the password itself), email verification status, account role, your edition (free or purchased license), the Terms of Service version you accepted, and timestamps. This is what makes sign-in work and your license honored.

Signing in with Google (optional)

If you choose “Continue with Google”, Google tells us your name, your email address, whether Google has verified that address, and an identifier for your Google account so we recognise the same account next time. We store those four things and nothing else: not your profile picture, not Google's sign-in tokens, and we ask for no other access (no contacts, calendar or Drive). Google learns that you signed in to Atlas Red at that moment; its own privacy policy governs what it does with that. Signing in with Google is never required — the email form stays.

Your content

Maps, nodes, field text, notes, cross-links and attached images. All content is encrypted at rest (AES-GCM with per-scope derived keys) before it is written to the database. We never read it except as required to serve it back to you, never share it, and never use it to train AI models or for advertising.

Settings

Your preferences are stored as an encrypted blob, like content.

How you found us

We record on your account how you found us: the campaign link you followed (for example from a creator we work with) and any promo code you use, the site that referred you to the app if your browser told us, and the AI assistant (such as ChatGPT or Claude) if you created your account while connecting one — to measure our marketing and to apply the discount that was promised to you. Nothing else rides along: no advertising identifiers, no cross-site tracking.

Feedback you send

If you send feedback (the in-app widget, or through a connected AI assistant), the report text and any screenshot you attach are stored encrypted like your content. The team reads them to respond; replies and status changes appear in the app, and the important ones are also emailed to you.

Security log

Security-relevant actions (sign-ins, share-link creation and revocation, account changes, admin actions) are written to an append-only audit log that can include the IP address of the request. IP addresses are automatically redacted after 12 months; the record of the action is kept longer to investigate abuse and account compromise. Where this log refers to an account that has since been deleted, it holds only a pseudonymized identifier, not your email address.

Backups

Nightly encrypted backups of the database are kept for a limited rolling window for disaster recovery, then deleted automatically. A second copy of each backup is stored outside Cloudflare, with Backblaze in the EU, so that one provider’s outage cannot take the backups with it. That copy is encrypted before it leaves our servers, Backblaze never holds the key, and it is deleted automatically after the same window.

Cookies

In the Atlas Red app (app.atlas-red.com), one strictly necessary session cookie keeps you signed in. No advertising or cross-site tracking cookies in the app, ever — we keep app.atlas-red.com permanently free of advertising tags.

Our marketing site (atlas-red.com) is a separate surface with its own cookie notice, which lists the advertising cookies used there and the vendors behind them. Those cookies are set only if you opt in on that site, and never on app.atlas-red.com.

Product analytics

To understand how Atlas Red is used (for example, where new users get stuck), we collect a small set of content-free usage events for signed-in users — things like “a map was created from an import” or “an export to Markdown happened”. By design these events can never contain map content, node text, map names, search queries, file names, share links or your email: the allowed events and their properties are a fixed, coarse list (counts are bucketed, pages are recorded as templates, not URLs).

Processed by PostHog on servers in the EU (Frankfurt), under a data processing agreement.
All traffic goes through our own servers; your IP address is never forwarded to PostHog.
Cookieless — analytics stores nothing on your device.
Only for signed-in users; visitors, the sign-in pages and shared-map views are never tracked.
Events are linked to your random account ID, not your email or name, and are deleted after 12 months.
You can turn analytics off at any time in Settings, and we honor your browser’s “Do Not Track” and Global Privacy Control signals automatically.

Our lawful basis is legitimate interest in improving the service (Art. 6(1)(f) GDPR), which we consider met because the data is content-free, EU-resident, IP-stripped and opt-out — you have the right to object at any time via the Settings toggle or by contacting us.

Email we send you

Two kinds, handled differently. Account email (verification, password reset, purchase receipts, replies to your feedback) is part of operating your account and is always sent. Product email (getting-started tips after you sign up, occasional product news) goes only to verified accounts, at most one message every two days, and every product email carries a working unsubscribe link; unsubscribing stops all product email while account email continues. Both kinds use your email address and nothing else about you beyond what the message itself is about.

AI features — only when you use them

Two features send content to an AI model, and both are entirely optional and only run when you invoke them. AI import turns a photo or scan, a document or pasted text, a voice recording, or a YouTube video’s captions into a map: the file or text you provide is sent to an AI model served by OpenRouter (or, if you have connected your own AI provider account, to the provider you chose) via Cloudflare AI Gateway. For a YouTube link, only the video ID is sent to our caption provider, Decodo, to fetch the video’s public captions — never your account details. AI restructure sends the topics of the branch you selected to the model and replaces them with its reorganization (undoable like any edit).

The uploaded photo or audio file itself is not kept after the import completes. The text an import was built from (the extracted document text, the transcript, the captions) is kept — encrypted, like all your content — attached to the resulting map as its “Source”, so you can read it and rebuild from it; it is deleted with the map. We also keep token counts, cost and duration per AI call for rate limiting and budgeting — never the content. If you bring your own provider key, it is stored encrypted and is write-only (it can never be read back out), and your provider’s own terms apply to that processing.

Connected AI assistants

You can connect an AI assistant (such as Claude or ChatGPT) to Atlas Red. The connection is authorized by you on a consent screen and acts only on your own account: the assistant can list, read, create and edit your maps on your behalf through a fixed set of tools, and your identity comes from the authorization — never from what the assistant sends.

Map content the assistant reads or writes passes to the assistant provider you chose (for example Anthropic or OpenAI), which processes it under its own privacy terms — connecting an assistant is your choice, and which provider sees your content is too.
Tool responses carry only your own data. Our own logging of assistant activity is content-free: which tool ran and whether it succeeded — never the content it carried.
Images transfer over one-time URLs that expire after minutes and work exactly once.
You can disconnect an assistant at any time in Settings → Connected apps, which immediately revokes its access.

Preventing repeat abuse of free trials

New accounts receive a one-time free AI-credit trial. To stop the same person from farming that trial by repeatedly deleting and re-registering, we keep a single pseudonymized identifier derived from your email address — a keyed one-way hash. We never store the email address itself in this record, the hash cannot be reversed to recover it, and it is used only to check whether a returning address has already had a trial (and, if a billing or abuse dispute arises, to correlate events to an account). It holds no other information about you.

Lawful basis: our legitimate interest in preventing fraud and abuse (Art. 6(1)(f) GDPR, Recital 47).
It is the one item deliberately kept when you delete your account — everything else is purged.
Retention: automatically forgotten after 24 months of inactivity, after which a returning address is treated as new.
An administrator can always grant credits manually, so this never permanently locks anyone out.

Who processes data for us

We use a small number of service providers (processors), each bound by a DPA:

Cloudflare — hosting, storage and content delivery for the entire service.
Backblaze (EU) — off-site storage of the encrypted backups (see Backups above). It receives encrypted data only, never the key.
Resend / Cloudflare Email — email delivery (account email and product email, as described above). Your email address and the message content only.
PostHog (EU) — product analytics as described above.
OpenRouter (or your own configured provider) — the AI features, only when you use them.
Decodo — fetching a YouTube video’s public captions for an import; receives the video ID only, nothing about you.

An AI assistant you connect (see above) is not our processor either: you choose it, and it handles what it reads under its own terms.

Paid purchases work differently: our merchant of record, Creem (Armitage Labs OÜ), Telliskivi Street 57b/1, Tallinn 10412, Estonia, is the seller of record for the Pro license and AI credit packs and an independent controller — not our processor — for the transaction data it needs for billing, tax and fraud prevention. It receives your email address, your billing and tax country/address, and the record of what you purchased. Card details are entered with and handled by the merchant of record and its payment providers; they never reach Atlas Red’s servers. A license bought on a marketplace (AppSumo) is sold by that marketplace, an independent controller for your purchase and payment data. The marketplace sends us only the license key, its tier and its status — never your email address or payment details; the account the license attaches to is the one you sign in with or create when you activate it.

We do not sell personal data, and the Atlas Red app has no advertising or data-broker integrations. Where a provider processes data outside the EU/EEA, transfers are covered by standard contractual clauses.

Share links

When you create a share link, anyone who has the link can view that map read-only, without an account. Share tokens are stored hashed for lookup, and a copy is stored encrypted with your content so the app can show you your own links again. You can revoke a link at any time; treat links you send as you would the content itself. We do not track visitors to shared maps.

How long we keep data

Account and content: until you delete them, or your account is deleted.
Backups, including the off-site copy: a limited rolling window, deleted automatically.
Security log: the action is kept as long as needed for abuse and security investigation; IP addresses are redacted after 12 months.
Analytics events: 12 months.
Anti-abuse trial identifier: a pseudonymized hash, up to 24 months after last activity (see above).

You can delete your account yourself in Settings → Account. Deletion permanently purges your content, settings, sessions and share links, and removes your analytics profile. Two things are kept by design: the append-only security log, and the pseudonymized anti-abuse identifier described above — neither contains your content, and the security log holds only a pseudonymized identifier rather than your email once the account is gone. This retention is limited to what fraud-prevention and security investigation require.

Your rights

Under the GDPR you have the right to access, rectify, export, delete and restrict the processing of your personal data, to object to processing based on legitimate interest, and to lodge a complaint with a supervisory authority. Export is built in (every map exports to open formats — JSON, Markdown, OPML and more), and deletion is self-serve as described above. For anything else, email hello@atlas-red.com.

Changes

Atlas Red is not directed at children under 16, and creating an account confirms you are at least 16. If we learn that an account belongs to someone younger, we delete the account and its content; a parent or guardian can ask us to at hello@atlas-red.com. If we materially change this policy, we will announce it in the app before the change takes effect. See also our Terms of Service.

Version history

1.9 — 28 October 2026: “Signing in with Google” added to “What we store” — an optional sign-in method, what Google tells us and what we keep (name, address, verified flag, account id; never the picture or tokens). Nothing changes for existing accounts.
1.8 — 25 October 2026: Backblaze (EU) added to “Who processes data for us” — it stores an encrypted second copy of the backups outside Cloudflare, without the key, and deletes it after the same rolling window.
1.7 — 2 October 2026: the children paragraph now says what happens when an account turns out to belong to someone under 16 (deletion, and how a parent can ask), matching the age confirmation added to the signup form. Clarification only; the 16-year minimum has been in the Terms since 1.0.
1.6 — 5 September 2026: marketplace purchases (AppSumo) — what the marketplace sends us (license key, tier, status; never your email or payment details).
1.5 — 19 August 2026: the cookie and advertising statements are now explicitly about the Atlas app (app.atlas-red.com) rather than unqualified absolutes, and point to the separate cookie notice for the marketing site atlas-red.com, where advertising cookies are used only with opt-in consent. Recorded as a minor clarification, not a material change, because the app’s own practices are unchanged: app.atlas-red.com stays permanently free of advertising tags, and the cookies now disclosed sit on a different site, are denied by default, and are disclosed where they are collected.
1.4 — 19 August 2026: added “Connected AI assistants” (what an assistant you connect can access and who processes what) and “Email we send you”; the AI section now covers all import kinds (photo, document, voice, YouTube — with Decodo as caption provider) and AI restructure, and discloses that an import’s source text is kept encrypted with the map; disclosed campaign attribution and feedback storage; share links are no longer shown only once — your own links are stored encrypted so they can be shown to you again.
1.3 — 3 August 2026: “Who processes data for us” now discloses the merchant of record — Creem (Armitage Labs OÜ, Tallinn, Estonia) — as seller of record and independent controller for purchase transaction data, distinct from our processors, including what it receives and that card details never reach our servers. Lemon Squeezy, previously named as merchant of record in the Terms, never processed an order for Atlas Red and holds no transaction data, so it is not listed.
1.2 — 24 July 2026: the controller is now named in full — Sinisa Dukic, trading as Electra Apps Studio, with a postal address and a Legal Notice; contact address is now hello@atlas-red.com.
1.1 — 22 July 2026: product name is now Atlas Red; account data now includes the edition and the accepted Terms version.
1.0 — 17 July 2026: initial version.