Designed to protect
- Message content in private matched 1:1 threads — end-to-end encrypted.
- Phone number — not required; start with a temporary name for random chat.
- Contact address books — not scraped for “find friends” growth.
Privacy architecture
Chatkode privacy architecture — plain language
This page explains what kinds of data are involved when you use Chatkode random chat, what private matched threads are designed to protect, and where to read the formal policy.
Needed to run the product
- Temporary session identity so Match/Skip random chat can work in the browser.
- Optional claim (email or Google) within 24 hours if you want to keep chats under the same user ID.
- Basic service operation data required to deliver a reliable browser app.
- Optional marketing-site analytics only if you accept cookies — see Cookie policy.
Your controls
Use Match/Skip, Block, and Report during random chat. Add app lock, hidden chats, and disappearing messages when the risk is a nearby screen. Request access or deletion via privacy requests.
Ready to Match?
Random chat that’s private — no phone number. Match, Skip, encrypted 1:1. Claim your account in 24 hours.
Start Random ChatFrequently asked questions
Does Chatkode sell my data?
Chatkode is built as a privacy-first random chat product, not an ads-driven social network. See the Privacy Policy for how data is handled.
Where is the formal privacy policy?
Read privacy.html for the full policy, and data-request.html to contact us about privacy requests.
Is analytics required?
No. Marketing-site analytics load only after you accept. Decline is remembered so the banner does not return every visit.