TRIPRO

    Privacy Policy – TRIPRO System

    Last updated: November 3, 2026

    This document describes what information is collected in the TRIPRO system (website, applications, and related services), what it is used for, with whom it is shared, how long it is kept, and what your rights are. It is written to reflect how the system actually operates. The Hebrew version is binding; the English is provided for convenience.

    1. Database Controller and Contact

    a. System operator: TRIPRO, operated by Amir Gez (sole proprietor). For personal data about coaches and clubs, TRIPRO is the data controller. For personal data about athletes and parents that a coach or club manages in the system, the coach or club determines the purposes of processing for training and group management, and TRIPRO processes the personal data on their behalf to provide the service, in accordance with this document and subject to its obligations under applicable law. b. Privacy inquiries, rights requests, and deletion requests: triproteam@gmail.com. c. [If a Data Protection Officer (DPO) is appointed, their details will be published here.] d. Providing information to the system is voluntary; without the required details the service cannot be provided. This section, together with the notices shown at collection points (signup, connecting a watch or health app, recording a workout, approving AI processing), is intended to provide the information required under Section 11 of the Israeli Privacy Protection Law, 1981.

    2. Information Collected

    a. Information you provide: account details (name, email, phone, date of birth, one-way-hashed password), profile details, and content you enter - training plans, feedback (effort, mood, free text), coach notes, results, and attendance. b. Information about minors is provided by the parent/guardian or by the coach, subject to recorded parental consent (Section 7). c. Operational information collected automatically: server-side usage records for system requests - identified user, endpoint, response times, and status codes - for operations, security, and product improvement. This information is linked to your account and is not anonymous; it is not used for advertising. d. Information from watch and health connections (only with your explicit consent): (1) The on-device health data store, with your approval in the operating system, read-only and without location. On Android (Health Connect): workouts your watch's companion app wrote to the store (such as Garmin Connect, Polar, Suunto, Samsung Health): workout type, name and times, distance, calories, heart rate, speed, total elevation gain, power and cadence. On iPhone (Apple Health): workouts and heart-rate data. You can revoke the permission at any time in your device settings. (2) Intervals.icu, your own account that you connect (age 18+ only): workouts your watch uploaded to that account, at source resolution, without location data. This is also a connection through which information is sent out of TRIPRO, see Section 6. (3) Garmin Connect, direct connection (if enabled, age 18+ only): workouts your watch synced to Garmin Connect. The scope of the data, its use and its deletion are set out in Sections 5, 6 and 10. (4) Heart-rate strap (BLE) and phone recording: data the app records directly, see paragraph f. e. Payment details: card processing happens at the external payment provider - full card details are never stored with us. We keep the transaction confirmations the provider transfers, which include payer name, phone, email, and amount. f. Location (GPS) data from in-app workout recording: when you choose to start recording a workout in the app, and only then, the app reads the device's location - including while the screen is locked - in order to compute distance, pace, splits, and cumulative elevation gain. An active recording is marked by a persistent device notification and stops when the recording ends. We do not collect location in the background at other times, and we do not use location for advertising, profiling, or sharing with third parties. The route track (the sequence of coordinates) is stored in the database only for athletes aged 18 and over. For athletes under 18 - and likewise where the date of birth is unknown - coordinates are not stored at all: they are stripped on the server before the record is written, not merely hidden in the UI, and only the derived metrics (distance, time, pace, splits, elevation gain) are retained.

    3. Especially Sensitive Information

    Some information in the system is "especially sensitive information" as defined by the Privacy Protection Law (Amendment 13): • Physiological and sports-health data: heart rate, lactate threshold, VO2max, training load, recovery metrics, body weight, and derived metrics - collected for training monitoring and display to you and your coach, based on your consent (or parental consent for a minor). Effort reports (RPE), attendance and training results may constitute personal data and, in certain circumstances, especially sensitive information, including when combined with physiological data. TRIPRO applies safeguards appropriate to their sensitivity. • Location data from workout recording (athletes aged 18 and over): collected only during a recording you initiate, for computing and displaying your training metrics to you and your coach. • Financial-activity information: activity dues and subscription payments - collected for collection management and bookkeeping. Our commitments regarding this information: we will not sell it, not rent it, not use it for advertising, and not disclose it to third parties other than the essential sub-processors listed in Section 6, under a legal obligation, or with your explicit consent. It is processed only for the purposes for which it was provided.

    4. How Information Is Used

    a. Service delivery: club management, training plans, statistics, and displaying data to you and your coach. b. Training data from a watch, a health store, Intervals.icu, Garmin, a heart-rate strap or phone recording: used for display, charts, statistics, load calculations and comparison against the plan. This data is disclosed to an AI service provider only under the conditions in Section 5, and Intervals.icu data is never disclosed to one. c. Operational access by system staff: TRIPRO's support and operations staff have controlled, logged access to user data across all clubs, solely for support, maintenance, security, and incident handling. Data separation between clubs applies to end users - not to operations staff. d. Operational communication: system notifications, reminders, and action confirmations. Further mailing - see Section 12. e. Security, fraud prevention, and compliance with legal obligations.

    5. Artificial Intelligence Transparency Statement

    a. TRIPRO uses artificial intelligence to assist coaches in creating training plans and, where the athlete has given explicit consent, to generate insights based on recorded workouts. Insights are intended to support training review. They do not replace the coach's professional judgment: decisions concerning an individual athlete's training load, injury-related adjustments or personalized training plan remain the responsibility of the coach. The monitoring analysis ("Attention") is computed in TRIPRO's own code, without an AI provider. b. What is excluded from requests to AI providers: the athlete's name, alias, email address, telephone number, identifier, age and date of birth; athletes' free-text feedback, notes and comments; injury and fatigue reports; perceived exertion (RPE) reports; attendance records; and Intervals.icu data. No request includes the athlete's identity or instructions referring to an athlete by name. Although direct identifiers are excluded, workout data may still constitute personal data, and it is protected as described in this document. c. Workout insights: for a workout recorded by a watch, a heart-rate strap, the phone or Garmin, TRIPRO may transmit to Anthropic a limited set of workout data: workout type, distance, duration, summary heart-rate metrics (average, maximum, zones and a downsampled heart-rate time series, never the raw samples), pace or speed, total elevation gain, cadence and power, together with the structured elements of the planned workout (type, distance, duration and steps, without free text). Processing takes place in the United States. TRIPRO requires the athlete's separate, explicit consent before submitting workout data, and for a minor, the consent of the parent or legal guardian. Insights are made available to the athlete and to the athlete's authorized coaches. They are not made available to a parent solely by virtue of the parent relationship. d. Withdrawal: consent may be withdrawn at any time in Settings. Withdrawal stops further AI processing immediately (consent is checked again right before every request), and stored insights are removed from the active service; copies in backups are deleted at the end of the backup cycle. e. Training plan generation: to create or edit a plan, TRIPRO sends the group's existing plan, the group's training characteristics (sport, level, goals and age range) and instructions written by the coach. No athlete list and no data about any athlete is sent. The system removes email addresses, telephone numbers and ID numbers from the instructions, and asks the coach not to write athlete names. Weekly plan generation is sent to Anthropic only. Initial plans, the template generator and spreadsheet import may also be sent to Groq, or through OpenRouter under a configuration that routes only to providers that neither retain the data nor train on it; if the system detects an identifying detail or a physiological value in the instructions, they are sent to Anthropic only. f. Transfers outside Israel: personal data is transferred outside Israel (to AI providers, backup, error monitoring and email delivery) in accordance with applicable law, on the basis of consent where required or other conditions permitted by law, and with appropriate safeguards. Consent to AI processing of workout data is given separately, as described in paragraph c. g. Model training: TRIPRO does not use athletes' workout data to train AI models. Anthropic does not train models on its API customers' data, and requests through OpenRouter are routed only to providers that do not train on them. Retention of requests by providers is governed by their terms. h. AI outputs are machine-generated and are not medical advice; see the Terms of Service, Section 11.

    6. Information Sharing and Sub-Processors

    We do not sell or rent personal information. Information is shared only with the following parties, to the extent required for operation: • Health Connect (Google) / Apple Health: reading workouts on your device, under a permission you grant in the operating system; no information is transferred to Google or Apple as part of it. • Intervals.icu: a connection you initiate (age 18+), by authorization (OAuth) or a personal API key. Data is exchanged in both directions: we receive the workouts your watch uploaded, and send your planned workouts for the coming week (title, type, time, planned duration and distance, and the step description) so they reach the watch. We do not send your name, contact details or other athletes' data. Subject to Intervals.icu's terms. • Garmin: direct connection, if enabled (age 18+), under an authorization you grant. Subject to Garmin's terms. • AI providers (Section 5): Anthropic; and for coach instructions without athlete data, also Groq and OpenRouter. • Oracle Cloud Infrastructure: hosting of the system and its data, in the Jerusalem, Israel data center. • Backblaze: backup of the database, in the Netherlands (European Union). The backup is encrypted on our server before it is sent, and the keys are not held by the provider. • Grow (Meshulam): payment processing. • Resend: operational email delivery. • Apple (APNs) and Google (Firebase Cloud Messaging): delivery of push notifications to devices. A notification may include a workout's title, a group's name or the name of someone who joined the group. • Sentry: error monitoring, stored in the European Union (Germany). It receives error messages, the page path, the app version and the browser or device type, and an internal user identifier only: no workout content, names or contact details. • Expo: the app update service; it receives the device's IP address and version details when checking for an update. Further disclosure occurs only under court order, legal obligation, or to prevent imminent harm. Data-processing agreements are signed with sub-processors as required.

    7. Minors and Parental Consent

    a. The system is designed, among other things, for minor athletes. A minor's account is opened only by a parent/guardian, who actively confirms - per child - the processing of the child's information, including sports-health information. The confirmation is recorded (version, time, wording). b. The parent may at any time view the child's information, update it, disconnect third-party integrations, and delete the account and its data - in the system or by contacting support. c. Connecting Intervals.icu requires age 18+, and the system blocks it for minors and where the birth date is unknown. Parental consent does not open this connection: a parent's consent permits us to process the child's information inside TRIPRO, but it cannot grant a minor an account with an external provider whose terms address adults only. The other sync channels remain available to minors: the device health store and a BLE heart-rate strap. d. The birth date is used for age verification and age-group assignment and cannot be changed after being set except by contacting support. e. When the minor turns 18, the athlete assumes control of their account and is asked to accept the terms themselves. From that point the parent may view the information but not edit it, and the adult may ask support to end the parent's access. f. In-app workout recording is available to minors as well, but the route track is not stored for them. A minor receives the training metrics only (distance, time, pace, splits, elevation); the coordinates are deleted on the server before storage. Where an athlete's age is not known to the system, the system treats them as a minor for this purpose.

    8. Cookies and Local Storage

    a. The system uses exactly one cookie - a display preference for the side menu (7-day lifetime). b. The browser's local storage holds: your login token, the signed-in user's details, language and theme preferences, and transient UI state (such as an active stopwatch or an active workout recording, including coordinates not yet uploaded - which are deleted from the device immediately upon upload or when the recording is discarded). c. We use no advertising cookies, social-network pixels, or third-party tracking tools. Usage measurement is server-side as described in Section 2c. The site's fonts are hosted on our own servers; the browser does not contact external font providers.

    9. Information Security and Security Incidents

    a. The system implements security measures in accordance with the Israeli Privacy Protection (Data Security) Regulations, 2017, at the level required by the data's sensitivity, including: one-way password hashing, encryption of third-party access tokens, role-based access control, administrative access logging, backups, and environment separation. b. A severe security incident will be reported to the Privacy Protection Authority as required by law, and affected users will be notified without delay. c. No system is completely immune; care is also required on your side - safeguarding your password, signing out of shared devices, and immediately reporting suspected misuse.

    9A. Personal (Solo) Training Account, Beta - Activity Monitoring

    This section applies only to "personal (solo) training" accounts (Section 7A of the Terms of Use), operating in an invite-only beta program. a. Scope of the account's data: a solo account contains the user's own data only. It has no coach–athlete relationship, and no other user is exposed to your training data. b. Monitoring during the beta: for system security and product improvement, the Operator's team may review technical activity of beta accounts at the metadata level only: which operations were performed (path, method, response code, time and duration). The content of your workouts, messages and metrics is not part of the monitoring view. Monitoring is enabled per account by a system administrator, is logged, and is available to super-admin permission holders only. c. Watch connectivity: sync on this account runs through the Intervals.icu connection (subject to Sections 2 and 6), the device health store and direct recording channels. d. When the beta program ends or the account is closed, the regular deletion and retention rules apply (Section 10).

    10. Data Retention

    Retention periods in the system: • Account data and training content - as long as the account is active; deleted upon account deletion (subject to the exceptions below). • Intervals.icu and health-store data: kept as part of the workout records after disconnecting, until you delete them or the account. Disconnecting stops the sync; planned workouts already sent to your Intervals.icu calendar remain there. • Garmin data (direct connection): deleted within 30 days of disconnecting or deleting the account, including metrics and insights derived from it. • AI insights: removed from the active service upon withdrawal of AI consent; copies in backups are deleted at the end of the backup cycle. • Route tracks from workout recording (18+) - retained alongside the workout record and deleted when the workout or the account is deleted; the track can be deleted separately, without deleting the training metrics. • Consent records (terms) - 7 years, as legal evidence, including after account deletion (with version, time, and acceptor details). • Financial records and transaction confirmations - 7 years, per bookkeeping law. • Operational usage records (Section 2c) and system logs - kept for security and operations; upon account deletion the link between these records and your identity is severed. • Attendance, results, and payment records of an athlete who left a club - retained as part of the club's records for as long as the club is active.

    11. Your Rights

    a. Access: you may access the information held about you. Most of it is available directly in the system; for a full copy - contact support and we will respond within 30 days. b. Rectification: most details can be updated in Settings; details not self-editable will be corrected via support. c. Deletion: a "Delete Account" button is available in Settings, and deletion is also available via support. Deleting a coach account requires orderly club closure first. Retention exceptions - Section 10. d. Consent withdrawal: disconnecting watch integrations, withdrawing AI processing and unsubscribing from mailing are available in Settings at any time; withdrawal of parental consent, Section 7. e. Complaint: you may approach the Privacy Protection Authority on any matter. f. Rights for a minor are exercised by their parent/guardian.

    12. Mailing and Notifications

    a. Service messages - action confirmations, system notifications, workout reminders, and billing notices - are sent as part of the service and require no separate consent. b. Periodic email summaries (weekly digest) are sent only to those who explicitly opted in, and can be cancelled in one click from any message or from Settings. Mailing consents are recorded. c. Advertising material will be sent only with explicit prior consent as required by Section 30A of the Israeli Communications Law, on a channel separate from service messages, with immediate opt-out.

    13. EU Users, Policy Changes, and Contact

    a. EU/EEA users: to the extent the GDPR applies, the legal bases for processing are your consent (Art. 6(1)(a), and Art. 9(2)(a) for health data) and contract performance (Art. 6(1)(b)); access, rectification, erasure, restriction, and portability rights are exercised through the channels in Section 11, within a 30-day timeframe. Israel holds an EU adequacy decision. b. A material change to this policy will be announced in the system and by email at least 30 days in advance, and will require renewed acceptance where it concerns the basis of consent. c. Questions, requests, and rights exercise: triproteam@gmail.com.