RINJA
EN

Privacy Policy — Rinja

Version of 21 October 2026 — draft for review, not yet published.

This policy explains what data Rinja (the "App") collects, why, who it is shared with, how long it is kept, and what your rights are. It is written to be read in full in a few minutes.

1. Data controller

Izi-IA [legal form, registration number and address to be completed].

Contact for any question about your data: support@rinja.com. We have not appointed a data protection officer: this address is read by the person who acts in that role.

2. The data we process

All this data comes from you or from your use of the App. Data marked "optional" can be left empty; the rest is needed to provide the service, and without it the account cannot be created or the programme cannot be generated.

2.1 Identity and account

Email address, password (stored hashed, never readable by us), first name, last name (optional), climbing gym (optional), profile photo (optional), language, account creation date.

2.2 Training profile

Sex (or "undisclosed"), date of birth, height, weight, the month you started climbing, how many times a week you climbed before the programme, fingerboard experience, current level and target grade, disciplines, practice environments, available equipment, goal, number and length of sessions, available days, other sports practised, the wall heights of your gym.

Some data is used to adapt training to your body and to protect you. This is health data under the GDPR (article 9), which we process only with your explicit consent, given at sign-up:

You can withdraw this consent at any time by deleting your account. Without this data, the App cannot generate a suitable and safe programme: this is why withdrawing consent ends the service.

2.4 Activity

Generated programmes, sessions (prescribed, done, skipped), validated sets, perceived effort, sends (boulders and routes), records, badges, consistency streaks, estimated metres climbed, and the free-text end-of-week comment (300 characters at most).

The coach's notebook: short observations (160 characters at most) that the coach writes about your training from one week to the next — for example "skips core work when it comes at the end of a session". They are not shown in the App, but are included in the copy of your data (see 7); an observation the coach does not renew is deleted after eight weeks.

2.5 Circle

Friends list, sent and received requests, invitation links, posts (text, photo, attached session or record), comments, reactions, reports you submit, people you block, the metrics you choose to share, invisible mode.

2.6 Subscription

The state of your trial and subscription (plan, status, end date), technical subscriber identifier. No banking data: payment is handled by Apple or Google, who do not pass your payment method on to us.

2.7 Technical data

Crash and error reports (device model, system and App version, technical error trace), programme generation log (duration, cost, safety adjustments applied). No advertising trackers, no cookies.

3. Why, and on what basis

PurposeDataLegal basis
Create and manage your account, sign you in2.1Performance of the contract
Generate and adapt your programmes2.2, 2.3, 2.4Contract; explicit consent for health data
Track your progress, records, badges2.4Performance of the contract
Run the circle between accepted friends2.1 (first name, last name, photo), 2.5, shared metricsPerformance of the contract
Moderate reported content2.5Legitimate interest (user safety) and legal obligation
Manage the trial and the subscription2.6Contract; legal obligation (invoicing)
Fix crashes, secure the service2.7Legitimate interest
Inform you of an important change (terms, security)emailLegal obligation / legitimate interest

We do not use your data for advertising and we do not sell it to anyone.

4. AI generation

To build your programme, our servers send Anthropic PBC (provider of the Claude model, United States) an extract of your data, strictly limited to what serves training:

Never sent: your first name, last name, email address, photos, circle posts, comments or friends.

The model only picks from validated exercises and session templates; our servers then check every programme against safety rules before showing it to you. Under Anthropic's commercial terms, this data is not used to train its models and is kept only for a limited period (30 days at most) for safety purposes. This transfer outside the European Union is covered by the European Commission's standard contractual clauses.

No decision with legal effect on you is taken automatically.

5. Who your data is shared with

5.1 Your friends

An accepted friend only sees a reduced card: first name, last name, profile photo, level, badges, and only the metrics you chose to share in the settings. Your weight, height, strength tests, injuries, detailed sessions and comments never leave your account; this filtering is enforced by the database itself, not by the App.

Your posts are visible only to your accepted friends. Invisible mode removes you entirely from search, suggestions and the ranking.

5.2 Our processors

ProviderRoleLocationData
Supabase Inc.Database hosting, authentication, photo storage, server executionEuropean Union (Ireland)All
Anthropic PBCProgramme generationUnited StatesSee section 4
Apple Inc. / Google LLCApp distribution, subscription paymentDepending on your countrySubscriber identifier, transactions
RevenueCat Inc.Subscription state trackingUnited StatesTechnical identifier, plan, status, dates
Sentry (Functional Software Inc.)Crash reportsEuropean Union (Germany)Technical data (2.7)
ResendAlert sent to our moderation team for each reportUnited StatesReported content, reason, first and last name of its author
[Transactional email provider to be completed]Confirmation and security emails[to be completed]Email address

Every transfer outside the European Union relies on the European Commission's standard contractual clauses or on an adequacy decision (Data Privacy Framework).

5.3 Authorities

We may disclose data where the law requires it or in response to a legitimate request from an authority.

6. How long

DataDuration
Account, profile, activity, circleAs long as your account exists
After account deletionErased immediately; technical backups purged within 30 days
Processed reports12 months after handling, to prevent repeat abuse
Generation log12 months, anonymised thereafter
Crash reports90 days
Subscription recordsStatutory accounting retention period (10 years), held by Apple or Google
Inactive accountDeleted after 3 years without sign-in, with prior warning by email

7. Your rights

At any time you may:

Write to us at support@rinja.com; we answer within one month. We may ask you to confirm your identity from the account's email address.

If you believe your rights are not respected, you may lodge a complaint with the French data protection authority, the CNIL (cnil.fr), 3 place de Fontenoy, 75007 Paris, or with the supervisory authority of your country of residence.

8. Security

Your data is encrypted in transit (TLS) and at rest at our host. Access to every piece of data is controlled row by row by the database (row-level security policies): a user can only read what belongs to them or what a friend chose to share. Post photos are stored in a private space and served through signed, time-limited links. The keys to the AI services never leave our servers.

No system is infallible: in the event of a data breach likely to harm you, we will inform you and the CNIL within the legal deadlines.

9. Minors

The App is for people aged 15 and over. For 15–18 year olds, more cautious training rules apply automatically. If you believe a child under 15 has created an account, write to us: we will delete it.

10. Changes

We may update this policy. A substantial change will be signalled in the App before it takes effect. The date at the top of this document indicates the version in force.

11. The website

The Rinja presentation website sets no cookies or trackers and does not measure its audience. Like any server, its host keeps a technical connection log (IP address, page requested, date) to keep the site secure, for [duration to be completed].