Privacy Policy
Last updated: 16 November 2026
A messenger holds what people say to each other. This policy says exactly what Whiskr does with it, and with everything else we need to run the service.
1. Who is responsible
The controller is Nerqis Ltd, a company incorporated under the laws of the Republic of Cyprus, registration number HE487200, registered office at 7 Magdanis Street, Flat/Office 101, Kato Polemidia, 4152 Limassol, Cyprus.
Questions about this policy, and requests under it, go to [email protected].
2. The short version
- Nobody can find you. There is no people search, no phone number, and no address book upload. Your name and photo are visible only to your contacts and to members of groups you share.
- Calls are end-to-end encrypted; messages are not, in this version. Messages are encrypted in transit and stored on our servers so that several devices, history and the web version work. End-to-end encryption for chats is planned and is not yet available.
- We do not read your messages. Our team sees a message only when somebody reports it, together with a few messages around it for context.
- No advertising. No advertising identifier, no advertising SDK, no third-party script and no cookies on this website. We do not sell personal data and we do not use it to train anybody's models.
- Usage statistics are our own, and never about who you talk to. We count how the apps and this website are used — installs, launches, screens, sign-ins, subscriptions — on our own servers, with no analytics company involved. Nothing about your messages, contacts, chats or calls is part of it, and you can switch it off in Settings → Privacy (section 3.9).
3. What we collect, and why
3.1 Your account
You sign up with Apple, with Google, or with an invite from someone who already uses Whiskr — then we know who invited you, and that person becomes your trusted contact until you change it: they can issue you a one-time code to sign back in, and see nothing else of your account. Another device signs in with a QR code from one already signed in. With Apple or Google we receive an identifier from the provider and, where you allow it, your name and email address. The address is used only to recognise the same person signing in with Apple and with Google; nobody else sees it and we send no email to it. We never see a password. We do not ask for a phone number and do not store one.
Your profile — a name, an optional photo and an optional "about" line — is shown only to your contacts and to members of groups you share. Your privacy settings (for example, who sees when you were last online) are stored with the account.
Basis: performance of the contract (art. 6(1)(b)).
3.2 Contacts, invitations and groups
Who is in your contacts, the name you gave each of them, who you blocked; the invitation links you created — stored as a hash of the code, with their expiry, use limit and use count; the groups you belong to, your role in them and when you joined or left.
Basis: the contract.
3.3 Messages and attachments
The messages you send and receive: text, photos, videos, files, voice and video notes, replies, forwards, edits, reactions, and read and delivery state. Files are stored in object storage and opened only through signed links that expire within minutes.
When a message contains a link, our server fetches the page to build a preview, so that the site never receives the IP address of the person who received the link.
Typing indicators are not stored: they exist only in memory, for a few seconds.
Basis: the contract.
3.4 Calls
The content of a call — voice and video — travels directly between the two devices, or through a relay when a direct connection is impossible, and is encrypted from one device to the other (DTLS-SRTP). We cannot hear or see it and we do not record it.
What we do keep is the record of the call: who called whom, whether it was voice or video, when, how long it lasted, how it ended, and whether it needed the relay to connect. It appears in the chat as a call message.
Basis: the contract, and our legitimate interest in calls that connect (art. 6(1)(f)).
3.5 Devices and notifications
For each device signed in to your account: a session, the platform and app version, the time of the last sign-in, and the push tokens Apple, Google or your browser issued so that messages and calls can reach it. You can see your devices and end any session in Settings.
Notifications show the sender and the message text unless you turn that off, in which case they say only "New message".
Basis: the contract.
3.6 Reports
When you report a message, a person or a group, we store the report, the reported content and a few messages around it, so that a person on our team can decide what to do.
Basis: our legitimate interest, and our obligation as a service, in keeping it free of abuse (art. 6(1)(f), 6(1)(c)).
3.7 Running the service
Technical records: error reports, and server logs containing an IP address and the time of a request. These exist to keep the service working, to find faults and to stop abuse. The text of messages and invitation codes are kept out of logs.
Basis: our legitimate interest in a service that works and is not abused (art. 6(1)(f)).
3.8 Subscriptions
Whiskr Plus and Whiskr Max are sold through the App Store and Google Play. The payment itself — your card, your billing address, the receipt — is handled by Apple or Google, and we never see payment details.
From the store we receive and keep: which plan you have, when it started and when the current period ends, whether it renews, cancellations and refunds, the price and currency of each charge, and the store's own identifiers for the purchase. We use them to turn the paid features on and off, and to answer questions about a payment. The notifications the stores send us about a purchase are kept as they arrived, as a record of what the store said.
Basis: the contract, and our obligation to keep accounting records (art. 6(1)(b), 6(1)(c)).
3.9 Usage statistics
To know whether Whiskr works for the people who use it — how many install it and keep using it, where they found it, which screens they reach, where they give up, whether the app crashes — the apps, the web version, this website and our server record usage events and send them to our own server. No analytics company receives them; they are kept by us and by our hosting and storage providers listed in section 5.
What is recorded:
- in the apps and the web version: the first launch after an install and where the install came from (the store, or the campaign named in a Google Play install link or an Apple Search Ads advert), app updates, when the app is opened and closed and for how long, which screen was shown — by its name only, such as "settings" or "chat", never which chat or whose profile — that a notification was received or opened and its kind (a message or a call, not who sent it or what it said), that a link into the app was opened and whether it was an invite to a contact or to a group (never the invite code, whose invite it was or which group), and that an error happened (its kind and whether the app closed, not its contents);
- on our server: that an account was created or signed in and how (Apple, Google, an invite, a sign-in code, a QR code), that an account was deleted, and subscription events — a purchase, renewal, cancellation, expiry or refund, with the plan, the store, the price and currency;
- on this website: which page was viewed, for how long and how far it was scrolled, clicks on the store and web-version buttons, and the site that sent you here and the campaign tags of the address, if any;
- with every event: the platform, the device type (phone, tablet, computer), the operating system and app version, the interface language, the country — worked out on our server from the IP address, which is then discarded and never stored with the event — and identifiers: once you are signed in, a random identifier of your account made for usage statistics alone (not your account number, and nothing in Whiskr accepts it or shows it to anyone), and a random identifier of the installation or browser. To tell a reinstall from a new install, the iPhone app also keeps a random key in the device's Keychain and the Android app sends a one-way hash of the device's Android ID combined with the app's name; neither can be reversed into anything about you.
- about the account, under that random identifier: the day it was created, the platform it was created on, and whether it belongs to our team or an app reviewer (so that we leave those out of the counts).
Never recorded: the content of messages, calls, photos or files; who you write to or call, your contacts, chats and groups, or how many of them you have; invite codes; your name, email address, phone number or IP address.
Raw events are kept on our server for up to 35 days and then in our own object storage, where they hold only the identifiers above. Daily totals (such as how many people opened the app) are kept indefinitely. When you delete your account, the record that ties its random identifier to its properties and devices is erased; archived events keep only that identifier, which no longer leads to you.
Country lookup uses IP to country data by DB-IP, licensed under CC BY 4.0.
Basis: our legitimate interest in understanding whether the service is used and works, measured by us alone, under random identifiers, without content and without advertising (art. 6(1)(f)). That is why there is no consent banner — and why you can object at any time, without giving a reason:
- in the apps and the web version: Settings → Privacy → Share usage statistics. It is a setting of your account: turned off, every device signed in to it stops recording and drops what it has not sent yet, and our server records nothing more about the account either — no sign-ins, subscription events or error reports — until you turn it back on. Only the fact that an account was deleted is still recorded, because that is what erases its record;
- on this website: the switch below, which applies to this browser only (the website does not know your account);
- by email to [email protected], if you also want what was already recorded under your account taken out.
4. What we do not collect
- your phone number, or your phone's contacts;
- your location (only a country, from the IP address, for usage statistics — section 3.9);
- an advertising identifier, or anything from a third-party analytics or advertising SDK;
- the content of your calls.
5. Who we share it with
Inside Whiskr: your messages go to the people you send them to; your profile is visible to your contacts and members of shared groups.
Outside: with the service providers below, each under a data processing agreement, each acting only on our instructions.
| Provider | What it does | Where |
|---|---|---|
| DigitalOcean | Servers and database | Amsterdam, the Netherlands (AMS3) |
| Cloudflare | Storage for files (R2), the relay for calls that cannot connect directly, and the network in front of our domains | EU and outside the EEA |
| Google — Firebase Cloud Messaging | Delivering notifications and incoming calls to Android devices | Outside the EEA |
| Apple — Push Notification service | Delivering notifications and incoming calls to iPhones | Outside the EEA |
| Your browser's push service | Delivering notifications to the web version, if you allow them | Depends on the browser |
| Apple, Google | App distribution, sign-in, and payment for subscriptions | Outside the EEA |
We also disclose personal data where the law requires it, and where it is necessary to establish or defend a legal claim. If we are ever compelled to hand something over, we will tell the person unless we are prohibited from doing so.
We do not sell personal data and we do not share it for advertising.
6. Transfers outside the European Economic Area
The providers marked above as outside the EEA are in the United States. Those transfers are covered by the European Commission's standard contractual clauses, or by the EU–US Data Privacy Framework where the provider is certified under it, together with the additional measures we assess as necessary. You can ask us for the details at [email protected].
The database holding accounts, contacts, chats and messages is hosted in Amsterdam, the Netherlands (AMS3).
7. How long we keep things
| What | How long |
|---|---|
| Messages and their attachments | Until they are deleted — for yourself, for everyone, or with the chat |
| The sync feed that brings your devices up to date | 30 days |
| An attachment whose upload was never completed | 1 day |
| Typing indicators | Not stored |
| Your account, profile, contacts and files | Until you delete the account — then deleted immediately |
| Your subscription and its payment history | Until you delete the account; cancelling a subscription does not delete them |
| Notifications the stores send us about a purchase | As long as accounting and tax law requires; they carry the store's identifiers, not your name or contact details |
| Usage statistics (section 3.9) | Raw events up to 35 days on our server, then in our archive identified only by random identifiers; daily totals indefinitely; deleting the account erases what ties the identifier to you |
| A report and the content attached to it | As long as needed to handle it and any appeal, and to stop repeated abuse |
What deletion actually removes, and what stays with the people you wrote to, is set out in Account Deletion and Data Retention.
8. Your rights
You can ask for a copy of your data, for a correction, for deletion, for the processing to be restricted, for your data in a portable form, and you can object to processing based on our legitimate interests — for usage statistics, with a switch in Settings → Privacy (section 3.9).
Several of these are controls in the app rather than emails to us — how to use each one is in Your Data Rights.
You also have the right to complain to a supervisory authority. Ours is the Office of the Commissioner for Personal Data Protection in Cyprus; you may also complain to the authority where you live.
9. Automated decisions
Whiskr makes no decision about anybody that produces a legal effect or anything similarly significant, and it does not profile people. Reports are decided by a person.
10. Children
You must be at least 16 to use Whiskr. If we learn that we hold the data of somebody younger, we delete the account.
11. Security
Traffic is encrypted in transit with TLS. Calls are encrypted from device to device. Data is encrypted at rest by our hosting and storage providers. Files are reached through links that are signed and expire within minutes. Every device has its own session, which you can end at any time. Access to production systems is limited to those who need it, and our administrative tools show message content only for reported messages.
If a breach occurs that is likely to result in a risk to people's rights, we notify the Office of the Commissioner for Personal Data Protection within 72 hours and, where the risk is high, we notify the people affected directly.
12. Changes to this policy
If we change how we use personal data in a way that matters — including when end-to-end encryption for chats arrives — we will update this policy and tell you in the app before the change takes effect. Where the change needs your consent, we will ask for it rather than assume it.
13. Contact
Nerqis Ltd, 7 Magdanis Street, Flat/Office 101, Kato Polemidia, 4152 Limassol, Cyprus.
Privacy: [email protected]
Supervisory authority: Office of the Commissioner for Personal Data Protection, Cyprus
Questions about this document?
Write to [email protected]. For anything about your own data, [email protected] reaches the same people faster.