Royaltalk, homeBack to Royaltalk

Your chats live on your phone. Here is everything else, in plain words.

Royaltalk Privacy Policy

Effective from: 21 November 2026

1. About this policy

1.1 Royaltalk is a social app for staying close to the people you choose. It is built and run by a small team of independent developers: Sayantan Das, Rathtala, Kanchannagar, Bardhaman, West Bengal 713101, India ("we", "us", "Royaltalk").

1.2 This policy explains what personal data we process when you use the Royaltalk app and the royaltalk.in website, why, on what basis, for how long, who else receives it, and how you can use your rights. It is our notice to you under India's Digital Personal Data Protection Act, 2023 and the rules made under it, and our privacy policy under the Information Technology Act, 2000 and the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021.

1.3 Words used here:

2. The short version

3. What stays only on your phone

3.1 Your chats, your photos, the names you give your connections, the About lines your connections send you, your disappearing-message settings, your letters for later until they open, and your private encryption keys are kept on your phone, in an encrypted database. They are not copied to our server, except the last messages of a chat that you, or the person you talk to, chose to include in a report (section 4.1).

3.2 Your SIM. Royaltalk works only while the SIM of the number you verified is in your phone (section 4.6). To check this, the app reads, on your phone, which SIM cards are active: each SIM's identifier on that phone, its slot, the operator's name and whether it is an eSIM. It keeps the one it needs on your phone. None of this is sent to our server. The app never reads your phone's IMEI, the SIM's serial number (ICCID) or its subscriber identity (IMSI).

3.3 Royaltalk switches off Android's own cloud backup for this data. So if you lose your phone or reinstall the app, your old chats cannot be brought back, by you or by us. Your account and your connections can come back (section 4.6); your old chats cannot.

4. What our server processes, why, and for how long

4.1 The table below is the complete list of personal data our server keeps.

