Privacy

What we hold, who else sees it, and how to get it back.

Delphi Monitor measures brands rather than people, so most of what it stores is about companies and public web pages. This page says exactly what the exceptions are. It covers Delphi Monitor, operated by Phantasm and Brain, and was last changed 21 October 2026.

What we hold about you

Five things, and whatever you send when you write to us. Delphi Partners keeps a little more, set out in its own section below. Everything else in the product is about brands, not about people.

Your name: So a colleague can see who invited them, and who is in the account.
Your email address: It is how you sign in, how a password is reset, and where a measurement lands.
A one-way hash of your password: So a password can be checked without anybody, including us, being able to read it.
Which organisation you belong to, and your role in it: It decides what you can see and whether you can spend the organisation's money.
When you signed in, and when a founder or a partner you gave access entered the account: So anybody opening your account leaves a record that you could be shown.

If you write to us through the contact form, we keep what you send: your name and work email, your company or website and how many brands you would measure if you give them, what your message is about, your question, where you heard about us with any detail you add, and which of our own links brought you to the form, if one did. It is stored with the time it arrived and emailed to our own inbox so a person can reply. An older demo request form, which nothing on the site links to now, keeps your name, work email, the brand, the market and any note in the same way.

We do not hold your card. The payment page is Stripe’s own and the card number never reaches us. We do not buy lists, we do not enrich your record from anywhere else, and we do not build a profile of you.

What we hold about your business

This is the bulk of it, and almost none of it is personal data.

The brands you measure: Name, website, category and market. You give these during onboarding and can edit them.
The questions put to the assistants: Drafted for your category, then edited by you. They are the measurement.
The rivals you are measured against: Name and website. Public companies, named by you or proposed and then kept or removed.
What each assistant answered, word for word: It is the evidence behind every figure. Without it a score is an assertion.
What was read from your public website: Delphi identifies itself when it fetches, obeys robots.txt, and reports a refusal as a finding rather than working around it.

One rule shapes all of it: nothing in a measurement is designed to hold personal data. Delphi asks assistants what they recommend to a buyer, and it does not know or ask who any buyer is. If you type something personal into a question or a brand name, it is stored because you typed it, so please do not.

Delphi Partners

If you apply to be a partner, work for one, or let one into your account.

An application: Your name, work email, company, company website, country, how many brands you work with if you say, when you applied and the IP address the application came from. We use it to decide on the application and, if it is approved, to run the partner account and pay the partner. Most applications are decided automatically: we check that the email is on the website's domain and is not a free or disposable mailbox, that the domain has web or mail records, and whether the email or the website belongs to a Delphi customer or a Delphi partner. Each automatic decision is emailed to you, a decline with its reason, and a reply reaches a person who can review it. A person decides an application from an address on Delphi's own domains, from the address of a member of a partner whose agreement Delphi ended for breach, from an address or a domain Delphi declined before, or on the domain of a partner that has ended.
Accepting the partner agreement: Which version was accepted, by whom, when and from which IP address, so either side can show what was agreed.
A partner's tax details: The legal name, whether the partner is an individual or a business, the address and, in Canada, the Business Number and GST/HST number. They are used only for the partner's statements and the tax slips the law requires. We do not hold a Social Insurance Number: if a Canadian partner with no Business Number is paid more than CA$500 in a year, we ask for it then, for the tax slip Canadian law requires.
Visits to a client's account: When somebody from a partner's team opens a client's account, the client sees their name and when they entered and left.
Referral fees: Which clients a partner referred, the referral fee on each of their payments, and every transfer. Stripe pays the partner and holds its identity and bank details; we keep only the id of its Stripe account.

A client that joins through a partner chooses what the partner may do in its account: View only, View and edit, or No access. View only shows the partner the measurements, questions, rivals and Plan; View and edit also lets it change questions and rivals, change the status of work on the Plan, confirm the business type, which decides what is measured, and start measurements, the monthly one included, that use the client’s allowance. The client can change this at any time in Settings, under Partner, where the latest visits are shown, and we send the full list on request.

A partner never sees a client’s invoices, card, payment details, team names or emails. It sees the client’s level, whether it is paying, and its own referral fees, which follow what the client paid, refunded or disputed. Delphi pays the partner a referral fee on what the client pays, and the client is told so, and agrees, before it joins.

