RadioChat

Privacy Policy

Last updated 4 November 2026 · Version 2026-11-04 · Vikhanden Pty Ltd, Brisbane, Australia · hello@radiochat.ai

Who we are

RadioChat is a chat app — stations (group chats, some with a shared board or notebook), friends and direct messages — run by Vikhanden Pty Ltd (ABN 32 672 072 758), Brisbane, Australia. This policy explains what we collect, why, and what you can do about it. Contact: hello@radiochat.ai.

If you use Sign in with Google, Google Drive or Google Calendar, the sections "Google user data", "How we share, transfer and disclose Google user data" and "How we protect your data (including sensitive data)" below explain exactly what we do with that data. If you use the Mail app (Gmail), the section "Gmail (the Mail app)" explains it: your mail stays on your device. A plain-language overview of the app and why it asks for each Google permission is at https://radiochat.ai/about.

What we collect and store on our servers

• Your Google account, when you sign in with Google: its unique id, email address (and whether Google has verified it) and name. We use them to sign you in and keep your account; your name becomes the nickname your friends see. Strangers see a separate public name, not your Google name or email.
• Visitors to published pages and service desks, if you sign in on one without a RadioChat account: see "Visiting a published page or a service desk" below.
• Your month and year of birth, to check you're old enough when you create an account. It's never shown to anyone.
• Your profile: nicknames, status message, and anything you choose to add (age range, country, interests).
• Your contact card: if you set one up (Settings → Account → Contact card), the photo you add (cropped and shrunk on your device to 300 × 300 pixels) and the name, titles and bios you write. We keep them on our servers with your account. For each part you choose who sees it — your contacts, members of your organisation, people in non-public stations, people in public stations — and we show each person only the parts you chose for them. Your card's emails are your confirmed email and your organisation's verified email, and they're hidden unless you tick them. Change or remove your card or photo any time; both are deleted with your account.
• Other sign-in methods: passkey public keys, a hashed password (only if you set one), a confirmed email, and a list of your signed-in devices labelled by browser and system (for example "Chrome on Windows").
• Your friends list and what you post: messages in stations and friend chats, station boards and notebooks, polls and drawings — so conversations are there when you come back. Older messages are removed when a conversation reaches its storage limit. Messages are encrypted on their way to and from our servers, and our servers can decrypt them (that's how your chats reach every device, how a station keeps its history and how your AIs can work while you're away). People at Vikhanden don't read your messages unless one is reported to us or the law requires it.
• Synced notebooks and AI setup, if you turn on sync: your notebooks, personas and AI settings (and your AI API keys, only if you choose to sync them), encrypted on your device before they're sent. Half of the key stays in your Google Drive and half with us. Because we keep your Google Drive connected (see below) so that sync turns on by itself on your devices, we could technically open what you sync. We don't: we only store it and pass it between your devices.
• Your Google connections, if you connect Google Drive or Google Calendar: an encrypted, revocable link to each (see "Google user data" below), with that Google account's id, email address and name, and which service it's for.
• Your organisations, if you add one: when you verify a Google Workspace account to join your organisation in RadioChat, its domain (for example acme.com), that Google account's id and email address, and when you verified it. Other members of the organisation see only the domain — never that email address.
• Your desktop profile: how your RadioChat is laid out and set up — desktop shortcuts, the order and groups of your friends and notebook lists, browser favourites, which Google accounts' calendars you've connected (their addresses, never a sign-in), and your theme and sound choices — so they follow you to every device. We keep it with your account, unencrypted, and delete it with your account.
• Chat archives you keep on RadioChat, if you use Archive chat on a direct chat with "Keep it on RadioChat" on (saved accounts only): the archive of that chat's messages, with a name for the chat (for example "Chat with Bea"), when you made it, its size, the dates of its first and last message and how many messages it holds. Each archive adds only what's new since the last one. A readable archive is stored as it is, so we could technically read it; we don't. One you protect with a password is sealed on your device before it's sent, so we store only the sealed file and can't open it — we never see the password and can't recover it. Only you can list, restore or delete your archives (Sync & Data → Your data → Restore), and they're limited to 100 MB for an account.
• Files you share in a chat: a share record — the file's name, type and size, its Google Drive id and link, and which chat it was shared in. The file itself stays in your Google Drive (see below).
• Reports and moderation records, if you report someone or are reported.
• Support messages you send from Help & Support, delivered to us by email.
• Short-lived security records: one-time codes and pairing codes, which expire within minutes to days.
• Invites: your personal invite link, kept until you reset it or delete your account. Invite emails are sent only to addresses you type in or pick from your phone's contacts, and contain only the name you choose, one of your own verified email addresses that you pick, and your invite link — the person you invite sees that address and can reply to it. You can only send an invite from an address we've verified is yours. We keep an invited address only as a one-way hash, for 30 days, so the same address isn't invited again — never the address itself, and nothing else from your contacts. People you text from your phone get your link in a message you send yourself.
• "Let people who know my email find me" is off unless you turn it on. When it's on, someone who invites your confirmed email address sends you a friend request in RadioChat instead of an email, showing the name and email address they chose to send it from; they never see your address or learn that you have an account.

