Privacy

Researchers once counted 223 trackers in a single minute inside a competing companion app, and twenty undisclosed advertising SDKs — none of them disclosed to the people being tracked. This page exists so you can check what we do, including what would change if we ever show ads.

This is the short version, and it is the one to read. The privacy notice is the long one: every category of data, the lawful basis for each, retention periods, the full list of who else touches it, and the rights that apply where you live.

YanMate is run by Galaxyway AI Ltd, a company registered in England and Wales, which is the controller of your personal data. Its company number and registered office are in the privacy notice.

Advertising, plainly

We do not show ads today. No advertising code is loaded on any page, on any plan, for anyone. Nothing on this site sends anything to an ad network, and there is no ad slot rendered anywhere — not an empty one, not a hidden one.

We are being straight about the plan rather than waiting: the intention is that a free tier is eventually paid for by advertising, and paid plans never are. That is the reason a free tier exists at all rather than a fourteen-day trial. The ads will come from Google AdSense, and the arrangement below is written now so you can read it before any of it happens:

• If you are on Free, whether you are browsing anonymously or using an account, we would serve ads through Google AdSense. They would load only after you consent, personalisation would be off unless you turn it on, and we respect Global Privacy Control.
• Ads would appear only on pages you browse — never in a chat, a call, a scene, your memory or your inbox.
• If you are on Plus or Deep, the ad code never loads. Not muted, not hidden — not loaded.
• Your conversations are never used for advertising, ever, on any plan. Nothing you say to a companion would reach an advertiser, an ad network, or a targeting profile. Ads would be chosen from the page you are on and from whatever Google already knows about your browser, and we would not add to that.
• We would tell Google your age bracket only to restrict what you are shown, never to target you with it. If you are under the age of consent where you live, personalised advertising is switched off and cannot be switched on.

Google's advertising cookies

When ads are running, this is what Google AdSense does, in the words it asks every publisher to use:

• Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites.
• Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and/or other sites on the Internet.
• You can opt out of personalised advertising in Google's Ads Settings. You can also opt out of some other vendors' use of cookies for personalised advertising at aboutads.info.
• How Google uses information from sites that show its ads is explained in Google's own policy.

In the UK, the EEA and Switzerland, Google's consent message asks you first, and "Do not consent" is a button on the first screen rather than a setting to go looking for. Refusing still gets you the product; it gets you ads that are not personalised, or none. The cookie policy lists what these cookies are.

What we don't do

• We never train models on your conversations. One provider's terms go further than ours: when a reply is read aloud — you play it, you call, or voice notes are on (the default on Deep) — its text goes to Fish Audio to be spoken, and Fish's terms let it use text it receives to develop and train its own models. Your own messages and your voice never go to Fish. Who else sees it has the details.
• We never sell your personal information, and we never share it for cross-context behavioural advertising.
• We do not build a profile of you from your conversations for any purpose, including our own recommendations.

What we store

• Your account: email, name, and the state of your plan.
• Your characters and companions: exactly what you wrote.
• Your conversations: kept per companion so your companion can remember them. They are yours; you can read, export, or destroy all of them.
• Your Memory Ledger: the facts your companion has learned, visible and editable by you, with an audit trail of every change.
• Your age, coarsely: the birth year you tell us when you create an account — not a full date, because we never need the day. It is asked before the account exists; if it is below the minimum where you live, no account is made and we save nothing. If an existing account's year is refused, we keep only the fact that you were turned away, and delete the year itself.
• Age eligibility: today we use only the birth year described above. We do not ask for an identity document, selfie, or biometric template. If a future age-assurance method requires a vendor, this policy must be updated before it is enabled.
• Moderation records: the rule that fired, the surface, and a hash of what was checked. Never the content itself.

Where the words actually go

Every model in this product runs on Cloudflare. Your companion's replies, the safety classifiers, the transcription of a voice note, the embeddings behind memory — all of it is Workers AI, inside the same platform the app runs on. There is no call to OpenAI, Anthropic, Google or anyone else with your conversation in it.

The one exception is speech, and it is worth naming. When a message is spoken aloud — a voice note, or a live call — the text of that reply goes to Fish Audio, who turn it into audio. They receive the words being spoken and nothing about your account. Nobody else in this product receives your text at all.

Analytics

We measure how the product is used and what an interaction costs us to serve. We do not build advertising profiles from it, we never sell it, and nothing you say to a companion is in it.

In your browser, the cookie waits for your yes. The first time you visit, we ask. If you accept, PostHog sets one cookie holding a random visitor id, and records the pages you open, what you click, and the country your IP address points to. When you are signed in it is linked to your account number, so we can see which features actually get used.

If you decline — and until you answer — nothing is stored on your device, but PostHog still records the pages you open and what you click, anonymously. There is no visitor id, no account number and no country. A visit is held together only by a one-way code worked out on PostHog's servers from your IP address, your browser and a key that changes every day, so it cannot be linked to a visit on another day, and it is never linked to you. If your browser sends Global Privacy Control, we treat that as a decline and do not ask. If you are under the age of digital consent where you live, we treat your answer as a decline too. You can change your answer at any time under Cookie settings.

Either way, on a chat, call, scene, memory or inbox screen only the fact that the page was opened is recorded — never a click. Everywhere else a click is recorded by what was pressed, never by the words on it: no text from any page reaches analytics. There is no session recording.

Your IP address reaches PostHog so a visit can be counted and, if you accepted, placed in a country. PostHog is set to discard it rather than keep it with the event.

Page-view counts come from Cloudflare Web Analytics. Cloudflare already runs this site (it is listed in the privacy notice), and it adds a small script to each page that reports which page loaded, the site that sent you, how fast the page was, and your kind of browser and device. It sets no cookie, stores nothing on your device, and gives us totals rather than a record of you. A content blocker stops it, and nothing breaks when it does.

Some measurement happens on our servers. Cost and usage events are recorded from requests you already made, and carry an internal account number rather than anything about your machine. Your IP address is not part of them, and no banner answer changes them.

PostHog runs on its EU cloud, so the measurement stays inside Europe and leaves the EEA for nobody. PostHog is a third party — we are not pretending otherwise, and they are listed as one in the privacy notice — but the region is the part that decides who else's law your usage data passes under, and the answer is nobody's but ours and theirs.

This was not always true. Analytics ran on their US cloud until 25 August 2026, and a still earlier version of this page described it as "self-hosted or EU-hosted" when it was neither. Both are fixed rather than quietly reworded, and the sentence you are reading is here because a page that only ever described its best state would not be worth checking.

If you want your account left out of the server-side measurement as well, ask — your privacy choices explains how and why that is a right rather than a setting.

Export and deletion

Both are self-serve, on your account page, and neither is behind a plan.

• Export gives you one JSON file with everything: characters, companions, every transcript, the whole Ledger, and your billing history. It works on a lapsed account and on an account under moderation review.
• Delete is a hard delete, immediately. Every character, conversation, memory, uploaded image, and the per-account vector namespace is destroyed — not deactivated. There is no recovery window, and we cannot undo it for you.

The one thing that outlives a deletion is the moderation and safety log, and it survives with your user id removed: what remains is a rule name, a timestamp, and a hash, linked to nobody. We are required to keep those counts; we are not required to keep them attached to you.

Your rights

Access, portability, correction, and erasure are all self-serve above, which is faster than emailing us. If you want something we haven't built a button for, ask.