Sail On
Sail On · Privacy

Your voyage.
Your data.

Sail On is developed and operated by Peter Coombes. You can play without an online account. Private crew leaderboards and recovery are optional, except that creating a crew requires recovery email and password.

Last updated: 18 November 2026

What we collect and why

Your game progress, preferences and personal run history are saved on your device. They support gameplay and your personal records. They are not automatically backed up to your online account. The Android publication build also excludes app data from Android cloud backup and device transfer to protect saved credentials. Updating the app normally retains local progress; uninstalling it, clearing its data or moving to another phone can lose that progress.

If you choose online crews, Google Firebase stores an account identifier, nickname, crew names and memberships, best scores by level, invitation codes and activity timestamps. We use these to provide private rankings, manage access and remove inactive data. A crew sees your nickname and best scores. Avoid using personal details in nicknames or crew names.

People with a crew invitation code can join it. Captains can replace invitations and remove members. Sharing uses your device’s normal share controls; Sail On does not read your contacts or send messages on your behalf.

Reports contain the reporting account, relevant crew and player identifiers, report category and time. Block lists contain the blocked player’s identifier and nickname; bans contain their identifier. We use these to address abuse. Reports are visible only to the operator. Blocking hides a player from your view and does not hide your profile from them.

Leaderboard eligibility

Everyone can play the puzzles. The mobile releases require a confirmed age of at least 18 for online crews and leaderboards. Unknown, declined or unavailable age information does not unlock those features. Regional age-assurance holds also prevent access. Account recovery for deletion and support remain available.

On Android, Google Play Age Signals is used on the device to check eligibility for adult-only crews. Google Play Integrity supplies an app and device integrity proof, which our server verifies with Google. We check the app package, signing certificate, Play licensing, device integrity and a one-use challenge. We do not upload the raw age range or birth date to our server. Play Integrity is not proof of personal identity. Temporary sessions and request limits follow the retention periods below. Failed verification leaves puzzles available.

On supported iOS devices we use Apple's Declared Age Range and App Attest services. We send a signed eligibility result and app-integrity proof to our server, not your birth date or the platform's raw age range. The server stores an account-linked eligibility session, expiry, public device key and security counters to control access and prevent replay. App Attest verifies app integrity, not personal identity. Leaderboards are unavailable on platforms without an accepted eligibility check; local gameplay remains available.

Eligibility sessions last up to ten minutes and are closed locally when the app backgrounds or the account changes. Server revocation requires connectivity; an unrevoked grant still expires. Temporary sessions and challenges are removed by the weekly cleanup after expiry. Public device keys expire after 90 days without renewal and are removed by that cleanup or account deletion. Eligibility request limits use hourly hashes of network addresses, expire after one day and are normally removed within eight days.

App review demonstration

Builds with review access provide a clearly labelled demonstration using a separate Firebase project and sample crews. Review credentials do not grant administrator rights, verify anyone's age, or provide access to real players. Demonstration progress and online accounts remain separate from normal gameplay. Do not enter personal information in demonstration names or reports.

The supplied review entry password remains reusable after testing password changes. Deleting a demonstration account removes its data; a later review sign-in creates a new demonstration identity and sample data. It does not restore the deleted account. This reset behaviour applies only to demonstration access, never normal player accounts. Review login limits use temporary hashes of network addresses, expire after one day, and are removed by weekly cleanup.

Private recovery details

Firebase Authentication manages recovery email addresses and passwords. Email is required to create a crew and optional for other players. These details are not shown to crew members. Normal sign-in sends no email; requesting a password reset asks Firebase to send a reset email when the address has an account.

You can also generate a private recovery code in Settings. The code can restore or delete your online account. We store a cryptographic hash rather than the code itself. It is displayed when generated; replacing it invalidates the previous code. Keep it private and separate from crew invitations.

Recovery restores online memberships and shared scores, not the full local run history or unlocked progress from another device. Without a signed-in session or recovery credentials, we cannot verify ownership. Support cannot bypass that requirement using a nickname or invitation code.

How this website works

The deletion page uses Firebase to verify your recovery credentials and process your request. Sign-in is kept in the page’s memory only and is lost when you close or reload it. We do not intentionally store your password or recovery code in browser storage. Your browser’s own password manager may offer to save credentials.

You can save a receipt or status link yourself. Receipt links put the private code after the # character, so it is not sent as part of the initial website page request. We do not use website advertising or analytics trackers.

90-day inactivity cleanup

Individual online accounts become eligible for deletion after 90 days without opening the app online. Crews become eligible after 90 days without a member completing a level and syncing online. Looking at a leaderboard or importing existing scores does not keep a crew active. Offline play does not reset either server clock.

Cleanup is scheduled weekly on Sunday at 3 am Brisbane time. Removal normally occurs between days 90 and 97; service interruptions may delay it. The account and crew clocks are independent: an active crew does not keep an inactive member’s account.

When an inactive captain is removed, an active teammate takes over where possible, preferring a member with a private recovery code and then recent activity. If no active member is available, the crew is removed. A guest can inherit captaincy. Other active crews and local game progress remain.

