Account & Data Deletion

1. Current availability

This is a review draft, not a confirmed live deletion service. The app contains a deletion screen and a server function, but the server has a readiness switch that blocks deletion until enabled. Its production status and complete deletion coverage have not been verified. The external request mailbox also awaits activation.

The controls and instructions below are substantive draft guidance for that implementation. A working in-app route and external request service must be tested before launch. Policy wording alone does not make either route operational.

2. Delete through the app

1. Open Freshwater Journal and choose Account details.
2. Check the account number and linked email, if any, so you are deleting the intended journey. You do not need to link an email merely to delete a guest account you can still access.
3. Choose Delete my account and read the consequences.
4. Type DELETE in the confirmation field, then choose Permanently delete my account.
5. Wait for the app to confirm the result. A failed request, unavailable-service message or closed screen is not confirmation of deletion.

The request checks the signed-in account on the server. If your account changes during the process, reopen Account and check it again. If the app reports that deletion was not confirmed, do not assume that all records have been removed. Use the external route once it is active.

3. Request deletion without the app

The designated external route is email to privacy@axocana.com with the subject Axocana account deletion request. This is intended to work without reinstalling the app. The mailbox is not yet active, so this private preview cannot currently accept or confirm an email request.

Once activated, send from your linked email where possible. State whether you want the whole account deleted or a particular category of information removed. Include an account number only if you already have it, and enough context to locate the correct journey. Do not send a password, verification code, full payment details or identity documents in the first message.

If you cannot access your linked email or have only a guest account, explain that. The operator will need a proportionate alternative way to establish ownership before deletion. Recovery or identification of a lost guest account cannot be guaranteed. Verification must not become an unnecessary obstacle to a valid request.

No particular turnaround is promised in this draft. Valid requests must be handled within applicable legal time limits, including requests received through other legally recognised channels. The operational process must acknowledge requests, explain any verification or lawful exception, and confirm the outcome.

4. What account deletion affects

The intended full-account scope includes your login, linked email, profile and passport details, journal and travel progress, saved conversations and Sirius memories, inventory and tank configuration, wallet and reward activity, and private supporter preferences or public recognition linked to the account.

The implementation deletes the authentication account and relies on database cascade rules for associated records. Complete coverage across all game tables, feedback, stored files and service providers still needs an end-to-end audit. The current draft must not be read as a verified promise that every possible record is already covered.

You lose access to the deleted journey and its virtual holdings. Recovery is not an undo button for deletion, and creating another account does not bring back the previous tank, progress or spent currency. Any applicable consumer or refund rights remain separate.

The app attempts to clear known account-specific data on the device that submitted deletion. If it reports that local data could not be cleared, remove the app’s stored data on that device after deletion is confirmed. Other devices, older caches and backups require separate handling; uninstalling on one device does not itself delete server records.

5. Records that may remain

The reviewed billing implementation removes the direct account link but retains a billing customer identifier, purchase and transaction details, and billing-event payloads. These can support duplicate-payment checks and prevent delayed store events from recreating a deleted journey. They are not necessarily anonymous simply because an account link has been removed.

The permitted fields, necessity and deletion schedule for those records are still awaiting approval. No automatic expiry period has been verified. Any record retained for a legal obligation must have a specific justification and a defined period; an unspecified “legal requirement” must not be used to keep everything.

Apple, Google, RevenueCat and AI or infrastructure providers may hold records under their own responsibilities and retention arrangements. Production provider deletion procedures, security-log limits and backup expiry remain unverified. A final response to a request should identify any relevant exception and expected retention rather than promising instant removal from every system.

6. Cancel subscriptions separately

Deleting your Axocana account does not cancel a monthly or annual store subscription. To stop future renewal, use Apple’s subscription controls or Google Play’s subscription controls. Cancellation is not a condition for requesting account deletion, but review your renewal settings so charges do not continue unexpectedly.

Deletion does not automatically refund a purchase. Use the relevant Apple refund route or Google Play refund guidance for a refund request. Keep any receipt you need before removing account access, with payment details kept private.

7. Remove less than the whole account

• Stop new AI sharing: open AI privacy below the Sirius message box and turn chat off. Existing records remain, and the choice applies on that device.
• Remove a saved memory: use the memory controls. This does not erase the original conversation in which the detail appeared.
• Start a new chat: clears the displayed conversation on that device and begins another; earlier account records and memories remain.
• Hide public recognition: return Book of Thanks recognition to private. The implementation removes the saved display name and region from that preference record; previously copied public content cannot be recalled.
• Clear this website’s sound preference: clear this site’s browser storage. This has no effect on your app account.

For access, correction or selective deletion beyond these controls, use the privacy request route once active. See the Privacy Policy’s rights section for relevant choices and complaints.

8. If something goes wrong

Record the visible error, approximate time, app version and whether you were using a guest or linked account. Do not repeatedly create new accounts to resolve a deletion failure. A failed local cleanup and an unconfirmed server deletion are different situations; retain the exact message so they can be distinguished.

The approved privacy contact is privacy@axocana.com, pending activation. General technical guidance is available on Support & Contact. The remaining activation and coverage checks must be resolved before this page is used as a live store-listing deletion resource.