Purpose before collection
Each source must name its data categories, coaching purpose, legal basis, recipients and retention period before connection.
← Back to the Performance BoardiForge / data use & decision controls
Clear purpose. Real control.
The public Performance Board uses illustrative data. Personal device, training and check-in data may only enter a member environment after identity, entitlement, purpose and consent checks have passed.
How personal data must be handled
Separate, explicit choice
Device and health-related data require a distinct positive choice. Optional analytics cannot be bundled with programme access.
Minimum useful data
Collect only the observations needed for the agreed programme and do not reuse them for unrelated advertising.
Human-governed decisions
AI produces suggestions and explanations. A participant can request review, challenge a suggestion and choose not to apply it.
Participant controls
Connect by source
Approve a wearable, training log or check-in separately and see the purpose before authorising it.
Withdraw and disconnect
Stop future collection without being forced to accept unrelated optional processing.
Inspect and export
View source, missingness, calculations and a portable copy of personal observations.
Correct and delete
Request correction or deletion through an authenticated rights workflow.
03 / Health boundary
Performance service—not medical care
iForge is designed for lifestyle, training and human-performance support. It does not diagnose, treat or monitor disease and does not replace a doctor, physiotherapist or emergency service. Recommendations remain conservative, explainable and subject to human review.
Personal-data release gates
The interface is prepared, but a live data connection remains blocked until every operational gate below is evidenced for the actual controller and providers.
Identity and paid entitlement
A signed-in identity must be matched to an active membership on the server.
Controller and privacy notice
Controller details, processors, purposes, legal bases and rights channel must be confirmed.
Explicit health-data consent
Consent must be granular, recorded, versioned and as easy to withdraw as to give.
EU processing and retention
Regions, subprocessors, transfers, deletion jobs and per-source retention must be verified before ingestion.
05 / Control
Rights workflow
The member environment must provide an authenticated route for requests and show their status. Applicable rights include:
- 01Information and access
- 02Correction
- 03Deletion and restriction
- 04Portability
- 05Objection and withdrawal of consent
- 06Human review of significant automated decisions
- 07Complaint to the competent supervisory authority