Who else sees it

Every company that receives any part of your data, what it does for us, and what it gets.

OpenAI: One of the assistants a question is put to. The buying questions in a workspace and the market they are asked in. No name, address or account detail.
Anthropic: One of the assistants, and the model that reads the answers back and labels what each one said. The buying questions, and the answers every assistant gave, so they can be read and classified.
Google: The assistants Gemini and Google Overview, Google Analytics and Google Ads, which count visits to our public pages and which of our adverts lead to a purchase, and YouTube, which plays the videos on the product demo page. The buying questions in a workspace and the market they are asked in, Google Overview's through SerpApi. For a public page, and only once the visitor has allowed it, Google Analytics also receives the address of that page, the site or search that linked to it, the browser, device and place it was opened in, and what was done on it. It never receives a signed-in page, a sign-in page or a link we emailed. After a plan is paid for, and only where the buyer allowed it, Google Ads receives that a purchase happened, with the amount, the currency, an order reference and the buyer's email address as a SHA-256 hash for matching, and no name or card detail. YouTube receives nothing until a visitor presses play on a video; from then its player is YouTube's own.
Microsoft: One of the assistants, as Copilot. The buying questions in a workspace, through SerpApi.
Perplexity: One of the assistants. The buying questions in a workspace and the market they are asked in.
xAI: One of the assistants. The buying questions in a workspace and the market they are asked in.
SerpApi: Collects the answers of Google Overview and Copilot on Delphi's behalf. The buying questions in a workspace, and the market they are asked in for a Google Overview search.
Supabase: The database everything is stored in. Everything the account holds.
Vercel: Hosting, and the cookieless count of visits to our public pages. Every page and every request passes through it. Requests, and the server logs they produce. For a public page it also receives the address of that page with anything after the question mark removed, the site or search that linked to it, and the country and browser it was opened in. It never receives a signed-in page.
Stripe: Taking payment, holding the card, and paying Delphi partners their referral fees. The billing name, address and card. Delphi never sees or stores a card number: the payment page is Stripe's own. For a partner, the identity, bank account and tax details Stripe asks for to pay it.
Resend: Sending the email this product sends. The address a message goes to, and what it says.
Inngest: Running a measurement in the background so a browser is not holding it open. The identifiers of a run, never its content.
Cloudflare: Telling a person from a script on the sign-up, forgotten password and Delphi Partners application forms, through the Turnstile check. A one-time token from the form. No account data.

That list is the whole of it, and when an integration is removed its row goes with it. We do not sell your data and we do not share it with advertisers. The one thing an advertising service receives is Google learning that a purchase followed one of our own adverts, with the buyer’s email address in scrambled form so it can match the two, and only where you allowed it, as the cookies section below says. What Delphi learns across accounts, and the rules that bound it, is the next section.

The assistants are asked your buying questions. Neither they nor the companies that collect an answer on our behalf are sent your name, your address, your account or anything about the people in it. Their own terms govern what they do with a prompt, and those terms are published by each of them.

What we learn across accounts

Delphi is a measurement product, so what it knows about how the assistants behave grows as more brands are measured. Four rules bound that, and each one is enforced in code rather than promised.

No customer, brand or category is ever named: A finding is a count or a share. The queries behind them return numbers and third-party publishers, and a domain belonging to any measured brand is excluded from every list that names one.
Nothing is reported from fewer than three independent companies: Below that floor the answer is that there is not enough to say. A pattern drawn from one or two companies is that company's data wearing a lab coat, and a reader cannot tell it from a real finding.
Nothing another account did can change your score: Your Delphi Index is computed from your own measurement alone. It would be indefensible for a score to move because a stranger signed up, so there is no code path from a cohort reading to any figure of yours.
What we publish is about the assistants, not about you: Published research answers how the assistants behave: how often one repeats itself, how much they disagree, how many brands they will name. Those need no customer identified and none is.

The cohort reading on your Claims page is this working for you rather than on you: it is how you find out which sources the assistants keep reaching for in your kind of business, which no single measurement can show. The same floor applies to it. Where fewer than three independent companies have been measured on the same footing, it says there is not enough to say rather than showing you a number computed from one.

