Axocana information

Axocana Privacy Policy

Updated 5 October 2026

How the app and website use information, the controls available and the records that may remain.

Who is responsible and how to contact us

Axocana is operated by Rebekah Irene Vaughan, 1916 SE 6th Lane, Cape Coral, Florida 33990, United States. For privacy, access, correction or account-deletion requests, contact privacy@axocana.com. This mailbox is active and monitored by Sam. For general enquiries, contact hello@axocana.com.

You can request account deletion without reinstalling the app through https://axocana.com/account-deletion/ or by emailing privacy@axocana.com. Do not send passwords, email verification codes or full payment-card details. This notice describes the app and website; available device controls depend on the app version installed.

Account deletion requests

Accounts, companions and your freshwater world

Axocana creates an account identifier, including for guest journeys. Supabase stores chosen player and companion names, companion appearance, journal and exploration records, progress, AxoCoins, wardrobe and tank inventory, placements, preferences, game activity, votes and suggestions to operate and restore your world. Email is used when you choose to link or recover an account and for verified-account purchase eligibility.

Authentication credentials use protected device storage on Android and iOS. Other account-specific caches hold recent app state, including companion, collection, conversation and billing-identity information. Signing out or uninstalling the app does not itself request deletion of server records.

Optional AI conversations and saved memories

When you enable AI chat, your messages, recent conversation context, saved memories and relevant chosen companion details are sent through Supabase to OpenAI for replies. The current request can include up to 16 recent messages and 20 saved memories, chosen names and companion context. Messages are also checked by moderation. Reported replies and suggestions can be retained for review.

AI privacy below the message box lets you stop new chat requests on that device. Saved memories have a separate remove control. Starting a fresh chat resets the displayed conversation; it does not delete every earlier account record. Android build 4 and iOS build 6 add Delete all chat history, which removes server conversations while preserving memories, progress and purchases.

OpenAI response requests use store:false. This is not a promise of zero retention by OpenAI or other providers. Provider safety logs and other retained copies have separate arrangements; no specific provider-wide deletion deadline is asserted here. Avoid including information you do not want processed by these services.

Payments and purchase records

Apple or Google processes store payments. RevenueCat receives store transaction information and an opaque billing identifier associated with your Axocana account to validate purchases and access. The app does not collect full payment-card numbers through its purchase interface.

Supabase stores purchase identifiers, products, verification times, ownership, memberships, coin grants and refund or revocation outcomes. Heartleaf checkout also records the selected product, storefront, currency, price, checkout attempt and terms version. These records support fulfilment, restoration and prevention of duplicate rewards. Optional public recognition is separate.

Optional public recognition

Recognition is private unless you choose to publish an entry. A published Book of Thanks entry can show a chosen display name or anonymous label, an optional broad region, the year support began and eligible supporter status to other signed-in users. It does not show your account email, payment amount, internal identifier or private journal name.

The publication flow previews the entry before a separate Publish my entry action. Names are validated and moderated. You can edit or remove your entry through Support the Colony. Returning to private clears its stored public name and region, but cannot recall copies another person has already made. A minimal consent-event record stores the action, version and time.

Service providers, cameras and device features

Supabase provides authentication, databases and server functions; the app project is hosted in US West. OpenAI provides optional AI replies and moderation. RevenueCat and Apple or Google process purchase verification. Cloudflare hosts the website and its database. Privacy and contact email is routed through Google. These services may process information outside your country under their own applicable arrangements.

The two live aquarium views use YouTube API Services. Opening the camera screen loads the embedded player and sends basic data to YouTube/Google before you press Play, to load the player, check whether the video can play and help prevent fraud and abuse. Playback can disclose further network and device information, viewing activity and browser storage to that provider. The youtube-nocookie.com player address does not eliminate these transfers. See Google's Privacy Policy for how Google handles information. The cameras show the aquarium; Sirius has not yet arrived.

Tilt effects use the accelerometer locally. Camera permission supports the torch feature; the current app does not capture or upload photos or record microphone audio for that feature. New builds disable optional RevenueCat diagnostics and automatic attribution-identifier collection; necessary purchase processing continues.

Website storage and visitor counting

The website remembers the sound choice for the current tab in session storage. Closing the tab clears that choice. Sound playback also depends on the browser autoplay setting.

A first-party counter keeps an approximate aggregate of browsers that visited. The total is private to the site owner. A browser marker prevents ordinary refreshes and page navigation from adding another visit for up to a year. Another browser, device, private session or cleared browser data can count again. The counter does not store names, email addresses, IP addresses, user-agent strings or referring pages with the aggregate.

