Your swim records are private.
Ripple stores your account identity, swimmer names or nicknames, optional academy names, the optional swimmer details you choose to add (date of birth, sex, school name and area, federation or club registration number, academy history (academy, branch or pool, squad or level and dates), a growth record (height, weight and arm span, with dates), learn-to-swim milestones (which steps a swimmer has reached, with dates), and a profile picture (kept small, with the photo’s location data removed)), and the swim results, notes and goals you enter so you can find your swimmers’ results again. Ripple keeps your email address and sign-in details in its own database in Amsterdam. When a parent account first agrees to Ripple’s terms, we also store the country you tell us you live in, so we know where families use Ripple. If you invite another parent to share a swimmer, Ripple itself stores the address you invited them at. If they accept, we keep it so you can see whose access it is, and so swims they added still say who added them — including after you remove their access. If they never accept, we keep it until you invite that address again. Either way it goes when you delete the swimmer, and if that person deletes their own Ripple account we remove their address from your invitations.
Child read-only accounts
A parent or legal guardian can invite a child aged 13 or over to read only their own swims and goals. We keep the invited email, account identity, access state and the version/date of the child’s terms/privacy agreement. Date of birth is required to confirm eligibility only when the parent enables this access. The child cannot see notes, growth or other profile details, cannot edit or share records, and cannot buy a subscription. Their email and sign-in details are kept by Ripple itself, in Amsterdam. Parents can turn access off at any time; deleting the child’s sign-in account removes its access and invited email while leaving the parent’s swimmer records.
You control your records
Use Account settings to download your results or delete your account. Deleting a swimmer profile also deletes that swimmer’s results. Account deletion blocks access while cleanup finishes.
Storage and backups
Records are stored in Ripple’s database at our hosting provider, Railway, in its EU West region in Amsterdam, the Netherlands. Only you can see your swimmers, unless you share one: a parent you invite can see that swimmer and add, change and delete their swims and goals. They cannot rename that swimmer, delete them, or share them with anyone else. You can remove someone’s access at any time, and you can hand a swimmer over to them for good. Records are not public. The web app keeps a copy of the swimmers, swims and goals you last saw in your browser, so you can read them without a connection; it is removed when you sign out or delete your account. The iPhone app keeps a copy on your phone for the same reason, and removes it when you sign out or delete your account. The sample preview stays in the current page and is discarded when you reload.
Deleted data expires from backups within 89 days. A restored backup must not reactivate deleted accounts.
Usage and errors
We do not send swimmer names, meet names, or swim results to analytics. When something fails on our server we record a reference for that request, the method, the path and the kind of error. Those notes hold no swimmer names, meet names, swim times or email addresses. A short alert, saying only what kind of failure it was, which part of Ripple it happened in and the request reference, is sent to Sentry, an error-reporting service, which keeps it in the United States, so we can find and fix the failure.
Who else handles your data
Ripple runs its own sign-in and keeps your email address and sign-in details in its database in Amsterdam. If you choose to sign in with Google or Apple, that company receives the sign-in request and tells Ripple your email address; otherwise neither is involved. The emails Ripple sends, such as sign-in codes, go through Resend, which keeps its email logs in the United States. When Plus can be bought, payments go through Stripe, and Ripple never sees card details. How Ripple looks after children’s data sets out what we hold about a child and where it is kept.
Feedback and interviews
Feedback you send from the app or to our support address arrives by email in Ripple’s support inbox; it is not stored in the app. During the beta we may copy what you say into our own notes, and write notes if you take part in an interview. Those notes use a household code, never your name, your swimmers’ names or your email address, and are deleted 12 months after the beta ends (by 15 December 2027 at the latest).
Waiting list
If you request early access, we store your email address, which plan you asked for and whether you asked for a founding-family place, your academy name and number of swimmers if you give them, your country and, if you give it, your city, the date you asked, what you said would help you most and anything else you wrote, and the campaign link that brought you to the form, if any. We use them only to email you a link to confirm a founding-family place, to give the places to the first 100 households in the UAE who confirm, to start your free month when you sign up with the same email address, to tell you when it starts, and to learn what families need from Ripple, and keep them until the founding-family beta ends or you ask us to remove you, whichever comes first. If you ask for a founding-family place and do not confirm it by email within 48 hours, the link stops working and we delete your request. To be removed, email support@silverlinefuture.com.
Cookies
Ripple uses no advertising or tracking cookies and has no analytics. The only cookies are for signing in. On the family site, Ripple sets one cookie that keeps you signed in, __Secure-ripple-family.session_token, once you sign in, plus a few short-lived ones while you sign in with Google or Apple. Nothing is set before you sign in. Each sign-in keeps the device’s IP address and its browser or app description with the session, for up to 30 days, to help keep your account safe. They are needed for the site to work, and you can delete them in your browser at any time; you will be signed out. When you are signed in it keeps two small choices in your browser’s local storage, which is not a cookie and stays on your device: that you have seen the welcome tour, and how you like your share cards. The web app’s offline copy of your records, described under Storage and backups, is kept in the browser too and is not a cookie. Our internal tools, which families never see, set sign-in cookies of their own for team members only; the sign-in ends within 12 hours.
Contact
Email support@silverlinefuture.com for help with access or deletion.