A 41-year-old man logs on one Tuesday evening to an adults-only chatroulette. Neutral backdrop, soft lighting, clean audio: he has read everything there is to know about framing. His username, however, is the same one he has used on his video game account since 2009 — an invented word, unique in the world. A fortnight later, a stranger messages him on a model-making forum: "Was that you I ran into the other night?" Nobody hacked anything. All it took was pasting that username into a search engine.
Adult video chat is almost always discussed in terms of images: what you show, what you let people see behind you. This blog has already picked apart what your backdrop reveals without your knowledge and what your microphone lets slip. But the most common leak comes neither from the camera nor from the sound: it comes from the technical identity you drag around with you — a username, an email address, a browser, a payment method. Four layers that, taken separately, say nothing, and that, cross-referenced, lead to your real name in a matter of minutes.
This article explains how to compartmentalise those layers, what the regulations allow you to demand from platforms, and why the question becomes even trickier when you live with a partner. Nothing technical, nothing illegal, no explicit content.

The real mechanism: correlation, not intrusion
We tend to picture the loss of anonymity as a hack. In practice, it almost always works through cross-referencing publicly available elements. This is exactly what the CNIL describes under the term indirectly identifying data: an identifier that does not name you but which, combined with another, makes it possible to trace an actual person.
Three examples of cross-referencing, all perfectly mundane:
- The unique username. The more original a username is, the more identifying it becomes. "alex92" is lost in the crowd; "korvax_mandrel" exists in only one copy on the internet, and is probably tied elsewhere to a real first name.
- The email address. Many services, during a "forgot password" request, reveal a clue about the existing account. A personal address used for an 18+ service links the two worlds together in databases — including in the data breaches that end up in circulation.
- The profile picture. An image reused from a social network can be found through reverse image search. Even cropped, even in black and white.
The principle to remember: an identifier is not dangerous in itself. It becomes dangerous the moment it is reused. Compartmentalisation isn't about hiding; it's about preventing two completely unrelated contexts from being joined together.
Layer 1: the username
The username is the most visible piece and the most underestimated. A few simple rules:
- One username per context, never recycled. If it has already been used on a forum, a game, an online shop or an email address, it's burned.
- No date of birth, no city, no initials. "DM_Lyon84" hands over three pieces of information in twelve characters.
- No overly personal references. The name of your dog, of your favourite obscure band or of your home village is one more clue for someone who already knows you.
- Test it. Paste your future username into two or three search engines before adopting it. If it returns nothing, that's a good sign; if it returns you, change it.
Many people end up managing several identities of this kind and remember them poorly, which pushes them to recycle everything. A password manager solves that problem: it stores the username, associated address and password for each site, and removes the temptation of "always the same one, it's simpler". For those who prefer paper, a password notebook with a lock, kept in a closed drawer, remains acceptable — provided it isn't sitting on the desk, visible in the camera's field of view.
Layer 2: the email address
This is the pivot of any online identity: it is what allows a password to be reset, and therefore an account to be taken over.
| Practice | Level of compartmentalisation | Comment |
|---|---|---|
| Main address (firstname.lastname@) | None | Links the account directly to your legal identity |
| Old secondary address | Low | Often already tied to other services and to breaches |
| Address created specifically, with no real name | Good | The simplest and most durable solution |
| Alias or disposable address | Variable | Convenient, but you lose access if the alias expires |
The right move is a dedicated address, created solely for services of this kind, with no first name, no surname, and no recovery phone number shared with your main account. Two-factor authentication via an authenticator app rather than SMS also avoids tying in your phone number — which, in France, is linked to your identity at the operator.
Note carefully: creating a dedicated address is neither a workaround nor a fraud. It is minimisation, a principle enshrined in Article 5 of the GDPR: providing only the data necessary for the service's purpose. You are applying, on your own scale, what the regulations require of platforms.
Layer 3: the browser and the device
A browser is an involuntary address book. It keeps your history, your passwords, your open sessions, your autofill suggestions. And in a household, it is very often shared.
The most common leak points:
- Autocomplete. You type three letters in the address bar and the site appears — in front of your partner, your child or a colleague during a screen share.
- Sync across devices. A tab open on the computer shows up on the phone, and vice versa. That's a feature, not a bug: it can be turned off in the browser account settings.
- Accidental screen sharing. In a work video call, a visible bookmarks bar is enough.
- Desktop notifications. An incoming message displayed at the top of the screen while you're showing someone a spreadsheet.
The sensible answer comes down to three actions: a separate browser profile (or a different browser) dedicated to this use, with bookmarks and toolbar emptied and notifications disabled; a session closed after each use; and above all, no browser account synced with your main identity.
The same reasoning applies to hardware. If the computer is shared, create a separate user session on the system, protected by a password. A privacy screen filter limits viewing from the side if you live in an open-plan space, and an adhesive webcam cover removes any question of the camera being on outside a session — two accessories costing a few euros that solve very concrete problems. The INRS, in its guidance on screen-based work, also points out that a workstation set up facing a door or a thoroughfare is the worst possible choice in terms of both privacy and comfort.
Layer 4: payment, the best-documented leak
A platform can be perfectly anonymous right up to the moment you buy a paid option. Your bank statement, on the other hand, is anonymous to no one: not to the bank, and not to a partner who is a joint account holder.
Three things to check before any payment:
- The description that will appear on the statement. Reputable services state it in their FAQ or terms and conditions. Its absence is a bad sign.
- Whether the subscription is recurring. A monthly direct debit that renews automatically reappears twelve times a year on a shared statement.
- The third party collecting the money. The payment provider retains billing data, subject to accounting retention obligations — in France, ten years for supporting documents.
This question of funding was covered in detail in this blog's article on who really pays for a free 18+ chatroulette: advertising, paid options, data resale. The practical summary fits in one sentence: if you pay, you are no longer anonymous to the platform or to your bank — only to the people you talk to.
And what about age verification in all this?
This is the apparent contradiction of the subject: you're being told to compartmentalise, while the law requires 18+ platforms to verify your age.
The two are not in conflict, because the French framework has deliberately chosen a solution designed to prevent any joining of the dots. The technical framework issued by Arcom, adopted following the opinion of the CNIL (resolution of September 2024) and under the SREN law of 21 May 2024, imposes the principle of double anonymity: the platform knows you are an adult but does not know who you are; the verifier knows who you are but does not know which site you are visiting. The European Digital Services Act (DSA) and the UK's Online Safety Act, whose age verification provisions came into force in July 2025, move in the same direction, with different arrangements.
In other words: a properly designed age check is not a form where you upload your ID document directly to the site. If that's what you're being asked to do, it's a warning signal. This blog has detailed the journey your data takes in what happens to your ID document after the check and the criteria for spotting a trustworthy 18+ chatroulette.
For readers in Russia, Kazakhstan or Belarus, the reasoning is different but the instinct is the same: in an environment where signing up to online services is increasingly tied to a phone number — and therefore to a passport — identity compartmentalisation depends less on the tool than on choosing what you don't fill in. The effects of restrictions on messaging apps and video calls have been described here: throttled messaging apps, blocks and VPN rules.
The case of couples: compartmentalising without hiding
When two adults live together, compartmentalisation changes in nature. It is no longer about protecting yourself from a stranger, but about answering a far more concrete question: what is shared, and what is not?
Three configurations exist, and none of them is "the right one":
- Everything shared. A single account, a username for both, an address known to each. That makes sense when the activity is a joint one, as described in the article on couples who chat with other couples.
- Everything separate, but known. Each person has their own account, the other knows about it and has agreed to it. The framework exists, and the identities remain distinct.
- Separate and hidden. This is the most fragile configuration: it turns a technical problem into a trust problem, and the slightest forgotten open session becomes a crisis.
The difference between the last two isn't technical, it's conversational. The topic was covered in detail in when only one of you wants to try. A shared notebook in which you write down in black and white the rules both of you accept — what is allowed, what isn't, and during which hours — may seem trivial, but it heads off half of all misunderstandings.
The checklist, five minutes before your first session
To be done once, not before every login:
- A brand-new username, never used anywhere else, tested in a search engine.
- A dedicated email address, with no real name, and two-factor authentication via an app.
- A separate browser profile, with no sync, empty bookmarks and notifications switched off.
- A separate system session if the device is shared, protected by a password.
- No photo reused from a social network, and no file bearing your surname in a visible downloads folder.
- Payment: statement description checked, subscription not set to auto-renew, never from a joint account without agreement.
- Microphone and backdrop checked — see the two articles mentioned at the start.
One final point, often forgotten: know how to erase. Before deleting an account, request access to and erasure of your data; Articles 15 and 17 of the GDPR entitle you to do so, and the legal response deadline is one month. A platform that offers no way to delete an account is precisely the one you should have been wary of from the outset.
What compartmentalisation does not do
Let's be honest about the limits. Compartmentalising your identity does not protect you against a screenshot taken right in front of you — that point is covered in "18+" doesn't mean "no rules". It does not make your face anonymous, does not remove your IP address, and does not prevent a careless platform from losing its own databases.
Compartmentalisation does one thing only, and it does it well: it stops one context from contaminating another. It ensures that the stranger you met one Tuesday evening doesn't become the person messaging you on a model-making forum. That's a small thing, and it's the essential thing: most of the nasty surprises users recount don't come from a sophisticated attack, but from a username they never found the courage to change back in 2009.
To go further into the full set of privacy habits to adopt in front of the camera, the rest of the articles on the blog complete this framework layer by layer.



