XAVIER APONTEINDEPENDENT DEVELOPER
Chisa and a white fox rest inside a protective crystal sakura shield
CHISA · PRIVACYA little trust. A little peace of mind.
Chisa Moonlight Flight!

Privacy Policy

Effective date: November 11, 2026

This policy explains how Chisa Moonlight Flight! handles information in its game and online leaderboard. The developer’s privacy contact is CHISA privacy and support requests.

Earlier local-only high-score editions

This section describes the earlier local-only high-score edition. The optional website-connected update is described below. The local-only edition stores only your highest score on your device. It has no accounts, nickname entry, online leaderboard, score uploads, advertising SDKs, analytics SDKs or runtime AI service. Gameplay does not send score or player information to the developer. The trophy button displays your local record. The information button provides a Reset best score action; removing the app’s stored data also removes local progress. There is no cloud score sync.

The app includes bundled game content and uses Apple’s local storage APIs. Opening a support link launches your browser; the website provider may process technical connection information separately. Apple separately handles App Store and TestFlight services under its own privacy policy.

Earlier online versions and the website: The following sections continue to describe the older online edition and any existing server records. Updating to the local edition does not delete records submitted by older versions. The browser game has been replaced by a developer and app support website; the current website does not submit gameplay scores. For privacy questions or legacy-data requests, use the contact route below.

1. Information handled by earlier online editions

The game does not require an account login, email address, phone number, precise location, contacts, camera, or microphone for gameplay. Avoid using your real name or other personal information as your leaderboard nickname.

2. Public leaderboard information

Your nickname and scores are visible to other people on the public leaderboard. Depending on the leaderboard view, flight dates and completion status may also be visible. Your randomly generated player identifier is used internally to associate your records; it is not intended as a public display name.

3. How information is used

Information is used to run the game, remember your preferences and best score, maintain online rankings and flight history, identify score submissions, protect the service against abuse, troubleshoot failures, and respond to privacy requests.

4. Advertising and tracking

The current game includes no advertising SDK or third-party analytics SDK. It does not use an advertising identifier or track your activity across other companies’ apps and websites for advertising. Leaderboard information is not sold.

5. Hosting and service providers

The developer website and this policy are hosted on Railway at xavier-is-working.com. Older GitHub Pages links redirect to this website. GitHub handles support requests submitted through GitHub Issues. Online leaderboard requests are handled by the CHISA score service hosted through ChatGPT Sites infrastructure. Hosting providers process the information needed to deliver and secure those services.

Relevant provider information: Railway privacy policy, GitHub privacy statement, OpenAI privacy policy, and Cloudflare privacy policy. Information may be processed in countries other than your own.

If you obtain the game through Apple’s App Store or TestFlight, Apple separately handles information associated with its distribution, purchase, and testing services under Apple’s privacy policy.

Optional website leaderboards — website-connected app update

The website-connected update adds an optional online leaderboard hosted on Railway at xavier-is-working.com. Earlier local-only builds continue to work without it. If you opt in, a nickname, random profile ID, public friend code, best accepted score and timestamps are stored in the website database. Nicknames, friend codes and accepted scores are public. Profile credentials are stored in the device Keychain and sent over HTTPS as authentication; only keyed hashes of the secret tokens are stored on the server. No email address or Game Center account is needed. Use a nickname instead of your real name.

Connected flights send a client run ID and receive a single-use server session. Checkpoints and final scoring evidence include active duration, gate IDs, gate scores, ability multipliers, rewind count and scoring times. These are used to check timing, totals, duplicate submissions and unusual scores. Run records are kept for up to 30 days; the profile and accepted best score remain until deleted. Suspicious profiles can be hidden by the developer. The service cannot guarantee cheat-free play.

Friend codes you add are stored on your device. They are sent to the website to filter public scores when you view friend rankings. They do not give access to your Apple contacts or Game Center friends. Background friend alerts and cross-device account recovery are not provided. Website profiles do not automatically sync local records between devices.

You can stop new uploads with Turn off score sharing in Rankings. Existing public scores remain. Delete online profile and scores removes the profile and its run records after confirmation, subject to hosting backup retention. Your local best is unaffected. If you lose access, use a private support conversation with your public friend code so the developer can review the request. Removing the app does not automatically remove server data.

Website analytics and private support

The website offers optional first-party analytics. If you choose Allow analytics, a random anonymous browser identifier is saved in local storage. The server stores a keyed hash of that identifier, the page path and visit time for up to 90 days. No name, precise location, query string or support conversation token is recorded in analytics. Counts cover consenting visitors and may omit blocked or automated traffic; they are not a list of identified people. Use Analytics preferences at the bottom of a page to change your choice. Do Not Track and Global Privacy Control signals are respected.

Private support conversations store your optional nickname, category, subject, messages, replies and timestamps in the website’s Railway PostgreSQL database. Only the developer and anyone holding your secret conversation link can access that conversation. Link tokens are stored as keyed hashes on the server. If available, conversation links are saved in your browser’s local storage so you can return. No email is required and no email notification is sent. Keep the link private. Request deletion through your conversation; support records are kept while needed to respond and maintain issue history, or until a deletion request is handled, subject to technical backup retention.

Owner access uses a secure, HttpOnly session cookie lasting up to 12 hours. Technical IP connection information may be processed by hosting providers and used transiently for abuse prevention; it is not shown in visitor analytics. The private dashboard is restricted to the website owner. You can also contact the developer using the private support form.

Optional PayPal support

The developer website links to PayPal for voluntary support. PayPal processes any payment and related information under its own privacy statement. This website does not collect card details. Donations do not unlock app features.

6. Retention and deletion

Local preferences and scores remain on your device until the app’s stored data is removed, or the browser’s website data is cleared. Removing local data does not by itself remove online leaderboard records.

Leaderboard records are retained to maintain rankings and flight history. To request access, correction, or deletion of your online records, open a request at CHISA privacy and support requests titled “CHISA privacy request.” GitHub issues are public and require a GitHub account. Include only your public game nickname and approximate flight dates or scores. Do not post your email address, real name, passwords, identity documents, or other sensitive information. The developer may ask for additional information to identify the correct records and avoid deleting another player’s data.

Technical logs and backups may be retained according to hosting-provider practices and applicable requirements. Clearing a device or changing a nickname should not be treated as confirmation that server records have been deleted.

7. Children and families

Players should not enter personal information into nicknames. A parent or guardian can contact the developer to request review or removal of a child’s leaderboard information. The game does not request a player’s age or birth date.

8. Security

Leaderboard requests use HTTPS. Reasonable safeguards are used to protect information, but no system can guarantee absolute security. Public nicknames and scores should be treated as information shared with other players.

9. Changes and contact

This policy may be updated when the game’s features or data practices change. The effective date above will identify the latest revision. For privacy questions or requests, contact CHISA privacy and support requests.