Privacy policy

Last updated

What Atlantive collects, why, who processes it for us and where, how long it is kept, and how to exercise your rights. Written from what the service actually does.

Contents

Who is responsible

The controller of the personal data described here is Atlantive, Via Roma 1, Roma ("we", "us"). You can reach us about anything on this page at hello@atlantive.ai.

This policy covers the Atlantive website, account signup, earlier beta requests, the workspace and the agent. It does not cover third-party websites the agent reads or platforms you export to, which have their own policies.

What we collect

Earlier beta request
Before public signup opened, the beta request form collected your email address, the markets you traded, your futures contracts if you traded them, your experience using AI to write code and what you would try first. Earlier requests may also hold a name and a written testing idea. If the link that brought you carried campaign tags (the source, medium, campaign, ad and keyword that an ad or a post of ours puts in its link), those tags were recorded with it. Your network address, browser and the page you came from were not. You can now sign up without sending a beta request.
Site measurement, with your consent
On the public pages, and only if you allow analytics: the pages you visit, the campaign and ad that brought you, and the random identifiers Google Analytics keeps in its cookies, together with what Google itself derives from your visit, such as your browser, device and approximate location. When you open an account after allowing analytics, the fact that an account was opened and whether through Google, email or an invitation, never your address or your name. For earlier beta requests sent with analytics consent, the fact that a request was sent and whether it named futures, never your address or your answers.
Invitation
If an administrator invites you without a request from you, the name and email address they entered and who issued the invitation. That information comes from them, not from you, and is kept as the request would have been.
Account
Your name, email address and a hashed password, when the account was created, whether it is an administrator or disabled, and the sessions that keep you signed in. If you were invited, the request the invitation was issued for.
If you sign in with Google, what Google shares when you choose to: the identifier of your Google account, its name and email address, and whether Google has verified that address. We ask Google for nothing else, and never receive your Google password. Google acts under its own privacy policy and learns that you signed in to this service. You can disconnect Google from your account in Settings.
Workspace
What you create and upload: strategies, files and attachments, backtests, charts and drawings, analyses and their outputs, and your conversations with the agent, together with the record of the work the service ran for them.
The two suggestions on the new chat page that are written for you, kept with the workspace until the next ones replace them, and when they were last written.
Spending
One record for every model call made for you (time, model, token counts and cost in US dollars), the market data read for you, and every change an administrator makes to your allowance, with who made it and why.
Activity
While you use the workspace, each minute in which its page was in front of you and you had used it in the last few minutes, and which part of it was open (the chat, a backtest, a file and so on), never what it showed.
Security
Your network address, used only to count attempts to sign in, to sign up, to change a password, to confirm an address and to open an invitation, so that repeated attempts can be refused. The server's own request log records the request, its result and how long it took, and no network address, browser or query.
Messages
What you write to us, and our replies, if you contact us.

We do not ask for, and ask you not to upload, special categories of data such as health data. We do not collect payment details: nothing in the service is paid for.

Why, and on what legal basis

Running your account and workspace
Creating and securing your account, storing your work, running the agent, backtests and analyses, and keeping your allowance. Basis: performing our contract with you (article 6(1)(b) GDPR).
Earlier beta requests and invitations
Before public signup opened, we reviewed your request, wrote to you about it and issued your invitation. Basis: steps you asked us to take before a contract (article 6(1)(b)).
Knowing which campaigns brought accounts
Keeping with your account the campaign tags of the link that brought your visit (its source, medium, campaign, ad and keyword) and how you signed up, and counting accounts, and earlier beta requests, by those tags, so we know which of our ads and posts are worth what they cost. The tags are read from the address you arrived at and never stored on your device. Basis: our legitimate interest in running our own promotion (article 6(1)(f)).
Measuring visits and our ads
Counting visits to the public pages, and telling Google Analytics that your visit led to a new account, and, if you also allow ad measurement, measuring visits and sign-ups from our ads with Google Ads. Basis: your consent (article 6(1)(a)), which you can withdraw at any time from Cookie settings at the foot of any public page, without affecting what was done before.
Keeping the service secure
Limiting repeated attempts, detecting abuse and investigating incidents. Basis: our legitimate interest in protecting the service and its users (article 6(1)(f)).
Accounting for spending
Measuring what the agent costs so that allowances work and the costs we pay can be reconciled. Basis: performing our contract (article 6(1)(b)) and our legitimate interest in controlling costs (article 6(1)(f)).
Understanding how the service is used
Counting accounts, visits and time spent, and which features and agent tools are used and how often they fail, from the activity minutes and from the records of the work the service ran, so we know what works and what to improve. Only our administrators see these figures, in total and per account, and they never include what you wrote or what your workspace contains. Basis: our legitimate interest in running and improving the service (article 6(1)(f)), which you can object to by writing to us.
Answering you, and legal matters
Replying to messages, enforcing our terms, and establishing or defending legal claims. Basis: our legitimate interests (article 6(1)(f)), or a legal obligation where one applies (article 6(1)(c)).

