Privacy Policy

Applies to the current Immortal Path v1.0.0 build

This policy explains what information Immortal Path processes, why it is used, who may receive it, how long it is kept, and how to request deletion. Cultivation saves are stored locally. Apple or Google sign-in also enables encrypted cloud-save copies, and you can create a separate password-encrypted recovery backup. These copies are not protected from unauthorized reads or overwrites by encryption alone; InstantDB access rules must also be correctly configured.

1. Information the game processes

Information stored on your device

The game stores its save and settings in the browser or app’s local web storage. Depending on how you play, this can include your character name and appearance, server choice, Qi and virtual currencies, progression, equipment, rewards, promo-code redemption history and in-game Mail, chat and story preferences, language and sound settings, account choice, Player ID, and timestamps used for saves and offline progress. Code rewards are delivered to the local in-game Mail inbox; the game does not email them to an external address. The game also keeps up to five recovery snapshots per server. Save exports you create are files you control; they may contain the same game information.

Account and Player ID information

You can play with a guest identity or, if enabled, choose Apple or Google sign-in. The identity provider handles your sign-in credentials. The game may receive an account identifier and profile details returned by the provider, such as a display name or email address, and stores the selected identity reference locally. To assign a shared Player ID, the game sends InstantDB the provider type, a hashed account reference, the Player ID, and registration/update timestamps. Passwords are not sent to Immortal Path.

Connected cloud journeys and password recovery

For Apple- or Google-connected identities, the game encrypts a copy of each saved server journey in your browser before writing it to InstantDB. The cloud record contains the Player ID, server ID, update time, encryption format, initialization vector, and ciphertext rather than the save as readable JSON. The encryption key is derived on-device from the connected identity reference and the game’s app identifier; it is not uploaded as a key, but it is not a separate password or secret held only by you. This is client-side encryption, not a server-authoritative save system.

You can also create an encrypted recovery backup using your Player ID and a recovery password. The game derives an encryption key from the password using PBKDF2 and AES-GCM, then uploads the encrypted bundle to InstantDB. The password is not stored or sent. The Player ID, timestamps, and encryption metadata remain outside the encrypted bundle. A new backup replaces the previous backup for that Player ID. Automatic refresh is available only while the recovery key remains in memory for the current session; after a reload, enter the recovery password again to create and refresh the backup. Restoring decrypts the bundle on this device and asks you to associate its journeys with Guest, Apple, or Google.

Encryption helps keep save contents out of readable database fields, but it does not prevent a client with database write access from replacing or deleting encrypted records. The game filters reads by Player ID; that client-side filter is not an access-control boundary. InstantDB server-side permissions must restrict reads and writes appropriately, and their deployed configuration is not verifiable from this policy.

Shared-server information

When you use online court features, the game sends data to InstantDB. Shared character and ranking records can include a character ID, server ID, character name, path, realm or stage, ascension status, Combat Power, and event-specific ranking information. Sect features can add sect names and membership, public member names, contribution amounts, and boss damage or attack summaries. Some of this information is visible to other players in the relevant server, sect, or ranking.

Server Chat, Sect Chat, and Direct Messages, where available, process the text you submit along with sender and recipient or channel identifiers, server/sect identifiers, and message timestamps. Messages are visible to the channel or recipient you choose. Do not include information you want to keep private.

Network and support information

When your device requests the game or connects to online services, the relevant hosting, authentication, database, and content-delivery providers may receive ordinary connection and diagnostic information such as IP address, request time, browser or device details, and requested resources. If you contact support, we receive the information you choose to include, such as your email address, Player ID, character/server details, device model, screenshots, and the issue you describe.

2. Why information is used

• To save and restore a local journey, calculate offline Qi, remember your settings, and provide local recovery snapshots.
• To sync encrypted journey copies for connected Apple or Google identities and to create or restore password-encrypted recovery backups when you request it.
• To authenticate an optional connected identity, assign a Player ID, and operate shared presence, character directories, rankings, sects, and chat.
• To display the public gameplay information needed for those shared features and help prevent duplicate or inconsistent Player ID assignments.
• To respond to support requests, investigate technical problems, maintain service security, and understand game progress events when the host’s progress-logging helper is active.

Immortal Path v1.0.0 does not include a live payment processor or third-party advertising SDK. Offers that display real-world prices and rewarded-ad experiences are local simulations: they do not charge you, create store receipts, or require payment or card information. Progress-logging helpers may still receive event summaries about game activity, including simulated offer interactions.

3. Who receives information

