Cookie Policy

CoomeChat Cookie Policy

This page names every cookie CoomeChat sets, says what each one does, and explains what is stored in your browser beyond cookies. Section 7 of the Privacy Policy covers the same ground in categories; this page gives the specifics.

Effective DateSeptember 19, 2026
Last UpdatedSeptember 19, 2026

Cookies here are set when the page opens, before you tap anything. That includes the analytics cookie. You can block or delete all of them in your browser, and Section 5 explains what stops working if you do.

1. What This Page Covers

A cookie is a small piece of text a site stores in your browser and reads back on your next request. Browsers also offer other storage — local storage, in particular — which is not technically a cookie but does a similar job. Both are covered here, because from your side the distinction rarely matters.

CoomeChat has no account to sign into, so cookies do less here than on most sites. There is no login you stay signed into across devices and no profile being tracked between sessions. What is stored is listed below in full.

This page is specific to CoomeChat. For everything else about data — what the person on the other end of a call can see, what we hold about a call, how long it is kept — read the Privacy Policy.

2. Cookies We Set

These are set when you open CoomeChat, before you tap start and before any conversation begins. There are five.

CookieSet byWhat it is forHow long
ACCESS_TOKENCoomeChatIdentifies the anonymous guest session created when the page loads, so a match can start without a sign-up.Persists between visits until you clear site data
device_fingerprintCoomeChatA value derived from your browser’s characteristics, used to act on abuse reports and enforce blocks.Persists between visits; derived rather than stored, so clearing does not reset it
C_UACoomeChatRecords which client and version you are on, so the right build and the right fixes are served.Persists between visits until you clear site data
_gaGoogle AnalyticsDistinguishes one browser from another so visits can be counted without identifying anyone.2 years (Google’s default)
_ga_8JE0KMPYTQGoogle AnalyticsKeeps analytics session state for this specific property.2 years (Google’s default)

Why there is a session token without a sign-up

ACCESS_TOKEN looks like a login cookie, and in a sense it is one — but it is not yours to create. CoomeChat signs you in as an anonymous guest the moment the page loads, so that a match can start in one tap rather than behind a sign-up form. That guest session is what the token identifies. It carries no name, no email and no phone number, because you were never asked for any.

The device signature

device_fingerprint is a value derived from your browser's own characteristics rather than something assigned to you. Its purpose is abuse control: it is what lets us act on a report against someone who simply reopens the page to get around a block. Section 3.1 of the Privacy Policy covers it in more detail, including the part worth knowing here — because it is derived rather than stored, clearing site data does not reset it.

3. Analytics

CoomeChat uses Google Analytics 4, and it is the only third-party script the site loads. There is no advertising pixel, no social network tag and no session-replay tool. The two _ga cookies in the table above belong to it.

It loads when the page opens, at the same time as everything else, and it is not conditional on anything you do. We would rather say that plainly than describe it as something that happens later.

What it is used for, and what it is not:

  • Used for: how many people arrive, which pages they open, roughly which country they are in, and which devices and browsers need to keep working.
  • Not used for: advertising profiles, retargeting, or selling anything about you. We do not run ads on this site.
  • Never sent to it: anything from inside a call. Video, audio and chat are not part of analytics and never reach Google.
  • Reported in aggregate. We look at totals and trends, not at what one person did.

If you would rather not be counted at all, the browser controls in Section 5 stop it, and Google publishes its own opt-out browser add-on that works across every site using Google Analytics.

4. What Else Is Kept in Your Browser

Beyond the five cookies, CoomeChat keeps a set of values in your browser's local storage. Unlike cookies these are never sent to a server on their own — they stay on the device and are read by the page itself. They fall into four groups.

Session and account

The guest session created on load, and the same device signature described above. This is what lets you reopen the page and carry on rather than starting over.

Your settings

Language, and the match preferences you set. Kept so you do not set them again on every visit.

Interface caches

Configuration the app would otherwise re-download every time — things like the current set of in-app items and layout settings. These are copies of public data, not information about you.

Safety and first-run state

Whether you have confirmed you are 18 or over, and whether you have been through the first-run screens. Without these you would be asked again on every single visit.

We have described these by purpose rather than listing every key by name, because the names are internal and change between releases while the purposes do not. Clearing site data for CoomeChat clears all of them.

5. Blocking and Deleting Them

Every browser lets you block cookies, delete them, or clear all data for a single site. In Chrome, Safari, Firefox and Edge it sits under privacy or site settings. Private or incognito windows discard everything when the window closes.

Because there is no account here, nothing you lose by clearing is recoverable from us — there is nothing on our side to restore it from. What actually happens:

Block all cookiesVideo calls stop working. The session token is what a call is held open against.
Block third-party cookies onlyNo effect here. Every cookie in the table is set by this site, including the two analytics ones.
Clear site data for CoomeChatGuest session, settings and caches are gone, and you start as a new visitor. The device signature is derived rather than stored, so it is not affected.
Use a private or incognito windowEverything is discarded when you close the window. The site works normally while it is open.
Install Google’s analytics opt-out add-onAnalytics stops counting you, on this site and every other site using Google Analytics. Nothing else changes.

Browsers also send a Do Not Track or Global Privacy Control signal if you enable one. Support for these is inconsistent across the wider web, and we would rather point you at the browser controls above, which work regardless.

6. Changes to This Page

The list in Section 2 describes what the site sets as of the Last Updated date at the top. If we add or remove something, this page is where it changes, and the date changes with it. A material change to how analytics works will also be reflected in the Privacy Policy.

7. Contact

Questions about anything on this page, or a request about data held about you, go to [email protected].

Related Pages

© 2026 CoomeChat. All rights reserved.