Account and billing
Privacy and analytics
What we store, what we measure, and how to turn the measuring off.
This page describes what RTLBridge stores, what it measures, and what you can switch off. It is a plain-language summary of behaviour, not a legal document; the terms and privacy policy remain the authority.
What is stored
| Data | Why it exists |
|---|---|
| Your account details | Email, a password hash, and your generated username. |
| Your chats | Specifications, follow-ups and the generated files, so a chat can be reopened later. |
| Uploaded project workspaces | Held while you work in them and then cleaned up; see Limits and retention. |
| Billing records | Charges, credits and reservations. These survive deleting a chat, because they are financial records. |
| Run statistics | Token counts and costs, used for our own capacity and pricing work. |
What a run can see
Your request, your coding style, the earlier turns in that chat, and in project mode the files you uploaded. Everything beyond that is opt-in through the tool switches; a run with all tools off reaches nothing outside your own words.
Generation happens through model providers, so the text of your request is sent to the provider serving the model you selected. Do not paste anything into a specification that you would not send to a third-party service.
Analytics and session replay
We collect product analytics and session replays to see where the interface confuses people. Replays are fully masked: text you type is not captured as text. The switch in Settings turns future collection off for your account.
Note
Disabling analytics changes nothing about how runs behave, what they cost, or what you can access. It only stops the measurement.
Deleting your data
- A chat. Delete it from the sidebar; the conversation and its generated files go with it.
- A project workspace. Discard it from the upload panel, or delete the chat that owns it. Unused workspaces are removed automatically.
- Your account. Contact support; see Support.
Who else can see your work
Nobody, unless you create a share link. Chats are private to your account, and a share link is the only way to expose one. There is no team-wide visibility and no cross-account access.