Privacy policy draft
Who operates Spardhe
[LEGAL OPERATOR NAME], [BUSINESS ADDRESS]. Privacy contact: [CONTACT NAME AND DESIGNATION]. General support: spardhe.care@gmail.com.
Data and purposes
Spardhe manages tournaments and player performance records. Depending on your role and entry, records may include name, email, phone, date of birth, city, photo, guardian contacts, account information, tournament participation, team assignment, match scores, results, and derived performance statistics. Officials and organisers may enter records on a player's behalf.
These records support registration, account access, tournament administration, scoring, standings, player history, and correction of records. Google sign-in supplies identity information for authentication. Spardhe does not collect payments.
Visibility and recipients
Published tournament views may show player names, photos, teams, results, and performance statistics. Authorised staff can access information needed for their role. Contact support about a visibility concern. [CONFIRM PUBLIC FIELDS, PROCESSOR LIST, HOSTING LOCATIONS, AND TRANSFER ARRANGEMENTS BEFORE PUBLICATION.]
Children and parental consent
Players under 18 may participate with parental consent. Parents and organisers should arrange consent before submitting a child's information. Authorised organisers record their identity-and-age review and parental consent using a restricted internal evidence reference, consent date, and notice version. [APPROVE THE FINAL NOTICE AND COMPLETE CHILD VISIBILITY, WITHDRAWAL, AND LEGACY-RECORD CONTROLS BEFORE FINAL PUBLICATION.]
Retention and requests
Contact support to ask about your information, report an error, request correction or deletion, or raise a privacy complaint. Match-record corrections may need confirmation from an authorised official. [SPECIFY RETENTION PERIODS, LAWFUL EXCEPTIONS, BACKUP EXPIRY, REQUEST DEADLINES, AND CONSENT WITHDRAWAL PROCESS.]
Optional analytics
When configured, PostHog measures visits and match-day actions only after you accept analytics. A random analytics browser ID is stored locally to recognize return visits; signed-in activity uses a pseudonymous account ID, and tournaments, ties and matches use pseudonymous grouping IDs. Sessions group activity during a visit. Guest counts represent browsers rather than verified people. We omit names, contact details, form contents, raw record identifiers, query strings and sealed lineups. Session replay and automatic interaction recording are disabled. The configured project uses PostHog’s EU ingestion endpoint. PostHog receives network connection information when events are sent. Analytics settings below lets you decline later; this clears analytics identifiers stored by this integration and stops future collection, but does not delete events already received. Scoring practice is excluded. [CONFIRM PROCESSOR TERMS AND RETENTION BEFORE PRODUCTION ACTIVATION.]
Analytics settings
Loading analytics choice…
Storage and security
Session cookies and browser storage support sign-in and preferences. See storage information. [CONFIRM SECURITY MEASURES, INCIDENT NOTIFICATION PROCEDURES, AND ANY OPTIONAL PROCESSING BEFORE PUBLICATION.]