Privacy Policy

1. Who is responsible for the data

The data controller is Vladyslav Nesterov, a private individual and citizen of Ukraine (the “Developer”, “we”). Processing follows the law of Ukraine, including the Law of Ukraine “On Personal Data Protection”. For any question about your data, write to the email address at the bottom of this page.

2. Account data

Using Squeek requires an account. For it we store:

• your email address — it is your login; at sign-up we send it a confirmation code, and you cannot sign in until it is confirmed;
• your password — only as a cryptographic hash (bcrypt); we do not store the password itself and cannot see it;
• the name and username other users see, plus an avatar and a short profile description if you add them;
• your public encryption key and your private key encrypted with a twelve-word recovery phrase. Only you have the phrase; we can neither decrypt that key nor recover the phrase;
• your plan and the settings you change in the app (for example, hiding the typing indicator).

3. Sessions, devices and notifications

To keep sign-in secure and deliver notifications, we store technical data about your devices:

• for each sign-in — the IP address, device and app details (user agent), the time of sign-in and of the last activity; a session is kept until you sign out or it expires;
• the push notification token, platform and device name — so notifications reach your phone;
• confirmation codes sent by email are stored as a hash, are valid for a short time and are then deleted;
• when you sign in on a new device we ask, besides the password, for a code sent to your email. A device where the code has been entered gets a trust mark: it is kept on that device, lasts 180 days and is cancelled when the password is reset or the key replaced;
• the list of devices your account is open on is shown in the app, and any session can be ended there;
• if you add another device by scanning a code in the app, it receives your keys and full access to your conversations — the same as the main one.

4. Conversations: what we are technically able to see

Different kinds of conversations are protected differently, and that difference is what decides what the Developer can access.

• Private chats and groups are end-to-end encrypted: messages and files are encrypted on your device and decrypted only on the participants’ devices. The server holds only ciphertext and a key wrapped for each recipient, and has no technical means to read the content.
• Channels and the discussions beside them are encrypted on the server with a key held by the Developer. Their content, polls and message reports are technically accessible to the Developer. We do not read them as a matter of routine, but we cannot claim we are unable to.
• For every conversation the server sees service data: who is in which chat, who sent a message and when and how large it is, reactions (emoji), read marks, pins, edits and deletions, self-destruct timers, and system messages — who joined or left, calls and their duration. These are not encrypted.
• Scheduled messages wait on the server until their time: in encrypted chats they are already encrypted, like any other message.
• Bots. A bot is an account run by another user’s program. A bot added to a group or channel receives a copy of every message from the moment it is added, and in a private chat with a bot — everything you write to it. Its owner sees that, not the Developer. Participants get a system message when a bot is added.
• Squeek’s official bots — the ones in the bot catalogue in the app (voice to text, text to speech, text from photos, background removal, stickers) — belong to the Developer. What you send them is processed on the Developer’s servers by our own models, with no third-party AI services. Files are held only in memory while they are processed and are not stored, and the logs carry only sizes and durations, never content.
• Voice-note transcripts. When you tap “Aa” under a voice note, your phone sends its audio to the Developer’s server, where the same model as the official voice bot turns it into text. The audio is held only in memory while it is processed and is not stored; the text comes back to your phone and is kept only there. Without that tap a voice note goes nowhere.
• Messages sent to a bot through its webhook link reach the server in the clear from whoever called the link, and are encrypted for the recipient only after that.
• Link previews. When you send a link, your phone itself opens that page, takes its title, description and a small image, and sends the card along with the message — encrypted in encrypted chats like everything else. The linked site sees your IP address, as with any ordinary visit; recipients and the Squeek server do not open the page. Link previews can be turned off under “Privacy and security”.

5. Calls

Audio and video calls (WebRTC) are encrypted between the participants’ devices. To find a path to each other the apps exchange network addresses, so your IP address becomes known to the other party. When possible, the devices connect directly. When no direct path exists (for example, both phones are on mobile networks), the stream goes through a relay (TURN) on the Developer’s server: it forwards encrypted packets without the key to the audio and video, and sees only the parties’ IP addresses and the amount of data passed. Google STUN servers are also used to discover network addresses. The Squeek server relays signalling — who calls whom, when, whether the call was accepted and how long it lasted.

• Group calls, channel broadcasts and meetings by link go through a media server on the Developer’s server. It sees the participants’ IP addresses, who is in the call and when, and whether their microphone, camera or screen sharing is on; you do not see other participants’ IP addresses.
• In groups and in meetings by link, audio and video are encrypted with a key only the participants know: in a group their devices hand it out, in a meeting it is part of the link itself. The media server forwards encrypted packets and cannot listen to or watch them.
• Channel broadcasts are not end-to-end encrypted, just like channels themselves: their audio and video are technically accessible to the Developer on the media server. We do not record or watch them.
• Anyone with a meeting link can join it; if the host turned on the waiting room, only once the host lets them in.