DataWhy we process itHow long we keep it
Your name, as you enter it at set-up or change it laterTo set up and run your account. Our server never sends it to your connections: they see the name they gave you.While your account exists, then 180 days (section 8.3)
Your phone numberTo tie your account to a real Indian mobile number; to bring your account back when you set up again; to detect and stop fraud, abuse and impersonation; and to answer lawful requests (section 7). We store it in two forms only: a keyed hash, which lets the server find your account by your number, and a sealed copy, which the server can write but cannot open. The sealed copy can be opened only by us, with a key that is kept off the server, and only for the purposes in this row. The number is never stored in plain text in our database.While your account exists, then 180 days (section 8.3)
The number check: a one-time check code, and the result of the checkTo confirm that the SMS came from the number you gave. The code is kept only as a hash.Deleted when the check is used, or within about 15 minutes after it expires
The SMS you send to verify your numberIt reaches a receiving number we run, which passes the sender's number, the text, the time and the operator's message-centre address to our server, and nothing else. The SMS also stays in that phone's message inbox.On our server, only as the number check above. In the receiving phone's inbox, until we delete it
Your PIN, if you make one (8 to 12 digits)To bring your account back to a new phone only for you (section 4.6). We keep it only as a slow, salted hash, from which the PIN cannot be read back, together with the count of wrong tries and any waiting time.While your account exists
Your account's public keys, and each phone's sign-in tokenThe public keys let other phones start end-to-end encrypted chats with you; your private keys never leave your phone. The sign-in token proves each request comes from your phone; we keep only a scrambled (hashed) form of it.Keys: while your account exists; replaced keys are removed over time. Tokens: 7 days, then renewed
Your phone's device token for Firebase Cloud MessagingTo deliver notifications (section 5.3)Until the phone is removed from your account, Google tells us the token is no longer valid, or the account is deleted
Facts about your phone: maker and model (for example "Xiaomi Redmi 9i"), Android version, processor type, the Royaltalk version, whether Royaltalk's notifications are allowed, whether Android's battery saving limits Royaltalk, and whether it is the phone your number was verified onTo show your phone in Settings → Account → Linked devices; to find and fix problems on particular phones and versions. We never read your phone's IMEI, Android ID or advertising ID, or the name you gave your phone.While your account exists, then 180 days (section 8.3). A phone that is removed stays listed on the server as removed, so that it cannot sign in again, until the account is deleted
When your phone last connectedFor Linked devices, for security, and for the 30-day rule in section 8.2While your account exists
The network (IP) address your account and each phone were set up fromFor security: to investigate abuse and attacksWhile your account exists, then 180 days (section 8.3)
When your account was set up on a phone: we keep the dates your account was set up on a phone, that is the date and time of your first set-up, and of every later set-up of your number on a phone (after a reinstall, or on a new phone)To keep accounts safe: to see when an account moved to another phone, to look into abuse, fraud and complaints, and to answer lawful requestsWhile your account exists, then 180 days after it is deleted (section 8.3), and then deleted
Your connections: which accounts you are connected to, and since whenOur server must know which two accounts share a chat in order to deliver messages between them. It does not know the names you give each other.Until you or the connection deletes the account
Messages waiting for delivery: the encrypted message, plus who sent it, to which chat, when, and its sizeTo deliver the message. We cannot read its content.Deleted when the other phone receives it, or after 30 days if it is never collected. When a message is deleted uncollected, we keep only its id, chat, sender and time (never its content) for up to 30 more days, so that the sender's phone can show "Not delivered"
Invite codes and invite linksSo the person you invite can connect with you. A link carries a one-time key in the part of the address that browsers do not send to any server; our server keeps only a hash of that key. A link names neither you nor your number.An unused code expires after 10 minutes and an unused link after 24 hours, and each is then deleted; a cancelled link is deleted at once. A used code or link is kept, as the record of which two accounts connected, until either account is deleted
People you block: your account and the account you blocked, nothing elseSo our server can stop their messages, buzzes, letters for later and "online" from reaching you, and yours from reaching them, and stop them connecting to you with a code or link. The person you block is never toldUntil you unblock them, or either account is deleted
Reports you send from the app: the account you report, the reason you pick, when you sent it, whether you also blocked them, and, only if you turn on "Include the last 10 messages", the text of the last 10 messages of that chat, yours and theirs, with their times. Photos are never sent: a photo shows as "[Photo]"To look into the report, act on the account under our Terms and Community Guidelines, keep a record of how we handled it, and answer lawful requests. The person you report is not told that they were reported, or by whomThe included messages: deleted 180 days after we close the report. The rest of the report: 1 year after we close it. Kept for these times even if either account is deleted, as the record of a complaint
A claim on your number from a new phone (section 4.6): a hash of the new phone's keys, and when the claim beganTo run the 7-day wait, and to tell your phoneUntil the claim ends, and at most 30 days
When you are here, and when you were last here ("Online and last seen"): whether Royaltalk is open in front on your phone right now, the minute you last left it, and your choices about who may see thisTo show the heartbeat or "last seen" only to people you are connected with, and only when you also see theirsWhether you are here is never stored, only held while you are here. The last-seen minute is replaced each time you leave, and deleted when you turn "Online and last seen" off; our encrypted backups may still hold an older minute for up to 35 days
Requests you send us (emails, grievances, deletion requests)To answer them, and to keep a record of how we answered1 year after the matter is closed
Crash and start-up reports, while "Send crash reports" is on (Settings → Privacy; it is on until you turn it off): a random report number your phone changes every 30 days, whether the app crashed or how long it took to start, the Royaltalk version, the Android version and the phone model, and for a crash only the kind of error and the places in our code where it happened. Never your messages, your name, your number, your account or your phone's identifiersTo find and fix crashes and slow starts30 days, then deleted; they are not kept in our encrypted backups. Turning the switch off sends nothing more and clears the reports still waiting on your phone

