Privacy Policy

1. What does this policy cover?

It covers La Porte, its presentation website and its browser game, including when installed as a web app. Administration tools are restricted to the publisher. A future app-store release or payment system will require this document to be updated.

The publisher identified in the contact section is the controller for the game’s own processing. ChatGPT account management and providers’ own processing are also covered by their respective privacy information.

2. What stays on your device

Browser storage holds your current run, language, audio and animation settings, tips you have read, personal counters, and local copies and pending sync queues for discoveries and progression. The app cache holds files needed to start offline.

These records let you resume play, keep your preferences and play offline. Guests can still buy talents and their progress stays on this device. Optional analytics, if you have accepted them, remain a separate mechanism.

Local records remain until replaced, cleared in your site-data settings or removed by the browser. Clearing them can erase the local run and unsynced information; it does not delete records already stored on the server.

3. Sign-in and synced progression

Google sign-in uses Firebase Authentication. After you choose it, Google/Firebase handles sign-in and the browser keeps the session for your next visit. The server verifies a signed token and uses only the Firebase identifier to associate your save. Google and ChatGPT accounts are not merged by email. No Firebase Analytics module is enabled, and Google sign-in does not grant administration access.

You can play without signing in. If you choose ChatGPT sign-in, the platform sends a site-specific account identifier and may send your associated email address. The game does not receive your password or read your ChatGPT conversations. The email is used in particular to check administrator access; it is not the key used for play-time analytics.

The server links discovered talents and progression summaries to your account identifier: heroes, actions and items used, damage, HP lost, MP spent, time played, victories, deaths, gates cleared, combos, achievements and unlocks. Run identifiers, revisions and dates are also stored for reliable syncing.

A current-run checkpoint can also be linked to your account: team, combat state at the last safe checkpoint, talents, equipment, inventory, gold and progression. When both the device and account have progress, a screen asks which to keep, followed by confirmation before replacement. Preferences and analytics identifiers are not transferred with this save.

After an explicit replacement, the previous account save is kept as a server-side backup; the previous local save is kept on the device when importing. Each further replacement overwrites the corresponding backup. Legacy discoveries and progression records remain as migration data; they are not automatically merged after the player chooses.

The proposed basis for this processing is providing the service you request, including retaining account-based progression. Without sign-in, account syncing is unavailable.

4. Optional run summaries to improve the game

No run analytics summaries are sent without explicit agreement. Closing the prompt declines. Settings → Optional sharing lets you change your choice. Run summaries begin with a new run; the periodic counter only measures time played after agreement. Declining does not affect gameplay or personal statistics. The separate global start counter is described below.

The prompt is not shown on the home screen or during the first two runs. A counter stored on this device makes it available when starting the third: the run waits for your choice, then starts with or without sharing. Accepting includes the start of that new run, never earlier runs. An existing choice remains respected; you can also choose manually in Settings.

At the start: random browser and run identifiers, local attempt number, engine version and consent version. At the end: outcome, gates cleared (0–13), team classes, final engine version and active play time. These summaries contain no attack logs, gestures, free text, name, email, account ID, IP or hardware fingerprint. A local attempt counter continues while sharing is off; those periods are never uploaded retroactively.

Consent v3 requests confirmation before a new run if the previous agreement did not cover periodic time collection for ongoing or abandoned runs. An existing refusal remains respected. Time is counted locally in the foreground: battles, talents and shop, excluding menus, background time and inactivity after two minutes without interaction. Final summaries retain campaign duration up to gate 13 or defeat, excluding endless mode and challengers. Separately, a cumulative counter includes unfinished runs, endless mode and challengers; it is sent about once a minute, when leaving for a menu or when the app moves to the background. The laboratory is excluded. No session timeline or action log is stored.

The server hashes identifiers and immediately adds counters grouped by engine, experience and composition. It stores no detailed combat records. Browser membership hashes and minimal run receipts remain necessary to count participants and prevent duplicates after offline retries. This is pseudonymisation, not guaranteed anonymity, and browsers are not necessarily individual people. Analytics are not linked to accounts.

Turning sharing off stops new submissions, cancels requests where still possible and clears pending summaries and unsent time on this device. It does not remove totals already received; a request that has arrived cannot be recalled. After re-enabling, periodic time resumes without backfilling; only summaries of a new run are eligible. Account-based syncing of personal statistics remains a separate service and is not used to populate these analytics.

