Privacy policy

Controller

KingPlay is published by Charles Pestel, 6 route du Parc, 14860 Ranville, France. For personal-data questions: privacy@kingplay.fr.

Browsing and security data

Using the site involves technical information required to deliver, protect and diagnose the service, including hosting requests and technical logs. These data are not used to build an individual advertising profile.

Account, profile and authentication

If you create an account, KingPlay processes information required for authentication and account recovery, your public username, optional avatar, adult declaration and settings needed for your space. Supabase provides authentication and associated persistence.

Account activity

While signed in, KingPlay may record operations needed to run your account: latest authenticated activity for a short-lived online state, private progression or wallet-operation history when present, favourites, onboarding state, announcement read markers and accepted terms versions. These items do not become public.

For free benefits, the server records credits, the calendar date in Paris and, when awarded, the welcome offer slot. This lets us credit each account once, track balances and prevent duplicate grants. Offer position is private.

Profile image

If you upload a photo or logo, the public image is normalised and its metadata removed before use. You must have the necessary rights to share it.

Games, scores and rewards

Plinko is publicly announced and can be played from an eligible account. Reward ordering remains closed. For a future opening, KingPlay is preparing server-side security and risk checks that may use operational facts such as account age, reward-request and economic-adjustment history, and verified game results. A future dedicated multi-account signal is designed to retain a technical evidence digest rather than raw data such as email, phone or a device fingerprint. These controls remain internal to KingPlay: no individual risk score is shared with partners or advertisers. No production threshold or real reward delivery is active today.

When Plinko is available, drops generate technical session records and server-calculated results. Completed daily missions and any related credits appear in the account’s private history.

Recipients and providers

Data access is limited to the publisher and providers needed for the service, notably Google Cloud for hosting and Supabase for database and authentication. Your email provider is involved if you contact us. Partners and advertisers do not receive your real identity for targeting.

Legal bases

Delivering the site and managing accounts rely on steps needed to provide the requested service. Security, abuse prevention and platform protection rely on legitimate interests where applicable. Legal obligations rely on law. Optional tracking that requires consent would be subject to your prior choice.

Retention

Account data are kept while the account is active, then deleted, anonymised or retained only where required for an obligation, security or legal defence. The latest-activity marker replaces the previous timestamp and is not a browsing-history log. Technical log periods depend on provider security and operating settings.

Local storage and preferences

The browser may remember language, theme, collapsed or expanded sidebar state, welcome guide, sounds, the identifier of the last update viewed and, if enabled, an optional update reminder for 180 days. These items serve the experience on this device and are not sent to the server to build a reading history. A promotional pop-up can store a session marker on this browser to avoid repeating during the visit. The PWA may cache an offline page and icon without caching private account data.

Plinko stores the last launch position, tutorial choice and the reference needed to resume a drop in the browser. These support play without advertising tracking. Results and credits are handled on the server.

Cookies and optional categories

No third-party audience measurement, profiling or advertising targeting tool is loaded today. If an optional category appears, KingPlay will update this information before activation and, where consent is required, make accepting, refusing and withdrawing a choice comparably easy.

The Google AdSense verification tag and public ads.txt file associate the site with the publisher account. These verification elements load no advertising script, set no cookies and are not a consent request. AdSense advertisements are not served in this version. Before activation, the applicable information and consent mechanism will be prepared and verified.

When first-party partner ad measurement is offered, it is optional and remains inactive without consent. Use Privacy preferences to refuse or withdraw a choice. Refusing does not affect play, points or tickets.

Your rights

You may request access, correction, erasure, restriction or portability and object to certain processing, subject to applicable conditions. Write to privacy@kingplay.fr. You may also complain to the French data protection authority, the CNIL.

Changes to this policy

This policy evolves with the product: every major release reviews data, purposes, providers, local storage, cookies and visible features. Candidate code or an internal screen alone does not change the description of the public service until it is actually active.

Professional B2B enquiries

The Partners and Advertisers pages may let a professional submit a private enquiry. KingPlay then processes the request type, organisation, professional contact name and email, optional HTTPS website, subject, message, language and a technical submission reference. These details are used only to review and follow the B2B relationship; they are not shown to players, grant no access to player accounts and automatically trigger no publication, campaign, payment or reward. Data are kept for the time needed to process and follow the professional relationship, protect the service and, where applicable, defend legal rights.

Professional relationship management may also include the contact’s job title and role, professional details, opportunity stages, a dated next action, notes and records of exchanges, references and audit records. These data remain in private administration and support enquiry handling and commercial follow-up; text templates are internal and do not send messages automatically. Entries must be limited to information useful for this professional relationship, without private player data. Retention is reviewed according to follow-up needs, applicable obligations and the defence of rights; archiving a template is not proof of erasure.

Transfers and subprocessors

A technical service’s primary region is not, by itself, a promise that no support or subprocessing can occur outside that region. KingPlay describes providers according to the information that genuinely applies and does not claim absolute data residency without matching contractual evidence.

Erasure and anonymisation

Closing an account starts the KingPlay erasure workflow. Some records required for consistency, security, a legal obligation or legal defence may be retained on a limited basis or anonymised. Complete erasure is confirmed only after applicable dependencies have been verified.