4.2 Server logs. Like every internet service, our server writes logs: the time, the network (IP) address that connected, what was asked for (the route) and whether it worked (the status). We keep these logs for 180 days, in India, because the CERT-In Directions of 2022 require it, and then delete them. If the law requires a longer period, we will keep them for that period and say so in this policy. Logs never contain the content of your messages, your keys, your PIN, your phone number, an invite link's key, or anything you write.

4.3 Counts. Our server records totals each minute, such as how many people are online and how many messages were sent. These counts never name or point to a person. We keep them for about 400 days.

4.4 Backups. We keep encrypted backup copies of the server's data, in India, so that accounts are not lost if the server fails. A backup copy is overwritten or deleted within 35 days. Backups never hold your chats, because your chats are not on our server; the only message text a backup can hold is what someone chose to include in a report (section 4.1).

4.5 What we can never see, and what the app asks for. We cannot read your messages, photos, buzzes or letters, see the names you give your connections or the About lines they see, or know what you talk about, except the text of the last 10 messages of a chat that you, or the person you talk to, chose to include in a report (section 4.1). Today the app does not ask for your contacts, your location, your microphone or your files, and it never reads or sends SMS itself: the verifying SMS is sent by your own SMS app, after you tap Send. If a later feature needs one of these, the app asks at the moment you use that feature, says what it is for, and you can say no; this policy is updated before it ships. The app asks for:

4.6 Your number, your SIM and your PIN.

5. Other companies' software inside the app

5.1 QR code scanning. Royaltalk uses Google's ML Kit to read QR codes. The camera image is read on your phone and is not sent anywhere. Google states that ML Kit may send Google basic facts about the phone (such as maker, model and Android version), a per-installation identifier and how the scanner performs, to keep the scanner working and improve it, encrypted in transit, and that it does not pass this data to anyone else.

5.2 Picking your number from the SIM. At set-up you can pick your number from a screen shown by Google Play services on your phone. We receive only the number you tap.

5.3 Notifications (Firebase Cloud Messaging). Royaltalk uses Google's Firebase Cloud Messaging, as our service provider, only to deliver notifications. For this, Google receives a device token for your phone, an installation identifier, and the app's package and version.

5.4 Where you get the app. Royaltalk is offered as a download from royaltalk.in, and may also be offered through Google Play. If you install it from Google Play, Google handles the download and updates under its own terms, and may tell us totals such as the number of installs.