Visiting a published page or a service desk

Pages published through RadioChat, and organisations' service desks (a chat window on the organisation's own website), can be used without a RadioChat account. The full visitor notice is at https://api.radiochat.ai/visitor/privacy; in short:

• Before you sign in you're anonymous. A service desk keeps your conversation with its AIs and members in a temporary visitor account tied to that browser and that website, so a conversation on one website is separate from one on another.
• If you sign in with Google (the "openid", "email" and "profile" permissions only), we keep a one-way hash of your Google account's id, when you first and last signed in, and that you confirmed your age, so you count as the same visitor next time. We don't keep your name, email or picture unless you choose to share them with a publisher.
• What a publisher gets. Each publisher sees you under an id made for that publisher only, so publishers can't match you up between them; we don't track you across publishers except to stop abuse. A publisher gets your conversations with their AIs and people, and your scores and saves on their pages. If you tick "Share my name and email", that publisher gets them too, so they can reply to you — a transfer you ask for, which Google's Limited Use rules allow. You can take them back at any time.
• Who is responsible. The publisher (for a service desk, the organisation) is the controller of what it receives and decides how long it keeps it, under its own privacy notice; RadioChat holds it for them as their service provider. The organisation's AIs on a service desk run on its RadioChat credits through Anthropic or Google as described in "AI friends" below, and messages there may be screened for abuse. The organisation can also have a conversation summarised, emailed to its own address, or copied into its own calendar when you book with it.
• How long. Conversations are kept for 90 days unless the publisher sets a period between 30 days and two years; a visitor with no visit anywhere for twelve months is forgotten; IP addresses are used only in memory, for rate limits.
• Your choices. "Your data" (https://api.radiochat.ai/visitor) lists every publisher you've signed in with, exports what is held, takes back your name and email, and deletes your data at one publisher or everywhere. Anything a publisher already exported is theirs to delete.

Google user data (Sign in with Google, Google Drive and Google Calendar)

RadioChat's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

We don't use Google user data to develop, improve or train generalised or non-personalised AI or machine-learning models, and we don't transfer it to anyone for that purpose. When you ask an AI in RadioChat to work with your Google data (for example, to look at your calendar), it's used only to produce that AI's reply to you.

• Sign in with Google (the "openid", "email" and "profile" permissions) gives us your Google account's id, email address (and whether Google has verified it) and name, used only as described above. We don't read your profile photo or anything else in your Google account. If you add an organisation, the same sign-in also tells us your Google Workspace domain. Signing in as a visitor on a published page or a service desk uses the same three permissions and keeps only what "Visiting a published page or a service desk" says.
• An organisation's service desk calendar: a member of an organisation may connect their own Google Calendar to the organisation's service desk (with the same "calendar.events" permission). Then, as the organisation chooses, RadioChat's servers read that calendar's free and busy times to offer bookings, and copy the desk's bookings into it — automatically, or only when the desk's AI decides to. Only that member can attach or detach their calendar, and it's used for nothing else.
• Google Drive is only used if you choose to connect it (to send files, to make Google Docs and Sheets, or to turn on sync), and only with the "drive.file" permission: RadioChat can see and change only the files it creates and ones you pick yourself in Google's file picker — nothing else in your Drive. Google Docs and Sheets are made through Drive with this same permission; RadioChat doesn't ask for separate Docs or Sheets access.
• RadioChat keeps what it creates in a "RadioChat" folder in your Drive, with a README explaining it: "Shared files" (files you send in chats), "Documents" (Google Docs and Sheets you ask RadioChat or one of your AI friends to make — a notebook saved as a Doc, a board exported to a Sheet, meeting notes) and, if you turn on sync, a small "Sync key" file — half of the key that encrypts what you sync. Your devices read it from your Drive. Don't delete it or share the folder.
• When you send a file from your device, it's uploaded to the "Shared files" folder in your Drive and shared as "anyone with the link can view" (not listed or searchable; in an organisation's chat, only people signed in to that organisation's Google Workspace can open it); RadioChat gives that link only to the people in the chat you shared it in. A file you pick from your Drive keeps its own Google sharing — RadioChat doesn't change it.
• Google Calendar is only used if you choose to connect it, with the "calendar.events" permission (to see, add and delete events in your calendars): RadioChat shows your primary calendar in its Calendar window and adds or deletes the events you ask it to. If you ask one of your AI friends about your calendar or to add an event, it reads the days it needs, and an event is only added after you confirm it. What the AI reads goes to the company that runs that AI — see "How we share, transfer and disclose Google user data" below.
• Staying connected: when you connect Google Drive or Google Calendar, Google gives RadioChat a long-lived permission (a refresh token) for that one service. We keep it on our servers, encrypted with a key that isn't stored alongside it, so Drive, Calendar and sync stay connected between visits and connect by themselves when you sign in on another device. We use it only to give your own signed-in devices short-lived access tokens (they expire within an hour); your browser then talks to Google directly. Our servers never use it to download your files or read your calendar (the narrow exceptions are a picture you send in an organisation's chat, described in the next section, and a calendar you attach to your organisation's service desk, described above), and we don't store your files' contents or your calendar events. The only times any of that content passes through our servers are the AI requests and photos described in the next section and pictures in organisation chats, which are relayed and never stored.
• Because we hold that link — and, for sync, the other half of its key — RadioChat could technically read and change the files it created in your Drive or that you picked in Google's file picker (including the sync key) and the events in your calendar, and so open what you sync. We don't.
• We don't use Google user data for advertising, don't sell it, don't use it to train AI models, and people at RadioChat don't read it — except with your permission, for security or where the law requires.
• You can stop sharing any file from its window in RadioChat. Removing a Google account in Account → Work, school & organisations deletes RadioChat's Drive link to it, and "Forget this account" in the Calendar window its Calendar link, on all your devices. Google only takes back all of RadioChat's access to a Google account at once, so while one of that account's services stays connected, Google keeps the other's permission too and we keep its link unused (never used to read anything); once the last one goes we delete them and ask Google to revoke RadioChat's access. You can also revoke RadioChat's access (Drive, Calendar or both) at any time at https://myaccount.google.com/permissions, which stops the links working. We delete the links, and ask Google to revoke them, when you delete your account.

Gmail (the Mail app)

RadioChat's Mail app (Start → Mail) lets you read, reply to and send your Gmail inside RadioChat. It is optional, and it works on your own device only. RadioChat's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

• What it accesses, and why. When you connect a Gmail account, Google asks you for the "gmail.modify" permission (to read your mail — messages, conversations, labels and attachments — and to change it: mark read or unread, star, archive, move to or out of Trash) and the "gmail.send" permission (to send mail as you: new messages, replies and forwards), plus "openid" and "email" so RadioChat knows which address it is. They are used only to show you your mail and to do what you click in the Mail window: list and search your conversations, open one, download an attachment you press, and send what you write and press Send on. RadioChat doesn't permanently delete mail, doesn't change your Gmail settings, and doesn't send anything you didn't write.
• It stays on your device. Your messages, attachments and contacts, and the Gmail access token, go straight between your browser (or the RadioChat desktop app) and Google. They never pass through RadioChat's servers and are never stored there; they are not part of your sync, your data download or any backup we keep. The one exception is a conversation you choose to export with Export to AI (below), which becomes a Private Library item and is stored and synced like your other Private Library items. The access token is held only in the page's memory for about an hour: closing or reloading the page forgets it, and Mail asks you to Reconnect. The only thing RadioChat remembers is the email address of each Gmail account you connected, in your browser's storage on that device, so the Mail window can list them. Our servers only tell the page which Google app (OAuth client id) to sign in with. (In the RadioChat desktop app, the sign-in is done in your system browser and Google's long-lived permission is kept on your device only, encrypted by your operating system, never on our servers.)
• Not used for ads or AI, and not read by people or AIs at RadioChat. We don't use Gmail data for advertising (including retargeting and interest-based advertising), don't sell it, and don't use it to develop, improve or train generalised or non-personalised AI or machine-learning models. No AI in RadioChat can read your Gmail. We can't read it either, because it never reaches us. Gmail data goes only to Google and, when you send a message, to the people you send it to.
• Export to AI — only when you press it. Mail has an Export to AI button on an open conversation. It is the one way a conversation leaves the Mail window, and only that one conversation, only when you press it: a copy (the subject, who it was from and sent to, the dates, the messages as plain text, and the names and sizes of any attachments — never their content) becomes a document in your Private Library, stored like your other Private Library items, and is sent to the AI friend you pick through that AI's provider, like a message you write to it. You choose whether to delete that document, protect it with a passkey or leave it once the AI has done the task. It is not used for advertising or to train AI models, and the AI is only used to do what you ask of that conversation. Disconnecting Mail does not delete a document you exported; delete it from your Private Library.
• Pictures and links in messages. A message is shown in a sandboxed frame in which nothing in it can run. Pictures from the web are blocked until you choose Show images, because they can tell the sender that you opened the message; links open in a new tab.
• Disconnecting. In the Mail window, open the options (the gear) and choose Disconnect for the account: RadioChat forgets the address on that device and asks Google to cancel the sign-in. You can also remove RadioChat's access to Gmail at any time at https://myaccount.google.com/permissions. Because we never keep your mail, deleting your RadioChat account leaves nothing of it with us to delete, other than any conversation you exported to your Private Library, which is deleted with the rest of your Private Library.

