Privacy Policy

This is version 1, not the current text.

Version 1· Effective November 6, 2026· First version

Back to the current text

This policy explains what personal data roomsφ collects, why, how long we keep it, who else sees it, and what you can do about it. It is written in plain English.

Who is responsible

The person responsible for your data (the "controller") is Chip, Dubai, United Arab Emirates.

Questions about privacy: anyaanyinyaa@gmail.com.

What we collect

  • From the service you sign in with: from Google your name, e-mail address and profile picture; from Telegram an account id, your name and profile picture; from Discord your Discord id and name. Telegram and Discord do not give us an e-mail address or phone number.
  • Your profile: display name, handle, a short bio if you write one, your birth year (to confirm you are 18 or older), your native and learning languages with levels, and your settings.
  • What you do in rooms: which rooms you joined and when you left, and your chat messages.
  • Your social graph: who you follow and who you block.
  • Reports you send and reports about you, with the chat messages attached as evidence.
  • Technical data: a keyed hash of your IP address (we never store the raw address), the time of your requests, and errors. We do not fingerprint your device.

We use no analytics service and no advertising trackers. There are no third-party cookies.

Sign-in data

roomsφ asks Google for exactly three scopes: openid, email and profile. That gives us your Google account id, your e-mail address, your name and your profile picture, and nothing else.

We use this data only to create and recognise your roomsφ account. We do not keep Google access or refresh tokens after sign-in, we do not read your Google contacts, calendar, Drive or mail, and we never ask for extra Google permissions.

Our use of data received from Google follows the Google API Services User Data Policy, including its Limited Use requirements.

If you sign in with Telegram, we ask only for your basic profile, never your phone number, and we do not send you messages through Telegram. If you sign in with Discord, we ask only for your basic profile, not your e-mail address or your servers. We use this data only to create and recognise your roomsφ account, and we do not keep Telegram or Discord tokens after sign-in.

How we use it

  • To run rooms: show who is in a room, pass your voice to the other people in it, and deliver chat messages.
  • To show your profile and your languages to other people, and to help friends find each other.
  • For safety and moderation: review reports, apply trust levels, warnings, restrictions, suspensions and bans, and detect people who come back after a ban.
  • To keep the service working: fix errors, prevent abuse and rate-limit automated use.
  • To meet legal duties, such as answering a lawful request from an authority.

We do not sell your data, we do not show ads, and we do not build advertising profiles.

Voice and recording

Your voice is relayed live from your browser to the other people in the room through our media server. It is never stored, transcribed or analysed by roomsφ. When you leave the room, nothing of your voice remains on our systems.

Other people in a room could record it with outside tools. Our Terms forbid this without everyone's consent, but we cannot technically prevent it. Please do not share sensitive details (your address, bank details, passwords, health information) in a room.

Cookies and storage

roomsφ uses only what the service needs:

  • a session cookie that keeps you signed in;
  • a few values in your browser's local storage: your light or dark theme, dismissed notices, your audio device choice and voice-processing switches, your room panel preferences, your lobby filters, and the recent picks of the quick switcher;
  • your browser's session storage, cleared when the tab closes: an onboarding draft and unsent chat drafts.

Nothing in this list tracks you across other websites, and there are no analytics or advertising cookies. That is why roomsφ shows no cookie consent banner. If we ever add something beyond what the service needs, we will ask first and update this page.

Who else sees your data

  • Other users see your display name, handle, picture, bio, languages and badges, and what you write in a room's chat. Friends can see which room you are in, depending on your privacy settings.
  • Our hosting provider, LoW, in Indonesia,, stores the database and runs the servers for us.
  • Our media server (LiveKit, run on our own servers) relays your voice live; it does not store it.
  • Google, Telegram and Discord provide sign-in, under their own privacy policies. Profile pictures from Google and Telegram load from their servers.
  • Our staff (moderators and admins) see reports and the evidence attached to them, and your profile, when they handle a report or a support request. Every staff action is logged.

We share data with authorities only when the law requires it. We do not sell or rent personal data to anyone.

Where data is stored

Our servers are in Indonesia, and roomsφ is run from the United Arab Emirates. If you use roomsφ from another country, your data is transferred to Indonesia, and the people who run roomsφ access it from the United Arab Emirates.

Where the law of your country requires safeguards for such a transfer, we rely on the measures described in this policy: data travels only over encrypted connections, IP addresses are stored only as keyed hashes, and access to the servers is limited to the people who run roomsφ.

How long we keep it

  • Your account and profile: until you delete your account.
  • Chat messages: 90 days, then deleted. Messages attached to a report: until the report is closed plus 180 days.
  • Room history (which rooms you joined and when): kept while your account exists; shown to you as recent people.
  • IP hashes: 30 days after they were last seen.
  • Media server events (join and leave signals): 7 days.
  • Notifications: 60 days.
  • Reports and sanctions about an account: kept after the account is deleted, so that a banned person cannot simply start again; we delete them when they are no longer needed for that.
  • Staff audit log: kept for as long as the service runs, to show how moderation decisions were made.
  • After you delete your account, your profile is replaced by "Deleted user", your e-mail and name are removed, and the same Google account can start fresh later.

Your rights

You can:

  • see and export your data: write to us at the contact e-mail below and we will send you a file, within 30 days, with your profile and settings, your languages, the people you follow, the people you blocked, your word list, your own chat messages from the last 90 days and your room sessions;
  • correct your data: edit your profile and languages in Settings at any time;
  • delete your account: Settings › Delete account;
  • object to or restrict a use of your data, or ask for a copy of data not covered by the export, by writing to anyaanyinyaa@gmail.com.

We answer requests within 30 days. If we need to confirm that a request really comes from you, we may ask you to sign in or to write from the e-mail address of your account.

Children

roomsφ is not for anyone under 18. We do not knowingly collect data from children. If we learn that an account belongs to someone under 18, we close it and delete the data we hold about that person as soon as we can. If you believe a child is using roomsφ, tell us at anyaanyinyaa@gmail.com.

If you are in Indonesia

Under Indonesia's Personal Data Protection Law (Law No. 27 of 2022, UU PDP) you have the right to know how your data is processed, to access and correct it, to have it deleted, to withdraw consent and to object to decisions made only by automated means.

Our servers are in Indonesia. roomsφ is run from the United Arab Emirates, so the people who run it access your data from there, with the safeguards described under "Where data is stored".

Changes to this policy

When this policy changes, the new version is published here with its date. Every version and a short summary of what changed is listed at Change history. For a material change we post the new version with its effective date at Change history at least 14 days before it applies.