5.5 Google processes this data under its own privacy policy (https://policies.google.com/privacy), and may process it outside India. We pass Google nothing else about you.

6.1 Your consent. When you set up Royaltalk you agree to this policy, and you give us the data in section 4 for the purposes listed there, and for no other purpose. We collect only what Royaltalk needs to work. If we ever want to use your data for a new purpose, we will tell you first and, where the law requires, ask you again.

6.2 Without asking again, where the law allows: to comply with Indian law, a court order or a lawful request from an authorised agency; to respond to an emergency that threatens someone's life or safety; and for the purposes for which you yourself gave us the data.

6.3 Withdrawing consent. You can withdraw your consent at any time, as easily as you gave it, by deleting your account (section 8): Royaltalk cannot work without the data in section 4. Withdrawing consent does not make past processing unlawful. When you withdraw, we stop processing and delete your data as described in section 8, except what the law requires us to keep. You can also turn off Royaltalk's notifications in your phone's settings at any time; the app then cannot tell you about new messages while it is closed.

7. Who receives your data

7.1 We do not sell or rent your personal data.

7.2 Our hosting provider. The company that rents us the server, in India, stores the server's data for us. It processes data only to run that server, and for no purpose of its own.

7.3 Google, only as described in section 5: as our service provider for notifications (5.3), and through the Google software on your phone (5.1, 5.2).

7.4 Authorities. If a court, or an Indian government agency with legal power, lawfully orders us, we must give it the account data our server holds (for example your phone number, which we would open from its sealed copy, when your account was made, and when your phone last connected), within the time the law sets. We cannot give anyone the content of your messages: we do not have it. The only exception is the text of messages someone chose to include in a report, while we keep it (section 4.1). Inside our team, your phone number is used only for the purposes in section 4.

7.5 If Royaltalk changes hands. If our business is sold or merged, your data may pass to the new owner, who must keep the promises in this policy. We will tell you first, in the app or on royaltalk.in.

8. Deleting your account, and what we keep

8.1 In the app. Settings → Account → Delete my account. Tap Delete my account, then Delete, and enter your PIN if you use the app lock.

8.2 Without the app (for example, if you lost your phone). Use https://royaltalk.in/delete-account, or write to privacy@royaltalk.in from any email address with the phone number you used at set-up.

8.3 What we keep after a deletion, and why.

8.4 If the purpose ends. If we stop offering Royaltalk, we will delete your personal data, except what the law requires us to keep, and tell you before we do.

9. Your rights

9.1 Under Indian law you have the right to:

9.2 To use any right, write to privacy@royaltalk.in with the phone number you used at set-up. In the app, Settings → Profile shows your name and number, and lets you change your name. We may ask a question to make sure the request is yours. We answer within 7 days, and always within the time the law sets.

9.3 You also have duties: give true information, do not pretend to be someone else, and do not make false or frivolous complaints.

10. Children

10.1 Royaltalk is only for people aged 18 and over. We do not knowingly accept anyone younger, and we do not knowingly process a child's personal data.

10.2 If we learn that an account belongs to someone under 18, we will close it and delete its data as in section 8, keeping only what the law requires. If you believe a child is using Royaltalk, please tell us at privacy@royaltalk.in.

11. Grievance Officer, and complaints

11.1 Our Grievance Officer, who also answers questions about your personal data: Sayantan Das, grievance@royaltalk.in, Sayantan Das, Rathtala, Kanchannagar, Bardhaman, West Bengal 713101, India. You can also report someone inside the app: open the chat, tap ⋮, then Report.

11.2 We acknowledge a complaint within 24 hours and decide on it within 7 days, or faster where the law sets a shorter time (see section 7 of our Terms of Use).

11.3 If you are not satisfied with our answer, you may complain to the Data Protection Board of India, through its online platform, about your personal data. For a decision about content or your account, you may appeal to the Grievance Appellate Committee set up under the IT Rules, 2021, within 30 days of our decision.

12. Security, and if something goes wrong

12.1 Messages, photos, buzzes and letters for later are encrypted on your phone before they leave it, with RTrivetX, Royaltalk's own implementation of the X3DH and Double Ratchet protocols. The app talks to our server only over an encrypted connection (HTTPS). The first time two phones connect, each trusts the keys it receives, as most messaging apps do; when you connect by QR code or invite link, the app also checks the other phone's keys against a fingerprint carried inside the code or link. Chats on your phone are kept in an encrypted database. Your number is kept as a keyed hash and a sealed copy, and your PIN only as a slow hash. Access to our server is restricted to our team.

12.2 No system can be made perfectly safe, and we cannot promise that a breach will never happen. What we promise is the process: if we learn of a breach that affects your personal data, we will look into it at once, limit the harm, and tell you without delay what happened, what it may mean for you, what we are doing, and what you can do. We will also report it to the Data Protection Board of India and to CERT-In within the times the law sets.

13. Where Royaltalk is offered, and where data is kept

Royaltalk is offered only in India for now. Our server and its backups are in India. Google may process the data described in section 5 outside India.

14. Changes to this policy

If we change this policy in a way that matters to you, we will tell you in the app, or on royaltalk.in where the app cannot show it, before the change takes effect, and ask again for your consent where the law requires. The date at the top shows the last change. Earlier versions are available on request.

15. Contact

Questions about this policy: privacy@royaltalk.in.