Loading…
Loading…
Pricing · Privacy & data · Terms · Contact
Effective September 17, 2026 · Version 2026-09-17
This Privacy Policy explains how Adelphos (“Adelphos,” “we,” “us”) collects, uses, discloses, and protects information in connection with Atlas (the “Service”). It is part of, and should be read with, our Terms of Service.
Atlas is built so that it proposes and you approve. It does not send an email, a message, or a CRM update to anyone on your behalf unless you direct it, and it does not expose your records to another customer except through the team setting described below, which stays off until you turn it on. That is the promise, and we hold to it.
It is a promise about outbound communication and about disclosure to other people - not a claim that your data never leaves one machine. To do its job at all, Atlas transmits what you give it to the providers named in the next section: a card photo has to reach the model that reads it, a voice note has to reach the service that transcribes it, and everything has to be stored somewhere. Those providers process it only to deliver the Service to you, under contracts that bar them from using it for their own purposes. We think you should see that list before you read what we collect, so it comes first.
These are the third parties that receive customer data in order to run Atlas. We will update this list before we start sending your content to a provider that is not on it.
| Provider | What it does | What it receives | Where it processes |
|---|---|---|---|
| Supabase | Database, authentication, and file storage | Account email, Your Content, card images, voice audio | United States |
| Vercel | Application hosting and content delivery | Request logs, IP address | United States |
| Anthropic | Reading business cards, structuring research, drafting follow-ups | Card images, notes, research text, writing-style samples | United States |
| Deepgram | Voice-note transcription | Voice audio and resulting transcripts | United States |
| AssemblyAI | Voice-note transcription (fallback provider) | Voice audio and resulting transcripts | United States |
| Stripe | Subscription payment processing | Billing contact, payment status (no card numbers reach Atlas) | United States |
| Your connected CRM (optional) | Reading and, where you approve a change, writing contact records | Contact records you choose to sync | Determined by your CRM provider |
A connected CRM is the one entry on that list that is yours rather than ours. You choose whether to connect one, you can connect only one at a time, and you can disconnect at any moment. Atlas reads your existing contact book to avoid duplicating what you already have, and it writes back only a change you have approved, and only after you have separately switched on permission for it to write to external systems at all. What that provider then does with the data is governed by your agreement with them, not by this policy.
Adelphos acts in two different capacities, and which one applies changes who is answerable for what.
We are the controller of your account and sign-in information, your billing and subscription records, our operational and security logs, our record of which version of these policies you agreed to, and the research Atlas gathers from public sources. For that information we decide the purposes and means of processing, and this policy is your notice for it.
We are a processor - a service provider acting on your instructions - for the contact records, card images, recordings, transcripts, notes, and drafts you put into Atlas. You decide what to collect about your contacts, why, and how long to keep it. We process it to run the Service for you and for no purpose of our own. If you are buying Atlas for a business and need that in contract form, our Data Processing Addendum sets it out; write to privacy@iatlas.live to have it executed.
Account information: the email address you sign in with. Sign-in uses a one-time code sent to that address; there is no password, so there is no password for us to store.
Content you provide (“Your Content”): business-card photos you capture; voice recordings you make and the transcripts produced from them; notes you type or dictate; text you paste (including, if you choose to teach Atlas your writing style, examples of your own past emails that you paste in yourself); and contact and relationship records you create or import.
Research data: when you enable research, Atlas gathers information about a company and a contact from public sources - the company’s own website and recent public news and press coverage. Every finding is cited and dated, and it becomes part of a record only after you approve it. You can turn research off at any time.
Billing information: if you subscribe, our payment processor collects and handles your payment-card details. We do not receive or store full card numbers; we receive limited billing status, such as your plan and whether a payment succeeded.
Usage and technical data: the logs needed to operate and secure the Service, such as request and error logs, which include IP address and timestamps.
We use information to provide and operate the Service - reading cards, transcribing voice notes, proposing research and drafts, and organizing your relationships; to authenticate sign-in; to process subscriptions and prevent abuse; to secure and troubleshoot the Service; and to communicate with you about your account. We do not sell your data, we do not use it to serve advertising, and we do not use Your Content to train any AI model.
We do not use Your Content to train, fine-tune, or evaluate any model, and we do not grant anyone else the right to. For the AI and transcription providers in the table above, that rests on the terms we hold with each of them, which bar training on data sent through their interfaces. We want to be exact about the shape of that claim: it is a contractual commitment we rely on and can show you, not something we can audit inside someone else’s infrastructure. If a provider changed those terms, we would move to another provider or disclose the change here before continuing to send your content to them.
Accounts are separate by default. Nothing you put into Atlas is visible to another customer unless you deliberately switch sharing on.
Atlas supports organizations: you can create one and invite colleagues, and each member decides individually whether to share their contact book with the rest of that organization. The setting starts off, it is the member’s own choice, and the member can switch it back off. While it is on, the other members of that organization can see the fields of that member’s contact records - the person’s name, employer, role, and contact details, and the fact that a relationship exists. That is the whole point of the feature: knowing that a colleague already knows someone before you call them cold.
What does not cross that boundary: your notes, your voice recordings and their transcripts, your drafts, your research, and your writing-style samples stay private to the member who created them, whether or not contact sharing is on. Members of one organization see nothing belonging to another organization or to an unaffiliated account.
Atlas does not send email or messages on your behalf - every follow-up is a draft you review, copy, and send yourself. It does not connect to or read a mailbox; writing-style examples exist only because you pasted them in. It does not write to your CRM unless you have both switched on permission to write to external systems and approved that specific change. It does not sell your data or use it for advertising. It does not make your records visible to another customer except through the team sharing you switch on yourself. And it does not train a model on what you put in.
A voice note you dictate to yourself is one thing. Recording a conversation with someone else is another. In many places - including a number of US states and most of the EU - recording a conversation is lawful only if the other person consents, and in some of them every participant has to consent. Atlas does not ask anyone for that consent and has no way to know whether you have it. Obtaining it is your responsibility, and nothing here is legal advice about when it is required. If you are unsure, tell the person before you start recording.
While your account is open: For as long as your account is open.
Voice recordings: Deleted once you approve the transcript, unless you choose to keep the recording.
After you delete something: Removed from the live database when you delete it. Encrypted backups are retained on a rolling window and expire on their own schedule - see below.
Backups: Encrypted backups are retained on a rolling window and expire on their own schedule, so a deleted record leaves the backups as that window rolls over.
Operational logs: Request and error logs are retained on a rolling window by our hosting provider and expire on that schedule.
Billing records: Transaction records are retained as long as tax and accounting law requires, typically seven years.
Record of the policy version you agreed to: Retained for as long as your account is open, and afterwards for as long as a claim could be brought.
You can delete any individual record, or your whole account and its data, from Settings. It is not a support request and not a flag on a row we quietly keep: the rows come out of the live database when you ask.
What we will not claim is that every copy everywhere disappears in the same instant, because that is not how backups and vendors work. Encrypted backups roll off on the schedule above, and a deleted record is gone from them once that window passes. Content that was sent to a provider in the table is deleted on that provider’s own schedule under our agreement with them. A connected CRM is your system rather than ours, so deleting in Atlas does not remove what was already written there - delete that in the CRM. And we keep the limited records the law requires, such as transaction records for tax and enough information to handle fraud, abuse, and disputes. If you want to know where a particular deletion stands, write to privacy@iatlas.live and we will tell you.
Your data is stored in a hosted Postgres database with row-level security policies enforced at the database layer: an application request carries the identity of the signed-in account and is evaluated against those policies before any row is returned. Traffic between your browser and the Service, and between the Service and the providers above, is encrypted in transit. Sign-in is a one-time code emailed to you, so there is no password to guess, reuse, or leak. Administrative credentials are held by the small number of people who operate the Service and are used for running it, not for reading customer content.
Row-level security is a strong control, not a proof. Administrative keys, support access, logging, and ordinary human error can all defeat a control that is otherwise working correctly, and no system connected to the internet is perfectly secure. We take measures that are reasonable for a product of this kind and we keep improving them, and if a breach affects your information we will notify you as the law requires. Report a suspected vulnerability or incident to security@iatlas.live.
You can access, correct, export, or delete your data from inside the app at any time. Depending on where you live, you may have further rights under laws such as the GDPR or the CCPA - to access, correct, delete, or port your data, to object to or restrict certain processing, and to withdraw consent, for example by turning off research, writing-style learning, external writes, or team sharing. We do not sell or share personal information as those terms are defined under applicable law, and we will not discriminate against you for exercising a right. To exercise one, contact privacy@iatlas.live; we will respond within the time the law allows.
Atlas exists to manage your business relationships, so most of what goes into it is information about other people. You are responsible for having a lawful basis to collect and keep it, for giving those people whatever notice your own obligations require, and for honoring a request one of them makes to you directly. We process it to run the Service for you, on your instructions, and for nothing else. If a request reaches you and you need help carrying it out inside Atlas, write to privacy@iatlas.live and we will help.
Most of the people described in Atlas never signed up for it. They handed a business card to one of our customers, or were named in a note. If that is you, you can still ask what is held about you, ask for it to be corrected, or ask for it to be deleted. Write to privacy@iatlas.live with enough detail to locate the record - usually your name together with the email address or company on the card.
Here is what happens then, so there is no surprise. The records belong to our customer rather than to us, so for anything inside a customer’s own content we act on that customer’s instructions: we will pass the request to them promptly, help them act on it, and come back to you with the outcome. Where we hold information about you in our own right, or where the law requires us to act directly, we act on it ourselves. We will not charge you for this and will not ask you to create an account to do it. We may need to confirm your identity before disclosing or deleting anything, so that this route cannot be used against you by someone else.
The providers above process data in the United States and, where a connected CRM is involved, in whatever region that provider operates. If you are in a jurisdiction that restricts transfers abroad, those transfers rely on appropriate safeguards, including the European Commission’s standard contractual clauses where they apply. Our Data Processing Addendum carries the transfer terms for business customers.
The Service is for business use by adults and is not directed to anyone under 18. We do not knowingly collect information from children. If you believe a child has provided us information, write to privacy@iatlas.live and we will delete it.
We may update this policy as the Service evolves. Every substantive change moves the version number shown at the top, and we keep a record of which version you agreed to, so it is always determinable what you were told and when. If a change is material, we will take reasonable steps to notify you before it takes effect. Continued use after a change means you accept the updated policy.
Privacy questions and requests: privacy@iatlas.live. Security reports: security@iatlas.live. Anything else: hello@iatlas.live.