Privacy Policy

Other people see your anonymous nickname, your Vibe Match score, shared interests, and whatever your Privacy settings allow (country, gender, bio, interests, online status, verified badge — all on unless you turn them off). They never see your email address, phone number, account ID, device information or real name unless you tell them yourself.

Guests have no Privacy settings, so the gender a guest picks (and their country, if set) is shown to the people they chat with. Voice calls connect the two browsers directly, so the other person’s device can technically see your IP address during a call.

• Guest sessions: a random session token, your nickname, the preferences you pick, a hashed (not raw) IP address, browser type, and the times you were active. Guest sessions expire automatically.
• Accounts: email, username, a password hash (Argon2id — we cannot read your password), profile details you enter, interests, languages, friends, blocks and settings. If you sign in with Google or Apple we receive your provider ID, email and name.
• Conversations: text messages, reactions, reply links, delivery/read times, and the media you share (stored in private object storage). Messages are kept so conversations, reports and moderation work; guests’ message history is retained for a limited period.
• Voice calls: only metadata — when a call started, connected and ended, its duration, and connection quality. We do not record audio.
• Safety data: reports you send or receive, blocks, moderator actions, and automated signals such as spam or suspicious-link detection.
• Technical data: hashed IP, browser type, approximate device fingerprint, and error logs — used for abuse prevention and reliability.
• Premium purchases: the name, email and billing address you enter at checkout, the card brand, last 4 digits and issuing country (the full card number stays with Stripe or Razorpay — we never see it), whether the bank authenticated the card, the IP address and browser used for the purchase, the time you accepted the Terms, and any refund or dispute. We use this to send receipts and to prevent fraud and answer chargebacks; for a chargeback we share these purchase records and how the account used Premium with the card network through Stripe.

Authorised moderators can open a text conversation for review when it is reported, when automated safety signals flag it, or as part of limited random quality checks. Each time this happens we create an audit record containing the moderator’s ID, the conversation ID, the time, the reason, and any action taken. Chitmet does not record voice calls. If you report a voice call, your own device sends the last few minutes of that call (kept only in your browser’s memory while the call runs) to our moderators as evidence; only the person who reports can send it. Moderators can listen only with a written reason that is logged, and each clip is deleted seven days after upload once the report is closed.

Photos, GIFs, videos and voice notes are stored in a private bucket. They are only viewable through short-lived signed links given to the two people in that conversation (and to moderators when a review is opened). Files are checked for type and size before they are accepted.

Profile photo (members only, optional): if you add one, it is resized in your browser (location data and other metadata are stripped), stored in the same private bucket and shown next to your nickname to the people you chat with and to your friends. You can hide it (Settings → Privacy → Show my photo) or remove it at any time; removing deletes the file. Moderators review new photos; a photo that breaks the Community Guidelines is hidden immediately, you are notified, and the file is deleted after 30 days.

If you press Keep in Touch, the other person is not told. Only if you both press it do you each see that it is mutual.

We use strictly necessary cookies to keep you signed in (as a guest or with an account) and to protect against request forgery.

We also use the Meta Pixel and Meta’s Conversions API to measure our ads on Facebook and Instagram. The Pixel sets a Meta advertising cookie (_fbp). Meta receives an event when you view a page, the first time in a browser session that you open a chat, and when a Premium payment through Razorpay is confirmed, along with technical details such as the page address, your IP address, browser type and Meta’s cookie IDs. Our code never sends chat content, messages or voice audio to Meta. Browser tracking protection or an ad blocker can stop the Pixel and its cookie, though the same events may still be sent to Meta from our server.

• Guest sessions: until they expire (about 30 days after last use), then they are deleted.
• Accounts: until you delete your account, after which personal data is removed within 30 days except where we must keep records for safety or legal reasons.
• Reports, bans and moderation logs: kept longer so repeat abuse can be recognised.
• Payment records and receipts: kept for as long as tax and accounting law requires (up to 8 years), even if you delete your account.

• Change your anonymous nickname at any time.
• Control what your profile shows and who can reach you in Privacy settings.
• Block anyone; blocked people are never matched with you again.
• Revoke media permission in any conversation.
• Ask us to export or delete your data through the Help page.

We use infrastructure providers (hosting, database, object storage, email delivery), Razorpay and Stripe for payments, Meta for the ad measurement described under Cookies and, when enabled, translation and human-verification providers. They process data only to provide those services. We never sell personal data and never show advertising based on your conversations.

Privacy questions or requests: use the Help page.