How we share, transfer and disclose Google user data

We share Google user data only in the ways listed here, and only to provide the features you use. We don't sell it or rent it, don't use it for advertising, and don't give it to data brokers, advertising networks or anyone else.

• With the people you chat with, when you choose to share. A file you send or pick in a chat goes to the people in that chat: they see its name, type and size and get a link to open it (shared in Google Drive as described above). Your Google account's name becomes the nickname your friends see; strangers see your public name instead, and nobody sees your Google email address. If you add an organisation, its other members see that you belong to its domain. If you ask an AI in a shared chat about your calendar, its answer is posted in that chat like any other message.
• With the AI provider that runs the AI you use, when you ask an AI to work with it. When an AI friend reads your calendar for you, or looks at a photo shared in a chat, that content goes to the company that runs the AI model — Anthropic (Claude), OpenAI (ChatGPT) or Google (Gemini) — only so the AI can reply, under that provider's API terms. With your own API key, your device sends it straight to the provider and it doesn't pass through our servers. With the free Starter AI (Google's Gemini on RadioChat's key), RadioChat credits, or an API key someone shared with you, the request passes through our servers on its way to the provider: we add the key and count usage, but we don't read, log or keep the request or the reply.
• Photos shared in a chat, with the AIs in that chat. AIs that are part of a chat — yours, other people's AI friends, and AIs that RadioChat's servers run for their owners while they're away — see the most recent few photos shared there, so they can talk about them, and send them to their provider as above. For an AI that runs on our servers, our server fetches a reduced copy (at most 800 pixels) of a photo shared in that chat from Google Drive — only one RadioChat shared by link that is still shared — and passes it to the AI's provider (Anthropic or Google); the copy is held briefly in memory and never written to storage. If you don't want the AIs in a chat to see a photo, don't share it in that chat.
• Pictures in an organisation's chat, on their way to the chat. A file sent in an organisation's chat is shared only with that organisation's Google Workspace, and Google won't show its preview to a browser inside RadioChat. So to show a picture there, our server asks Google Drive for that one picture's small preview using the sender's Drive permission and passes it on to the people in that chat who may open the file — only while it's still shared. It passes through our servers on its way and is held in memory for about five minutes (so many people opening the same picture cost Google one request); it is never written to storage or logs.
• With the organisation whose service desk you talk to, if you share it. A visitor who ticks "Share my name and email" on a service desk or a published page gives that publisher their Google name and email address, so they can reply; nothing else from the Google account is shared, and it can be taken back on "Your data".
• With the service providers that host and carry it for us. Fly.io runs our servers and database (in Sydney, Australia), where the records described in this policy are kept; Cloudflare serves the RadioChat website and runs our domain; Resend delivers our emails — so it gets your email address, which may be your Google account's address, when we send you a code, an account notice or a data export, and the address of someone you invite by email. We use them only to run RadioChat.
• When the law requires it, or to protect people. We disclose data if we're legally required to (for example, by a valid court order), or where it's necessary to protect someone's safety or to investigate abuse of RadioChat — and only what's needed.
• If RadioChat changes hands. If RadioChat or its operator is merged, acquired or sold, your data may move to the new owner, who must keep to this policy, including the Limited Use requirements above. We'll tell you in the app before that happens.

