Privacy Policy
28/08/2026 · This policy explains how data is handled in the GK Performance AI pilot version.
1. Data we process
We may process account data (name, email and preferences), team and goalkeeper data entered by the user, calendars and match actions, security logs and technical identifiers required to operate the platform. Test-mode billing may also generate technical Stripe identifiers without charging real money.
2. Purposes
Data is used for authentication, delivery of application features, cloud synchronisation, reports and comparisons, security, support, abuse prevention and improvement of the pilot experience.
3. Athlete and minor data
The application is intended for coaches and professionals, not for children as direct users. Anyone entering athlete data is responsible for having a lawful basis and for complying with club, academy and applicable legal rules. Avoid medical, sensitive or unnecessary information and minimise identifiable data relating to minors.
4. Legal bases
Processing required to provide the account and application is based on performance of the terms of use and pre-contractual steps related to the pilot. Security, abuse prevention and technical improvement may rely on legitimate interests while respecting user rights.
5. Technology providers
The platform uses technology providers for hosting, database, authentication and test payments, including Supabase, Vercel and Stripe. These providers may process technical data under their own terms, security measures and lawful international-transfer mechanisms where applicable.
6. Retention
Data is retained while the account is active or as long as needed to provide the pilot and meet applicable obligations. The user can export data and delete the account from Settings. Technical copies and security logs may remain for limited backup and audit periods.
7. Security
We apply authentication, team-based access control, Row Level Security in the database, protection for sensitive functions and two-factor authentication options. No system is completely immune to incidents, so we recommend unique passwords and 2FA whenever possible.
8. Rights
Subject to applicable law, a data subject may request access, correction, deletion, restriction, portability or objection. During the pilot, requests can be made through the same contact channel used for the invitation. Formal privacy contact details will be published before commercial launch.
9. Cookies and local storage
The pilot version does not use behavioural advertising. The application and essential providers may use local storage, cookies or equivalent technologies that are strictly necessary for sessions, security and payment processing when those features are used.
10. Changes
This policy may be updated when the commercial structure, providers or features change. Material changes will be reflected in a new version and effective date.