1. Information we use
Account information includes your email, account ID, salted password hash, policy versions and acceptance time, watch connections and security records. Workouts include swims and related health samples you authorize, select and confirm for upload: time, distance, strokes, lengths, pace, stroke counts and heart rate, plus available energy, HRV, resting heart rate, water temperature, depth, measured or estimated workout effort scores and GPS routes. Uploaded files also contain workout sources, recording devices and related workout metadata. Routes may include timestamps, coordinates, altitude, speed and accuracy. Available fields depend on your device, workout and permissions. We also process feedback, app versions, replies and support emails, and technical information such as device and system versions, language, time zone, sync status, IP addresses and necessary error and security logs.
2. How we use it
To sign you in, connect your watch, sync and display workouts, calculate metrics, compare swims, create simulated replays, respond to feedback and protect the service. Replays come from workout data, not video footage or medical conclusions. We do not sell personal information or use health or route data for advertising or training general-purpose AI models.
3. You control uploads
Swimiyo can read swimming workouts after you grant access in Apple Health. On iPhone, it reads summaries for your selected date range and sends their workout identifiers to Swimiyo to check which workouts have already synced to your account. Workout details are uploaded after you select workouts and confirm on iPhone or Apple Watch. Depending on the source record and permissions, an iPhone import may include workout times, duration, pool length, distance, lengths, swim strokes, stroke count, heart rate and active energy. iPhone import does not read GPS routes. Accepting an account policy does not grant Apple Health access. Revoking permission stops future access but does not erase cloud copies. Disconnecting the watch revokes its credentials. To remove cloud data, delete your account or contact support. We do not write workouts back to Apple Health.
4. Storage and providers
Our account API, MySQL database and server database backups are hosted by Tencent Cloud in Singapore. Workout files are stored in Tencent Cloud COS in Singapore. Cloudflare Pages hosts the website. Cloudflare Email Routing forwards support messages to Gmail for the operator to handle. Cloudflare and Google may process access or email information outside Singapore; not all information stays in one country. We share only what providers need for their roles, or what applicable law requires. iPhone Health import and sync-status checks may pass through Cloudflare Workers before reaching the same Swimiyo backend. Cloudflare processes the sign-in token, workout identifiers and, for uploads you confirm, workout details in these requests. The forwarding service uses HTTPS, does not cache responses or store workout copies, and does not write tokens or workout contents to application logs. Cloudflare may still process infrastructure information needed to operate and protect its network. Processing locations depend on its network and may be outside Singapore or your country.
5. Scanning and device storage
Android linking uses Google Code Scanner / ML Kit, which processes scan images on your device. According to Google's SDK documentation, it also sends Google technical data over HTTPS: device, system and app information, device or installation identifiers, initialization and usage events, latency, errors, API settings and input/output sizes. Google uses this for diagnostics, usage analytics, service maintenance and improvement, and abuse detection under its privacy rules. On-device image processing does not mean the SDK sends no data. Swimiyo has no separate in-app switch to disable this collection. Deleting your Swimiyo account does not also delete SDK information Google processes independently. Android and iPhone store sign-in credentials and workout caches. iPhone also stores import progress and pending files so you can retry. Apple Watch stores connection credentials and queued files. Device copies and cloud copies are managed separately.
6. Retention and erasure
We keep accounts and workouts while needed for the service. Once a verified deletion request is accepted, credentials are disabled immediately. Online account data, workout files, linked feedback and connection records are erased within 7 calendar days. Database backups expire by file age, with affected copies removed within 30 days. Before serving a restored database, we disable previously deleted accounts again. A separate deletion record contains only an account ID and timestamps, retained for up to 31 days to prevent restored backups from reviving accounts.
7. Support emails and logs
Separate support emails are kept for no more than 90 days after the case closes; valid requests for earlier erasure are handled promptly. The operator marks the actual closure date and checks expiry daily, manually if scheduled checks are unavailable. Self-managed API access, error and cleanup logs rotate daily and are kept for at most 12 days under normal scheduling; they do not include passwords, full tokens or workout contents. Cloudflare and Google's own infrastructure logs follow their service rules, not our server rotation. Any legally required retention is limited to the necessary purpose, period and access.
8. Account deletion and other rights
In the app, go to Profile → Account security → Delete account, enter your current password and confirm. If you cannot use the app, email [email protected] from your registered address. We acknowledge requests within 3 business days and verify email ownership and your intent before accepting deletion. We do not need your password or ID document. You can also request access, correction, export or erasure. The erasure period starts when a verified request is accepted; acknowledgement is not proof that erasure is complete.
9. Security and limits
We use HTTPS, salted password hashes and revocable credentials. The service is not end-to-end encrypted, and no system is guaranteed completely secure. Account deletion does not erase Apple Health or other apps' records. You may need to clear device caches and Watch files separately. Uninstalling does not delete your cloud account.
10. Website, age and changes
The website has no account-registration form or advertising. With your permission, it loads Google Analytics 4 and analytics cookies to measure page views, referrals and clicks on download, help or contact buttons. A click does not confirm installation. You can change or withdraw your choice through Analytics choices in the footer. We do not send account details, email addresses or health data to GA4, and advertising signals and ad personalization are disabled. Google may process analytics information outside your country. Cloudflare hosting, security and separate website statistics may still process necessary access and security information. The app does not load the website’s GA4 scripts. Swimiyo is for people aged 18 or over, is not a medical service and is not designed specifically for children. Contact us if a child's information has been collected. Updated versions and effective dates appear in the app and on the website. We give separate notice of material changes and seek renewed consent where required. Google privacy policy: https://policies.google.com/privacy. Cloudflare privacy policy: https://www.cloudflare.com/privacypolicy/.
11. Email verification and password recovery
Resend sends verification codes for registration and password recovery. We provide the recipient address, code and necessary message content, not passwords or swim, health or route data. Our sending domain uses the North Virginia, US region. This does not mean all Resend processing or storage stays there; email information may be processed outside Singapore. The free plan retains message content and sending records for 30 days by default. That is not the code's lifetime: codes expire after 10 minutes and cannot be reused after success. Our own code records contain only digests and are periodically removed after expiry. Short-lived abuse-prevention counters use digests for email-related identifiers. Resend's retained emails and copies in recipients' mailboxes are separate from the online account-database erasure described in section 6. Verification emails do not use open or click tracking. Resend privacy policy: https://resend.com/legal/privacy-policy.
[email protected] · 2026-11-05.1