How we protect your data (including sensitive data)

• Encrypted connections. Everything between your device, our servers and Google travels encrypted over HTTPS (TLS). The RadioChat website tells browsers to use only HTTPS (HSTS), our servers redirect any plain-HTTP request to HTTPS, and the app's security policy lets it connect only to the services it needs.
• Google permissions encrypted at rest. The long-lived Google permissions (refresh tokens) we keep are encrypted with AES-256-GCM, using a key derived (with HKDF-SHA256) from a secret that's kept in our server's protected settings — never in the database or the code — so a copy of the database alone can't use them. Each one is bound to its own RadioChat account, Google account and service, so it can't be moved to another. Short-lived access tokens are only ever held in memory, and Google codes and tokens are never written to our logs.
• Least privilege. RadioChat asks for each Google permission separately, only when you use the feature that needs it: signing in gets only your identity, never Drive or Calendar (our server refuses a sign-in token that could open your Drive); Drive uses the narrow "drive.file" permission (only files RadioChat made or you picked); and Calendar is asked for apart from Drive, so neither permission carries the other.
• Access only for you. Our server gives Google access only to the RadioChat account that connected it, and only to that account's own signed-in sessions. Requests are rate-limited, and unusual patterns (for example, one address getting access for several accounts) send us an alert.
• Keeping as little as possible. Our servers don't copy or store your Drive files' contents or your calendar events. For a shared file we keep only its share record (name, type, size, Drive id and link). AI requests that pass through our servers, photo copies for AIs that run there, and pictures passed on in organisation chats, are never written to storage or logs.
• Encrypted sync. If you turn on sync, your notebooks, personas and AI settings (and API keys, if you choose) are encrypted on your device with AES-256-GCM before they're sent, with a key made from two halves — one in your Google Drive and one on our server (see "Synced notebooks and AI setup" above for what we could technically do). API keys you share with others are encrypted on our servers the same way as Google permissions.
• Sharing you control. Files RadioChat uploads are shared only by link, aren't listed or searchable (an organisation's only within its domain), and the link goes only to the people in the chat. Stopping sharing in RadioChat stops the file opening there and switches off its link sharing in your Drive (people who already opened it may have kept a copy).
• On your device. Message moderation runs on your own device. With your own API key, your AI requests — including any Google data in them — go straight from your device to the AI provider.
• Deleting and revoking. Disconnecting Drive or Calendar deletes our link to it (see above); deleting your account deletes all of them and asks Google to revoke RadioChat's access; unused accounts are deleted automatically (see "How long we keep it"). You can also revoke RadioChat's access yourself at https://myaccount.google.com/permissions.
• No system is perfectly secure, but these protections are in place today. If we learn of a breach that affects your data, we'll tell you, and the authorities where the law requires.

