← PERFORM ARC

Privacy

PERFORM ARC Privacy Policy

This policy explains how PERFORM ARC handles account, training and health data for coaches and athletes.

Updated: 23 October 2026

Data we process

Purpose and access

PERFORM ARC uses these data to display readiness, support training-load analysis, track plan execution and provide the coach-athlete workspace.

Athletes see their own information. A linked coach can see information needed to manage that athlete's training. Role and athlete-access checks limit workspace access.

Health-data boundaries

Health synchronization is read-only. PERFORM ARC does not write samples to Apple Health or Health Connect, sell health data, use it for advertising or cross-app tracking.

Raw health records are not sent to an external AI service. PERFORM ARC may use deterministic calculations inside the service for readiness and training-load views.

Consent and revocation

PERFORM ARC requests app-level consent before reading or uploading supported health data. System permission is requested separately by Apple Health or Health Connect.

You can revoke PERFORM ARC consent in Privacy settings. This stops new reading, background synchronization and uploads on that device. Consent on another device and the operating-system permission are managed separately. Revocation does not delete data already synchronized; use account deletion for that.

Voluntary cycle journal

An athlete may choose to store bleeding start/end dates, optional pain ratings and the reported impact on training. She can separately allow her currently linked coaches to view the calendar and allow them to view symptoms. Previously granted access to dates and symptoms remains in effect until changed. Neither a coach nor an administrator can enable collection on the athlete's behalf. Declining does not limit other platform features.

Turning off sharing blocks subsequent coach requests. Turning off collection hides retained records and stops new entries; re-enable the private journal without sharing to review or delete them individually. Deleted observations are cleared from the active database; backups follow the protected backup lifecycle. The journal is not kept in offline caches or sent to external AI, advertising or model-training services. The athlete can enter an optional typical cycle length. PERFORM uses it, or the athlete's observed start-to-start intervals once enough exist, only for a clearly labelled calendar estimate. A separate, default-off choice may allow the coach to see median resting heart rate, sleep duration and readiness from three-day windows around confirmed starts. That comparison is descriptive, does not establish cause, does not determine a cycle phase, fertility or a medical condition, and does not automatically change readiness scores or training plans.

Public website statistics

On public information pages, we count page views and clicks on the demo, registration and app-download links to understand which materials are useful. A click on the demo email link is counted, but the email contents and whether a message is sent are not recorded by this counter. Workspace, sign-in, registration and recovery screens are excluded.

The counter sends only a fixed page category, page language, action category and source category (such as Google, LinkedIn, direct or other). It does not send full URLs, search queries, campaign names, account or athlete information. It uses no analytics cookies, local storage, visitor identifiers, fingerprints or session recording, and it respects Do Not Track and Global Privacy Control. Requests still pass through our infrastructure and its technical security controls.

Our server stores daily aggregate counts for 180 days. The private report is available only to authorized administrators and specifically authorized site-report viewers. These counts are not unique visitor totals and do not confirm an installation, registration or message. We do not send these statistics to an external advertising or analytics provider.

Technical error monitoring

To investigate software failures, our server sends minimized technical error records to Sentry in the EU region. These identify the error category and application component, not the athlete. Mobile and web reports use the authenticated PERFORM ARC service; they do not connect directly to Sentry.

Before forwarding, we discard original error messages, user names and identifiers, email addresses, passwords, session tokens, request contents, health data, training records and coach messages. Session recording, advertising tracking and Sentry's generative AI features are disabled. Diagnostic reporting is best-effort and does not replace your training records.

Account recovery and bot protection

When password recovery is enabled, we send account security messages from accounts@performarc.app. Reset links expire after 30 minutes, work once and are stored in the application database as hashes. A successful reset signs out previous sessions.

When enabled on registration and recovery forms, Cloudflare Turnstile processes technical browser and network signals to check for automated abuse. Our verification requests do not include passwords, recovery links, training records or health data. The application also uses request limits to protect accounts and prevent unwanted email.

Storage, retention and security

Data are sent over encrypted connections and stored on PERFORM ARC infrastructure. Account, training and synchronized health data are kept while the account is active or until a valid deletion request is completed.

Security, fraud-prevention or legal records may be retained where required. Backup copies expire through the normal protected backup lifecycle.

Account deletion and contact

An authenticated user can request deletion in the mobile app under Privacy. A public request path is also available on the account-deletion page. Requests are scheduled for completion within 30 days and can be cancelled before completion.