Last updated: August 26, 2026
This policy covers roleplay.xl.net, operated by XL.net Inc., and every channel on which you can reach XL Roleplay Coach, our AI agent — web chat, SMS, email, and voice.
We believe transparency beats fine print, so here is everything this site does to understand its visitors — including the parts most sites leave out. All of it is first-party: we use no third-party analytics service, advertising network, or social-media tracker, and none of this data leaves our own server.
Conversations with XL Roleplay Coach — web chat, SMS, email, and voice — are processed by our AI systems and stored so the agent can answer you and we can review quality.
Every email XL Roleplay Coach sends is copied to a human at XL.net Inc., so an unsupervised AI is never our only record of what was said.
While you use the chat widget, XL Roleplay Coach can see the page you are on — its address, title, and visible text — so it can answer questions about what you are looking at. While the chat panel is open, it is also told short descriptions of elements you point at or text you select (for example, “the ‘Pricing’ heading”) so you can gesture at what you mean.
Nothing is captured while the chat is closed, form values and passwords are never read, and the widget shows a “Sees this page” indicator with an off switch whenever sharing is active. Shared page context is stored with the conversation like any other chat content.
If you report a problem through the chat, your report — including a short excerpt of the conversation and, when page sharing is on, a snapshot of the page you were viewing — is emailed to XL.net Inc. staff so a human can act on it. If you include a contact address, staff may use it to follow up. To review or erase a report, contact adam@xl.net.
XL Roleplay Coach keeps a private, per-person memory: facts you share and your conversation history, so later conversations can pick up where you left off. Your memory is visible only to you (and to XL.net Inc. staff reviewing quality) — never to other visitors — and XL Roleplay's own published knowledge always outranks remembered facts when they conflict.
If you sign in, we store your email address and display name (provided via Google OAuth or Microsoft OAuth, or an emailed sign-in link). This information is used only to authenticate you and personalize your experience. We never post on your behalf or access anything else in your provider account.
If you register a mobile number for text messaging, we also store that number, the date you verified it, and your opt-in consent record (see SMS / Text Messaging Data below).
Signed-in users can exercise both rights directly, without emailing anyone:
/api/account/export while signed in./api/account/delete, confirmed by typing your account email. This permanently erases your conversations, memories, and personal records, then removes the account itself, and returns an itemized count of what was erased.Deletion keeps the narrow records the law or basic security requires: SMS consent records, the deletion-audit record proving the erasure happened, security logs with the account link removed, and — where you have made purchases — financial records with your identity removed. If anything blocks a deletion (for example an active paid subscription), the request tells you exactly what to resolve first. Questions or problems with either right: adam@xl.net.
Essential cookies only. We set a single httpOnly session cookie (roleplay_session, 30 days) when you sign in, plus short-lived cookies during the sign-in handshake. A first-party cookie (roleplay_attrib) remembers the landing page, the site that referred you, any advertising click identifier in the address (gclid, msclkid, fbclid and similar), and campaign parameters of your first visit; it is read only by our own server. Your theme preference and interface choices are kept in your browser's localStorage, and the chat widget's conversation state in sessionStorage. If you listen to an article, your chosen playback speed and how far through that article you got are also kept in localStorage, so you can pick up where you left off; that stays on your device. None of this is sent to any third party.
Because we set no analytics or advertising cookies, there is no cookie consent banner — there is nothing to consent to. Blocking all cookies in your browser will prevent you from signing in but does not affect the rest of the site.
We share data only with services necessary to operate the site:
None of these providers receive your data for their own marketing purposes.
If you communicate with us via SMS, your mobile phone number and message contents are used solely to respond to your inquiry. Your mobile information will not be sold, rented, or shared with third parties or affiliates for their own marketing purposes. Mobile opt-in data and consent are not shared with any third parties except service providers that help us operate our messaging program, and those providers are restricted from using your information for any other purpose.
If you register your number with us, we record your opt-in consent (the consent language you agreed to, your IP address, and browser) and verify the number with a one-time code before it is added to your account. Message frequency varies based on your interactions with us. Message and data rates may apply. Text STOP to opt out at any time.
For full details on our text messaging program, see our SMS Terms & Conditions.
Upon a deletion request, all associated personal data is permanently removed within 30 days, except records we are legally required to keep (such as SMS consent logs).
We may update this Privacy Policy from time to time. Changes are effective when posted to this page, and the “Last updated” date above reflects the most recent revision. Your continued use of the site after changes are posted constitutes acceptance of the updated policy.
To object to any of this processing, request deletion of your account and associated data, or ask privacy questions, contact adam@xl.net.
This policy is generated from the site's actual configuration so it cannot drift from behavior. It reflects engineered defaults, not legal advice.
The sections above are generated from this site's configuration, including the line just above saying the policy is generated from configuration and cannot drift from behavior. That line is about those sections. This one is written by hand, because it covers the part the generator does not know about: the live video stage where you practice a sales conversation with an AI character, and the free live demo on our homepage. Read it together with the sections above, not instead of them.
What we do with your camera. When a roleplay runs in video mode, and during the free live demo, your browser takes still images from your webcam about twice a second and sends them to our server. These are ordinary photographs of you at your desk: your face, and whatever is behind you. Each one is shrunk so its longest edge is 384 pixels, which is for speed and bandwidth, not anonymity. Our server passes each image to Google's Gemini API and asks one question about it: what is this person doing right now. Google returns a short structured answer with seven fields and nothing else: whether you are in frame, whether you are looking at the lens, at your screen or away, whether your hands are at rest, raised or out of the picture, how many fingers you are holding up when you deliberately hold some up, a short phrase when something about you has changed since the previous image, for example “looked down at screen” or “stepped out of frame,” how confident it is in what it reports, and one short factual clause of about fifteen words describing what is plainly visible, such as clothing colors, a headset or a mug you are holding, and what is behind you.
Why we do it. So the AI character can behave like a person on a video call: notice when you step out of frame, answer honestly when you ask whether it can see you, and react when you gesture. In a practice session the same readings become the body-language part of your coaching debrief. The instructions we send with every image forbid any reading of age, gender, ethnicity, attractiveness, identity, grooming, health or mood, and forbid transcribing writing, logos or printed text that happens to be visible in the picture.
Where this happens, and that your camera is on by default. It applies to the two video practice modes, Run Meeting and Attend Meeting, and to the free live demo. It does not apply to the phone-call modes, Book Meeting and Answer Sales Call, where there is no video at all, or to Watch a Meeting, where both seats are played by the AI and nobody is on camera. In both places where it does apply, your camera is switched on for you, not by you.
We do not keep the images. We do not write them to disk, we do not put them in any database, and no image appears in any log. Our server holds an image in memory only until Google's answer comes back, and then it is gone. Ending the session leaves no camera stills behind on our side. Two things this sentence does not cover, both described below: our ordinary server logs do record the readings themselves, and your session recording is a separate thing that does contain your camera.
What the server logs keep. Our voice server writes ordinary operational log lines about the readings: whether you were in frame, where you were looking, where your hands were, a finger count, the short change phrase when there is one, and how long the call to Google took. Those lines carry no image and no description of your appearance: the fifteen-word visible-detail clause is stripped before anything is logged. We do not put a retention window on operational logs here, because we cannot honestly commit to one.
What we cannot tell you. We send each image to Google's Gemini API using an API key. What Google does with an image after that, including how long Google keeps it and whether Google may use it for anything of its own, is governed by Google's terms and is not something we can verify from our side. So we make no claim about it here. The paragraphs above are about our servers, and they are the part we can stand behind. If Google-side handling matters to you, keep the camera off.
Written descriptions of you can last, even though the pictures do not. This is the half a short on-screen notice cannot carry, so it is spelled out:
Session recordings. Separately from the camera reading, practice sessions are recorded. When the Video avatar switch is on, the recording is the side-by-side picture from the stage, the AI character on one side and your webcam on the other, with the audio of both; when that switch is off, the session is recorded as audio only, even if you turn your camera on by hand during it. The recording is stored as a file on our server and it is deleted automatically about 30 days after the session. Turning your camera off during a session does not stop the recording: it keeps running, and your side of the picture is blank for as long as the camera is off. The free live demo is not recorded: the server refuses the recording connection for demo callers.
Who can play a recording back. You can download your own recording from the session. Our own staff can review recordings, transcripts and debriefs for support and quality. And if your account sits under a company whose administrator we have promoted for your email domain, that administrator can play back the recordings, read the transcripts and read the debriefs of everyone in that domain, including yours. That is what the manager review feature is: if you are practicing on a company account, assume your manager can watch the video of your face.
How to turn it off. The camera button in the control bar under the stage switches your camera off at any point during a session, in the demo as well as in practice. With the camera off, no images are captured, nothing goes to Google, and the character stops being told what it can see. In a practice session you can also turn the Video avatar switch off before you start, so the camera never comes on in the first place and the recording is audio only.
How to have this removed. Email adam@xl.net to have any of it deleted, or to ask anything about this section. That is the route we can promise, because this site has no Delete button today: the deletion request described under Your Data Rights above is an API endpoint with no page or control wired to it yet. What deletion does reach when we run it for you: your practice sessions, your debriefs and your scores, including the body-language numbers stored with them. What it does not reach, and why the email matters: the turn-by-turn transcript of a practice session, and everything held for a demo, which has no account behind it at all. Both of those we remove by hand on request. Deleting an account does not delete recordings either. They go on the automatic sweep, up to about 30 days after the session, so tell us if you want one gone sooner.
How to read the sections above once a camera is involved. The sections above are generated for a site whose channels are text, email and audio. Most of what follows is a scoping note: those sentences are accurate for what they describe and simply do not describe the video stage. The last two are different. They are data-rights promises that the video stage does not keep, and they are the reason this list exists at all:
This section was added on August 26, 2026, the day the camera reading was switched on for every video session and for the live demo. Before that it ran only for administrator accounts with debug mode on.