What stays on your device

RadioChat uses your browser's storage (local storage and IndexedDB) for things the app needs to work: the token that keeps you signed in, your settings, saved stations, a copy of your chat history, your Notebooks and Personas, the list of Google accounts you've connected (and the addresses of Gmail accounts connected to Mail — never a sign-in or a message), your AI API keys, and small copies of photos from chats that your AIs have looked at. These stay on your device and we don't receive them — except your desktop profile and your Google connections (above), and, if you turn on sync, your notebooks, personas and AI settings (and your API keys, if you choose), which are also kept on our servers encrypted (we could technically open them, as explained above, but don't). We don't use advertising or analytics cookies, and we don't track you across other websites.

AI friends

If you add Claude (Anthropic), ChatGPT (OpenAI) or Gemini (Google) with your own API key, your device sends what the AI needs — the conversation, and any notebooks or personas you give it — straight to that provider under your key. That provider's privacy policy applies to it. Our servers don't see those requests, or your key — unless you choose to sync your keys (see "Synced notebooks and AI setup" above), or to have a station's AI moderator use one (see "AI moderators in your stations" below).

• Shared AI keys: if you share one of your API keys with an organisation or with friends, that key is stored encrypted on our servers (and deleted when you revoke it or delete your account). The AI requests of the people you share it with — and yours, if you use an AI on a key shared with you — pass through our servers on their way to that provider: we add the key and count how many messages and tokens each person used that month (the owner sees this), but we don't read or keep the messages themselves.
• AI moderators in your stations: if you give a station of yours an AI moderator, every message people send there is sent from our servers to that AI (Anthropic, OpenAI or Google) to screen it for abuse, spam and anything against the station's chosen level, and any it flags is taken out for everyone. On your own API key, that key is stored encrypted on our servers, only after you agree to it, while one of your stations (or your default for new ones) uses it — it's deleted when none does, and when you delete your account; that provider bills you. On RadioChat credits, it runs on RadioChat's key and we keep what each check cost. If you add a moderator personality, a copy of the persona and notebooks you picked is kept with it. We don't keep the messages it reads beyond the station's own history.
• Starter AI: every account gets a free Starter AI that runs on Google's Gemini with RadioChat's own key, on our paid Gemini account: under Google's terms for it, Google doesn't use what it reads to train its models, and keeps it only for a limited time to detect abuse. Its requests pass through our servers on their way to Google: we count how much each person uses it each month, but we don't read or keep the messages.
• RadioChat credits: if you buy credits, the AIs that use them (Claude from Anthropic, Gemini from Google, ChatGPT from OpenAI, and pictures from Google's Gemini) go through our servers the same way, on RadioChat's key: we keep your balance and what each request cost, not what was said. Stripe handles the payment; we never see your card.
• AIs that run on our servers: if you turn this on for one of your AIs in a station or chat, we keep a copy of its setup (its name, instructions, what it knows there and its settings) while it's on, and our servers run it on your credits while you're away. While it does, the messages in that chat are also sent to Google's Gemini (on RadioChat's key) to screen them for abuse and spam and to decide when your AI should answer, and the AI sees the chat and its recent photos as described in "How we share, transfer and disclose Google user data". It has no access to your Google Drive, Calendar or anything else private of yours.