A temporary random receipt helps prevent duplicate increments. Receipts expire after 24 hours, and expired server receipts are removed on a later count request. Open Visit counting options in the footer to exclude your browser. Global Privacy Control and Do Not Track signals are respected. An earlier visit remains in the aggregate. Hosting security and connection logs are separate from this counter.

Website launch notification

If you choose to join the launch list, the website stores your email address, signup date and consent-wording version in a private Cloudflare database for the requested launch notification. This does not create an app account or reserve a purchase. Duplicate signups do not add another entry. The list is not public.

To withdraw, email privacy@axocana.com from the address you registered and ask to leave the launch list. Entries remain until removed; the website does not currently apply automatic time-based deletion to this list. No fixed automatic deletion deadline is promised. The signup table does not store your IP address, although rate limiting temporarily uses it and hosting logs may be processed separately.

Deleting your account and device copies

From the Gateway, open Settings on the right of the wooden footer, then Manage your account. Check the account, choose Delete my account, type DELETE and confirm. The server validates the signed-in account, revokes its refresh sessions and deletes its authentication account and associated profile, conversations, memories, progress and linked game or recognition records. Wait for confirmation; an error or a closed screen is not confirmation of deletion.

The app attempts to clear account-specific data on the device making the request. Android build 4 and iOS build 6 extend this cleanup to companion, collection and billing-identity caches and add chat-cache expiry and online deletion checks. A closed, offline or older app cannot be guaranteed to remove its stored copy at the same time. If local cleanup fails, follow the app instruction to clear its stored data.

Without app access, email privacy@axocana.com with the subject Axocana account deletion request. Send from your linked email where possible and include an account number only if you have it. If you used a guest journey or lost email access, explain that. Account ownership must be established before a manual deletion; a claimed email or account number alone is not proof. Recovery of a lost guest account cannot be guaranteed.

Account deletion queues a request to delete the associated RevenueCat customer profile and retries failed requests. A provider acknowledgement is not proof that every internal copy or backup has been erased. Apple, Google, OpenAI, RevenueCat and infrastructure providers can retain separate records. Account deletion does not cancel a store subscription or automatically refund purchases; cancellation is not a prerequisite for requesting deletion.

Account and data deletion

What is retained and for how long

Account, progress, inventory and saved-memory records support your continuing journey until removed through the relevant controls. Accounts are not automatically deleted for inactivity. Saved memories are separate from conversation history.

Scheduled hourly cleanup removes conversation messages older than 90 days and raw billing-event payloads older than 30 days. It removes AI retry-response bodies after 7 days, content-free request markers after 90 days and per-user AI usage after 30 days. Daily AI cost totals without user identifiers remain for 12 months. Cleanup uses bounded batches, so expiry is a processing threshold rather than a promise of deletion at an exact instant.

Suggestions and reported-reply records expire 12 months after their recorded closure. Unclosed cases remain for handling. For requests recorded in the private privacy-case register, correspondence is removed 30 days after closure and the minimal case record after 24 months, except for a recorded hold. RevenueCat deletion-job identifiers are removed 30 days after acknowledgement and the minimal outcome record after 24 months. These database controls do not automatically remove mailbox copies, attachments, forwards or exports.

Some billing identifiers, transaction details, grant and refund outcomes remain after the account link is removed. They prevent duplicate credits, handle delayed store events and preserve necessary purchase evidence. These records are not necessarily anonymous and currently have no automatic financial-record expiry. No blanket three-year deletion promise is made.

Mailbox records, provider security logs, backups and provider-internal copies have separate retention. No universal 30-day backup expiry, immediate erasure of every copy or fixed completion time for an external deletion request is promised. You can contact the privacy address about the information that remains and the reason it is retained.

Your choices and requests

You can contact privacy@axocana.com to request information, access, correction or deletion and to raise a privacy concern. Depending on applicable law, other rights such as restriction, objection or portability may apply. Verification may be needed before information is disclosed or an account deleted. Applicable legal requirements continue to apply even though this notice makes no guaranteed support turnaround.

Axocana is intended for people aged 13 and above. If you believe a child has provided personal information outside that intended audience, contact the privacy address without sending passwords, private conversation histories or identity documents in the initial message. This statement does not claim that every age or territory is verified automatically.

This notice was updated on 4 October 2026. Changes to data processing will be reflected here. The date does not change past purchases or claim that every provider copy has the same retention as Axocana records.

← Back to Axocana