This policy explains what data the Blyk messenger collects (the apps for iOS, Android, Windows, macOS and Linux, the web version at app.blyk.chat and the website blyk.chat — "Blyk", "we"), why we need it, who receives it and how you can control it. By using Blyk you agree to this policy. If you do not agree, please do not use Blyk.
1. Who we are and how to reach us
Blyk is run by the Blyk team. For any question about your data, write to contact@blyk.chat or to the Support account in the app.
2. What we collect
Account data. Your email address, password (we keep only a strong bcrypt hash, never the password itself), @tag and display name. Optionally: bio, avatars, banner, birthday (the year is optional), profile music, status and other profile styling. If you turn on passkeys or two-factor authentication, we store your device's public key or the one-time-code secret — never biometric data, which stays on your device.
Sign-up application. While Blyk is in closed testing, moderators review sign-up applications. For that, the IP address, device type, platform and time of sign-up are stored with the application. The same data helps us limit mass registrations.
Device data. To prevent more than three accounts on one device, the app sends an installation identifier, and the web version sends a hash of general browser characteristics (screen size, time zone, CPU core count, graphics card, installed fonts). The server stores only irreversible hashes of these values.
Sessions. For each sign-in: the device name reported by the app (for example "Chrome on Linux"), platform, last IP address, sign-in time and last activity. You can see and end sessions in Settings. When you sign in on a new device, we email you the time, device and IP address. We do not determine your location from your IP.
Messages and files. Message text, attachments (photos, videos, voice and video messages, music, files), reactions, and call records (who called whom, when, how long, whether it was a video call). Calls themselves are not recorded.
Contacts. Your contact list in Blyk lives inside the app: you add people yourself and can give them your own name and a note. We do not upload your phone's address book.
Payments. If you buy a Blyk Flare subscription or brawls, we keep the invoice: amount, currency, product, payment provider, transaction number and status, plus the country and currency you selected. You enter card or crypto-wallet details on the payment provider's side — we never receive them.
Reports and requests. When you report a message, we keep your report, comment, an excerpt of the message (up to 1,000 characters — including from a private chat, if that is what is reported), its author and your IP address. A bug report you submit contains its text, steps, app version, platform, device, language, a screenshot and a redacted log excerpt. Support requests are kept as a conversation.
Automatic error reports. If the app crashes, it sends us a redacted report (without your conversations). You can turn these off in the app settings. Blyk has no third-party analytics or trackers.
Technical logs. Our servers keep operational logs for troubleshooting and protection against attacks; they may contain IP addresses. Server metrics are collected without identifying users and are kept for 30 days.
3. How data is stored and protected
Data is stored on Blyk's servers. Connections to the app are encrypted (TLS); files additionally travel over a separate channel where every part is encrypted on its own (AES-256-GCM), and links to files expire.
4. Why we use data
- to run Blyk: delivering messages and calls, syncing devices, notifications;
- to protect accounts and the service: sign-in, email confirmation, new-sign-in alerts, protection against spam, bots and mass registrations;
- for moderation: handling reports, restrictions and bans for breaking the Terms of Use;
- for search: by @tag, name, bio, email (exact match only) and by message text in your chats;
- for payments and providing paid features;
- to answer your requests and fix bugs.
We do not sell your data and we do not show ads.
5. Who else sees data
Other users see your profile as your privacy settings allow (your email is hidden from everyone by default) and your messages in the chats where you sent them.
Blyk moderators. To handle reports, moderators see excerpts of reported messages. Staff can view messages in groups and channels; they do not read private chats.
Bots. A bot receives your ID, name, @tag and avatar. In a private chat with the bot and in groups it was added to, a bot reads all messages; on servers, it reads the channels its roles allow. Bots are made by third-party developers, and data a bot receives is handled under its owner's rules.
Sign in with Blyk apps. With your permission, a third-party app receives your ID, name, @tag and avatar — not your email. You can disconnect an app in Settings.
Providers Blyk relies on:
- Cloudflare — protects the website and servers from attacks; traffic passes through it, and it may check that you are not a robot;
- payment providers Platega, xRocket Pay and Cluecat — receive the amount, currency and product name; you give them payment details directly under their rules;
- KLIPY — GIF search: receives your search query and a pseudonymous identifier (not your name or email); the GIFs themselves reach you from our servers;
- Resend email service — may be used to send emails (sign-in codes, security notices);
- jsDelivr — the app loads emoji images from this network;
- STUN servers (Google, Cloudflare) — help set up a call connection and see your IP address;
- browser push services — receive an encrypted notification that only your browser and we can read. It contains the sender's name, the chat title and the beginning of the message.
Speech recognition (voice message transcripts) runs on our own servers or right on your device — recordings are not sent to anyone else.
Link previews are fetched by our server, not your device — the linked website sees our server, not you.
Telegram import. If you link Telegram to bring over stickers and emoji, we keep your Telegram ID, username and name.
6. How long we keep data
Account data and conversations are kept while the account exists. In particular:
- a deleted message disappears for everyone and its text is erased, but a record of it (and its attachments) is kept for 72 hours to handle possible reports;
- a deleted chat or community is deleted together with all its messages;
- a group's action log is kept for 365 days;
- verification codes are valid for 5 to 30 minutes, unpaid invoices for 1 hour;
- server metrics — 30 days.
7. Deleting your account
To delete your account, write to Support in the app or to contact@blyk.chat from the address linked to the account. Deletion erases your name, @tag, bio, avatars and other profile data, ends all sessions and removes the account from search. Messages you sent to other people stay in their chats — without your name. The email address is kept so that an account deleted for violations cannot immediately be registered again.
8. Your rights
You can:
- view and change your profile data and privacy settings in the app;
- find out what data about you we keep and get a copy;
- correct inaccurate data;
- ask us to delete your account and data, unless keeping it is required by law or to protect other users' rights;
- revoke access for bots and third-party apps;
- turn off automatic error reports.
Send requests to contact@blyk.chat. We will reply within 30 days.
9. Cookies and browser storage
The website blyk.chat stores one cookie — your chosen language. The web version app.blyk.chat does not use cookies: sign-in data is kept in browser storage (localStorage, IndexedDB) on your device and is removed when you sign out or clear the site's data.
10. Children
Blyk is not intended for children under 14. If you learn that a child under 14 uses Blyk without their parents' consent, write to us and we will delete the account.
11. Changes to this policy
We may update this policy. The current version is always published at blyk.chat/privacy, with its effective date at the top. We will announce significant changes in the app in advance.