RYPT Privacy Policy
Last modified: 9th November, 2026 · Version 2.0
1. Who we are and how to contact us
1.1 RYPT is operated by Flamenco IL Holdings Limited, trading as RYPT, company number 620421, 6 The Crescent, Galway, Ireland, H91 NHP3.
1.2 For anything about your personal data, including exercising your rights, email [hello@rypt.app] or write to the address above marked “Privacy”.
1.3 Our Data Protection Officer is Daniel O’Beirne, who can be contacted at the same address.
1.4 You have the right to complain to the Data Protection Commission, Ireland (dataprotection.ie), or to the supervisory authority where you live. We would welcome the chance to resolve your concern first.
2. The short version
- RYPT is a coaching platform. Most data on it is athlete data held in a Gym run by a club, school, team or coach. That organisation is the controller of that data and RYPT processes it on their behalf. To discuss how they use your data, please contact them.
- RYPT is the controller, and this policy applies, for: our website visitors; the accounts, billing, support and marketing of the organisations and coaches who are our customers; your own athlete account when it is not connected to a Gym; and purchases of programs until you redeem them.
- We store data in the European Union. A few of our providers are US companies; transfers to them are covered by the EU-US Data Privacy Framework or standard contractual clauses.
- We do not sell personal data, use it for advertising, or use it to train AI models.
- You can see, export, correct and delete much of your data in the app, and you can ask us for the rest.
3. Who is responsible for your data
3.1 Athlete data in a Gym: your Gym is the controller. When you use RYPT as an athlete or client connected to a Gym, the organisation or coach that runs the Gym decides what data is collected about you and why. They are the controller. RYPT is their processor: we store and process the data on their instructions, under a data processing agreement, and only to provide RYPT. This policy does not cover how your Gym uses your data; your Gym must give you its own privacy notice. If you want to access, correct or delete data your Gym holds, ask your Gym first; we will help them respond.
3.2 Your account when it is not in a Gym: RYPT is the controller. Your RYPT account is yours. If you unlink from a Gym, or have never joined one, the data in your account can be seen only by you. For that data RYPT is the controller and this policy applies.
3.3 Health data in your own account. If your account holds injury, wellness, body composition or menstrual cycle data and no Gym can see it, we hold that health data for you on the basis of your explicit consent, which we ask for in the app. You can withdraw consent at any time and request that your account be deleted.
3.4 Coaches and organisations: RYPT is the controller for your account, billing, support, security and marketing data. What you and your Trainers put in your Gym about your athletes is covered by 3.1.
3.5 Buying a program: RYPT is the controller for your account and purchase until you redeem the program; Stripe is a separate controller for your payment card data; after redemption, the Gym that sold it becomes the controller of your training data (3.1).
3.6 Website visitors: RYPT is the controller.
4. What we collect, why, and on what legal basis
The tables below cover the data RYPT is controller for. “Legitimate interests” means we have weighed our interest against yours and concluded the processing is justified; you can object (Section 9).
4.1 Website visitors (rypt.app)
| Data | Purpose | Legal basis |
|---|---|---|
| IP address, browser and device type, pages viewed, referrer, timestamps (server logs) | Run and secure the website, detect abuse | Legitimate interests (security and operation) |
| Analytics cookies and identifiers [CONFIRM tool] | Understand how the site is used, improve it | Consent, via the cookie banner |
| Name, email, organisation, message (contact, demo and trial forms) | Respond to you, set up a trial | Steps before a contract (for trials); legitimate interests (responding to enquiries) |
| Email and engagement data where you opt in to our newsletter | Send marketing about RYPT | Consent; or, for existing customers, legitimate interests with an opt-out in every message |
4.2 Customers, Gym administrators and Trainers
| Data | Purpose | Legal basis |
|---|---|---|
| Name, email, phone, role, organisation, profile photo, login credentials | Create and run your account and Gym; authenticate you | Contract (Customer Terms, End User Terms) |
| Billing contact, invoices, subscription history; card details are held by Stripe, not us | Charge and account for subscriptions | Contract; legal obligation (tax and accounting records) |
| Stripe Connect account status and payout records for Product sales | Pay out sales, prevent fraud | Contract; legal obligation (anti-money-laundering checks performed by Stripe) |
| Support correspondence and ticket history | Help you, improve the product | Contract; legitimate interests (service quality) |
| Product usage events (features used, errors), pseudonymised | Improve RYPT, fix problems, plan capacity | Legitimate interests (product improvement) |
| Marketing preferences and engagement with our emails | Tell you about RYPT features and offers | Legitimate interests (marketing to existing customers) with opt-out; consent for others |
| Security logs: logins, IP address, device, admin actions | Protect accounts and data, investigate incidents | Legitimate interests (security); legal obligation (GDPR Article 32) |
| Records of your agreement to our terms and policies | Prove what was agreed | Legitimate interests; legal obligation |
4.3 Athletes and clients, where RYPT is controller (Section 3.2)
| Data | Purpose | Legal basis |
|---|---|---|
| Name, email, date of birth, profile photo, login credentials | Run your account, authenticate you, apply age rules | Contract (End User Terms) |
| Training, activity, body composition, nutrition and performance data you keep in your account | Let you keep and view your own training history | Contract (End User Terms) |
| Injury, wellness, readiness and menstrual cycle data you keep in your account | Let you keep and view your own health-related training data | Explicit consent (Article 9(2)(a)), which you may withdraw at any time |
| Invitations from Gyms to connect, and your response | Connect you to a Gym when you accept | Contract |
| Service emails and push notifications about your account, sessions and programmes | Operate the service | Contract |
| Crash and performance reports from the app, pseudonymised | Keep the app working | Legitimate interests |
| Messages between you and Trainers, after you leave a Gym | Kept in your account for your reference | Contract |
4.4 Purchasers of programmes
| Data | Purpose | Legal basis |
|---|---|---|
| Name, email, account details, the Product bought, price, date, redemption status | Deliver the purchase, issue receipts, handle refunds and disputes | Contract; legal obligation (tax records) |
| Payment card data | Processed by Stripe as its own controller; we receive only the last four digits, card type and the result | Not held by RYPT |
| Confirmation that you asked for immediate access and waived the cancellation right | Comply with consumer law | Legal obligation |
4.5 What we do not do
We do not sell personal data. We do not use personal data for advertising or share it with advertising networks. We do not use personal data to train AI or machine-learning models. We do not obtain data about you from social networks or data brokers. We do not make decisions about you by automated means that have legal or similarly significant effects; training-load and readiness scores in RYPT are calculations shown to you and your coach, not decisions made about you.
5. Who we share data with
5.1 Service providers that process data for us. Each is bound by a contract that limits what it may do with the data.
| Provider | What they do for us | Data | Where |
|---|---|---|---|
| Microsoft (Azure) | Hosting, databases, storage, backups | All platform data | EU (Netherlands) |
| MongoDB (Atlas) | Database for Gym invitations | Name, email, invite link | EU |
| Intuit (Mailchimp and Mandrill) | Service emails (invitations, password resets, notices) and, if you opt in, our newsletter | Name, email, message content | USA |
| Google (Workspace) | Our email and support mailbox | What you send us | EU / USA |
| Google (Firebase) | App crash and performance reporting | Pseudonymous device and app identifiers | USA / EU |
| Microsoft (Application Insights) | Platform performance monitoring | Pseudonymous usage identifiers | EU |
| Stripe | Subscription payments and programme sales | Billing details and transaction data; card data held by Stripe as its own controller | EU / USA |
| HubSpot | Customer relationship management and support for organisations and coaches | Name, email, organisation, correspondence | EU hosting |
| Atlassian | Engineering issue tracking; may contain support details when we investigate a problem; no identifiable personal data | Account identifiers, problem descriptions | EU / USA |
| Slack | Internal communication; no identifiable personal data | Occasional customer names in support discussion | USA |
| AccountsIQ | Accounting and invoicing | Customer billing details: Name, Invoice number | Ireland |
5.2 Your Gym. If you are an athlete connected to a Gym, the Gym’s Trainers see your End User Data; that is the point of the service, and your Gym is the controller of it (Section 3.1).
5.3 Sellers of programs. When you redeem a program, the Gym that sold it sees your training data for that program.
5.4 App stores and operating systems. Apple and Google receive the data they need to deliver the app and push notifications under their own privacy policies.
5.5 Professional advisers, insurers and auditors, under confidentiality, where needed to run our business or certify our security.
5.6 Authorities. We disclose data where the law requires it or where it is necessary to protect someone’s safety, to investigate fraud or abuse of RYPT, or to establish or defend legal claims. Where lawful we tell you first.
5.7 A buyer of our business. If RYPT is sold or merges, the buyer receives the data on the same terms as this policy, and we will tell you.
We do not share data with advertisers, data brokers or “co-marketing partners”.
6. International transfers
6.1 All platform data is stored in Microsoft Azure data centres in the European Union. Some providers in Section 5 are based in the United States or may access data from there for support.
6.2 For those transfers we rely on the EU-US Data Privacy Framework (and its UK Extension) where the provider is certified: Microsoft, Google, Intuit, HubSpot, Slack and Atlassian. Where a provider is not certified, we use the European Commission’s standard contractual clauses and, for UK data, the UK Addendum, together with an assessment of the destination country’s laws.
6.3 You can ask us at [hello@rypt.app] for a copy of the safeguards used for a specific provider.
6.4 If a transfer mechanism we rely on is invalidated, we will move to an alternative lawful mechanism or stop the transfer.
7. How long we keep data
| Data | Kept for |
|---|---|
| Your account and the data in it | For as long as your account is open. After you close it, deleted within 30 days and removed from backups within a further 90 days |
| Athlete accounts not connected to any Gym and not used | Closed after 24 months of inactivity, after we email you 30 days beforehand; then as above |
| Billing records, invoices, payout records, tax records | 7 years after the transaction, as required by Irish tax law |
| Support correspondence | 3 years after the ticket is closed |
| Marketing consent and preferences | Until you withdraw consent or 24 months after your last engagement with us |
| Records that you accepted our terms, or waived a cancellation right | For as long as your account is open and 6 years after, for the limitation period on contract claims |
| Security and access logs | 12 months |
| Website server logs | 90 days |
| Website analytics | 14 months |
| Crash and performance reports | 90 days |
| Data in a Gym that is controlled by your Gym | Decided by your Gym. When a Gym’s subscription ends, or you unlink from it, the Gym’s access ends immediately; the data stays in your own account under the rules above |
Where a legal hold, dispute or investigation requires it, we keep the relevant data until it is resolved.
8. Security
We protect personal data with measures that include hosting in EU data centres certified to ISO 27001, encryption of data in transit and at rest, role-based access with multi-factor authentication for staff, access logging, regular penetration testing, and a tested backup and incident-response process. Our security programme is aligned with ISO/IEC 27001. No system is perfectly secure; if a breach affects your data and poses a risk to you, we will tell you and the relevant authority as the law requires.
9. Your rights
9.1 For data RYPT controls, you have the right to: access it and receive a copy; have it corrected; have it deleted; restrict how we use it; receive it in a portable format; object to processing based on legitimate interests, including direct marketing; and withdraw consent where we rely on it, without affecting what was done before.
9.2 In the app you can view and edit your profile, and unlink from a Gym.
9.3 By request: email [hello@rypt.app]. We will respond within one month; we may extend by two further months for complex requests and will tell you if so. We may ask you to confirm your identity. Requests are free unless clearly unfounded or excessive.
9.4 Data your Gym controls: ask your Gym. If you contact us instead, we will pass your request to the Gym within five business days and help them respond. We will not change or delete data in a Gym on our own initiative, because the Gym is responsible for it.
9.5 You can complain to the Data Protection Commission (Section 1.5) at any time.
10. Children
10.1 RYPT is used by youth academies, schools and clubs, so many athletes on it are under 18. An athlete under 16 may only use RYPT through a Gym that holds a parent’s or guardian’s consent, or with an account created by a parent or guardian. The Gym is responsible for obtaining that consent as the controller.
10.2 We do not knowingly allow anyone under 16 to create their own account without a Gym. If you believe a child has an account in breach of this, email [hello@rypt.app] and we will close it.
10.3 We never use children’s data for marketing.
11. Cookies and analytics
11.1 Website. https://www.rypt.app uses strictly necessary cookies to work, and analytics cookies only if you accept them in the cookie banner. You can change your choice at any time via the cookie settings link in the footer. Our Cookie Policy at [https://www.rypt.app/cookie-policy] lists each cookie, its purpose and its lifetime.
11.2 Platform and apps. The web platform and apps uses session cookies needed to keep you logged in and to secure your session. The apps send pseudonymised crash and usage events to the providers in Section 5 so we can keep the apps working. These events are not linked to your name or contact details and are not used for advertising.
11.3 Email. Our newsletter emails may record whether they were opened or clicked, so we can measure what is useful. Service emails do not track you.
12. Marketing
12.1 We send marketing about RYPT to organisations and coaches who are customers or who have opted in, and to anyone else only with consent. Every marketing email has an unsubscribe link, and you can also email [hello@rypt.app].
12.2 Unsubscribing from marketing does not stop service emails about your account, which we need to send to run RYPT.
12.3 Your Gym may contact you separately. That is their responsibility; to stop receiving emails from them you must unsubscribe with them.
13. Changes to this policy
We review this policy at least annually and when our practices change. We will post the new version here with a new “Last modified” date, and for material changes we will tell account holders by email or in the app before they take effect. Previous versions are available on request.