Privacy policy

Who we are

SailStarter teaches sailing fundamentals through short lessons and quizzes. This policy covers sailstarter.com, the learning app at sailstarter.com/app, and the native SailStarter app, including iOS.

SailStarter is operated by Ihor Tykhonenko. Our business address is 91-1037 Cleveland Ave, Riverview, NB E1B 0T9. For privacy questions or requests, email tikhonenkoigor@gmail.com. You can also delete your account in the app as described below.

What we collect

Your account and sign-in

Lessons need an account so your progress and paid access can follow you between devices. You can sign in with an email code or one-time link, Google, or Apple. Supabase Auth stores your email address, account ID and sign-in records. Email sign-in does not use a password. Resend delivers the sign-in email and processes its recipient address, message content and delivery records.

Google or Apple supplies a provider identifier and the profile information you authorize it to share. This can include a name and email address; Google can also supply a profile picture. If you choose Apple's Hide My Email, we receive its private relay address in place of your real address. We process authentication tokens to sign you in and to revoke SailStarter's Apple authorization when you delete an Apple-linked account.

Your course activity

We store these records against your account:

• lesson completion, best scores, first-pass dates and the platform used (web, iOS or Android);
• quiz attempts, scores, pass results and selected answers;
• activity dates, reward and achievement records, including miles and streak counts;
• profile details such as display name, timezone and daily-goal settings.

The app shows lesson and quiz progress. Stored activity and reward records may remain even though the former miles, streaks, flags and daily-goal screens are no longer shown.

Course-update emails and support

If you request course updates on the marketing site, we store your email address and a tag identifying the page or button used. This mailing list is separate from your account. If you email support, we receive your address and the message and attachments you send. We use them to answer your request. If you have submitted a learner quote, we hold the quote, optional display name and publication consent.

App updates and diagnostics

On native, Expo Updates collects a random installation UUID used as a device identifier, operating-system and app/update-version information, update-check and download activity, crash data and other diagnostic data about update loading, failures and recovery. Expo uses this information to deliver compatible updates and recover from failed updates. It also aggregates update requests for analytics about installation and update usage over time and by platform.

SailStarter does not directly send your account ID through this update path. A random installation identifier does not by itself guarantee that the collected data cannot be linked to you.

Payments and billing

For web purchases, Dodo Payments handles checkout. We link its customer ID, subscription or payment ID, product, plan, status, billing-period dates and renewal settings to your SailStarter account. Subscription and purchase records also retain the billing-event data sent by Dodo, which can include the email and billing address supplied at checkout.

Apple handles in-app purchases on iOS. RevenueCat receives purchase history and your SailStarter account ID to validate purchases, restore access and provide subscription reporting. This purchase information is linked to your account; it is not anonymous. We store a summary in Supabase: store, product, plan, access status, expiry, renewal status, subscription-management link and sync date.

Separate payment-event records contain event or payment IDs, status and timestamps so billing notifications can be processed and retried correctly. These records do not contain full billing-event messages. We never receive, see, or store your card number. Dodo or Apple processes your payment details.

How we use it

• To sign you in and keep your account secure.
• To save course progress, quiz results and activity records.
• To unlock paid modules and support purchases, renewals and restores.
• To understand website use and purchase activity.
• To deliver sign-in emails and answer support and privacy requests.
• To maintain the websites, deliver app updates and recover from update failures.
• To understand app installation and update usage.
• To keep billing records and handle refunds, disputes and notification retries.

We do not sell personal information, share it with advertisers or build advertising profiles.

Who else handles your data

These services handle information when you use the relevant features:

• Supabase hosts account, course, mailing-list and billing records, and runs authentication and server functions. See Supabase's privacy policy.
• Resend delivers sign-in emails for Supabase and keeps email content and delivery records. See Resend's privacy policy.
• Netlify hosts the marketing site and web learning app. Hosting requests expose technical details such as IP address, browser information and the requested URL for delivery, security and service logs. See Netlify's privacy policy.
• Dodo Payments is the merchant of record for web purchases and handles checkout, payment details, tax, billing and refund records. See Dodo's privacy policy.
• Applehandles iOS purchases, subscriptions and refund requests, and provides Sign in with Apple when you choose it. Apple's own account and transaction records are governed by Apple's privacy policy.
• RevenueCat processes the account ID and purchase history for native purchase validation, access and restore, and purchase analytics in its dashboard. See RevenueCat's privacy policy and its purchase-data disclosures.
• Expo delivers native app updates through EAS Update and processes installation identifiers, update activity, crash and diagnostic data, and network details such as IP address. Its purposes include update delivery and recovery, plus installation and update-usage analytics. See Expo's privacy policy, update-usage documentation and crash-data disclosure guidance.
• Google provides optional Google sign-in and Google Analytics on the websites. Our support inbox uses Gmail, so Google also handles messages you send us. See Google's privacy policy.