These summaries are used solely to improve La Porte and will never be sold. Only the administrator can view grouped results. The local queue holds at most 128 summaries. Deduplication hashes and aggregates have no automatic purge and remain while this analysis operates; a more precise retention policy and erasure procedure must be finalised with the privacy contact. No consent exemption is claimed.

Historical time totals are retained and new periodic measurements add to them after v3 agreement, without importing time played during the collection pause. This table stores only a hashed random browser identifier, a total, a deduplication counter and the day of first receipt. It remains separate from engine- and experience-filtered summaries; the two views are not added together. Offline storage can delay uploads; clearing data or abruptly closing the app can lose unsent time.

Global run-start counter

From your first new run, even when summary sharing is off, an empty request adds +1 to a server counter. This mechanism creates no tracking cookie or identifier. The request body contains no player or run identifier, class, outcome, duration, attempt number or engine version; the referring page is omitted. An existing sign-in session may be sent automatically to the same site, in particular to pass the private development site’s access gate. The counter does not read or use it to identify starts.

The database retains only one global total and the date of its first receipt, with no per-event record. The counting service stores no IP address, headers or individual log and does not link this total to accounts or optional summaries. This total is retained while the counter operates, is used only to measure usage of La Porte and is never sold. Only the administrator can view it.

Resumed runs, unlock duels and the laboratory do not count as new runs. There is no local queue, automatic retry or backfill of earlier or offline starts. The total is not a count of people and may be incomplete. Technical information received by the hosting provider for any connection, including IP addresses, remains separate and is covered below.

5. Feedback, security and technical storage

Comments in authorised review tools are stored with the account, the reviewed entry, the comment text, a revision and a date. They are used to process feedback about the game. Do not include passwords or sensitive information.

Internet requests necessarily transmit technical information to providers, including IP addresses and request information. This is separate from the play-time table. Provider logs, access arrangements and retention periods still need to be confirmed.

La Porte uses local storage and caching to work; the sign-in service may use its own session cookies. No advertising module or third-party advertising tracker was identified in the game code reviewed. Play-time measurement, described above, is separate processing.

Responding to feedback and protecting access may rely on the publisher’s legitimate interest in maintaining a secure, functioning service. This basis and its proportionality safeguards must be validated before publication.

6. Who receives data?

The publisher accesses data needed to operate the game. The website is hosted through OpenAI Sites and uses Cloudflare infrastructure, including a D1 database for server records. Access to administration tools is controlled.

The game does not integrate data sales, targeted advertising or decisions with legal effects on players based on their statistics. Enemies’ tactical decisions are part of the game rules.

Before publication, the exact contracting entities, their roles, processing countries and any safeguards for transfers outside the European Economic Area must be confirmed, along with how to obtain a copy of those safeguards. Exclusively European hosting is not promised without that verification.

7. How long is data kept?

Local data follows the rules described in the device section. No automatic deletion schedule is currently configured in the game for server-side progression, discoveries, play-time measurements or comments.

Retention periods or criteria, inactive-account handling, technical backups and erasure requests must be defined and implemented before this policy is finalised. It would be inaccurate to promise automatic deletion after a period that has not been implemented.

8. Your choices and rights

Depending on the processing and the GDPR’s conditions, you can request access, correction, erasure or restriction, object to processing based on legitimate interests, and request portability of qualifying data. Where processing relies on consent, you can withdraw it for the future.

Requests should go to the privacy contact that must be supplied below. The verification and handling procedure must be finalised before publication. Never send your password. Locating a pseudonymous measurement may require information held in the original browser; an email address alone cannot identify that record.

The usual response period is one month, subject to extensions allowed by law. You can also complain to the CNIL or the competent data-protection authority in your country. This policy does not restrict those rights.

9. Young players and changes

If you are a minor, ask an adult to help you understand sign-in, sharing and this information. Creating and using a ChatGPT account remains subject to that service’s terms. La Porte does not currently collect dates of birth.

Changes to collected data, providers, payments or distributed apps must be explained in a new version of this policy. If fresh consent is required, simply continuing to play will not replace it.