Your name and email address are necessary to have an account. You can verify your email and choose a password, or continue with Google. Without this information we cannot provide the service. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.

What is sent to a model provider

The agent runs on third-party language models. To answer a turn, the service sends the conversation, a summary of your workspace (the date, file and project names, and recent runs), the files and attachments the agent opens, and the results of the tools it calls, to the model provider over an encrypted connection. Your name, email address and account are not sent, and the conversation is identified only by an opaque value the provider cannot link to you.

Once a day, if you worked in a workspace since its last suggestions, the service sends a summary of that work (the titles of your recent conversations, your last prompts in them, which tools the agent used, and your recent runs and their figures) to a model that writes the two suggestions on the new chat page. The call is made the same way as the agent's, and its cost is recorded in your spending like any other model call.

The request goes to OpenRouter, which forwards it to a provider that serves the model the conversation uses. The models offered today are made by Google and OpenAI. The title of a conversation is written by an OpenAI model from its first message, and the suggestions on the new chat page by an OpenAI model from the summary above. Each provider processes a request under its own terms, which can allow it to keep requests for a limited time, for example to detect abuse. If you have code or information you cannot share with those providers, do not put it in a workspace.

Who receives your data

We do not sell personal data. If you allow ad measurement, Google receives what it needs to measure visits from our ads, as described under Analytics; nothing else is shared for advertising. Your data is processed for us, on our instructions, by the following providers, each receiving only what its task needs:

Hetzner Online GmbH, Germany
Hosting of the servers that run the service, located in Helsinki, Finland.
Cloudflare, Inc., United States
Delivery of the website through its network, which protects it from attacks and automated abuse. Every request to the site passes through Cloudflare, with your network address and browser details, and Cloudflare may set the security cookies the Cookie policy lists. The security check on the sign-in, sign-up, password recovery, verification and invitation forms is Cloudflare Turnstile, which receives what it needs to tell a person from a script, and our server sends it your network address with the result it checks.
Supabase, Inc., United States
Database and sign-in. Your data is stored in Frankfurt, Germany.
OpenRouter, Inc., United States
Routing of the agent's requests to language models, as described above.
Google LLC and OpenAI, L.L.C., United States
Producing the agent's answers with their models, the title of each conversation and the suggestions on the new chat page.
Exa Labs, Inc., United States
Web search, when the agent searches the web. It receives the search query the agent writes, which can reflect what you asked.
Our email provider
The provider of the mailbox we write from, when we write to you about access or answer a message.
PostHog, Inc., United States
Product analytics and private error diagnostics, as described below. Browser analytics requests pass through our domain to PostHog's managed proxy, operated by Cloudflare. Cloudflare processes this traffic as PostHog's subprocessor, potentially in multiple geographic locations.
Google Ireland Limited, Ireland, and Google LLC, United States
Google Analytics and Google Ads measurement of the public pages and of the accounts they lead to, only with your consent, as described below.

When the agent reads a web page for you, the request is made by our server, so the website sees our server's address and not yours. The administrators' console shows accounts, what they have spent and their allowances, and has no view of the contents of a workspace. Members of a workspace you share see what is in it. We may disclose data where the law requires it, or to protect the rights and safety of users and of the service.

Transfers outside Europe

Some of the providers above are established in the United States, so your data may be transferred there. Where it is, the transfer relies on an adequacy decision of the European Commission, such as the EU-US Data Privacy Framework for a certified recipient, or on the standard contractual clauses adopted by the Commission together with supplementary measures where they are needed. You can ask us for a copy of the relevant safeguards.

How long we keep it

Account and workspace
For as long as the account exists. Deleting the account deletes it, its workspaces and everything in them, its sessions, its settings, its activity minutes, its spending records and any earlier beta request linked to it. A workspace you share with somebody else stays with them, including what you contributed to it.
Earlier beta request
Until the beta ends, or until you ask us to delete it, whichever comes first. If you join, it is kept with your account and deleted with it.
Site measurement
Google Analytics keeps the events linked to its identifiers for two months, and its cookies last up to 13 months unless you withdraw your consent, which removes them. When you sign up after allowing analytics, the identifiers of your visit are held, sealed, in the confirmation link or the sign-in step for up to an hour, and with your new account only until the report is sent, within a day at most; the same held for earlier beta requests.
Security counters
A network address is kept in its counter for the minute it was used and the minute after, and removed with the first attempt anybody makes after that.
Server logs
Kept for a limited period for operating and securing the service, and overwritten as newer entries arrive.
Messages
As long as we need to answer you and deal with what you raised.
Backups
Before each release we copy the database, so a failed release can be undone; those copies are kept on our servers for up to 30 days and then deleted. Where our database provider keeps backups for disaster recovery, deleted data remains in them until they expire. Data is never restored from a copy or a backup except to recover the service.

Deleting a conversation removes it from your workspace. The record of the work it ran can still hold the text of a request until the workspace is deleted, and a record of what the conversation cost survives it, no longer naming it, because the accounting has to add up.

