AHV Chat Privacy Policy
Effective date: September 24, 2026 · Last updated: November 10, 2026 · Data controller: AHV HOLDING INVESTMENT JOINT STOCK COMPANY (“AHV Holding”, “we”, “us”).
This policy explains what data AHV Chat collects, why, where it is stored, for how long, and how you can delete it. It applies to every version of AHV Chat: the web app at ahvchat.com and the apps for Windows, macOS, Linux, Android and iOS.
- We don’t sell your dataWe never sell or rent your personal data to anyone.
- No adsAHV Chat shows no ads and does not use your data for ad tracking.
- Only what is neededData is used to run the chat service: deliver messages, sync your devices, keep your account safe.
- Delete it yourselfYou can delete your account and all of its data inside the app, at any time (section 7).
1. Data we collect
Account
- The username (@username) and display name you choose when signing up, and the account ID the system assigns.
- Password: stored only as a one-way hash (scrypt with a per-account salt). Nobody, including us, can read your original password.
- Email: signing up in the app does not ask for an email. An email is stored only for accounts an administrator created or linked to one (for example to sign in by email).
- Account creation date, account status (active or suspended), and when you agreed to the Terms of Use and this Policy at sign-up.
Reports and blocks
- When you report a message, a bot or a person: who reported, the reported account, the reason, your note, the time and a copy of the reported message (for a message in Chats: that message and the 4 messages before it) so administrators can review it (even if the message was deleted).
- The list of people and bots you blocked, so our servers can stop their messages from reaching you.
Messages and files
- Chat content: text messages, photos, videos, files, reactions, replies, buttons, and when they were sent or edited; in groups, also the group name, description and member list.
- Unsent drafts per chat, so your other devices open with the same words you were typing.
- Read status, pinned and muted chats, your chat folders (names, icons and the chats in them), and your settings (language, sounds, notification previews, night hours).
- If you create a bot: its name, @username, description and command list. The bot token is stored only as a hash.
Messages and files are stored on our servers so they can be delivered and so you can read them again on any device. Traffic between the app and our servers is always encrypted with HTTPS/TLS. Messages are not end-to-end encrypted, so our servers process their content in order to deliver them; we do not read your conversations except when needed to handle an abuse report or when required by law.
Messaging other people
- Messages and files between you and other people (the Chats tab): text, photos, videos, files, voice messages, replies, forwarded messages (with the original sender’s name), pins, times sent and edited, read status.
- Contacts: the people you add yourself and the private name you give them (only you see it). Your phone’s address book is not read or uploaded.
- Profile others can see: display name, @username, profile photo, a short bio (up to 140 characters) and last seen, as your Privacy settings allow.
- Privacy settings: who can find you by @username, who can message you, who can call you (Who can call me), whether calls may connect directly device to device (Direct calls), who sees your last seen time and profile photo, whether read receipts are sent.
Messages between people are stored on our origin server in Singapore so they can be delivered and so both people can see them on every device. Connections are always encrypted with HTTPS/TLS; messages are not end-to-end encrypted (like Telegram’s regular chats), so they can be synced, searched and restored. We do not read your conversations except when needed to handle an abuse report or when required by law. Bots cannot read conversations between people. Messaging does not reveal your IP address to the other person.
Voice calls between people
- Calls are not recorded and the server does not store call audio. The server keeps a call log: who called whom, when, for how long, how it ended, the kind of device that answered (for example "iPhone", "Windows") and a random ID of the device each side used for the call, connection quality measurements (delay, packet loss, jitter, whether the call went through the relay, the audio codec) and your rating if you give one; the log is kept for 365 days and then deleted automatically, and you can remove an entry from your own list at any time.
- Until the other person answers, audio and connection data always go through a relay machine, so your IP address is not revealed. After they answer, if both of you allow Direct calls (device to device), the two devices connect directly and each person’s IP address is visible to the other; choose Direct calls (device to device) = Nobody and calls always go through the relay.
- The call relay machine in Vietnam: when a call goes through it, it sees the IP addresses of both people (it needs them to forward packets), but the audio is still end-to-end encrypted (DTLS-SRTP) between the two devices: the relay only forwards encrypted packets and cannot listen. To use the relay, the app gets a short-lived ticket that carries your account number (not your name, email or phone number), so the relay machine’s logs can link an IP address to that account number; these logs are kept only to operate it and prevent abuse.
- You choose who can call you in Who can call me and who may connect directly in Direct calls, both in Privacy settings; someone you blocked cannot ring your phone. A missed call appears in your call list and as a line in the conversation.
- Calls to an iPhone use Apple’s call notification (VoIP push, via APNs) only to announce or cancel a call; it goes through Apple and may contain the caller’s name (and a link to their profile photo); it is never used for messages.
- Calls to an Android device use FCM only to announce or cancel a call, with the caller’s name encrypted as described above.
Sign-in sessions
- When you sign in, the server issues a session token, stored only as a hash, together with its creation time, expiry (90 days from its last use, renewed while you keep using it) and the browser/app identifier (User-Agent) so your devices can be told apart.
- On desktop and mobile the session is kept in the operating system’s protected storage (Keychain on iOS/macOS, Android Keystore, Windows DPAPI); on Linux, a file only your own user account can read. The app never stores your password. The web app uses a session cookie for signing in only — no advertising or tracking cookies.
- Signing in with your face or fingerprint (iPhone, Android, if you turn it on): the phone makes a key pair in its security chip that only that phone's own face or fingerprint check unlocks. The server keeps only the device's public key, with the kind of phone (iOS/Android), its name and when the key was made and last used; your face image and fingerprint never leave the phone — neither the app nor the server receives them.
- Changing your password signs out all your other devices and removes every face/fingerprint sign-in key you turned on.
IP addresses and access logs
- All traffic to ahvchat.com passes through Cloudflare (content delivery and attack protection). Cloudflare processes IP addresses, browser information and request logs under the Cloudflare privacy policy.
- Cloudflare passes our server an IP-based country code so we can route you to the nearest server; it is not stored with your account.
- Our servers use your IP address only transiently, in memory, to stop mass account sign-ups, and do not keep per-request access logs. Technical error logs may be kept for a short time to fix problems; they never contain passwords or tokens.
- The call relay machine in Vietnam sees the IP addresses of both people when a call goes through it (see Voice calls above).
Device tokens for push notifications
To tell you about new messages and calls while the mobile app is closed, the iOS app uses Apple Push Notification service (APNs) and the Android app uses Google Firebase Cloud Messaging (FCM). When you allow notifications, the app sends our server a device token issued by Apple/Google; the server uses it to ask Apple/Google to deliver the notification to your device. A notification may contain the sender’s name and, if you turn on Message previews, part of the message. You can turn notifications off in the app under Settings → Notifications or in your phone’s settings; the device token is deleted when you sign out or delete your account. On Android, the sender’s name, message excerpt and caller’s name are encrypted with a notification key unique to your device before being sent to Google. Google cannot read the content, but can still see technical data such as the device token, timing, notification size and IP address. This is not end-to-end encryption: the AHV Chat server can still read message content as before; this encryption only prevents Google from reading it. On desktop and on the web, notifications are shown by the app or browser itself, without any third-party push service.
Usage analytics
We will use Google Analytics for Firebase (GA4) in the apps to learn which features are used, which versions are running and where the app fails, so we can fix bugs and improve the product. This data includes: usage events (screens opened, features used), app version, device model, operating system, language, approximate country/region and a random per-installation identifier. It does not include message content, files, names, emails or passwords; it is not used for advertising and is not linked to Google’s advertising services. When analytics is turned on, the app’s Settings will include a switch to stop sending usage data.
2. Third-party bots
Many bots on AHV Chat are built and run by other users or organisations, not by AHV Holding. When you message a bot, the bot owner’s program receives the messages and files you send to that bot, together with your account ID, display name and @username. In groups, a bot only receives a message when it is mentioned (@bot), when you reply to one of its messages, or when you send it a command. A bot never receives what you send to other people or bots, and cannot message anyone who has not messaged it first.
Bot owners are responsible for how they handle the data they receive; some bots use artificial intelligence and may pass content to their AI provider. Only send a bot what you are comfortable sharing with its owner. Before you first message a bot that is not yours, the app asks for your explicit permission: the messages and files you send to that bot are processed by its owner and may be passed to a third-party AI provider; if you decline, nothing is sent. Your choice is kept per bot on our server and deleted with your account. If you delete a message before the bot has fetched it, the bot never receives it. A message the bot already received before you deleted it may still be kept by the bot owner’s program (for example, the bot still remembers it in its own session).
3. How we use data
- To create and maintain your account, sign you in, and sync messages and settings across your devices.
- To deliver messages between you, other users and bots, and to notify you of new messages.
- To keep the service safe: prevent abuse, spam and mass sign-ups; filter objectionable words in group messages and display names; enforce blocks; handle abuse reports within 24 hours.
- To fix bugs, measure performance and improve the app (aggregated statistics).
- To comply with legal obligations.
We do not use your data for advertising, do not build advertising profiles, and do not sell data.
Report and block inside the app
- Report a message: tap it (desktop: right-click) → Report → pick a reason; you can block the sender at the same time.
- Report or block a bot: tap the bot’s name at the top of the chat → Bot info → Report bot / Block bot. A blocked bot can no longer message you.
- Report or block a person in a group: the group’s info page → the menu next to their name → Report / Block. Their messages are hidden from you and they cannot add you to groups.
- Report or block a person in Chats: tap a message (on a computer: right-click) → Report, or use the bar "This person is not in your contacts" → Block / Report, or their profile page. Reporting a message sends that message and the 4 messages before it in the conversation to the moderators as evidence.
- A person you block is not told they are blocked: their messages do not reach you, and they cannot see your profile photo, last seen, read receipts or typing status. Files and photos from people who are not in your contacts are not downloaded automatically.
- Unblock in Settings → Blocked. Administrators are notified of every report at once and act within 24 hours.
4. Where data is stored
- The main server in Singapore stores accounts, sign-in sessions, settings, groups, conversations between people, and chats with bots hosted on the main server, along with the call log.
- The regional server in Singapore stores the messages and files of chats with bots hosted in that region, so users in Asia get their messages faster.
- The call relay machine in Vietnam forwards a call’s (encrypted) audio and connection data when needed; it sees the IP addresses of both people and does not store call content.
- Data passes through Cloudflare’s global network; push notifications go through Apple/Google; usage analytics (once enabled) is stored by Google.
Your data may therefore be transferred to and processed outside the country where you live. We apply the same level of protection wherever it is stored.
5. Sharing
We share data only in these cases:
- People and bots you chat with receive the messages you send them (see section 2).
- Infrastructure providers that work on our behalf and only under our instructions: server hosting providers (including the call relay machine in Vietnam), Cloudflare, Apple (APNs), Google (FCM, Firebase Analytics).
- When required by law, in response to a valid request from a competent authority, or to protect the safety of users and the service.
6. Retention
| Data | Kept for |
|---|---|
| Account, messages, files, groups, settings | Until you delete your account (or delete the related bot/group). Messages you delete disappear from every device at once and their content is erased from our servers; an attached file is erased once no other message uses it (the storage is freed); a copy you saved to Saved Messages is a separate copy and stays until you delete it. In conversations between people: "Delete for me and <name>" (the default, also when you select several messages or clear the history for both) erases the message content from our servers — only an empty "Deleted message" marker stays so devices stay in sync; an attached file is erased once no one holds it any more. "Delete for me" only hides the message from you; the other person keeps their copy; once both of you have deleted it for yourselves, its content is erased from our servers. A file you sent that the recipient still holds, or that was forwarded on to someone else, still counts toward your storage until its last holder deletes it; deleting it in "Manage storage" only removes your own copy. When you delete your account, the messages you sent in conversations with other people and the files you sent (including copies others hold) are erased; the other person keeps their own messages and the conversation shows "Deleted account"; your contacts, your privacy settings and every other person’s contact entry for you are erased too; messages others forwarded or saved to Saved Messages from you (their own copies) no longer show your name, photo or account ID but "Deleted account". Messages in bot chats that you deleted before our server update of October 4, 2026 were only hidden; their content is erased when you clear the history of that chat, delete that bot (if it is yours) or delete your account. Notifications already shown on your phone are not removed. System backups may still contain deleted data until those backups expire (usually within about 6 months); backups are only used to restore the service after a failure. |
| Call log | 365 days from the call, then deleted automatically. You can remove one entry or your whole call list at any time; once both people have removed an entry it is deleted from our servers. Calls from someone you have blocked are not shown to you and are kept on our servers for up to 365 days from the call, even if the caller removes the entry from their own list (unless either person deletes their account). Deleting your account deletes your call log too. |
| Sign-in sessions | 90 days from their last use, or until you sign out / change your password. |
| Public keys for face/fingerprint sign-in | Until you turn it off, change your password or delete your account; or until an administrator resets your password or locks the account; or until you turn on an 11th key (each account keeps at most 10 keys; the one unused the longest goes, and an old key not yet deleted still counts). When the phone can no longer use its key (a new face or fingerprint was added), you choose Forget this account, or you turn it off while offline, the app deletes the key on the phone and asks the server to delete it the next time you sign in on this device. |
| Abuse reports | Reports (including the excerpt) are kept after they are handled, as a record of how abuse was dealt with, until the reporter or the reported person deletes their account (and longer where the law requires it). When an account is deleted, reports it made are deleted; reports about it keep only the fact that a report was made, without the copied content. A report keeps an excerpt of the reported message, even if that message is later deleted; a message removed by administrators for abuse is hidden from everyone but its content is kept to handle the report. |
| Messages waiting for a bot | Deleted once the bot receives them, at the latest after 7 days. |
| Link preview images | Cached for up to 24 hours. |
| Device tokens (push) | Until you sign out, turn notifications off or delete your account. |
| Usage analytics | Up to 14 months in Google Analytics, then deleted automatically. |
| Technical error logs | Short term, only to fix problems. |
7. Account deletion and your rights
You have the right to access, correct, export and request deletion of your personal data, and to withdraw consent (for example by turning off notifications or usage analytics).
Delete your account inside the app
- Open AHV Chat (web, desktop or phone) and sign in.
- Tap your profile picture at the top of the chat list and choose Settings.
- Under Privacy and safety, tap Delete account.
- Read what will be deleted, enter your password again and tap Delete permanently.
Deletion takes effect immediately and cannot be undone. It erases from all our servers (the main server and every regional server): your account; every message you sent and received, including your messages in groups; files, photos and videos on disk; drafts, chat folders, settings, your block list and the reports you made; your call log (including the call lines in your call list and in the other person’s conversation); sign-in sessions and device tokens; the bots you own with all of their messages, files and pending updates. Groups you own pass to another person in the group (its earliest-joined administrator, otherwise its earliest-joined member); a group with nobody else left in it is deleted with all of its messages. The administrators’ log keeps one line saying an account deleted itself, with how much data was erased, and no content. The last administrator of the service must hand the role to someone else before deleting their own account. System backups may still contain deleted data until those backups expire (usually within about 6 months); backups are only used to restore the service after a failure.
If you can no longer sign in, email support@ahvchat.com from the email linked to your account (if any), stating your @username; we verify and delete as above within 30 days. Copies already delivered to bot owners or other people before that (for example a message a bot owner’s program already received) are outside our systems.
Short of deleting the whole account, you can also: delete messages (your own, or the bot’s messages in a chat with a bot), clear the history of a chat with a bot or of Saved Messages, delete a bot under My bots (which deletes that bot’s messages and files), leave groups, and change your password to sign out other devices.
8. Children
AHV Chat is not intended for children under 13 (or a higher minimum age required by the law where you live). We do not knowingly collect data from children under 13. If we learn that an account belongs to a child under 13, we will delete it. Parents or guardians can contact us at support@ahvchat.com.
9. Security
Connections are always encrypted with HTTPS/TLS; passwords, session tokens and bot tokens are stored only as hashes; files can only be opened through signed links that expire within seconds; the website runs under a strict Content Security Policy. No system is perfectly secure; if an incident affects your data, we will notify you as required by law.
10. Changes to this policy
When this policy changes, we update the effective date at the top and, for significant changes, tell you in the app. The latest version is always at https://ahvchat.com/privacy?lang=en.
11. Contact
AHV HOLDING INVESTMENT JOINT STOCK COMPANY
Email: support@ahvchat.com
Support: https://ahvchat.com/support
Website: https://ahvchat.com