Where we publish a finding, it is about the assistants rather than about any brand, and it carries the number of measurements behind it inside the sentence so it cannot be quoted without its own denominator.

Cookies, and what we count

A sign-in cookie: One cookie keeps you signed in. Without it you would sign in again on every page.
A partner's working cookie: When somebody from a partner’s team opens a client’s account, one more cookie holds that visit, for 8 hours at most. Nobody else is ever given it.
A check on three forms: Sign-up, the forgotten password form and the Delphi Partners application ask Cloudflare Turnstile to tell a person from a script, which may set its own cookie in the process. It is a fraud check and nothing else.
A count of visits to our public pages: We keep a running count of how many times each of our public pages is served, and, the same way, how many times the sign-up, account setup and payment pages are opened and a payment is started. A row is the name of the page, the hour it happened in, and one mark saying whether the request called itself a crawler. Nothing else is kept: no cookie is set or read for it, no address, no browser details, no account and no brand. The time is deliberately blunt, to the hour rather than the instant, so that a row is one of many in that hour rather than a moment we could line up against anything else. It counts requests rather than readers, and it can never tell us who visited.
What is used inside your account: Inside a signed-in account we record which pages of the product are opened, which panels are expanded and which controls are pressed. A row is the brand it happened in, the page, what was opened or pressed as it is labelled on screen, and when. We keep this so we can see which parts of the product are worth building on and which are not being used, and so we can tell that a measurement somebody paid for has not been looked at.

It records the brand and not the person. There is no name, no address, no device and nothing that separates one colleague from another, so it can tell us that a page was opened and never which of you opened it. No cookie is set or read for it beyond the one that keeps you signed in. It covers the product only: nothing you type, no question you write and no answer we measure is part of it.
Where a visit to our public pages came from: On our public pages we also record the site or search that linked you to us, along with the country you opened the page in and the kind of browser and device you used. We keep this so we can tell which of the places we write and appear actually sends anyone.

No cookie is set or read for it and your address is not kept. Anything a link carries after the question mark is removed before the page address is recorded, so a link sent to you privately cannot travel with it. It covers our public pages only and is never switched on inside a signed-in account.
Google Analytics and Google Ads on our public pages: Separately, our public pages run Google Analytics, so we can see how people find us and what they read, and Google Ads measurement, so we can see which of our adverts on Google lead to a purchase. It records the page you opened, the site or search that sent you, the country and city your connection is in, your browser and device, and what you do on the page, such as how far you scroll, which links you follow to other sites and whether you start or send a form, but never what you type into one. Google works out the place from your connection’s address and says it does not keep the address.

Both run only if you allow them, when the small question at the bottom of the screen asks, and nothing of either loads until you do. If you allow them, Google Analytics sets two cookies, _ga and _ga_G74X1JGPE5, to tell a browser that has been here before from a new one, and they last two years from your most recent visit. Google Ads measurement sets _gcl_au, and _gcl_aw when you arrived by clicking one of our adverts on Google, to remember that click, and they last ninety days. Only this site can read these four cookies. Google receives the page address as your browser shows it, including anything a link added after the question mark, such as the label an assistant or a newsletter adds to say where a reader came from.

Your answer is kept in your browser for six months, so you are not asked on every page, and then you are asked again. You can change it at any time with Cookie choices at the foot of any page. Saying no stops both at once and deletes all four cookies.

They never run inside a signed-in account, on the sign-in and sign-up pages, or on the links we email to confirm an address, reset a password, join a team or make a partner login, or on an invitation link a partner sends, and they switch off as soon as you move to one of them. There is one exception, and it sends one thing: when you have paid for a plan and allowed these cookies, the page you pass through on the way back from payment tells Google that a purchase happened, with the amount paid, the currency and an order reference, so Google can match it to an advert you clicked. To make that match, it also sends the email address you paid with in a scrambled form: it is put through a one-way function, SHA-256, before it leaves our server, so Google receives a code rather than the address, and can only compare that code with the accounts it already holds. This is Google Ads’ enhanced conversions. It sends no name and no card detail, and the address Google receives for that page is /checkout/complete with nothing after it.

