Privacy Policy

Review draft · 2026-11-killer-case-draft-1 · Effective date pending approval.

Available reference: English draft. Translations have not been legally reviewed or approved.

Scope and operator

This draft describes implemented application flows, not a guarantee about unverified hosting configuration. Zekto Technologies is the public developer brand; the legal operator, privacy contact and effective date require verification before an approved policy is published.

Account information

Authentication processes email and credentials and associates an internal user UUID with your profile. The application uses account usernames, optional game display names, avatar/character appearance and preferences. Administrative account views may display an existing optional phone field; the current registration form does not request a phone number. Do not provide unnecessary personal information in names or messages.

Gameplay and social records

The backend maintains rooms, membership, match participation and outcomes, necessary private game state, friend requests, invitations, presence, histories, achievements, rewards and rankings. Authorized participants receive only their permitted private role view. Public profile settings affect eligible profile/ranking visibility; other participants still need appropriate room identity information.

Text chat and sent recordings

Chat is scoped to a lobby or particular match. Text and deliberately sent voice recordings are processed in authenticated relay/storage. Source code provides cleanup at lifecycle transitions and a scheduled three-hour expiry for ordinary relay content; operation of the deployed cleanup schedule requires verification and is not promised as an absolute deletion deadline. Access-limited audio URLs can remain usable until their short expiry.

Live microphone audio

LiveKit transmits live voice after joining and explicitly enabling the microphone. The application separately supports recorded audio messages, so it would be inaccurate to say no audio is ever stored. The inspected application does not implement automatic whole-room recording; media-server recording configuration, infrastructure logs, processing location and contractual retention still require owner verification. Local listener mute does not disable another participant’s microphone.

Safety evidence

A reported message or explicitly sent recording may be copied into protected moderation evidence; this is separate from ordinary chat cleanup. Source retention settings specify 30-day report/evidence expiry, but scheduled enforcement must be confirmed. Decisions, penalties and non-content audits may remain for safety and appeals; the final retention schedule is not approved. Live voice incidents can be reported through descriptions rather than a claim of undisclosed recording.

Technical information and services

Lovable Cloud provides the current account/database/storage infrastructure, and the app is hosted through Lovable. LiveKit provides the media protocol/service integration. The application includes error reporting and presence/connectivity handling, and loads fonts from Google Fonts. Network services necessarily process requests; exact production logging, location and retention must be reviewed. No optional analytics or AdMob SDK collection is asserted active by this document.

Advertising and purchases

Manual-campaign settings exist, but production advertising remains gated; AdMob/native consent are planned, not active integrations. Optional advertising consent must be separate from registration. Future store processing must verify purchases server-side before granting benefits; transaction/status and entitlement records may be retained. The app does not implement storage of full payment-card details. No real checkout is currently available.

Purpose, sharing and security

Information supports authentication, authorized gameplay, communication, social features, progression, fraud prevention, moderation and requested purchases. Intended recipients include relevant participants and necessary service providers; private roles and safety evidence are restricted. Server authorization, RLS and limited audio URLs are protections, not a promise of perfect security. Applicable legal bases and contractual provider disclosures require review for distribution territories.

Retention and choices

Account/progression records persist independently of temporary chat. You can edit eligible profile details, choose supported language, manage friendships and use microphone/listener controls. The deletion-request page records a verified account’s request for owner review; no instant erasure promise is made. Shared match data, safety evidence, transactions and audits need a retention/anonymization assessment, as do backups and provider records. Access, correction, objection and other applicable rights require a verified contact and operational response process before production.

Children, international processing and updates

Age eligibility, child-privacy requirements, processing regions, cross-border safeguards and response timelines are not yet approved. This available English draft is the reference version; no legal translation is represented as reviewed. Approved updates must include effective date, version and verified contact details.