← Back to Seven to King Français

SEVEN TO KING

Privacy policy

Controller and contact

Seven to King is published by an individual acting in a personal and non-professional capacity. The publisher is responsible for the processing they determine for the game and can be contacted at Contact-Seven-to-King@protonmail.com. The conditions for identifying the publisher are described in the legal notice.

Playing without an account

No account is needed to play, and the game does not ask for your email address to start a match. Bot decisions, solo statistics, and solo replays are calculated in your browser. The game code does not send solo matches to the multiplayer server.

Loading the site does send the hosting provider the technical information needed for the connection, including your IP address and HTTP metadata sent by your browser.

Local saves and preferences

Browser storage keeps your selected preset avatar, sound setting and volume, animation setting, and manually selected language. In Very Hard mode it can also keep the game and the data needed to resume it. Other difficulty levels stay in the tab’s memory. Session markers prevent multiplayer results you have already seen from being shown again.

The game does not set an expiry date for preferences or the local save. They remain until replaced, removed by the game, or cleared by the browser or user. Session markers last for the tab’s storage session, subject to the browser’s restoration options.

You can clear Seven to King data in your browser’s storage settings. This removes the relevant preferences and the ability to resume locally. It does not delete data already held in server-side lobbies.

Nicknames, avatars, and lobbies

To play with friends, you choose a nickname of 1 to 24 characters and an avatar from the available portraits. Avoid using your real name if you do not want to share it. The service processes this information, lobby, member, connection, action, and match identifiers, presence, card choices, and game state to support duels, spectators, seat changes, rematches, and reconnections.

The server knows the cards and choices necessary to run the duel. Other lobby members see nicknames, avatars, presence, public duel information, results, and resolved rounds. Before resolution, each player receives only their own choice, and spectators receive no secret choice. Replays are restricted to participants and authorized observers of the match. Match nicknames and avatars may remain in replays after someone leaves or changes seats.

Technical cookie and invitation links

The stk_<identifiant-du-salon> cookie identifies you in a lobby. It is limited to that lobby’s path and protected by the HttpOnly, Secure, and SameSite=Strict attributes. Its maximum lifetime is seven days after issue or reissue when creating or joining a lobby. The game code does not renew it on each round.

The server stores a hash of the identification secret. Invitation links contain a lobby identifier and an access token in the URL fragment. This fragment is not automatically sent with the initial HTTP request. The game reads it and sends the token when it joins the lobby. Share your invitation only with the intended people.

At your request the game can copy a link or a recap to your clipboard. It does not read other clipboard contents. If you then share a recap, recipients can access the nicknames and game information you send them.

Server-side game retention

A lobby is scheduled to expire after 24 hours without qualifying activity. Some actions, connections, state requests, and replay views reset that period. Connection keepalive exchanges do not reset it. A lobby in regular use can therefore be retained for more than 24 hours. The current code sets no overall maximum from creation.

On expiry, the service closes connections and deletes the lobby’s application storage when the alarm runs or an access detects the expiry. New archives are normally limited to twenty previous unprotected matches, in addition to the current match and any older archives preserved for compatibility. New detailed round histories are limited to 2,048 rounds, with exceptions for protected archives. Archives that fall off the retained list are deleted from application storage.

The two-minute seat reservation concerns seat availability, rather than deletion of personal data. Leaving a lobby, clearing the cookie, or waiting for it to expire does not immediately delete old matches or server-side member information.

These application retention periods are separate from Cloudflare’s technical mechanisms. Its documentation describes a point-in-time restore feature for Durable Objects SQLite storage over the previous thirty days. This capability neither extends access to replays in the game nor guarantees that all copies will be erased by a particular date. The game does not call this restoration feature. Any technical backups or copies follow the provider’s terms.

Technical data and abuse prevention

Cloudflare receives information including the IP address to route requests and protect the service. The API uses a SHA-256 hash of the IP address to limit abusive requests. This is pseudonymization, rather than a guarantee of anonymity.

Application counters keyed by hash use sixty-second windows and their stored data is scheduled for deletion at expiry. A global lobby-creation counter uses a twenty-four-hour window. The service also keeps recent command receipts to avoid processing the same action twice. These mechanisms are separate from any security or error logs managed by Cloudflare. The Workers Logs documentation states a maximum retention of seven days for that product when enabled. This does not describe all Cloudflare logs or establish that the product is enabled on this account. The game code adds no application log of nicknames, cards, or raw IP addresses.

Audience measurement and search visibility

The publisher enabled Cloudflare Web Analytics in the dashboard and wishes to keep it to measure traffic. The presence of the beacon and actual transmission of measurements could not be confirmed in the last checks. The data actually sent, including whether invitation tokens are excluded, and the notice or consent requirements applicable to this setup must be established before describing the measurement as operational. The game installs no additional script and its security policy is not broadened to allow audience measurement.

Audience measurement is separate from technical information needed to operate and secure the service and from the hosting provider’s technical statistics. The code contains neither Google Analytics nor Google Tag Manager.

Google Search Console is used to verify site ownership and track visibility in search. Its static verification file does not install a tracker in the game or receive card choices. Keeping Analytics requires checking the data actually sent and providing appropriate information. The absence of cookies alone does not establish an exemption from consent.

Providers and recipients

Cloudflare provides Pages hosting, Workers, and Durable Objects storage. Lobby members receive the game information described above. GitHub hosts and delivers the code. The game code does not provide for sending player histories to GitHub.

If you write to the contact address, Proton receives your sender address, message, and attachments to deliver them to the publisher. The site has no additional feedback form or database.

The contracting entities, providers’ own technical processing, processing locations, and safeguards for possible transfers outside the European Economic Area must be confirmed against the terms and settings actually in force. No claim is made that data is stored exclusively in France or the European Union.

Purposes and legal bases

The service provides the game, keeps preferences and local resume data, manages duels and replays, protects the service, and handles player requests. Providing the requested free service, maintaining duel continuity, preventing abuse, and replying to player feedback rely on the publisher’s legitimate interest in operating and protecting the game and handling requests. The data used is limited to these needs, and no advertising or commercial profiling purpose is added. Handling requests concerning data rights fulfils the corresponding legal obligations.

Contact, access, correction, and deletion

For a question or request concerning your data, write to Contact-Seven-to-King@protonmail.com. Subject to the conditions set by applicable rules, you may request access, correction, erasure, or restriction of processing, object to certain processing, and request portability when the conditions are met. Where processing relies on your consent, you can withdraw that consent for the future. You can also lodge a complaint with the CNIL.

Describe your request and provide information useful for locating the data, without publicly sharing your private invitation or cookie. Proportionate additional information may be needed to verify the request. As a rule, a response to a request to exercise your rights must be given within one month of receipt. An extension may apply under the applicable rules, with notice to the person concerned. There is no automatic server-side button to delete an individual’s data. The publisher reviews requests in light of the data actually accessible, other participants’ rights, and applicable obligations.

Contact messages and their attachments are kept while the request is being handled and for any follow-up needed to resolve it. They are then deleted unless a legal obligation or identified dispute justifies retaining the necessary items for a limited period. Unnecessary items, particularly attachments containing excessive data, are to be removed when no longer needed. This is a manual process for contact messages, rather than automatic deletion by the game.