Both are set so that nothing they record is used to choose which adverts you see, here or anywhere else, or for Google’s reports on visitors’ age, gender and interests. Google explains what it does with what it receives in how Google uses information from sites that use its services, and Google’s opt-out add-on switches Google Analytics off in your browser on every site.
Videos on the product demo page: The product demo page shows videos hosted on YouTube. Before you press play, each one is a picture stored on our own site, and nothing is loaded from YouTube. Pressing play loads YouTube’s player from youtube-nocookie.com. Without JavaScript, or if you open a video in a new tab or window, the press takes you to the video on YouTube itself. Either way, from then YouTube’s own privacy policy applies, including anything YouTube stores in your browser.
Nothing that follows you across the web: Nothing here is used to choose which adverts you see, and unless you allow Google’s cookies or press play on a video, nothing here could recognise you on another company’s website. Nothing above stores or reads anything on your device except the sign-in cookie, a partner’s working cookie, the fraud check, your answer about Google’s cookies, those four cookies if you allow them, and YouTube once you press play. The first three are necessary for the thing you asked for. Only this site can read your answer and the four Google cookies; what Google itself keeps from the visits and the purchase it receives is covered by Google’s policy linked above, and YouTube’s policy covers what YouTube stores.

How long we keep it

While you have an account: Everything, and deliberately. A measurement is only useful next to the ones before it, so nothing is thinned out or aged away. If you cancel, we keep it: the account drops to the free level, every past measurement stays readable, and resubscribing puts you back where you were rather than starting you again.
When you ask us to delete it: We delete it. See below.
Diagnostic logs: Server logs are held by our hosting for a short window and are used to work out why something broke. They are not a copy of your account.
An application that is not approved: Its name, email and IP address are removed after 12 months.
A waitlisted application: Kept until Delphi can pay partners where the applicant is, or for 24 months, then its name, email and IP address are removed.
A client's email on an invitation: Removed 30 days after the invitation expires or is withdrawn.
Visits, consents and acceptances: Kept while the referral lasts or referral fees are still paid on it, and for at least 6 years after, as the record of what was agreed and who entered an account.
Tax details and payment records: Kept for at least 6 years after the end of the tax year they relate to, as Canadian tax law requires.

Your rights

See it: Every workspace exports as CSV and as a document from inside the product, at any level, at any time, including after a cancellation. If you want the whole account in one go, ask and we will send it.
Correct it: Your name, the brands, the questions and the rivals are all editable in the product. For anything else, write to us.
Delete it: Write to contact@delphimonitor.com from the address on the account. We remove the account, the organisation, its workspaces and every measurement taken for it. We keep only what the law requires or what proves what was agreed: payment and tax records, and, where a partner referred you or you are a partner, the consent, acceptance, visit and referral fee records, for as long as the section on how long we keep it says. We will confirm when it is done. Export anything you want first, because after this there is nothing to send you.
Object, or take it elsewhere: Tell us and we will stop. The export above is a machine-readable copy you can take to anybody.
How long we take: We aim to answer within a few days and will not take longer than a month. There is no charge.

Security

Passwords: Stored as a one-way hash, so nobody at Phantasm and Brain can read yours, and neither could anyone who obtained the database.
Separation: Every read of your data is scoped by your membership of your organisation, and no other customer can reach your workspace. Nobody outside it does, except in two ways: the founder of Phantasm and Brain may enter an account to help with it, and every entry is recorded and kept, so ask and we will show you the record; and a partner you gave access to, which you can see and remove in Settings at any time.
The database: Encrypted at rest and in transit by our hosting, and not reachable from a browser: the data interface our database provider offers is switched off, and the application talks to it directly.
If something goes wrong: If we ever hold a breach affecting your data, we will tell you what happened, what it touched and what we did, without waiting to be asked.

The rest

Where it is processed: The companies listed above operate internationally, so your data is processed outside the country you are in. Each of them publishes the safeguards they use for that.
Children: Delphi Monitor is sold to companies and is not for anybody under 18.
Changes: If we change how we handle your data in a way that matters, we will email everyone with an account before it takes effect. The date at the top says when this last changed.
Ask us anything: contact@delphimonitor.com. A person reads it. The terms and the refunds page cover the commercial side.