← SwimRead

Privacy Policy

Last updated: October 1, 2026

Developer: H2N Ventures LLC · Florida, USA

Privacy contact: henrique@swimread.com

This policy covers the current SwimRead app and swimread.com. The app and website have different data flows, described separately below.

1. The Short Version

2. Your Video and Local App Data

Video processing and pose detection run on your device. When you select a video, the phone gives SwimRead a working copy in private app storage. The app does not change, move, or delete the original in your photo library. A recording made inside the app stays in private app storage; SwimRead does not add it to your gallery. The camera may record sound with the video, but SwimRead does not analyze audio.

Analysis history, profile preferences (such as level and best time), feedback, language, and the result of the age check are stored on the device. Swimmer nicknames, links between swimmers and analysis records, and chosen training focuses are kept for the current account or guest profile on this device. They are not a shared coach dashboard.

Date of birth is used locally to check age and is not saved. Only the adult or blocked status is retained. This is a self-declared age check, not identity or document verification.

3. Data Sent by the App

3.1. Account — only if you sign in

Sign-in uses Supabase with an email code, Google, or Apple. We receive your email address, provider account identifiers, and your name if Apple shares it. You can use the core analysis flow without an account.

3.2. Analysis results — only if you sign in

Results synchronize to your account in Supabase: stroke, category measurements and validity, legacy score and tier fields when present, report text, analyzed video time window, and date. A time window describes which seconds were analyzed; it is not a video upload. Legacy numeric fields do not mean the current interface grades swimming technique.

3.3. Feedback — only if signed in and you choose to send it

When you rate or report a result, feedback can include your comment, category, related score and stroke, and technical pose information, linked to your account.

3.4. Technical measurements — after every analysis

To check and improve the analysis, the app sends category values and validity, legacy overall score and tier, median body angles, body-roll amplitude, frame count, processing time, app and scoring versions, and profile level and best time if provided. It also sends coordinates for up to 33 body landmarks in each analyzed frame as numbers, not images.

These records do not contain your name, email address, account ID, video frames, or images. They describe body movement and are sent from your app, so we do not call them anonymous or promise that they cannot be linked to a person. There is currently no setting to opt out of this transmission. Collecting data does not mean the model automatically retrains or becomes more accurate after every analysis.

3.5. Configuration, subscriptions, and reminders

The app can request analysis configuration from our cloud. RevenueCat, our subscription provider, can receive an app-generated identifier and purchase or subscription status to check access and restore purchases. New purchases are paused in the current beta, but the RevenueCat integration is present. If purchases are offered, the App Store or Google Play handles payment; we do not receive card details.

The weekly reminder is scheduled locally. The app does not send us a push-notification token for that reminder.

4. Providers and Sharing

We do not sell or rent app data or use it for advertising. The app does not display ads or use third-party advertising analytics. This does not mean it sends no data to service providers. Providers can process data outside your country.

5. Retention

6. Choices and Requests

You can analyze without an account; account synchronization and signed-in feedback do not occur in guest mode. Technical measurement transmission still occurs as described in Section 3.4.

You can delete an analysis from history and request account deletion from Profile. Account deletion asks our server to remove the account and its linked results and feedback. It does not cancel a store subscription or automatically remove separate technical measurement records.

To request access, a copy, correction, or deletion of your data, or removal from the waitlist, email henrique@swimread.com. We may need information to locate the relevant records. Do not send passwords or payment details. Rights and applicable response periods depend on your jurisdiction. This policy does not promise that records without account identifiers can always be matched to an individual request.

For users in Brazil, applicable LGPD rights include confirmation, access, correction, anonymization, portability, deletion, information about sharing, and withdrawal of consent. You can also contact the ANPD.

7. Age

This version of SwimRead is for adults aged 18 and over. The app blocks access when a user declares an age below 18. It does not offer a parental-consent flow. Beta and coach waitlists are intended for adults. If you believe a child has submitted personal data, contact us so we can investigate the relevant records.

8. Website Data and Cookies

The website waitlist sends your email address, whether you selected swimmer or coach, and the form source to Supabase. The coach form also displays name, club, and athlete-count fields; the current submission does not send those values to the waitlist database.

The server uses request IP addresses temporarily in memory to limit repeated form submissions. Hosting services receive the request information necessary to deliver the site and may maintain their own operational logs.

The site includes Vercel Analytics for traffic measurement. When configured, Google Analytics 4 also receives page and browser or device information and can use cookies or similar identifiers. These website analytics are separate from the app's technical measurements. Browser tracking protection or cookie blocking can restrict some collection. The site does not currently implement an on-site analytics consent or opt-out control.

The private administrator area uses an essential signed session cookie. Public visitors do not need an administrator account. We do not use the website waitlist as an app sign-in account.

9. Security

Data sent to our cloud travels over HTTPS. App sign-in uses an email code or an external identity provider rather than an app password. These measures do not guarantee that every security risk is eliminated.

10. Changes and Contact

Significant changes will be communicated through the app or website before taking effect. This page's date identifies the policy text; it does not mean a new app build was released on that date.

H2N Ventures LLC · Florida, USA

henrique@swimread.com