Analytics

The public pages (the home page, the beta page and the legal pages) ask before measuring anything. If you allow analytics, Google Analytics records the pages you visit and the campaign that brought you, each address kept to its path and campaign tags. If you also allow ad measurement, Google Ads may use the same visits to measure traffic from our ads. Declining, or never answering, loads nothing from Google.

When you open an account after allowing analytics, the sign-up page reads the identifiers Google Analytics stored for your visit and hands them to our server with the request, and our server tells Google Analytics, once per account, that an account was opened and whether through Google, email or an invitation. Without analytics consent nothing is read or sent. Your email address and your name are never sent to Google.

Before public signup opened, when you sent a beta request after allowing analytics, our server told Google Analytics that a request was sent and whether it named futures, together with the identifiers of your visit, once per address. Your email address, your answers, and anything you wrote were never sent to Google. The workspace itself is never measured by Google.

We use PostHog to learn which screens are opened and which actions are taken, so the product can be improved. Product events contain action names, counts and opaque account and workspace identifiers. PostHog also records clicks and the text of the element clicked, where on a page people click and scroll, page load timings, and short surveys we may show you. Addresses contain only a coarse page name, without query parameters or fragments. On public pages, PostHog counts visits only after you allow analytics in Cookie settings.

With analytics consent, we remember your first campaign, external referring domain, coarse landing page and anonymous browser identifier for up to 90 days. The signup page passes them through the sealed account-opening steps, without loading analytics on authentication pages. Once a new account is confirmed and opened, our server reports sign_up to PostHog with its opening method and first source, linked to the opaque account identifier. Existing accounts and unsuccessful attempts do not produce this event. Your email address, name and authentication secrets are not included. The temporary report is removed after delivery or within a day at most; withdrawing consent removes the remembered browser attribution.

PostHog records sessions: a replay of what was on screen while you used the site, including the workspace, its files, charts and conversations, together with browser console messages and the timing of network requests. Form values and text you type, including prompts, are recorded. Password fields are masked and authentication pages are not recorded. The contents of network requests and replies are not recorded. We use replays to find where the product is confusing or broken.

We also use PostHog to investigate errors and service failures. Diagnostic records may include redacted exception messages and stack traces, incident and request references, software version, and opaque account and workspace identifiers. Server records include job outcomes and AI token usage and cost, without prompts or answers. Essential server error reporting continues when browser analytics is disabled.

Until you allow analytics in Cookie settings, PostHog keeps nothing on your device and its identifier lasts as long as the tab. Once you allow it, PostHog keeps an identifier in a cookie and in local storage so that later visits are recognised, and withdrawing removes it. A Do Not Track signal from your browser switches analytics off. You can object to this processing at any time by writing to us or by enabling Do Not Track.

Your rights

Under the GDPR you have the right to:

  • access the personal data we hold about you and receive a copy of it;
  • have inaccurate data corrected;
  • have your data deleted;
  • restrict how we process it in certain circumstances;
  • receive the data you gave us in a structured, machine-readable format and have it transmitted to another controller;
  • object at any time to processing based on our legitimate interests, on grounds relating to your situation.
  • withdraw a consent you gave at any time, without affecting what was done before you withdrew it.

To exercise any of them, write to hello@atlantive.ai from the address on your account, or tell us how to verify that the request is yours. We answer within one month, which the law allows us to extend by two further months for complex requests, and we will tell you if we do.

You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the European Union member state where you live, where you work or where you think the infringement happened. In Italy that is the Garante per la protezione dei dati personali. We would appreciate the chance to address your concern first.

Deleting your data

You can delete strategies, files, backtests, analyses and conversations from inside the workspace at any time.

To have your account deleted, write to hello@atlantive.ai. An administrator deletes it with everything described under How long we keep it; a deletion cannot be undone, so copy anything you want to keep first.

Security

Connections to the service are encrypted. Passwords are stored only as hashes that nobody can read, including us. Sessions are opaque tokens stored as hashes so they can be revoked, and requests are checked against the address and origin they claim to come from. Attempts to sign in, to sign up and to open an invitation are rate limited.

Strategy and analysis code runs in an isolated container with no network access: it cannot reach the service, the internet or anything else on the machine.

No system is perfectly secure. If you find a vulnerability, please report it to hello@atlantive.ai rather than testing it against other people's accounts, as the Legal notice describes. If a breach puts your rights at risk, we will tell you and the supervisory authority as the law requires.

Children

The service is not directed at anybody under 18 and we do not knowingly collect data about them. If you think a minor has given us personal data, write to us and we will delete it.

Changes to this policy

We will update this policy when what we do with personal data changes, and change the date at the top of this page when we do. If a change is significant, we will tell you in the service or by writing to the address on your account before it takes effect.

May we measure this visit?

With your consent, Google Analytics and PostHog count visits to these pages. You can separately allow Google Ads to measure visits from our ads. Visit measurement starts only after you choose. Cookie policy