Private first should mean understandable too.

Who controls the information

FlatStrong determines why and how FlatStrong account data is used. Privacy contact: not yet supplied.

What stays in the browser

Guests can create a Foot ID, comfort map, training log, consent choices, wear reports, and private community drafts in local browser storage. That copy is not sent to FlatStrong. Clearing site data or using Privacy controls removes it from that browser.

What a signed-in account can hold

• Identity and access: email, display name, handle, account level, and security records.
• Health-related tracking you choose to sync: Foot ID values, comfort-map locations and sensations, session notes, function checks, goals, and journey records.
• Community material you explicitly publish: display name, posts, replies, structured context, reports, blocks, and reactions.
• Membership and payment references: Stripe customer, subscription, status, and billing interval identifiers. FlatStrong does not receive full card details.
• Timestamped consent records and an administrative audit trail.

Purposes and choice

Account identity and membership are used to provide the service. Health-related account sync is off until you give explicit consent; you can withdraw it and delete synced health rows while keeping your login. Community publishing, anonymous aggregate contribution, and future research contact are separate choices. FlatStrong does not use synced health records for advertising or solely automated decisions with legal or similarly significant effects.

The organisation must document and approve the precise Article 6 basis for each purpose and the Article 9 condition for health data before public launch. The implemented sync flow is designed around explicit consent, but final legal determination belongs to the controller and its adviser.

Processors and international transfers

Supabase provides authentication, database, and private storage; Stripe provides payment and subscription services; the selected deployment host serves the application. The controller must complete processor agreements, region choices, transfer safeguards, and the final vendor list before launch.

Retention and deletion

Private account rows remain until you delete synced health data or the account. Community material remains until you delete it or moderation removes it. Security, moderation, payment, and audit records may need a defined longer period for fraud, disputes, tax, or legal obligations. Exact retention periods are a launch requirement and must be added here after operational and legal approval.

Your controls and rights

The Privacy controls let you export browser and account data, view consent, stop sync and delete health rows, clear a browser copy, or permanently delete the account. Depending on the applicable law and basis, rights can include access, correction, erasure, restriction, objection, portability, withdrawal of consent, and a complaint to the ICO. Contact the controller to exercise a right that is not self-service.

Cookies and device storage

FlatStrong currently uses essential Supabase authentication cookies and browser storage required for the features you request. No advertising cookies are built into this version. Non-essential analytics must not be enabled until an appropriate consent and notice flow is added.