KRACKO

KRACKO · A product by Klippers

Privacy policy

Last updated: 25 October 2026. This policy covers KRACKO at www.kracko.in and its Android app, which opens the same service in a supported browser. Klippers operates KRACKO. Contact contactklippers@gmail.com for privacy questions or data requests.

What stays on your device

Your chosen player name, preferences, optional-analytics choice and supported solo results are stored in browser storage where available. Local puzzle state is also used to run your game. KRACKO does not require a general player account for ordinary solo or friend-room play. Local storage is not an online account backup.

Online rooms and contests

The game server processes your player name, a randomly generated tab/session identifier, room membership, guesses, actions and results to run online games and reconnect players. Infection's optional room conversation also sends the text you submit to the server and other participants during the discussion phase. Other participants receive the name and game information intended for their match. Secrets are handled according to the selected game's rules. Do not put personal information in your display name or room messages.

If you choose to register for a hosted contest, we collect the name, email address and registration/contest details you supply. Registration records and contest results are stored separately from ordinary live room state. A contest registration is not required for ordinary solo or friend-room play.

Service statistics and technical connections

Our server counts connections and games to understand service operation. It uses the connecting network address as input to an approximate daily unique-connection counter. The current counter expires after 48 hours; it is a probabilistic count, not a table of stored raw IP addresses. Total connection/game counts remain as aggregate numbers. These server counters are separate from the optional PostHog usage statistics below.

Like other online services, our hosting and network providers receive technical request information, including network addresses and connection metadata, to deliver and protect the service. Server logs can contain connection, room and reconnect identifiers. We do not use these logs for advertising profiles.

Optional usage statistics

PostHog usage statistics are off by default. If you allow them in the home screen's “Optional usage stats” section, we send a random browser identifier, a limited campaign-source category, the chosen mode and basic play events such as starting or finishing a puzzle. Events go to PostHog US Cloud. We do not include names, email addresses, guesses, room answers, chat or raw URLs in these events. Session recordings and automatic click capture are not enabled.

We instruct analytics not to add IP/geolocation properties, although the provider still receives the network connection needed to accept an event. Do Not Track and Global Privacy Control suppress these events. Turning usage stats off stops future optional events and removes the local analytics identifier. It does not itself delete events already received by the provider. You can copy your usage ID in that same section before revoking it and use it for a deletion request.

Providers and disclosures

Vercel delivers the website, Render hosts the game server, and our Redis storage service holds contest records and aggregate counters. PostHog processes the optional usage events described above. These providers process the information needed for their service. Supported Android browsers and Google Play also operate under their own privacy notices and user settings.

The current Android release does not include advertising, payment or Google Play Billing SDKs, and does not request camera, microphone, contacts, precise location or advertising-ID access. Its manifest requests internet access. We do not sell player data or use it for cross-app advertising profiles. Other publishing platforms may have separate SDKs and disclosures; those do not describe the current Android release.

Retention

Local data stays until you remove it, the browser evicts it, or a relevant app control replaces it. Ordinary online room state is held in the running server while the room exists, including the game's reconnect period, and is removed when the room is cleared or the server restarts. A room is not a durable account backup.

Contest registrations, results and any contest archives remain until removed by the organizer or through a verified data request; there is currently no automated age-based purge for these records. The daily unique-connection counter expires after 48 hours, while non-identifying aggregate totals remain. Optional analytics and provider logs follow their configured retention and deletion processes; KRACKO does not currently impose one uniform automatic expiry across those systems. Contact us to request removal of identifiable data.

Control and deletion requests

You can change your display name, turn optional analytics off and clear KRACKO site data in your browser. The Android app uses browser-backed website storage, so clearing only the Android wrapper's storage may not clear KRACKO's browser data. Clearing site data can remove local progress, saved invitations, preferences and offline files.

For contest records or previously collected identifiable analytics, use our data request page or email contactklippers@gmail.com. Include only the details needed to identify the record, such as the contest ID and registration email, or your copied usage ID. We may verify ownership before removing records. If limited retention is necessary for a specific security or legal obligation, we explain it when responding. An aggregate count that can no longer identify a person cannot be located as an individual record.

Security and changes

Production web, game and analytics traffic uses HTTPS/WSS. Data is processed by the service; multiplayer is not end-to-end encrypted between players. No online service can promise uninterrupted availability or absolute security. We update this policy when behavior changes and show the revision date above.