This Privacy Policy is provided pursuant to Articles 12, 13, and 14 of Regulation (EU) 2016/679 (General Data Protection Regulation — "GDPR"), Article 2-quinquies of the Italian Privacy Code (Legislative Decree 196/2003), the UK GDPR & ICO Age Appropriate Design Code (Children's Code), and applicable international data protection laws. It explains how the TIERO mobile application ("Application" or "TIERO") collects, uses, shares, and safeguards your personal data.
(If you are under 18, please also read the Plain-Language Youth Summary in Section 5.4).
1. Data Controller
The TIERO service is operated by:
- Service / Data Controller: TIERO Project — Data Controller: Lorenzo Pichi (independent developer based in the European Union, Italy)
[TO BE VALIDATED BY LEGAL COUNSEL: inclusion of physical/professional address pursuant to GDPR Art. 13(1)(a)] - Direct Privacy Contact Email:
privacy@tiero.it(physical mailing address for formal legal notices is provided upon request via the dedicated privacy email) - Technical Support & Abuse Reporting Contact (
D72):supporto@tiero.it
2. "Offline-First" Architecture & Local Processing Before Account Creation
TIERO is built on privacy by design and privacy by default principles (GDPR Art. 25):
- No-account usage (available to everyone): core workout logging features on your phone (logbook, routines, rest timer, local history, and the Logbook muscle map) work entirely offline on your device using a local
SQLitedatabase. Using the local logbook without an account sends zero data to our servers. - Initial onboarding data: information entered during the initial setup steps (biological sex, birth year and optional birth month, bodyweight, weekly training frequency, known maxes, and the practice set) is stored exclusively in your phone's local storage.
- Onboarding practice set: the practice set logged during the interactive onboarding step is for demonstration only and is never saved to your logbook or sent to any server.
- No cloud transmission without age verification, account, and explicit consent: no personal or physical data ever leaves your device until you meet your country's statutory minimum age and choose to create an account with explicit consent recorded on our servers.
3. Categories of Data Processed, Purposes, and Legal Bases
When you create an account or use network-connected features, TIERO processes the following data:
3.1 Account, Country, Identity, and Technical Preference Data (D67)
- Data collected:
- email address (used to send one-time login codes / OTP via email);
- internal unique identifier (
UUID), chosenusername, and optional display name (display_name, shown strictly to you for the personal Home greeting and never visible to others); - Country (
country): initially pre-filled from your device's operating system region setting (viaexpo-localization, without requesting GPS or location permissions), displayed during the account creation step where you can correct it, and saved on your profile; - UI language, device
timezone, preferred weight unit (kgorlb), weekly session target (weekly_targetand its change history); - optional cryptographic public key generated on your device (only for adult users 18+ using the "Gym Leaders" witness feature).
- Purpose: account creation and management, server-side enforcement of your country's statutory digital consent age and under-18 protections, passwordless authentication, multi-device logbook synchronization, abuse prevention, and rate limiting.
- Legal basis: performance of a contract to which the data subject is party (GDPR Art. 6(1)(b)) and compliance with legal obligations regarding age of digital consent and minor protection (GDPR Art. 6(1)(c) and Art. 8).
3.2 Physical, Body, and Workout Data (Special Categories of Data — GDPR Art. 9)
Because bodyweight, demographic parameters paired with physical exertion, and load progression may reveal information about your physical health and condition, TIERO treats them under the heightened protections of GDPR Article 9.
- Data collected: biological sex (
M,F, or undisclosed), birth year (plus birth month when your birth year falls on the boundary year for your country's minimum consent age or for turning 18, ensuring exact age determination), bodyweight entries (always stored internally in kilograms with timestamp), declared maxes, workout sessions (UTC start/end timestamps, timezone, notes), logged sets (exercise, load in kg, repetitions, optional dropsets with load and reps, duration in seconds, RPE, warm-up vs. working set flag, and optional soft-deletion timestampdeleted_at), training routines (name, sessions, preset graphical cover identifiers without user-uploaded images, target sets/reps, rest timers, drop counts, and per-exercise notes), and user-created custom exercises (including up to 3 target muscle groups). - Purposes of processing:
- Logbook Cloud Sync & Backup: securely storing your training history so it can be restored across devices and synced without duplicates;
- Strength Metrics, Weekly Rhythm & Logbook Body View (
D80): computing estimated one-rep maxes (1RM), the 4-week working-set distribution across the 11 muscle groups in the Logbook ("Body"), muscle district volume, weekly consistency streaks, and personal records; - Individual Strength Grade (Rank — Adults 18+ only, when active): calculating an adult user's relative standing within their demographic cohort (same exercise, biological sex, age band, and bodyweight ratio);
- Aggregated Statistical Distributions (Adults 18+ only): validated records from adult users (18+) are used in aggregated, statistical form to build TIERO's empirical percentile curves. A grade for an exercise is only unlocked and displayed when a cohort reaches a strict minimum anonymity threshold (at least 100 active users for Bronze through Platinum; at least 200 active users for Diamond and Elite).
- Legal basis: explicit and separate consent of the data subject (GDPR Art. 9(2)(a) and Art. 6(1)(a)), collected via a dedicated checkbox prior to account creation and verified/recorded on the server with a timestamp, country, applied age threshold, and policy version identifier.
3.3 First-Touch Creator Attribution Data
- Data collected: if you install the Application via a creator invite link, an App Store Custom Product Page, a Google Play install
referrerparameter, or manually enter a creator code during sign-in, TIERO records once (first-touch only) the creator/campaign code (campaign_id), arrival source, and timestamp. - Purpose: attributing the referral to the respective creator or coach. TIERO does not use third-party advertising identifiers (such as Apple IDFA or Google Advertising ID) and never sells or shares data with ad networks.
- Legal basis: legitimate interest in measuring referral effectiveness (GDPR Art. 6(1)(f)) or performance of a user request when entering a code (GDPR Art. 6(1)(b)).
3.4 "Notify Me" Waitlist for Upcoming Pro Features
- Data collected: where displayed in the interface, if you tap "Notify me" ("Avvisami") on any "Pro, coming soon" card, we record your user ID, the feature area where you tapped, and the request timestamp.
- Purpose: notifying you when the Pro subscription launches (including founder pricing eligibility) and measuring aggregate demand for Pro features.
- Legal basis: pre-contractual steps taken at the data subject's request (GDPR Art. 6(1)(b)).
3.5 Reports, Blocks and the Name Filter (D72)
- Data collected: if you report a person or a gym, the server records your identifier, who or what you reported, the reason you picked from those offered, the date, and the status of the report. If you block a person, it records who blocked, who was blocked, and the date. Usernames and new gym and crew names are also checked against a server-side list of banned terms.
- Purposes: keeping the shared spaces of the Application free from offensive content, harassment, and abuse, as also required by App Store rules (including Apple App Store Review Guideline 1.2 for apps with user-generated content).
- Legal basis: the legitimate interest of the Controller and of other users in community safety and moderation (GDPR Art. 6(1)(f))
[TO BE VALIDATED BY LEGAL COUNSEL: confirmation of legitimate interest balancing test under GDPR Art. 6(1)(f)]. - Who sees it: only the Controller reads reports. The person reported or blocked receives no notice and never learns who submitted the report or block. A block hides the blocked person (including their name next to witnessed sets) only from the person who blocked them, in the gym views; it does not apply inside a private Crew.
- Automated decisions: no report removes content or an account automatically without review by the Controller. The automated name filter only prevents registering a new name containing banned terms; existing names are not modified automatically.
- Retention and rights: report and block records stay until the account of the person who reported or blocked, or of the person concerned, is closed, and are permanently erased with the 30-day purge described in §7. Your JSON data export (Profile → Your data) includes the reports you submitted and the blocks you made (without exposing other users' internal identifiers).
4. Social Visibility Rules: Crews, Gyms, and Gym Leaders
TIERO is not an open public feed: your workout data is never visible to other users unless you actively join a Crew or (if you are 18 or older) select a Gym.
4.1 What is NEVER Visible to Other Users
Under no circumstances do other users (whether in a Crew or in a Gym) ever see:
- Your bodyweight;
- Your birth year/month or exact age;
- Your email address or your Home display name (
display_name); - Your workout session notes or daily set-by-set logs outside the specific summary blocks listed below (per-exercise notes inside a routine are shared only if you voluntarily export a Routine Code, as explained in §4.4).
4.2 What Members of Your "Crew" Can See (Invite-Only Private Groups)
Joining a Crew (up to 15 members) requires entering a 6-character invite code shared among friends. While you are in a Crew, other members of that specific Crew can see:
- Your
username; - Weekly Rhythm: how many sessions you completed this week against your weekly target (e.g.,
3 of 4), your "On track" or "Paused" status, and the day of your last workout; - Crew Weeks On Track (
D98), Seal (D112,D115) & Banner (D100): consecutive weeks in which all active members hit their weekly target (including current-week progress status per member, such as remaining sessions or paused status), shown on the banner as a seal with the number of weeks; and the Crew banner, an illustration chosen from a fixed list (no free-text descriptions or uploaded photos); - Crew Month (
D99, active from 3 members): at the close of each calendar month, up to three monthly highlights (Strongest ranked separately by biological sex on shared exercises, Most Improved by median estimated1RM% gain, and Steadiest by weeks on track and sessions), displayed solely viausernameand summary figures; - Common Exercises (last 60 days): for exercises performed by multiple Crew members, your best set over the last 60 days (
weight × repsor bodyweight reps), its estimated1RM, and workout date. Leaderboard ordering on each exercise is computed exclusively among members of the same biological sex; - 30-Day Progress: your median percentage change in estimated
1RMover the last 30 days compared to the prior 30 days (computed only when at least 3 comparable exercises exist, without exposing starting weights) and, for adult users once unlocked, your Grade.
Leaving a Crew: you can leave a Crew at any time by tapping "Leave crew", immediately stopping all sharing with that group.
4.3 What Members of Your "Gym" Can See & the "Gym Leaders" Podium (Adults 18+ Only)
The Gym (D51) and Witnessed Gym Leaders (D65) features are strictly restricted to users aged 18 and older (both for the lifter and for the witness) and are completely optional:
- Gym Leaderboard: if you are 18+ and select a gym, once enough active members join that gym, your
usernameand your 30-day percentage progress become visible to other adult TIERO users who have selected the same gym (including people you do not personally know). - "Gym Leaders" Witnessed Podium (Bench Press, Squat, Deadlift): to appear on your gym's top-3 podium per sex on the main lifts, an adult user may optionally have a set verified in person by another active adult member of the same gym ("Witness") who scans a rotating cryptographic QR code displayed on the lifter's phone (refreshing every 20 seconds on a protected screen that blocks screenshots and screen recording). When a set is witnessed:
- Your
username, the verified set (weight × reps), the date, and the witness'susernameare displayed on that gym's podium; - Conversely, if you act as a Witness by scanning another lifter's QR code at your gym, your
usernamewill appear next to their lift as the verifier (and you can withdraw your confirmation from your Sets and confirmations list).
- Your
Leaving a Gym: you can change or remove your selected gym at any time under Profile or Crew / Gym → Leave gym, immediately removing yourself from that gym's leaderboards.
4.4 Routine Sharing via "Routine Code" (D89, D104, 0056)
If you choose to share a routine by generating an 8-character Routine Code:
- Server-side snapshot (
routine_codes): a copy of that routine structure is saved on our database (eu-west-1), containing solely the routine name, optional split, session names, exercises (catalog slugs or custom exercise names/categories/muscles), target sets/reps/rest timers, optional last-set drop counts (lastSetDrops), and per-exercise notes (D104). - What is NEVER shared: no lifted weights/loads, no workout history/logs, no body metrics, and no author
usernameare included in the Routine Code snapshot or shown to recipients. - Security & control: Routine Code lookups go through a rate-limited server function (
routine_code_reads: maximum 20 lookups per hour per authenticated user). If you delete the routine from your logbook or delete your account (deleted_at), the code immediately stops working and is permanently purged upon account deletion (ON DELETE CASCADE). Note: unlikeusernames, Crews, and Gyms, shared routine names and per-exercise notes are not checked by the server banned-term filter (0047); please do not include personal or third-party data in shared routine exercise notes.
5. Protection of Minors & Country-Specific Age of Digital Consent (D67)
5.1 How the Minimum Age for Account Creation Is Determined by Country
Under GDPR Article 8 and equivalent international laws, each country establishes the statutory age at which an individual can independently consent to digital data processing. TIERO enforces a server-side table of verified statutory minimum ages by country:
- Italy: the minimum age to create an account is 14 years old, pursuant to Article 2-quinquies(1) of the Italian Privacy Code (Legislative Decree 196/2003);
- All Other Countries: the minimum age to create an account defaults to 16 years old (the maximum threshold under GDPR Article 8, which also safely covers the United Kingdom and the United States where the statutory threshold is 13), unless a country's specific verified statutory age is configured in the server table.
Your country is pre-selected from your device's region setting (expo-localization) at the account step, can be edited by you before continuing, and is stored on your profile and verified server-side when recording consent. If your birth year is on the boundary for your country's minimum age or for turning 18, we also ask for your birth month so your age is never miscalculated.
5.2 Users Below Their Country's Minimum Age (Under 14 in Italy; Under 16 Elsewhere)
- Users below their country's statutory age cannot create an account, and v1 of the Application does not offer a parental-consent verification flow.
- However, the workout logbook remains 100% functional and free on your phone: the app explains the age rule ("In [Country], accounts open at age [X]") and guarantees that zero data ever leaves your device.
5.3 Users Between Their Country's Minimum Age and 17 Years Old (e.g., Ages 14–17 in Italy; 16–17 Elsewhere)
In accordance with high privacy by default standards (including the UK ICO Age Appropriate Design Code / Children's Code), accounts belonging to users under 18 are subject to strict server-enforced safeguards:
- What they CAN do: sync their personal workout logbook to the cloud and join a Crew (which is a closed, invite-only group of friends where bodyweight and age are never exposed);
- What they CANNOT do until they turn 18:
- Excluded from Public Rank: they never enter public strength rankings (Rank) and their sets do not feed public leaderboard distributions;
- Blocked from Gyms (
D51) and Witnessed Gym Leaders (D65): server functions block under-18 accounts from joining or viewing Gyms and from using the in-person QR Witness feature (neither as lifter nor as witness), preventing any exposure of their username/progress to strangers at a physical gym or any in-person witness interactions with strangers.
5.4 Plain-Language Youth Privacy Summary (Under 18 / Ages 14–17)
If you are between 14 and 17 years old (in Italy, or 16–17 in other countries), here is a simple summary of how TIERO protects your data:
- Why we ask for your consent: to back up your workouts and bodyweight on our secure servers in Europe (Ireland) so you don't lose your logbook if you get a new phone. If you don't want an account, you can still use the logbook on your phone for free without sending us any data.
- Your weight and age are secret: no other user in the app can ever see how much you weigh, when you were born, or your email address.
- What members of your Crew see: if you join a private Crew with a friend's invite code, members of that Crew only see your
username, how many workouts you did against your weekly target (and the weeks the whole Crew stays on track), any monthly Crew titles, your best set on exercises you have in common, and your percentage progress. You can leave a Crew anytime. - Zero strangers until you turn 18: until your 18th birthday, the app automatically turns off public Gym leaderboards, in-person QR witness verification, and public Rank leaderboards.
- You can download or delete everything anytime: go to Profile → Your data to download a copy of your data, or Profile → Delete account to erase your account. You disappear from your Crews immediately, and after 30 days all your data is permanently deleted from our servers.
6. Data Storage Location, International Transfers, Security, and Sub-processors
6.1 European Union Hosting & Safeguards for U.S. Providers (GDPR Chapter V)
All cloud-synced data and transactional email dispatch are physically operated within the European Economic Area (EEA):
- Database & Authentication Provider (Data Processor under GDPR Art. 28): Supabase Inc. (a U.S. corporation headquartered in the United States), with PostgreSQL databases, server functions, and storage provisioned in Amazon Web Services (AWS) region
eu-west-1(Dublin, Ireland — European Union). - Transactional Email Provider (Data Processor under GDPR Art. 28): Resend, Inc. (a U.S. corporation headquartered in the United States), configured to send one-time sign-in codes (
noreply@tiero.it) through infrastructure located in AWS regioneu-west-1(Dublin, Ireland — European Union). - Transfers Outside the EEA (United States): because Supabase Inc. and Resend, Inc. are U.S.-headquartered companies, while primary data storage and email dispatch take place in Ireland (
eu-west-1), ancillary technical support, infrastructure maintenance, or administrative operations by the providers may involve international data transfers to the United States. Any such transfers are governed in accordance with Chapter V of the GDPR by the European Commission's *Standard Contractual Clauses (SCCs) pursuant to GDPR Article 46(2)(c) (incorporated into the respective Data Processing Addenda) and, where applicable for certified sub-processors (including Amazon Web Services Inc.), the EU-U.S. Data Privacy Framework (DPF)* pursuant to GDPR Article 45[TO BE VALIDATED BY LEGAL COUNSEL].
6.2 Security Measures (GDPR Art. 32)
- Row-Level Security (RLS) & Server-Side Age and Consent Enforcement: PostgreSQL RLS policies ensure each authenticated user can only read or write their own rows; writing workouts, sets, bodyweights, and routines to the cloud and accessing social features require a recorded explicit consent on the server (
has_consent); the server consent function enforces the country-specific statutory age table, birth year cannot be freely overwritten by the client to bypass age restrictions (update_birth_year), and Gym / Witness server functions exclude all users under 18; - Encryption: all traffic is encrypted in transit via
HTTPS / TLS 1.2+and at rest viaAES-256. Device signing keys for witness verification are stored in operating-system encrypted secure storage (iOS Keychain/Android Keystoreviaexpo-secure-store) and read into device memory solely at the moment of signing a QR frame or witness confirmation; - No Privileged Keys in Client Bundle: the compiled mobile application contains only the public anonymous key and is automatically verified before every release to prevent secret leakage.
6.3 Other Sub-processors (Active or Planned)
- Resend, Inc. (servers in EU region
eu-west-1, Ireland): for sending service emails strictly required for authentication, such as one-time sign-in codes (noreply@tiero.it), receiving only the recipient's email address. Internal alerts sent to the Controller regarding open moderation reports (D72) contain numerical counts only and no personal data; - Apple Inc. / Google LLC: strictly for app distribution, system push notifications (if enabled by the user), and future in-app purchase processing;
- RevenueCat Inc. (active upon launch of the Pro plan): for technical validation of App Store and Google Play subscription receipts (no credit card or banking details are ever seen or stored by TIERO).
7. Data Retention & Automated 30-Day Hard Purge ("Right to Erasure")
We retain your data for as long as your account remains active. You can delete your account at any time directly inside the app (Profile → Delete account):
- *Immediate Removal & Leaderboard Exit (Day 0 — Soft Delete): upon confirmation, your account is immediately marked with
deleted_at. Local data on your phone is wiped right away; you immediately disappear from Crews and Gym leaderboards, and you leave the Rank distributions and grade calculations at the next recalculation*. - 30-Day Grace Window (Days 1–30): to protect against accidental deletion, your server data remains frozen and invisible for 30 days. Signing back in within 30 days allows you to restore your account.
- *Permanent Physical Deletion (Day 30 — Hard Purge): after 30 days without restoration, an automated daily database job (
pg_cronjobpurge-deleted-accounts, running every night at03:17 UTC) permanently and irreversibly deletes* your profile, bodyweights, routines, any shared Routine Codes and read logs you generated (ON DELETE CASCADE), workouts, sets, Crew memberships, reports, blocks, and associated records from our servers.
Unconfirmed Accounts (0052): if email OTP registration is started but never verified within 7 days, an automated nightly database job (pg_cron job purge-unconfirmed-accounts, running at 03:47 UTC) permanently deletes the unconfirmed account record.
8. Your Rights & Instant In-App JSON Portability (GDPR Arts. 15–22)
You have the right to:
- Access & Instant Data Portability (
JSON): go to Profile → Your data → Download your data to immediately generate and export a complete, machine-readableJSONfile containing your on-device and server data across the exported datasets (profile includingdisplay_name, bodyweights, workouts, sets and dropsets, routines and covers, custom exercises, consents, attributions, Pro requests, witness keys and witnessed sets, Crews, submitted reports, and active blocks); for any auxiliary server-side Routine Code records (routine_codes/routine_code_reads) not yet included in the instant JSON download, you may request a copy by writing toprivacy@tiero.it; - Rectification: edit your bodyweight, Home display name, username, biological sex, weekly target, gym, or delete individual sets, sessions, or routines directly in the app; to rectify your account
countryafter registration or other age fields locked in the app, please write toprivacy@tiero.it; - Erasure & Consent Withdrawal: delete your account at any time in Profile → Delete account, without affecting the lawfulness of processing based on consent before its withdrawal;
- Restriction & Objection: contact us at
privacy@tiero.it; - Lodge a Complaint: contact the Italian Data Protection Authority (Garante per la protezione dei dati personali,
www.garanteprivacy.it), the UK Information Commissioner's Office (ico.org.uk), or your local supervisory authority.
9. Changes to This Privacy Policy
If new features introduce material changes to how personal data (especially GDPR Article 9 special-category data) is processed, we will update the consent_version of this Policy and, where required by law, request renewed explicit consent in the app.
For any privacy inquiries, contact: privacy@tiero.it.