6. The copy on your device

So that chats open instantly, the app keeps a decrypted copy of your conversations and downloaded files in its protected storage on the device, and the keys in the system’s secure storage. That copy is as safe as the device itself: anyone with access to the unlocked phone can read it. Its size is shown in Settings, where it can also be cleared. You can also turn on an app lock with your phone’s fingerprint, face or PIN: the check is done by the system itself, and biometric data never leaves the device or reaches us.

7. How long it is kept

The server is not an archive of your conversations. The periods are:

• messages and files stay on the server for a limited time that depends on the sender’s plan: 90 days from sending on the free plan, 180 on Premium, 365 on Premium Plus. After that they are deleted from the server for good; the copy on your device stays;
• if a chat has a self-destruct timer, messages are deleted from the server when it runs out;
• messages you delete by hand are emptied at once; only an empty record remains so that replies to them keep their link;
• account data is kept for as long as the account exists; the volume of files sent per month is counted to enforce the plan;
• server logs are kept for the limited time needed for security and troubleshooting.

8. Notifications and email

To get messages through, we rely on third-party delivery services:

• push notifications go through Expo Push Service (Expo, USA) and on through Google Firebase Cloud Messaging or Apple Push Notification service. Message text never goes into a notification — only the sender’s name or the chat name, the fact of a new message, a mention or a reaction;
• confirmation emails are sent through Resend (Resend, Inc., USA), which receives your address and the contents of the email for that purpose.

9. Server logs, metrics and updates

To run the service we process a minimum of technical data and use no third-party analytics or advertising trackers — neither on the website nor in the app.

• the web server keeps standard request logs for the site, the API and downloads: IP address, time, requested address, browser or app details;
• we collect anonymous service metrics — counts of connections, messages, uploads, calls, notifications and emails sent — with no content and no link to individual people;
• the Android and desktop apps ask squeek.net whether a newer build exists and download it from there when you say so; those requests land in the site’s logs like any other.

10. What other users see

Some data is visible to others by the nature of a messenger:

• your name, username, avatar and profile description — to anyone; you can be found in search by username;
• whether you are online and typing (the typing indicator can be hidden on a paid plan), and whether you have read a message;
• when you were last online. You can hide the exact time in settings — others then see only “recently”, “this week” and so on, and you no longer see the exact time of others either;
• your membership in groups and channels — to their participants; groups and channels are visible in search by default and anyone can join unless the owner requires a request or an invitation;
• bot owners see what their bots receive (section 4).

11. Who we share data with

We do not sell data and do not share it for advertising. Data is processed only by those without whom the service does not work:

• the hosting provider whose servers Squeek runs on;
• Cloudflare (Cloudflare, Inc., USA) — the network every request to the website and the Squeek server passes through. It sees IP addresses and technical request data, and technically has access to the same things as the server: service data and channel content, but not the content of end-to-end encrypted conversations;
• Resend — email delivery; Expo, Google and Apple — push notification delivery; Google — STUN servers during calls (sections 5 and 8);
• Ukrainian public authorities — only where the law expressly requires it. We cannot hand over the content of end-to-end encrypted conversations, because we have no access to it.

12. Your rights and controls

Under the law of Ukraine you have the right to know what data about you is processed, to have it corrected or deleted, and to object to processing. To exercise them, write to the email address below. In the app itself you can:

• change your name, avatar and profile description;
• delete your messages for all participants and set self-destruct timers;
• block users — a blocked user cannot message or call you; leave groups and channels; hide private chats;
• see the devices your account is open on and end any session;
• turn off link previews and turn on the app lock;
• clear the local copy of conversations and files in Settings;
• delete your account — in your profile, confirmed with your password. We erase the profile, keys, sessions and everything you sent, files included; groups and channels you owned are deleted and your bots are switched off. Messages already delivered to other participants remain on their devices, and in shared chats they see “Deleted account” where your name was.
• if you do not have the app at hand, you can ask for your account to be deleted by writing to the address below from the account’s email. We will delete it just as completely within 30 days and reply once it is done.

13. Security and its limits

Data between the app and the server travels over an encrypted channel (TLS), passwords are stored as hashes, and encryption keys are created on your device and leave it only encrypted with your recovery phrase. At the same time Squeek is a beta product: we do not guarantee the absence of vulnerabilities. A forgotten password can be reset with a code sent to your email. A lost recovery phrase can be replaced with a new key, but the history of end-to-end encrypted conversations sealed with the old key stays inaccessible — neither we nor you can restore it. We will announce incidents affecting your data that come to our knowledge in the app or on the website.

14. Age of users

Squeek is intended for people aged 18 and over. We knowingly collect no data about children; if we learn of an account belonging to someone under 18, we will delete it.

15. Changes to this Policy

We update this page as the product evolves; the date of the current edition is shown at the top. We announce material changes in the app or on the website. Continuing to use the service after a change takes effect means you accept the new edition.