Group deletion removes its shared leaderboard, invitations, membership records and related reports. Reports may also be removed after review or when a related account is deleted.

Request permanent deletion

Use this account-deletion page with a private recovery code or recovery email and password. No app installation is needed. In the game, use Settings → Account & crew → Privacy, support & deletion → Delete my account & online data. In-app deletion is available to guests too.

After confirmation, deletion is processed automatically and retried if interrupted. It removes your Firebase sign-in account, private profile, recovery-code mappings, online scores and memberships, associated report and block/ban references, and all crews you own. Those crews disappear for other members as well. Unlike inactivity cleanup, explicit account deletion does not transfer captaincy.

Your local progress remains on your devices. Clear app data or uninstall the game to remove local records; platform backups may follow your device’s own settings. We cannot remove copies made independently by others, such as screenshots.

A random deletion receipt contains only status and expiry, with no nickname, email or player identifier. It is available for 30 days after completion and removed by the following weekly sweep, normally within 37 days. No email receipt is sent.

Temporary records containing a deleted account’s identifier prevent still-valid sign-in tokens from recreating it. These expire after one day and are removed by the weekly sweep, normally within eight days. To limit recovery and invitation attempts, we store hourly hashes derived from the requesting IP address and, for invitations, the account identifier, with attempt counters rather than raw IPs in these records. These expire after one day and are swept weekly, normally within eight days.

Providers, security and international processing

Google Firebase provides authentication, database storage, server functions and website hosting. Our Firestore database and account functions are located in Sydney, Australia. Other Firebase services, technical processing and security logs may operate in other countries. Google processes technical information such as IP addresses to operate and protect its services. See Firebase’s privacy information and Google’s privacy policy.

Access rules restrict private profiles and crew records. Recovery codes are generated randomly, hashed for storage and subject to attempt limits. No system can guarantee absolute security. Never share account credentials or private recovery codes.

Application deletion removes data from our live game records. Provider-managed logs and backup systems may retain data under Google’s own retention schedules. Google states that Firebase Authentication information is removed from its live and backup systems within 180 days after deletion is initiated. Authentication IP logs remain for a few weeks and Hosting IP information for a few months. Sail On has not enabled scheduled Firestore backups. Provider retention does not restore deleted game access.

Advertising, audience and changes

Sail On is a general-audience puzzle game that children can also play. Mobile builds may show Google AdMob interstitial advertising between levels. Levels 1–3 are ad-free. Advertising requests use a General content rating and disable personalised advertising. We do not send crew nicknames, email addresses, scores or recovery details to advertising providers. There are currently no purchases.

Age preferences and advertising choices

On supported iOS devices, Sail On asks Apple for an age range. We use this on the device to apply advertising protections. We do not send the platform age range to Firebase or pass it to AdMob; only the applicable advertising-treatment settings are supplied. Where an in-app birth-year fallback is available, the year is used on your device and discarded. Only the resulting protective or adult treatment preference is stored locally. Unknown ages receive protective treatment; failed or required-verification checks leave advertising off. This is age screening, not proof of identity.

Android advertising always uses protective child treatment, non-personalised requests and a General content rating, regardless of leaderboard eligibility. Google Play Age Signals is used only for leaderboard access, never to select advertising treatment. Android advertising-ID and AdServices permissions are excluded. Advertising providers may still process technical information such as IP addresses, interactions and diagnostics; non-personalised ads do not mean that no data is collected.

A saved adult fallback does not automatically grant adult treatment on a fresh launch. Advertising settings are refreshed after the app returns from the background. Publisher first-party advertising IDs are disabled. These choices do not mean that Google processes no technical data. Advertising eligibility and leaderboard eligibility are separate checks.

Google Mobile Ads and its consent service may process technical information, including IP addresses, device/app information, diagnostics and advertising interactions, for ad delivery, security, fraud prevention and measurement. Non-personalised advertising does not mean no data is processed. Google may process this information internationally under its own retention policies. See How Google uses information from partner apps.

Advertising privacy choices are available in Captain’s preferences. Where required, Google’s consent service presents applicable choices before ads are requested. You can also report an inappropriate ad from that screen. Ad reports are sent only when you choose to send an email; please omit your birthdate and account credentials. Manage platform age sharing through your device’s account settings. Clearing app data removes the locally stored fallback preference.

Sharing a leaderboard image

Players can preview and share an image of an individual crew's leaderboard, including its displayed crew name, nicknames, rankings and scores. The image is prepared locally. Sail On does not upload it automatically; the player chooses a recipient or destination through their device's sharing options. Recipients can retain or forward the image. Account credentials, recovery details and crew invitation codes are not included.

Contact Peter Coombes

For Sail On support, privacy questions or requests to access or correct personal data, contact sailongamers@gmail.com. You can change your nickname and recovery details in Settings. We may need to verify ownership before responding to requests about an account. Never email your password or private recovery code.

If you cannot verify ownership, your individual account and crews still follow the separate inactivity rules above. Contacting support is not required for the normal deletion process.