What we don't do

• We don't sell your data or show ads.
• We don't read your messages to profile you. Moderation runs on your own device before a message is sent (and, where someone's AI runs on our servers in a chat, that chat's messages are also screened for it — see "AI friends").
• Other people never see your email, your Google name (unless they're your friend), your backup code, or your account ids. Strangers see your public name and a session number that changes every visit.

Services we rely on

• Fly.io hosts our servers and database (in Sydney, Australia); Cloudflare serves the app, runs our domain and runs the "I'm human" check on sign-up.
• Google provides Sign in with Google, Google Drive, Google Calendar and a network helper (STUN) for direct connections.
• Resend delivers our emails (codes, support and account notices, and invites you ask us to send).
• Hugging Face serves the on-device moderation model (its runtime comes with the app).
• GIPHY provides GIF search.
• YouTube, only when you watch a video in the in-app Browser.
• Anthropic, OpenAI and Google (the Gemini API) run the AIs: with your own key, a key someone shared with you, the Starter AI, RadioChat credits, or an AI running on our servers (see above).
• Stripe handles payments when you buy RadioChat credits, and an organisation's automatic top-ups on the card it saved with Stripe (we never see the card number).
• Your browser's push service (run by Google, Apple, Mozilla or Microsoft, depending on your browser) delivers notifications, if you turn them on: who wrote and where, not what was written (unless you turn on message previews).

How long we keep it

Temporary accounts are deleted 30 days after last use. Saved accounts unused for about 18 months are deleted (with a data export emailed first when there's a confirmed email). Deleting an account removes its profile, friends, sign-in methods, Google sign-in link, Google Drive and Calendar connections (we also ask Google to revoke them), synced data, desktop profile, chat archives you kept on RadioChat, contact card and its photo, file share records, the stations you own (and their boards), your Cloud moderation and server-run AI settings, and friend messages still waiting to be delivered.

A chat archive you keep on RadioChat stays until you delete it (Sync & Data → Your data → Restore lists them, and each archive — or all of a chat's — has a delete button) or your account is deleted. We don't remove one on a timer of its own.

Some things stay after an account is deleted: messages you posted in other people's stations and chats stay there without your name; an organisation's audit log and admin-check records stay with that organisation (the admin checks without your name or email); and records of credit purchases are kept, without your account, because payment records have to be kept for tax and accounting.

Your Google Drive is yours, so when you delete your account in the app (Settings → Account) you choose what happens to what RadioChat made there, for each Google account connected: RadioChat's settings (the sync key file and README) and RadioChat's files (Shared files, Notebook pictures and Documents). What you choose is moved to your Drive's bin — Google deletes it for good after 30 days, or sooner if you empty the bin — and link sharing on files you sent is switched off first, so they stop opening for the people you sent them to. Files you moved out of the RadioChat folder, and files other people own, aren't touched. What you don't choose (and everything, for a Google account that isn't connected at the time, or when an account is deleted for being unused) stays in your Drive, with any link sharing still on until you switch it off in Google Drive. Your notebooks, chat history and settings stored on the device you delete from are cleared from it too.

Your choices

You can edit your profile, remove sign-in methods and devices, disconnect Google Drive and stop sharing files from within the app. You can delete your account yourself in Settings → Account. You can download a copy of your data yourself in Sync & Data → Your data → Download my data: your library, AI setup, desktop profile and chat history, plus any chat archives you keep on RadioChat (a protected one stays protected), made on your device. A protected backup is the same file locked with a password you choose — we never see that password and can't open the backup or recover it. Your own AI keys are only included if you ask. Restore, beside it, puts a download, a protected backup or a chat archive back, from a file on your device or from the archives you keep on RadioChat; you can delete those there too. To ask for a copy of your data, or for help deleting your account, contact hello@radiochat.ai or use Help & Support in the app.

Children

RadioChat is only for people old enough under our Terms of Service. Sign-up asks for your month and year of birth and refuses anyone under age, and a visitor who signs in on a published page or a service desk confirms their age first. If you believe a child has an account, contact us and we'll remove it.

Changes

If we change this policy materially we'll show you the new version in the app and ask you to accept it.