• InstantDB: authentication, the shared Player ID registry, character directory, rankings, sect records, chat features, encrypted Apple/Google cloud journeys, and password-encrypted recovery records. Save records still include Player IDs, server IDs where applicable, timestamps, and encryption metadata. InstantDB processes information under its own privacy terms and service configuration.
• Apple or Google: only when you choose a sign-in option that is enabled. They handle their own account credentials and provide the authentication response under their own policies. Immortal Path does not control their separate account records.
• Rosebud-hosted helper services: the web bundle loads host scripts for chat/platform features, image-related helpers, progress logging, and related hosting features. When a helper is used, it may process the request or event data needed for that feature and technical connection information. The game does not send the full local save through its progress-event calls.
• Content and hosting providers: Google Cloud Storage serves host scripts and game media; esm.sh serves the InstantDB JavaScript module; the web bundle also preconnects to Google Fonts. These providers may process ordinary web-request metadata when content is requested.
• Other players: people in your chosen server or sect can see the shared character, ranking, membership, contribution, and chat information described above.
• Support email provider: messages sent to immortalpath@yahoo.com are handled by the email provider used for that mailbox.

We do not sell personal information. Providers may process information in the countries where their systems or service partners operate, subject to their own terms and safeguards.

4. How long information is kept

• Local saves and settings: remain on your device until you clear the app/browser storage, remove the app, or overwrite the save. Local recovery snapshots are limited to five per server and are replaced as new snapshots are created. Exported files remain wherever you saved or shared them.
• Encrypted cloud journeys and recovery backups: the current client does not set an automatic expiry. Cloud journey records are replaced as that server’s connected-account save is synced; the password recovery record is replaced when a new backup is created for the same Player ID. These remote records can remain in InstantDB until overwritten or removed by the service operator/provider. Automatic recovery-backup refresh does not continue after a reload unless you re-enter the recovery password.
• Shared chat: the current game sets a 24-hour expiry for stored chat messages and attempts to prune expired records. Cleanup can be delayed, so a message may remain somewhat longer while cleanup is pending.
• Player ID mappings, character directories, and sect records: the current client does not set a general automatic expiry for these records. They may remain in InstantDB until removed by the service operator or provider. The game has no self-service remote save deletion or account-wide data deletion control in this build.
• Online presence: is intended for currently connected players and ends when the session disconnects; service or diagnostic logs may have separate provider retention periods.
• Support correspondence and provider logs: are kept as needed to handle the request, maintain security, and meet applicable obligations. Their exact retention can depend on the email, hosting, authentication, or logging provider; the game does not control all provider log schedules.

5. Your choices and deletion requests

You can play without entering a shared server, and you can leave shared features. Character names, chat, and other shared information may be visible to other players while the related records are available. You can delete local game data by clearing the app’s storage in device settings or removing the app. On the web, clear the site’s stored data in your browser. This also removes local saves and recovery snapshots unless you have kept an export elsewhere; it does not remove cloud journeys or a recovery backup already uploaded to InstantDB.

The in-game “Remove guest identity” action removes the guest identity reference from this device; it does not delete local cultivation journeys, encrypted cloud/recovery records, or shared server records.

To request deletion of shared Player ID, character, sect, chat, encrypted cloud-save, recovery-backup, or support information that may be associated with you, email immortalpath@yahoo.com with “Privacy deletion request” in the subject. Include your Player ID, the relevant character name and server, and the sign-in provider if applicable. Do not send recovery passwords, sign-in passwords, authentication codes, or payment details. We may ask for reasonable information to confirm that you control the account before acting. We will review the request and delete or de-identify information we control where feasible and legally required; some limited records may be retained for security, fraud prevention, dispute resolution, or legal compliance. A request to Immortal Path does not delete an Apple or Google account, or copies held under a provider’s own retention rules; contact that provider separately where needed.

For an initial response, please allow 3–5 business days. A response time is not a guarantee that every third-party copy can be removed within that period.

6. Permissions, children, and changes

The cultivation game does not need access to contacts, photos, camera, microphone, location, or motion sensors. Music and sound effects are bundled with the game and are unlocked by a player gesture. The mute and volume choices are stored locally.

This policy describes the current v1.0.0 build. Features and service providers may change; this policy should be updated when the released product’s data practices change. Service providers’ own privacy notices also apply to their services.

7. Contact

For privacy questions or a deletion request, contact immortalpath@yahoo.com. Include only the details needed to identify the relevant game record; never email a recovery password or sign-in code.