Privacy Policy
Last updated 18 November 2026.
This policy explains what personal data Otag handles on otag.chat, why, for how long, and what you can do about it. It covers the hosted service, the Otag apps when they are connected to it (the web app in your browser included), and otag.chat's own pages: the front page, its guides and the guide for developers. Other Otag servers are run by their own operators, who are responsible for the data on them.
In short: we keep what Otag needs to work, we don't show ads, we don't sell or share data for marketing, and we don't track you across apps or websites. Calls in voice channels are end-to-end encrypted: we can't hear or see them. Stages, for events, aren't (see section 2). Two features make your app load content from outside services directly: GIFs and links straight to images (see section 2). In a channel a server has translated for its readers, the words of the messages go to an AI service that translates them for us (see section 2). Push notifications, once you turn them on, reach you through your browser's or phone's own push service, encrypted so that service can't read them (see section 2). When you pay for Aga, kor or something in the shop, you pay in Otag, in Stripe's card field: your card's details go straight to Stripe, never to us, and we keep a record of what you paid for (see section 2).
1. Who is responsible
Fly by wire AB, company registration number 559316-3313, Flädervägen 1 b Lgh 1401, 611 46 Nyköping, Sweden, is the controller of your personal data. Contact us about privacy at support@otag.chat.
Otag for iPhone is published on Apple's App Store by Pocket factory AB, which the App Store shows as its seller. Fly by wire AB runs Otag, and is the controller of your personal data in the iPhone app too.
2. What we handle, why, and on what legal basis
| Data | What it's for | Legal basis (GDPR) |
|---|---|---|
| Account: username, display name, password (stored only as a secure hash), email address, avatar, when you joined, which version of the Terms of Service you accepted. An account you start with just a name has no password or email address until you add one. | Creating and running your account, signing you in, sending you codes and important notices | Contract (Art. 6(1)(b)) |
| Signing in with Google, if you use it: the ID Google gives your Google account, the email address Google shares for it, with whether Google confirmed that address, and your first name | Signing you up and in with your Google account, connecting it to your Otag account, and showing you in Settings which Google account that is | Contract (Art. 6(1)(b)) |
| Two-factor sign-in, if you turn it on: your authenticator app's secret (stored encrypted), when you turned the app on and when you last used one of its codes, so each code works once; your passkeys' public keys, each with its name (at first, the browser and system that made it), when you added it and last used it, and the details a sign-in checks it by, such as its counter; your recovery codes, stored only as hashes; for a few minutes, a sign-in waiting for its second step; and, if our admins turn it off for you, which admin did it, the reason they gave and when | Asking for your second step when you sign in and before changes to how you sign in, signing you in with a passkey, letting you in with a recovery code, emailing you when how you sign in changes, and keeping a record when our admins turn it off | Contract (Art. 6(1)(b)); for the record of an admin turning it off, our legitimate interest in being able to show who changed how an account signs in, and why (Art. 6(1)(f)) |
| Profile: what you write about yourself, your banner (a picture you upload, or a pattern you pick), your card's colors, the decorations you pick for your avatar, card and name (Otag's own, or pictures you upload), and your status; in a server, the nickname and picture you choose for it | Showing people who you are, the way you choose | Contract (Art. 6(1)(b)) |
| Name effects: a look, such as a rainbow, that our admins, or someone in that server whose role lets them, give your name in a server, and when it ends (a week at most) | Showing it on your name to that server's members until it ends | Legitimate interest in giving Otag's communities something fun for their members (Art. 6(1)(f)) |
| Badges: the badges Otag gives you, each with its number (such as No. 312 of a thousand), when you got it and when your app first showed it to you, which of them your profile shows, and which one is beside your name | Giving out badges, and showing the ones you choose to the people who see you | Contract (Art. 6(1)(b)); for the ledger that seals them, our legitimate interest in badges nobody can copy or make up (Art. 6(1)(f)) |
| Notes you keep about other people | Keeping them for you, on all your devices | Contract (Art. 6(1)(b)) |
| Saved messages: the messages you save for later, and when you saved each | Keeping them for you, on all your devices | Contract (Art. 6(1)(b)) |
| Date of birth | Checking that you are at least 15, the minimum age for Otag | Legitimate interest in keeping young children off the service and following the laws of the countries our users live in (Art. 6(1)(f)) |
| What you share: messages, voice messages (the recording, with its length and a waveform of it), files, reactions, your votes in polls, which messages you pin and when, emoji, stickers and decorations you add to a server, servers, channels and group chats you create, link previews | Delivering and storing what you share, for the people you share it with | Contract (Art. 6(1)(b)) |
| Sending a message: a random code your app can give a message as it sends it. The code says nothing about you or about the message. | Making sure a message that is sent again after a connection problem is there once, not twice | Contract (Art. 6(1)(b)) |
| Friends: friend requests you send and receive, and your friends | Letting you add people and keep in touch with them | Contract (Art. 6(1)(b)) |
| Last seen: when you were last connected to Otag | Showing your friends when you were last online, for example "Last seen 3 hours ago". You can turn it off in Settings. | Legitimate interest in letting your friends know when you're likely to answer (Art. 6(1)(f)); turning it off is how you object |
| Game activity: the name and icon of the game you're playing, when the desktop app recognises one | Showing it next to your name in voice channels to the people you share a server or group chat with, and to your friends. You can turn it off in Settings. | Legitimate interest in letting the people you play with see what you're playing (Art. 6(1)(f)); turning it off is how you object |
| Presence: whether you're online or away, and the presence you pick: online, away, do not disturb or invisible | Showing people whether you're around, the way you choose; your pick is kept with your account, so all your apps follow it | Contract (Art. 6(1)(b)) |
| Preferences kept on the server: your notification settings for servers and conversations, how far you've read in each, the order you keep your servers in, the lace you hang at the top of the window and, with Aga, your theme of the app (one of Otag's, or colors you pick) | Notifications, unread markers, the order of your servers, your lace and your theme that follow you across your devices | Contract (Art. 6(1)(b)) |
| Push notifications, on the devices you turn them on for: each device's push address (the address its browser's or phone's push service gives it), the keys notifications are encrypted with for it (its private key stays on the device), its name (such as "Firefox · Linux"), when you added it and when it last got a notification; whether your notifications show what was written; and in each conversation, the newest message your phones were told of, until you read it | Telling you of messages meant for you (direct messages, group chats, mentions of you and replies in threads you follow) while none of your Otag apps is open and in use, and taking a notification off your phones once you've read the conversation | Contract (Art. 6(1)(b)) |
| Server rules: which servers' rules you agreed to, and when | Letting you talk in servers that ask newcomers to agree to their rules first | Contract (Art. 6(1)(b)) |
| Aga, Otag's plan for a person: from when to when you have it, and how each stretch of it came: paid by the month or the year, with Stripe's numbers for its invoice and its payment and what you paid, given by our admins, to you or to everyone at once, with the note kept with it and, when given to you, which admin gave it, or claimed by you as a gift of ours; and when a stretch was taken back | Giving you what Aga brings while you have it, and keeping account of what you paid for | Contract (Art. 6(1)(b)); for the records of what you paid, our legal obligation to keep accounts (Art. 6(1)(c)) |
| Aga's sign on your profile: that you have Aga, and whether you chose to hide its sign | Showing Aga's sign on your profile, to everyone who opens it, while you have Aga. You can turn it off in Settings. | Legitimate interest in letting people wear the plan they have, as they wear their badges (Art. 6(1)(f)); turning it off is how you object |
| Gifts: which of our gifts you claimed, and when | Giving you what a gift gives, once: Aga until the gift ends, and its kor on the servers you own and on those you make before it ends | Contract (Art. 6(1)(b)) |
| Kor: the kor that come to you (how many, and whether you bought them or a month of Aga brought them: one you paid for, or one a gift of ours gave you), and each kor you give: to which server, when, until when it burns, and whether a refund put it out | Letting you give kor to the servers you choose, and showing their members who stokes them | Contract (Art. 6(1)(b)) |
| The shop: what you hold from it: each item and bundle you got, its number where it comes in a numbered run, how it came to you (as what you wore when the shop opened, free, bought, or with a bundle), and what you paid and when | Letting you wear what you hold, and keeping account of what you bought | Contract (Art. 6(1)(b)) |
| Payments: each payment you start for Aga, kor or the shop: what it is for (for kor bought for a server, which server), its price and currency, when you started it, how it went and when, and Stripe's numbers for it; and the number of the customer Stripe keeps for you | Taking your payment through Stripe, giving you what you paid for, refunding it, and keeping our accounts | Contract (Art. 6(1)(b)); our legal obligation to keep accounts (Art. 6(1)(c)); for a payment in dispute, our legitimate interest in settling it (Art. 6(1)(f)) |
| Your orders and withdrawals: for each purchase, what the app showed you before you paid and what you agreed to (the version and language of those words and a fingerprint of them, the boxes you ticked, and in Turkey that you confirmed the pre-information form and the distance sales contract), what you bought, at what price, in which currency and when; when we emailed you its confirmation, and while it didn't go, how often we tried and when; if you withdraw, the name and email address you give, when your withdrawal reached us, what we paid back, and the language of its receipt and our tries to email it; and if we suspend or delete your account, what we pay back of what you paid for and hadn't had yet, and when Stripe made each payback | Showing what you were told and agreed to before paying, sending you the confirmation of your order and the receipt of your withdrawal (again later if they didn't go), carrying out your withdrawal, and paying you back what you hadn't had when we suspend or delete your account | Contract (Art. 6(1)(b)); legal obligation, as consumer law has us inform you, confirm your order and take your withdrawal (Art. 6(1)(c)); our legitimate interest in being able to show what you agreed to (Art. 6(1)(f)) |
| What you give in Stripe's card field: your card's details and, where the field asks for them, your country and postal code; Stripe also sees your IP address and your device | Taking your payment and preventing fraud. Stripe collects it in its own field, and we never see your card's number (see below) | Contract (Art. 6(1)(b)) |
| Your device's time zone, when the apps show you the prices of Aga and kor or an order, and when you start paying | Showing you, and charging you, the prices for where you are: in lira in Turkey, in euros elsewhere; and, for an order made in Turkey, giving you the pre-information form and the distance sales contract before you buy. Our server uses it only for these and doesn't keep it; the record of an order keeps only whether it was made in Turkey | Our legitimate interest in pricing Aga and kor for where people are (Art. 6(1)(f)); legal obligation, as Turkey's consumer law has us give buyers there these documents (Art. 6(1)(c)) |
| Selling in the shop, if you apply: your application (where your work can be seen, and what you write), our answer and its reason; which version of the creator terms you accepted, and when; the items you send (their pictures, names, how many copies there are and prices) and our review of each; what each sale earned you and when we sent it, with Stripe's number for the transfer; and your payout account at Stripe: its number, and whether it takes payouts | Deciding on your application, selling your items in the shop with your name on them, and paying you your share through Stripe | Contract (Art. 6(1)(b)); for what you earned and were paid, our legal obligation to keep accounts (Art. 6(1)(c)) |
| Apps you use: when you use an app in a server (run one of its commands, press a button on one of its cards, fill in one of its forms, open its settings) or add one to a server and pick a channel for it to say hello in, what you did, with your user ID, username, display name, picture, language, your roles, nickname and permissions in that server, and whether you may use its commands there | Sending it to the app, so it can answer you (see below) | Contract (Art. 6(1)(b)) |
| Apps and webhooks you make: an app's name, description, colour, icon and logo, the address it hears from Otag at, the permissions it asks for, whether anyone may add it, its listing in the app list and the servers it is in; a webhook's name, picture and channel, and that you made it | Running your app or webhook, and listing your app when our admins approve it | Contract (Art. 6(1)(b)) |
| Translated channels: the words of the messages in a channel a server's managers turned translation on for, their translations, and the language each is asked for in | Showing those messages to each reader in their own language. An AI service translates them for us; see below. | Contract (Art. 6(1)(b)) |
| GIFs: what you search for in the GIF picker, and the GIFs you pick and see | Finding, sending and showing GIFs. Your app gets them from KLIPY directly; see below. | Contract (Art. 6(1)(b)); for GIFs other people send, our legitimate interest in showing conversations as they were sent (Art. 6(1)(f)) |
| Music and videos with Vibe: what you ask Vibe for (a song or words to search for, or a YouTube link), and in a voice room you're in, the videos queued there, who queued each and where the room's player is | Finding what you asked for on YouTube and playing it for everyone in the room at once. The videos themselves come straight from YouTube; see below. | Contract (Art. 6(1)(b)) |
| Voice, video and screen sharing | In a voice channel, encrypted end to end on your device and relayed live through our server to the others in the call, whose devices alone can decrypt it; on a stage, relayed live through our server to its audience as it is (see Stages below). Never recorded or stored. | Contract (Art. 6(1)(b)) |
| Stream previews: while you share your screen, a small picture of what it shows, renewed as you share, encrypted on your device | Showing the people who can see the voice channel what your stream shows, before they join to watch it | Contract (Art. 6(1)(b)) |
| Sessions: a label for the app (for example "Otag for macOS", "Otag for Web" or, with the phone's model, "Otag for Android (Pixel 8)"), when you signed in, last entered your password, last gave your second step and last used it | Keeping you signed in, letting you end sessions, and asking for your password, or your second step, again before account changes if you haven't given it lately | Contract (Art. 6(1)(b)) |
| IP address | Connecting your app, and limiting abuse such as password guessing | Legitimate interest in running a secure service (Art. 6(1)(f)) |
| Safety: blocks, reports you file or that are filed about you, a copy of reported content (for a report about a person, their profile and pictures as they were), moderation decisions, and what our admins see when they look into a server (see section 3) | Keeping Otag safe, handling reports, telling people about decisions, handling appeals | Legitimate interest (Art. 6(1)(f)); legal obligation under the EU Digital Services Act (Art. 6(1)(c)) |
| Moderation in servers: what a server's moderators and managers do there (such as timing someone out, removing or banning someone, deleting someone's message, or changing a role, a channel or the server's settings), who did it, to whom, what changed, the reason they gave if they gave one, and when; and a timeout that holds you back in a server, until it ends | Letting a server's moderators work together and see who did what there, and holding back someone a moderator timed out | Legitimate interest in keeping servers orderly and safe, and their moderators accountable for what they do (Art. 6(1)(f)) |
| Requests from authorities | Answering valid legal orders | Legal obligation (Art. 6(1)(c)) |
| Usage and performance data, from the desktop app and the web app: how often and for how long Otag is used, which features get used, and how well it runs for you, in calls and screen shares as well (for example how much sound or picture is lost on the way, the delay, the picture's size and frame rate, and freezes); in the web app, also the website and campaign that brought you there. It comes with technical details: Otag's version, the kind of device, its system and browser, and the region and language set on it | Seeing which features get used, and finding what makes Otag slow or unreliable. The app asks before it sends any, and you can change your answer at any time with Share usage counts in Settings → App | Your consent (Art. 6(1)(a)), which you withdraw by turning it off |
| Crash and error reports, from the desktop app and the web app: what went wrong when Otag crashed or hit an error and the last few things done in the app before it, and detailed reports on how screen shares and cameras went; never what is shown, or who shares or watches. They come with the same technical details and the device's model | Finding and fixing what goes wrong. The app asks before it sends any, and you can change your answer at any time with Send crash reports in Settings → App | Your consent (Art. 6(1)(a)), which you withdraw by turning them off |
| Diagnostics you share, from the desktop app and the web app, when you use Share diagnostics in Settings → App: what you write about your problem, and a snapshot of how Otag runs for you at that moment: its version and settings, your device's system and hardware, the names of your microphones, speakers and cameras, where you were in the app and how your connection and calls went in the last minutes (numbers and the IDs of servers and channels: never your messages, and never other people's names), the app's recent errors and, from the desktop app, the end of its own log file, which can name the games you played, the programs in front of Otag and the files you sent. With Include my account ticked, also your display name, username and account ID | Finding and fixing the problem you tell us about | Your consent (Art. 6(1)(a)), which you give each time by pressing Send, and withdraw by asking us to delete what you sent |
| Website visits, on otag.chat's own pages (the front page, its guides and the guide for developers): which pages are shown, the website and campaign that brought you there, and clicks on Download, on the links to the web app, in the language menu and on sending the self-hosting application; when a page runs into an error, what went wrong. It comes with technical details: the kind of device, its system and browser, and the region and language set on it | Seeing how people find Otag and what helps them start, and fixing what goes wrong on the pages. The pages ask before they count anything, and you can change your answer at any time with the switch at the bottom of every page | Your consent (Art. 6(1)(a)), which you withdraw by turning it off |
| Service data: what our server counts of how the service runs, such as requests, connections, new accounts, messages sent, time in voice, screen shares and cameras, call quality, and the errors and crashes it runs into. Everything is counted by which app, never by who | Keeping the service running and fixing what goes wrong | Legitimate interest in running a reliable service (Art. 6(1)(f)) |
We don't use your data for advertising, we don't profile you, and no decisions about you are made automatically. Every moderation decision is made by a person.
Things worth knowing
- Calls are end-to-end encrypted; messages aren't. In every voice channel, your device encrypts your voice, your camera and your screen before they leave it, with keys that only the devices in the call share and that change whenever someone joins or leaves. Our server passes them on without being able to decrypt them. What it still knows is who is in which call, when and for how long, who shares a screen or turns a camera on, and how much is sent and when. Each of your devices makes its own keys for calls by itself, and our server tells the others in a call which account each device belongs to. Everyone in a call sees the same voice privacy code: comparing it with someone in the call checks that you share the same keys, and your app lists the devices that hold them. Messages and files are stored on our server, as before. Our admins can look into any server to keep Otag safe (see section 3). Direct messages and group chats they see only when something in them is reported to them.
- Stages: a stage is a channel for events. A few speakers talk, show their cameras and share their screens, and everyone else joins as its audience, which listens and watches. Whoever can see a stage sees who speaks on it and how many are in its audience, and can see up to 50 of the audience by name, their own friends first. The stage's moderators see all of its audience by name, and the hands raised to ask to speak. A speaker who shares their screen sees how many watch it, and up to 50 of them by name. Stages aren't end-to-end encrypted, unlike calls in voice channels: our server passes their sound and video on to the audience, as for a broadcast, and never records or stores them.
- Starting with just a name: you can make an account with a name, your date of birth and our Terms alone. It has no email address or password, so it lives only on the devices you're signed in on. Until you set a password, confirm an email address or connect Google, signing out deletes it, and so does leaving it unused for 30 days (see section 4).
- The check at sign-up: when you make an account, your app solves a small puzzle our server sets, which makes signing up by the thousand costly for automated programs. It runs on your device and sends nothing about you. Our server keeps only a fingerprint of the solved puzzle, which says nothing about you, for 5 minutes, so it can't be used twice. No other company is involved.
- IP addresses: the Otag server uses your IP address to connect you and to limit abuse. It keeps it in memory only and doesn't store it with your account or in its logs. The hosting platform our server runs on may keep short-lived technical connection logs, including IP addresses, for security.
- Signing in with Google: when you choose Continue with Google, your browser opens Google's own sign-in, run by Google (Google Ireland Limited in the EU, part of Google LLC in the United States), and Google then sends your browser back to Otag. Google tells our server your Google account's ID, its email address and whether Google has confirmed that address, and your name. Our server reads only these, and of your name only your first name: the rest of what Google sends is never read or kept. We never see your Google password, and Otag gets no access to your email, contacts, files or anything else in your Google account. We use what Google tells us only to sign you in and to make and connect your account: the address becomes your account's email address, already confirmed, and your first name is offered as your display name, which you can change. If an Otag account already has your Gmail or Google Workspace address, Google signs you in to it and connects it; with any other address, you first log in to that account with its password once. Google learns that you sign in to Otag, and handles that under its own privacy policy. If you don't finish making your account, what Google told us is deleted after 30 minutes. An account made with Google has no password until you set one in Settings, and you can disconnect Google there once it has one. Our use of what we receive from Google follows the Google API Services User Data Policy, including its Limited Use requirements.
- Two-factor sign-in: in Settings → Account you can make signing in ask for a second step: a code from an authenticator app, or a passkey. Our server keeps your authenticator app's secret encrypted, and your recovery codes, which let you in once each if you lose your second step, only as hashes. A passkey lives on your device, in your password manager (such as Apple's, Google's, Microsoft's or another) or on a security key, which keeps its private key, with your username and display name to tell it apart, under its own terms; our server gets only the public key. The desktop app uses passkeys through your browser, which hands the result back to the app on your computer. We email your confirmed address when two-factor sign-in is turned on or off, a passkey is added, a recovery code is used or new ones are made, and, once a day at most, when a wrong second step follows your password or your Google sign-in. If you lose every second step, write to us: once our admins have checked that the account is yours, they can turn two-factor sign-in off for it. You then get an email with their reason, and every session of the account ends. We keep a record of which admin did it, the reason and when for as long as you have the account; your data export shows when and why.
- Link previews: when you post a link, our server fetches that page to build a preview. The website sees our server, not you. Links straight to an image are different: the image shows in the conversation and loads from that website for everyone who sees it, so the website sees their IP addresses.
- Servers from a template: when you make a server from a template link, our server reads the template from the service the link comes from, and makes your server with its layout: its channels, categories and roles. It sends that service only the template's code. The service sees our server, not you. Its answer also names who made the template, which we don't keep. The server you make is kept as any server you create.
- Videos you send: our server reads from the file how wide and tall a video is, how long it lasts and what format it is in, so the apps can show it at the right size before it plays. When your app makes the picture shown before a video plays, it makes it on your device and sends it with the video. All of this is kept with the video and deleted with it.
- Voice messages are recordings you make and send yourself. Your app records only while you record, once your browser or system lets it use your microphone, and makes the recording on your device. Our server keeps it like any file you send, with its length and the waveform your app measured as you recorded, for as long as the message; it reads only how the recording is put together, to check its length, and never decodes the sound. Like other messages, voice messages aren't end-to-end encrypted: whoever can read the conversation can play them, and so can our admins where they may read messages (see section 3). Calls are still never recorded.
- Translated channels: once our admins have given a server translation, its managers can turn it on for a channel where only some people may post, such as its announcements. Each reader then sees that channel's messages in their own language. The first time someone reads a message there in a language, our server has it translated by Claude, an AI model made by Anthropic, and keeps the translation with the message for everyone who reads in that language afterwards. To have it translated, our server sends Anthropic the words of the message and the language to put them in, and nothing about who wrote it, where, or who is reading: mentions, links, server emoji and code are taken out before the words go and put back after. Anthropic does this for us as a service provider (see section 3), and may not use the words to train its models. Above the message box, the apps tell whoever writes in such a channel that its readers read it in their own languages. A translation is deleted when its message is edited or deleted. In Settings → App you choose the language you read in, or turn translation off for yourself: that choice stays on your device, and our server doesn't keep which language you asked for.
- GIFs: GIFs come from KLIPY, a GIF service run by Kikliko, Inc. in the United States. When you use the GIF picker, your app sends KLIPY what you search for, the GIF you pick, your language's country code and a code made from your account. That code stays the same each time but doesn't contain your username, email address or anything else that names you. GIFs in conversations load straight from KLIPY for everyone who sees them. Each time, KLIPY sees your IP address. KLIPY handles this data under its own privacy policy. Our server never fetches GIFs and never sees your searches.
- Music and videos (Vibe): Vibe is Otag's own app for playing YouTube videos in voice rooms, and it uses the YouTube API Services. When you ask Vibe for something, and while you type in its search box (once you pause), our server sends YouTube what you typed (the words or the link) to find videos; YouTube doesn't learn who asked. While you're in a voice room where something plays, your app loads YouTube's own player and the video straight from YouTube, which is run by Google (Google Ireland Limited in the EU, part of Google LLC in the United States). YouTube then sees your IP address and your device, may store or read cookies and similar data on your device, and may show its own ads in its player. Google handles all of this under its own privacy policy, and using Vibe means agreeing to the YouTube Terms of Service. Stop listening in the room, or leave it, and nothing more loads from YouTube for you. Our server never fetches or keeps the videos; it keeps a room's queue (the videos' titles and who queued them) only while the room plays.
- Away: the desktop app shows you as away after five minutes without a key press, click or mouse movement on your computer. It only checks how long it has been; it never records what you type or click. The web app does the same, counting only key presses, clicks and movement in its own tab.
- Presence: you pick how you show: online (Otag tells when you're away by itself), away, do not disturb (your apps show no notifications and play no sounds for them) or invisible. Invisible shows you as offline to everyone and hides your game, and your friends see when you were last online as of the moment you turned invisible. You can still use all of Otag, and the people in a voice channel with you still see you there.
- Push notifications are off on each device until you turn them on there, and your browser or phone may ask you to allow notifications first. A notification goes only while none of your Otag apps is open and in use, a few seconds after the message, and not if you read it meanwhile, turned on do not disturb, or your notification settings for that server, channel or conversation keep it quiet. It says who wrote and where and, unless you turn off Show message text, what they wrote; on a locked phone, the Otag apps show only who wrote, unless you change that in your phone's settings. Notifications travel through your browser's or phone's own push service: Apple's for Safari and iPhones, Google's for Chrome, most other browsers built on it and Android phones, Mozilla's for Firefox and Microsoft's for Edge. Our server encrypts each notification for your device alone before it leaves, so these companies can't read it: they get your device's push address, see when a notification goes to it, about how big it is and a mark that keeps one conversation's notifications together without saying which conversation it is, and keep one your device hasn't received yet for up to a day. On Android, turning notifications on also registers the app with Google's Firebase, which gives that installation of the app an ID beside its push address; turning them off or signing out deletes both. You can turn notifications off on a device, or remove any of your devices, in the apps' settings; signing out of a device ends them there.
- Game activity: to recognise a game, the desktop app regularly looks at the programs that have a window open and where they're installed: in a game store's library, such as Steam's, or on macOS, an app that says it is a game. Only the name and icon of the game it finds leave your computer. Our server keeps them in memory while you're connected and doesn't store them. You can turn this off in Settings → App. The desktop app still looks for a game then, to offer you to share it in one click, but nothing about it leaves your computer.
- Stream previews: while you share your screen, your app sends our server a small picture of what it shows, shortly after you start and then regularly until you stop. Your app encrypts each picture with a key of your share first, so our server can't see it. The people who can see the voice channel see the latest one as your stream's preview, before they join to watch: their device asks yours for the key, and your device sends it encrypted to theirs. Our server keeps only the latest picture, in memory, for at most 90 seconds, deletes it when your share ends, and never writes it to disk.
- Emoji and stickers you add to a server belong to that server. Anyone in it can use them anywhere on Otag, so they also show to people outside the server: emoji in messages, reactions, profiles and statuses, stickers in messages. The server's members see who added each one, and its owner and moderators can rename or remove them.
- Decorations you add to a server belong to that server, like its emoji: its members can wear them anywhere on Otag, so people outside the server see them too. The server's members see who added each one, and its owner and moderators can remove them. Decorations you upload for yourself are yours alone to wear.
- Pinned and saved messages: in a server, those allowed to manage messages can pin a message to its channel or thread; in a direct message or a group chat, anyone in it can. Everyone who can read the conversation sees who pinned each message and when, and the conversation gets a line saying who pinned one, which stays like a message; in a server, its audit log also keeps pins and unpins. The messages you save for later are yours alone: nobody else sees what you saved.
- Your status shows only while you're online, and is removed when the time you chose for it runs out.
- Otag's community server: when you make an account, Otag adds you to its own community server, once. You can leave it at any time, and Otag won't add you again.
- Badges: on otag.chat, Otag gives a badge to the first thousand accounts made during the beta, and another to the first hundred, numbered in the order the accounts were made. An account you start with just a name gets its badges once you set a password, confirm an email address or connect Google. Each badge Otag gives is also written in a ledger that Otag signs, so that nobody can copy one or make one up. The ledger doesn't name you: for each badge it keeps only a fingerprint of your account, made with a secret that is kept with your badge, and without that secret the fingerprint leads to nobody. Your profile shows your badges, up to six, and one beside your name, as you choose in Settings. Anyone on Otag who looks a badge up by its number sees who holds it, but only while their profile shows it. When you delete your account, the secret is deleted with it: the badge's line stays in the ledger, its number is never given to anyone else, and nothing in it leads back to you.
- Aga is Otag's plan for a person. Its stretches are kept with your account: each month or year you paid for, with Stripe's numbers for its invoice and its payment and what you paid, and the months our admins give, to you or to everyone at once, with the note kept with them and, for months given to you, which admin gave them. A gift of ours gives Aga only when you claim it: we keep which gift you claimed and when, and the stretch it gave you says it came from a gift. While you have Aga, your profile shows Aga's sign to everyone who opens it, unless you turn that off in Settings (Account, Privacy): then nobody but you and our admins learns that you have it. Until when you have it, and whether you paid for it, claimed it as a gift or were given it, only you and our admins learn. Others also see what Aga brings, such as your sharper screen shares. A refund takes back the stretch it paid for, with the kor it brought.
- Kor are what you give a server to stoke its fire. They come to you when you buy them, at least five at a time, or go straight to the server you buy them for, and two come with each month of Aga you pay for or hold by a gift of ours you claimed; Aga our admins give brings none. A kor you give burns on that server for 30 days and is then spent: it is never taken back, and it goes on burning there if you leave the server or delete your account. The server's members see who stokes it: each one's name, how many of their kor burn there and since when. While a kor of yours burns there, you also wear the role the server gives those who stoke it, if it gives one. Our server keeps the kor that came to you and each one you gave: to which server, when and until when. A refund takes back the kor it bought, and puts out as many of yours that still burn, the newest first.
- The shop: what you wear on your card and your name is what you hold from the shop: what you wore as it opened, and what you got there since, free or bought, alone or in a bundle. Our server keeps each item you hold, its number where it comes in a numbered run, how and when you got it and what you paid. Others see what you wear, never what else you hold or the numbers of your copies. A refund takes back the copy it paid for, and takes it off you if you wear it.
- Paying: you pay for Aga, kor and the shop's items in Otag: the order's sheet holds Stripe's own card field, which runs in a page our server serves for it and loads only Stripe's code. Stripe Payments Europe, Limited in Ireland takes the payments for us, with Stripe, LLC in the United States. You type your card's details into that field, for Stripe: they go straight to Stripe, never reach Otag, and we never see your card's number. If your bank wants you to approve a payment, its window opens over Otag. The field may also ask for your country and postal code, which Stripe stores with the customer record it keeps for you; Stripe sees your IP address and your device too, and may store or read cookies and similar data on your device to prevent fraud. Our server sends Stripe your account's ID, your confirmed email address, which Stripe needs for a payment, a number for the payment, what you buy (such as "Otag Aga", or "Otag kor:" with the name of the server you buy them for), its price and, if you already have Aga, when it ends, so paying starts then; it keeps the numbers Stripe gives your customer and your payment. When a payment goes through or is refunded, Stripe tells our server. Its messages also carry what Stripe holds, such as your email address and your card's last digits, which our server doesn't read or keep: it keeps which payment it was, how it went, what was paid and the period it paid for, and a note of each message it took, so it takes none twice. In Stripe's dashboard we can see what Stripe keeps for us, such as your email address, the country and postal code you gave, your card's country, brand, last four digits and expiry date, and your payments. Payments and receipts in Settings → Aga shows your subscription to Aga: when it renews or ends, what it costs, and the card it is charged to, whose brand, last four digits and expiry date our server reads from Stripe each time you look and doesn't keep. There you stop Aga renewing or let it renew again, put another card in its place in Stripe's card field (Stripe keeps the card, and nothing is charged), and see what you bought. For some purposes of its own, such as preventing fraud and meeting the duties the law puts on it, Stripe decides itself how it uses this data, under its own privacy policy.
- Prices by place: Aga and kor have one price in Turkey, in lira, and one everywhere else, in euros. To show you yours, the apps send our server the time zone your device is set to (such as Europe/Istanbul) when they show you these prices and when you start paying: Turkey's time zone gets the lira prices, any other the euro prices. Our server uses it only to pick them and doesn't keep it; each payment keeps the currency it was made in. The shop's items are in lira for everyone. The same time zone also goes with every order, the shop's items' too, and tells whether it is made in Turkey, where the law has us give you the pre-information form and the distance sales contract before you buy; the record of an order keeps only whether it was.
- Selling in the shop: anyone can apply in Otag's portal to sell what they make in the shop: banners, avatar decorations, card frames, profile effects and nameplates. Our admins read your application (a link to your work and a few words) and decide on it, with their reason when they give one; once you're accepted and have accepted the creator terms, each item you send goes into the shop after our admins have reviewed it. Your items show your name to everyone who opens the shop; you see how many hold each, never who. Your share of each sale is paid through Stripe Connect: setting up payouts opens Stripe's own pages, where you give Stripe who you are and your bank account. Stripe provides that payout account under its own agreement with you, checks who you are, and handles those details under its own terms and privacy policy. Our server keeps your payout account's number and whether it takes payouts, and of each sale what it earned you and when we sent it, with Stripe's number for the transfer. Until your payout account takes payouts, what you earn waits for it.
- Themes of your own: with Aga, you can dress the whole app, by day and at night, in one of Otag's themes or in colors you pick. Your pick is kept with your account, so every device you sign in on wears it, and nobody else learns it. When Aga ends it stays kept, for when you have Aga again, and the apps wear their plain theme meanwhile. A theme you try without Aga is kept nowhere. The desktop app and the web app also keep a copy of its colors on your device (see On your computer below).
- Discover and previews: a server whose owner lists it in Discover can be found by everyone on Otag, with its name, icon, description, rules, tags, how many members it has and how many of them are online, and anyone on Otag can read its channels open to everyone before joining. If you post there, people who aren't members yet can read it. When you preview a server, its members don't see you, and nothing about the preview is stored: it ends when you leave it or close Otag.
- Invite links: anyone who opens an invite link, with or without an account, sees the server it leads to: its name, icon, description, and how many members it has and how many are online. Apps that show link previews, where someone posts the link, may show the same.
- Apps are made and run by their developers, under their own terms and privacy policies, even the ones in the app list; our admins list the apps they approve, but don't run them. A server's admins choose which apps join it, what each may do there and who may use its commands. When you use an app, Otag sends it what you did and who did it (see the table above). An app in a server also sees what its role there lets it see, as a member would: the messages in the channels it can read, and who is in the server and in its voice channels. The pictures in apps' cards and forms are fetched and kept by our server and shown from there, so an app doesn't see who looks at them. When an app asks you to sign in to its own service (for example Execute asks for your Steam account so you can play on its match servers), that page is the app's: what you enter there goes to the app, not to Otag, and the desktop app shows it in a window of its own, kept apart from Otag. Apps can't send you private messages or become your friends, and they show with an App tag wherever they appear.
- Webhooks post in a channel what an outside system sends to their address. A server's admins make them; their messages show with an App tag.
- Last seen: your friends see when you were last connected to Otag. Nobody else does: people you only share a server or a group chat with see just whether you're online. If you turn it off in Settings, your friends see just "Offline".
- Usage and performance data and crash reports go to Koru Analytics, our own analytics service, which keeps them on the same servers in Frankfurt as the rest of Otag. None of it is tied to your name, email address, account or any ID for your device, and your IP address is never stored: counts are added up as they arrive, so no single visit, session or event is kept. Crash and error reports can contain parts of error messages, so the app encrypts them on your device and only Otag's developers can read them; when they ask an AI coding assistant to help fix a problem, the assistant and its provider see that report too. Because nothing is tied to you, we can't find or delete one person's data on its own: it is deleted when the periods in section 4 end. The desktop app and the web app send neither until you allow it: counting keeps a few dates on your device, which the law allows only with your consent (Swedish Electronic Communications Act (2022:482), chapter 9, section 28), so they ask once, the first time you open them. No thanks is kept, and they ask again only if what they send changes. Turning either switch off deletes at once what the app kept on your device for it, and your choice is kept. In the web app, a browser that sends Global Privacy Control isn't asked: usage data stays off, and crash reports are sent only if you turn them on in Settings → App. Otag servers that others run send us their data only if whoever runs them turns this on. The iPhone and Android apps send neither. On otag.chat's own pages, website visits are counted the same way, but only once you allow it in the small bar the pages show on your first visit; until then nothing is counted. The switch at the bottom of every page changes your answer, crash reports included, and a browser that sends Global Privacy Control is never asked or counted there. If you allowed counting there, when you go on from those pages to the web app, the campaign that brought you, or else the name of the website that sent you, goes along in its address, so the web app can count it too if you allow usage data there as well. An invite link on otag.chat passes on the campaign it was shared with, or else the name of the website that sent you, in the same way, without storing anything on your device. When you make an account, our server counts it: whether it came through an invite, whether you made it with a password or with Google, in which app, and, when usage data is on in the web app, the campaign or website that brought you there, which the web app sends with your sign-up. None of this is stored with your account.
- Diagnostics you share go to Koru Analytics too, but not like the data above: only when you press Send, each time, and whatever you answered about usage data and crash reports. The app takes out what looks like a password, a key or a network address, and encrypts the rest on your device, so only Otag's developers can read it. With Include my account unticked it says nothing of who you are: the app also takes your display name and username out of all of it, and the desktop app your computer's user name and the computer's own name too, along with IDs, email addresses and phone numbers. When our developers ask an AI coding assistant to help with your problem, the assistant and its provider get what you shared without the line that says who it is from, and with IDs, email addresses, phone numbers and network addresses taken out again; a name that stands somewhere else in it, such as in a device's name, can remain. We keep what you shared for 90 days. Once it is sent the app shows you a reference: write to support@otag.chat with it and we delete what you sent. Until you press Send nothing is gathered for it, apart from the last minutes of connection readings and errors that the app holds in memory while it runs. The iPhone and Android apps can't share diagnostics yet.
- Updates: the desktop app checks our release server for new versions, which means that server sees your IP address.
- On your computer: the app stores your sign-in token, your settings, the keys it encrypts your calls with and a log file of its own. These stay on your computer, apart from what you choose to send with Share diagnostics, and are removed when you uninstall the app and delete its data. The web app keeps your sign-in token, your settings (such as your language, theme, microphone and push-to-talk choices) and the keys it encrypts your calls with in your browser's storage for Otag's site, and uses no cookies. To show its notifications, it also registers a small worker in your browser, which keeps nothing but the words they use; with push notifications on, your browser also keeps the web app's subscription at its push service. Signing out removes the token, those keys and the subscription; clearing the site's data in your browser removes the rest. Both remember your answer about usage data and crash reports. With Aga, both also keep the colors of your theme of the app and when your Aga ends, so that they open in it; signing out removes them. While usage data is on, they also keep the day, week and month Otag was last opened, so each device is counted once a day, week and month without any ID; the desktop app also keeps a crash report until it is sent. While usage data is on, the web app also keeps the campaign or website that brought you there until you close the tab, and sends it with your sign-up if you make an account there. On otag.chat's own pages, your browser keeps in its storage for that site your answer about counting and, once you allow it, the day, week and month a page was last opened, and the campaign or website that brought you there until you close the tab; no cookies are used for this. The one cookie otag.chat sets, otag_lang, keeps the language you pick in its menu for a year, so the pages open in that language; as it only does what you asked for, it needs no question.
- On your phone: the iPhone and Android apps keep your sign-in token, your settings and the keys they encrypt your calls with on your phone, and, once you turn on push notifications there, the keys they open them with. The iPhone app keeps the token and the keys in the phone's keychain, for that phone alone. The Android app keeps them encrypted with a key of the phone's own that never leaves it, and keeps all it stores out of the phone's backups. Signing out removes the token and the keys for calls; uninstalling the app removes your settings.
3. Who can see what
- Other people on Otag see your username, display name, avatar, your profile (what you write about yourself, your banner and card colors, the decorations you picked, the badges you show, Aga's sign while you have Aga unless you turn it off, and while you're online your status), whether you're online, away or busy (do not disturb) unless you appear invisible, the game you're playing unless you turn that off or appear invisible, and the messages, voice messages, files, stickers and reactions you post where they can read them (servers you share, group chats, direct messages), with the messages you pinned there and when. Polls aren't anonymous: everyone who can read a poll sees who voted for which answer. While you share your screen, the people who can see that voice channel see a small picture of what it shows. When you watch someone's screen share, they see that you're watching it (on a stage, they see how many watch, and up to 50 of them). In a server, its members see the nickname and picture you chose for it, a name effect you were given there, while it lasts, and, if you stoke it, how many of your kor burn there and since when. Everyone who opens the shop sees your name on the items you made for it. Your friends also see when you were last online, unless you turn that off. Anyone who knows your username can send you a friend request. They never see your email address, your date of birth, the notes you keep about people, the messages you save, your payments, your theme of the app, or what you hold from the shop and don't wear.
- Everyone on Otag can see a server listed in Discover and read the channels it opens to everyone, and anyone who has an invite link can see the server it leads to (see section 2).
- Server owners, and the members they give moderation permissions, can delete messages in their servers, remove or ban people from them, time people out (for a while, someone timed out can read the server but not write, react or talk there), keep a channel to one message every so often, and mute people in voice channels or move them to another one. Those who manage a server pick the role worn by those who stoke it, and once its fire burns at its second flame, members whose role lets them can give a member's name an effect for up to a week. Those allowed to view a server's audit log see what its moderators and managers did there in the last 90 days: who did what, to whom, and the reason they gave. When you're timed out, only you and the server's moderators see until when.
- Apps that a server's admins add see what their role there lets them see, and get what you do with them, as described in section 2. Their developers decide themselves how they use it.
- Our admins review reports and can see the reported content and accounts. To keep Otag safe and enforce our Terms of Service, they can also open any server on Otag, whether they belong to it or not: read all of its channels, private ones included, join its voice channels, and do anything its owner can, such as delete messages, remove or ban people, change its settings, hand it to another member or delete it. Its members don't see an admin who is only looking; they see the admin once the admin writes, reacts or joins a voice channel there. Nothing about an admin's look into a server is stored. When an admin removes something of yours this way, or hands your server to someone else, you get an email saying what and why. In a server they belong to or look into, they can also give a member's name an effect for up to a week. Admins show as admins wherever their name appears, and a server's own moderators can't remove, ban, mute or move them. Direct messages and group chats aren't part of this: our admins see them only when something in them is reported. In Otag's portal our admins also see who has Aga and until when, how each stretch of it came, and the applications and items of those who sell in the shop; in Stripe's dashboard, what section 2 says.
- Our service providers process data for us under data processing agreements, only on our instructions:
- OVHcloud runs the servers in Frankfurt, Germany, where all Otag data is stored, usage data and crash reports included. We run Otag and Koru Analytics on them with Koru hosting, our own hosting platform.
- The provider of the AI coding assistant our developers use sees a crash report's contents when they ask the assistant to help fix that problem, and the diagnostics you shared, without who they are from, when they ask it to help with yours. It may be outside the EU, such as in the United States; for that transfer we rely on the safeguards in its data processing agreement.
- Amazon Web Services (AWS) keeps backups of Otag's data in Frankfurt, Germany. The backups are encrypted before they leave our servers, so AWS can't read them. AWS belongs to a group based in the United States; for any transfer outside the EU we rely on the safeguards in its data processing agreement.
- Resend delivers our emails (codes, notices). It receives your email address and the email content. Resend is based in the United States; for that transfer we rely on the safeguards in its data processing agreement.
- Anthropic translates the messages of translated channels (see section 2). It receives the words of those messages and the language to translate them into, and nothing about who wrote or reads them. Anthropic belongs to a group based in the United States, where it may handle them; for that transfer we rely on the safeguards in its data processing agreement.
- Stripe takes the payments for Aga, kor and the shop (see section 2): Stripe Payments Europe, Limited in Ireland, with Stripe, LLC in the United States. It receives what you give in its card field and what our server sends it about each payment. For the transfer to the United States we rely on the EU-US Data Privacy Framework, which Stripe, LLC has joined, or, where that doesn't apply, on the standard contractual clauses in Stripe's data processing agreement. For some purposes of its own, such as preventing fraud and meeting the duties the law puts on it, Stripe decides itself how it uses this data, under its own privacy policy.
- Stripe, for those who sell in the shop, also provides their payout account, under its own agreement with them: it checks who they are, and handles the details they give it under its own terms and privacy policy (see section 2).
- KLIPY provides GIFs (see section 2). It isn't one of our service providers: your app talks to it directly, and KLIPY decides itself how it uses what it receives.
- Google signs you in when you choose Continue with Google (see section 2). It isn't one of our service providers either: you sign in at Google directly, and Google decides itself how it uses what it receives. Our server sends it only the one-time code of your sign-in, to learn who signed in.
- YouTube (Google) plays the music and videos people queue with Vibe (see section 2). It isn't one of our service providers either: your app loads its player directly, and Google decides itself how it uses what it receives. Our server sends it only what people search for.
- The push services of browsers and phones (Apple, Google, Mozilla and Microsoft, companies based in the United States) carry the push notifications you turn on, encrypted so they can't read them (see section 2). They receive your device's push address and the encrypted notifications.
- Authorities, when the law requires us to share data, for example under a court order. If we find a threat to someone's life or safety, we tell the police.
We never sell your data.
4. How long we keep it
| Data | How long |
|---|---|
| Account data | Until you delete your account |
| Messages, voice messages and reactions | Until you, or a moderator, delete them, or the server or channel they're in is deleted. When you delete your account, your messages stay, credited to "Deleted user". Delete messages first if you want them gone. |
| Votes in polls | Until you change or withdraw your vote while the poll is open, the poll is deleted, or the server or channel it's in is deleted. When you delete your account, your votes stay like your messages, credited to "Deleted user". |
| Pins: which messages you pinned, and when | Until the message is unpinned, or it, its channel or its server is deleted. The line saying you pinned a message stays like your messages, credited to "Deleted user" once you delete your account. |
| A deleted message | Its text and files are removed immediately. A record that a message existed (when, and from which account) stays so conversations remain consistent. |
| The random code your app can give a message as it sends it | 1 day, then removed within about an hour; sooner if the channel or server the message is in is deleted |
| Translations of messages in translated channels | As long as the message they translate, and until it is edited |
| Profile: what you write about yourself, banner, card colors, decorations | Until you change them or delete your account |
| Decorations you upload | Until you remove them or delete your account; those you add to a server stay with it until it removes them |
| Status | Until you clear it, or until the time you chose for it runs out (removed within about an hour) |
| Your nickname and picture in a server | Until you change them, you leave the server, or it is deleted |
| A name effect on your name in a server | Until it ends (a week at most), and up to an hour after; sooner if it is taken off, you leave the server, or it is deleted |
| Your badges: which you hold, their numbers, when you got them and which you show | Until you delete your account. Each one's line in the ledger stays for good, with only a fingerprint of your account, which leads to nobody once its secret is deleted with your account |
| Aga: the stretches you had, paid, given or claimed as a gift | Kept, also after you delete your account. For a stretch you paid for, Swedish bookkeeping law requires us to keep its record until the end of the seventh year after the year in which the financial year it was paid in ended |
| Payments: what each was for, its price, how it went and Stripe's numbers for it, with the number of your customer at Stripe (until you delete your account) and the notes of Stripe's messages our server took | Kept, also after you delete your account: Swedish bookkeeping law requires us to keep the records of a payment until the end of the seventh year after the year in which the financial year it was made in ended. A payment you started and didn't make is kept the same way |
| What you gave in Stripe's card field | At Stripe, under its own privacy policy and the laws on payments that bind it; deleting your Otag account doesn't delete it there |
| Your device's time zone | Not kept |
| The gifts of ours you claimed: which, and when | Until you delete your account. The kor a gift put on a server you own stay on that server until the gift ends |
| Kor: those that came to you, and those you gave | Kept, also after you delete your account. A kor you gave burns on its server until its 30 days end, also if you leave the server or delete your account; the record of one given to a server goes when that server is deleted |
| What you hold from the shop | Until a refund takes it back. It stays after you delete your account, and a numbered copy's number is never given to anyone else |
| Your theme of the app | Until you change it or delete your account; it stays kept while you don't have Aga |
| The copy of your theme on your device | Until you sign out, or the app finds your Aga has ended |
| Selling in the shop: your application, our answer, and which creator terms you accepted | Kept, also after you delete your account |
| The items you made for the shop | As long as people hold them. When you delete your account they leave the shop, and those who hold one keep it, credited to "Deleted user" |
| What your sales earned, the payouts we sent and your payout account's number | Kept, also after you delete your account: Swedish bookkeeping law requires us to keep the records of what we paid until the end of the seventh year after the year in which the financial year we paid it in ended |
| Emoji and stickers you add to a server | Until someone allowed to removes them, or the server is deleted. Deleting your account doesn't remove them. |
| Notes you keep about people | Until you change them or delete your account |
| A message you saved | Until you remove it from your saved messages, the message is deleted, or you delete your account |
| Files | Removed from storage within about two hours after nothing uses them any more (their message deleted, an avatar, banner or emoji replaced or removed) |
| Sessions | Until you sign out, or 30 days after last use |
| An account you started with just a name, before you set a password, confirm an email address or connect Google | Until its last session ends (you sign out, or 30 days pass without using it); it is then deleted within about two hours, as when you delete your account yourself |
| Your devices' keys for calls (the public halves) and their names | Until you sign out of that device, or its session ends |
| The Google account you sign in with: its ID, and the email address Google gave for it | Until you disconnect it or delete your account |
| What Google told us when you haven't finished making your account | 30 minutes |
| Two-factor sign-in: your authenticator app's secret, your passkeys and your recovery codes | Until you remove them, turn two-factor sign-in off or delete your account. A recovery code goes once it's used, and all of them when you make new ones. |
| A record of our admins turning off your two-factor sign-in: which admin did it, the reason and when | Until you delete your account |
| An authenticator app you started to set up but didn't finish | 30 minutes, then removed within about an hour |
| A sign-in waiting for its second step, a passkey's challenge, and the desktop app's hand-off to your browser | 5 minutes at most (a hand-off, 10), then removed within about an hour |
| Game activity | Only while you're connected and playing; never stored |
| The presence you pick | Until you change it or delete your account |
| Stream previews | Only the latest picture, in memory, for at most 90 seconds; deleted when your share ends |
| A call's encryption group (the public keys of the devices in it) | While the call lasts; deleted when it ends |
| On a stage, that you're in its audience, and a raised hand | Only while you're on the stage |
| Email codes | 15 minutes |
| Reports and moderation decisions | 12 months after the decision. Reports still waiting for a decision are kept until they get one. |
| Bans from a server | Until the server's owner or one of its moderators lifts the ban, or the server is deleted |
| A server's audit log | 90 days, then removed within about an hour; sooner if the server is deleted |
| A timeout | Until it ends, then removed within about an hour; sooner if the server is deleted |
| Friends, friend requests and blocks | Until one of you ends them (a block, until you lift it), or either of you deletes their account |
| Notification settings, read markers and the order of your servers | Until you change them or delete your account |
| A device that gets push notifications: its push address, keys, name and dates | Until you turn notifications off on it or remove it, you sign out of it or its session ends (30 days unused), you delete your account, or its push service tells us the address no longer works |
| Whether your notifications show what was written | Until you change it or delete your account |
| The newest message your phones were told of in a conversation | Until you read the conversation |
| That you agreed to a server's rules | Until you leave the server or it is deleted |
| Previewing a server | Only while you preview it; never stored |
| What you did with an app | On our server, 15 minutes, while the app can still answer it. The app keeps what it got under its own policy. |
| A voice room's queue in Vibe | While the room plays; deleted when the room empties or Vibe is taken out of the server |
| Apps you make | Until you delete them or your account |
| Pictures in apps' cards and forms | As long as the cards and forms that show them |
| Webhooks you make | Until someone allowed to deletes them, or their channel or server is deleted |
| A refused sign-up (under 15) | Nothing is stored |
| What you were shown and agreed to for a purchase, its confirmation, your withdrawal from it, and what we paid back of it when we suspended or deleted your account | For as long as we keep the record of the payment, the bookkeeping period: until the end of the seventh year after the year in which the financial year of the purchase ended. Deleting your account doesn't delete it. |
| Usage and performance data, website visits, and the server's service data | Up to 25 months |
| Crash and error reports, the server's own included | 90 days; the title of each kind of problem, which says what went wrong and where, stays with that problem's counts until 13 months after it last happened |
| Detailed reports on how screen shares and cameras went, from the apps and the server | 14 days |
| Diagnostics you share | 90 days, or until you ask us to delete them |
| Backups of all of the above, messages and files included | Up to 40 days more |
When you delete your account we remove your profile (what you wrote about yourself, banner, card colors, decorations and status), your nicknames, pictures and name effects in servers, your badges (each one's number stays taken, and its line in the ledger stays, leading to nobody), the notes you kept, the messages you saved, your email address, date of birth, avatar, password, your two-factor sign-in (the authenticator app's secret, passkeys, recovery codes and any record of our admins turning it off), the connection to your Google account, when you were last online, the presence you picked, sessions, the devices that got your push notifications, friends, friend requests, blocks, notification settings, read markers, the order of your servers, the lace you picked and your theme of the app right away. The decorations you uploaded for yourself go too, and the apps you made leave every server and are deleted; what they posted stays, credited to "Deleted app". Emoji, stickers and decorations you added to servers stay with those servers, like your messages, and so do your pins. If something you posted was reported, the report keeps a copy of it, without your name, because it is the evidence the decision rests on: the text until 12 months after the decision, attached files and pictures only until the decision is made.
These stay after you delete your account: the records of your payments and of the stretches of Aga you paid for, what each order showed you and what you agreed to, with its confirmation, your withdrawals and what we paid back, and, if you sold in the shop, what your sales earned, our payouts and your payout account's number, which Swedish bookkeeping law requires us to keep (see the table); and the stretches of Aga our admins gave you or a gift of ours gave you, the kor that came to you and those you gave, which burn on where you gave them, what you hold from the shop and, if you applied to sell there, your application and the creator terms you accepted. The items you made leave the shop, and those who hold one keep it, credited to "Deleted user". Deleting your account ends your subscription to Aga at Stripe at once and removes your customer record there; Stripe keeps its own records of your payments (see section 3). If Stripe can't be reached at that moment, we can't delete your account yet: try again a little later.
5. Children
Otag is for people aged 15 and over. When someone gives a date of birth under 15 at sign-up, we don't create the account and don't keep the answer. If we learn that an account belongs to someone under 15, we delete it. Parents and guardians who think their child uses Otag can contact us at support@otag.chat.
6. Security
Connections to our server are encrypted (HTTPS, and DTLS-SRTP for voice and video). Calls in voice channels are end-to-end encrypted too: the devices in a call agree its keys by MLS (RFC 9420), and each piece of sound and picture is encrypted with AES-GCM on the device that sends it. Passwords are stored with Argon2id and sign-in tokens only as hashes. Authenticator apps' secrets are stored encrypted, with a key kept apart from the database, and recovery codes only as hashes; a passkey's private key never leaves your device or password manager. Push notifications are encrypted for the device they go to (RFC 8291), so the push services that carry them can't read them. When you pay, your card's details go from Stripe's card field straight to Stripe, never through our server, and our server acts on Stripe's messages only after checking Stripe's signature on each. The web app's page may only run Otag's own code, and that code may only connect to our server, KLIPY and, once you allow usage data or crash reports, Koru Analytics; the page Vibe's player runs in may load only YouTube's player, and the page Stripe's card field runs in only Stripe's own code. Links to files are signed and expire after 24 hours; anyone who has such a link can open the file until then. Links to a server's emoji and stickers are signed too, and last as long as they do: anyone who has one can open its picture. No system is perfectly secure; if a breach puts your data at risk, we will tell you and the authorities as the law requires.
7. Your rights
You have the right to:
- get a copy of your data. Settings → Account → Your data downloads what your account holds, in a machine-readable format (JSON). It includes the records of your Aga, your payments, what each order showed you and what you agreed to, your withdrawals and what we paid back, your kor and what you hold from the shop and, if you sell there, your application, the items you made and what they earned;
- correct it: change your display name, avatar, profile and email in the app, or ask us;
- delete it: Settings → Account → Delete my account (on iPhone, You → Account → Delete my account). Our page Delete your account says how, with or without the app. If you pay for Aga, deleting your account ends it at Stripe;
- object to processing based on our legitimate interests, and ask us to restrict processing;
- withdraw your consent at any time where we rely on it (usage data, crash reports and counting on otag.chat), with the same switches, and for diagnostics you shared by asking us to delete them, with their reference; this doesn't affect what was done before;
- complain to the Swedish Authority for Privacy Protection (IMY), imy.se, or to the data protection authority where you live.
Write to support@otag.chat for anything the app doesn't do for you. We answer within a month.
If you live in Turkey
Under the Turkish Personal Data Protection Law (KVKK, Law No. 6698) you have the rights listed in its Article 11, including to learn whether your data is processed, to request information about it, to learn its purpose and who it is shared with at home and abroad, to have it corrected or deleted, to object to results produced solely by automated processing, and to claim compensation for unlawful processing. Apply to us at support@otag.chat; we answer within 30 days. If you are not satisfied, you can complain to the Turkish Personal Data Protection Authority (Kişisel Verileri Koruma Kurumu). Your data is collected electronically through the Otag apps and otag.chat's own pages, and stored in Germany; what you give in Stripe's card field when you pay goes to Stripe, in Ireland and the United States. The full notice in Turkish is our Gizlilik Politikası ve Aydınlatma Metni.
8. Changes
If we change this policy, we update the date at the top. For important changes we also email you.