1. Who operates Courta
Courta is operated by Craig Pickerill (the data controller). Contact us about your personal data at privacy@courta.co.uk. General support is available at support@courta.co.uk.
2. Information we collect
When you use Courta, we may process:
- Player information: your chosen display name and your player profile identifier.
- Match information: manually entered team/guest names, match participants, the join code, scoring formats, points awarded or undone, serving order, match timestamps, results and match history.
- Device/session information: controller/device labels, temporary match-access credentials and profile access credentials. The server stores access-token hashes rather than the original tokens.
- Operational information: network information such as IP addresses and technical requests or errors needed to run, protect and diagnose the service.
Offline matches and certain preferences can remain stored on your device. When you create or join an online match, the related data is sent to the Courta API to synchronise scoring.
The current version uses device-linked profiles. It does not yet offer the future email/password sign-in or paid subscription system. This notice will be updated before those features are introduced.
3. What we use it for
We use this information to create matches, synchronise scores, identify the players in each match, provide histories and summaries, support watch and kiosk connections, prevent abuse and keep the service secure and reliable. Depending on the activity, our lawful grounds under applicable data-protection law include providing the service you request and our legitimate interests in running and protecting Courta.
4. Who can see or receive information
A person who knows a valid match join code and joins or views the match may see the players' displayed names and match score. Connected controllers and read-only kiosk displays receive the shared match state. Please enter other people's names only when appropriate and tell them Courta is being used.
Our infrastructure provider, Akamai/Linode, hosts the Courta server and database. Other operating-system or distribution providers may process information according to their own policies when you install or use the app. Courta does not currently use advertising trackers on this website or sell player data to advertisers.
5. Storage, transfers and security
Courta's online service uses PostgreSQL on its hosted server. Connections to the production API are encrypted with HTTPS/WSS. We limit who can access the server and maintain operational backups. We do not publish private player access tokens on the public website.
Hosting and support infrastructure can involve processing outside your country. Where required, we assess and apply appropriate data protection safeguards for international processing.
6. Retention and deletion
We retain profile and match information while needed to provide the service, manage connected match records and meet applicable operational or legal requirements. Some data also remains temporarily in routine backups according to our backup schedule.
Deleting an entry from your personal Match History is not the same as deleting a shared online match or your entire player profile. Other participants' records may still refer to that match. If you request full profile deletion, we will verify that you control the profile and assess which personal data can be erased or anonymised without improperly affecting other participants' data or required records.
To request data access, correction, export or deletion, visit Delete profile & data or email privacy@courta.co.uk.
7. Your rights
Depending on where you live and the applicable law, you may have rights to know about, access, correct, erase, restrict or object to certain processing of your personal data, or request portability. You may complain to the UK Information Commissioner's Office at ico.org.uk. Contact us first if you would like us to investigate an issue.
8. Website and cookies
This public website uses no advertising or analytics cookies and does not embed third-party tracking scripts. Standard infrastructure requests may still process technical connection data. See our cookie information.
9. Changes
When we add portable accounts, verification emails, subscriptions or new analytics features, we will update this notice to describe any new collection, processing or partners before those features go live. Any material changes will be reflected on this page with a revised update date.