These providers may use their own service providers and process information outside your country. Their linked policies explain their handling of service logs, backups and records they keep for their own purposes. The site's fonts are served from our host.

Cookies and on-device storage

The learning app stores a sign-in session on your device. On web, Google Analytics uses cookies such as _ga and _ga_<container-id>. Your browser settings can block or delete those cookies. Sign-in and payment providers can use their own storage when you open their services.

Browser or app storage also holds queued lesson and quiz completions, including answers, until they can sync, along with preferences such as whether you have seen the welcome screen. The marketing site remembers when course prompts have been shown or dismissed. Native apps cache course assets and update files.

Signing out clears the local sign-in session. Successful in-app account deletion also removes that account's pending local completion queues on the device used for deletion. It does not remotely clear storage on your other devices; clear SailStarter's browser or app storage there to remove remaining local copies.

Analytics and advertising

The marketing site and web learning app run Google Analytics. It receives pages visited, approximate location derived from IP address, device and browser type, referral information and interactions with lessons and purchase links. On blog articles, it records when a reader has spent at least ten seconds and reached 60% of the page, when an article link into a lesson is clicked, and when a quick-check answer is revealed. Those events carry the article handle, lesson reference and link placement, not answer text or form input.

Google Analytics does not run in the native app. Native purchase activity still goes through RevenueCat for purchase reporting and app functionality. Expo aggregates update requests for installation and update-usage analytics, and processes crash and other diagnostic data for update delivery and recovery. We do not enable Google Signals or advertising personalization, and we do not run advertising pixels or session recording.

How long we keep it

• Account, profile, course activity and account-linked billing records remain while you have an account. Deleting it removes these records from our active database, including quiz attempts and stored reward records.
• Separate payment-event records may remain after deletion to reconcile billing, prevent duplicate processing and handle retries. They contain event or payment IDs, status and timestamps, not your course progress or full billing-event messages.
• Dodo and Apple keep their own transaction records for billing, refunds, tax, fraud prevention and legal obligations. Deleting a SailStarter account does not erase those records. We request deletion of the associated RevenueCat customer before removing your sign-in account.
• Backup copies and provider service logs, including email-delivery, update, crash and diagnostic records, may remain after account deletion. Their expiry depends on the provider's retention settings and applicable obligations; account deletion does not immediately erase every backup or log.
• Course-update addresses remain until you request removal from that separate list. Support correspondence may remain to resolve your request and keep a record of its handling. You can ask us about removal of those records too.

Contact us about retained information. If a record must be kept to meet a legal obligation or resolve a billing issue, we will explain what remains and why.

Your rights

You can ask us what information we hold about you, request a copy in a portable form, ask us to correct it, or request deletion. Email tikhonenkoigor@gmail.com. We may need to confirm that the account or information belongs to you.

You can withdraw your request for course-update emails by asking us to remove your address from that list. Where processing depends on your consent, you can ask to withdraw it. If we cannot fulfil a request, we will explain why. We do not charge for making a request or treat you differently for doing so. Depending on where you live, you may also complain to your data-protection regulator.

Deleting your account and your data

Deletion stops future renewals for all active web Monthly subscriptions on your account, including any on hold or past due. It does not cancel Apple subscriptions. Cancel Apple Monthly separately in your iPhone Settings: your name, Subscriptions, SailStarter, then Cancel Subscription. This applies even if you also have a web plan. See Apple's cancellation instructions. Deleting an account does not automatically refund a purchase.

We complete RevenueCat customer cleanup before removing the sign-in account and revoke SailStarter's Sign in with Apple authorization for an Apple-linked account. If required cleanup fails, deletion is not reported as complete; retry or contact support. Deletion removes your profile, lesson progress, quiz attempts, stored activity and rewards, account-linked billing records and any account-linked learner quote from our active database. The app also clears the local completion queues for that account on the device used for deletion.

The retention section explains which separate payment-event records, provider records, logs and backups may remain. Deleting your SailStarter account does not delete your Apple or Google account.

To remove your address from the separate course-update list, email us and ask, whether or not you have a SailStarter account. Account deletion does not remove it automatically. We do not currently send course-update emails; before we begin, each will include an unsubscribe link.

Children

You must be at least 16 to create a SailStarter account. SailStarter is not directed at children, and we do not knowingly collect information from anyone under 16. If you believe someone under 16 has an account, contact us so we can delete it.

Changes to this policy

We update the date above when this policy changes and explain material changes to collection, use or sharing. This update adds native app, Apple purchase, RevenueCat, Resend and Expo disclosures, and clarifies in-app deletion and records retained after deletion.