COURTPrivacy Policy
Version 2026-08b · Last updated: 16 August 2026
In short: CourtSide is a club-management app. Your club's data lives in a database used only to run the club — schedules, training, progress, messages. We run no advertising, no analytics and no trackers, in the app or on this website. Data is never sold. This page is the same notice that ships inside the app, and explains your rights under the GDPR.
1. Who is responsible for your data
Inside the app, each tennis club that uses CourtSide decides whose data is entered and how it is used. Your club is the data controller of member data. CourtSide's operator acts as the club's processor: we host and maintain the platform, and our technical administrators can access club data only for support, maintenance and license management.
This website and license sales are operated by CourtSide's operator as data controller.
CourtSide is made by AI Resynapse, Bucharest, Romania. The operating company is currently in formation; until its registration completes, the platform is operated by its owner. Contact for all privacy matters: ai.resynapse.official@gmail.com. For questions about your data in the app you can also always contact your club.
2. What data the app processes
- Account data — name, email address, phone number (optional), date of birth (players), profile photo (optional), role (player, parent, coach, physio, admin), club membership.
- Family linking — a family code connecting a parent account to their child's account. A parent link created with the code starts as a request and only works after a coach approves it.
- Training and club data — schedules, attendance and availability (including a free-text reason you may choose to give — please never write medical details there), court hours, training programs and roadmaps, skill assessments and practice grades recorded by coaches, match results, training-notebook entries.
- Photos — profile photos and photos posted to the club gallery and feed (see section 6).
- Messages — private messages between club members. Messages are readable only by their participants; club staff and our administrators cannot read them through the app. You can delete your own messages and remove conversations from your inbox at any time.
- Device data for license protection — a randomly generated identifier created on installation or first use, together with the device's name. It contains no hardware serial numbers and is used only to link your club's license to a limited number of devices.
- Legal acceptance record — which version of the Terms and this notice your account accepted, when, and in which language.
The app contains no advertising or analytics SDKs and requests no device permissions beyond internet access.
Providing account data — your name, your email address, and your date of birth if you are a player — is required in order to hold an account: the account exists to give you your place in your club's CourtSide space under your club's membership agreement, and without these details an account cannot be created and the service cannot be provided. Everything else (phone number, profile photo, notebook entries) is optional.
No decision that produces legal effects for you, or similarly significantly affects you, is made automatically by the app. There is no automated decision-making and no profiling in CourtSide: coaches record assessments and make selection decisions themselves.
3. What the app and this website store on your device
CourtSide uses no cookies at all — neither this website, nor the app, nor its web version sets a single one, and there are no advertising, analytics or tracking technologies of any kind. What the web app does keep on your device is a small amount of storage that the service cannot run without:
ac_device_id(local storage) — a randomly generated identifier, created the first time you open the web app, before you even sign in. It is what links your club's licence to a limited number of devices (see section 2). It contains no hardware serial numbers and identifies a browser, not a person.ac_license_checked_at(local storage) — the date of the last licence check. Written only once you are signed in.- Firebase sign-in storage (IndexedDB databases
firebaseLocalStorageDbandfirebase-heartbeat-database, plus small version markers in per-tab session storage) — created by Google's login library so that you stay signed in and are not asked for your password on every screen. - On a coach's device only — if the head coach has entered the club's Anthropic AI key for the "Read with AI" feature, that key is stored locally on that device. It is never sent to our database.
All of it is strictly necessary to provide the service you asked for: keeping you signed in, and protecting the club's licence. None of it is used for advertising, audience measurement, analytics or building a profile of you, and nothing about your browsing is shared with anyone.
Because this storage is strictly necessary for a service you explicitly requested, it falls under the exemption in the ePrivacy rules (Art. 5(3) of Directive 2002/58/EC, implemented in Romania by art. 4 of Law 506/2004) and does not require your consent. That is why CourtSide shows no cookie banner — there is nothing to ask you about. You can clear this storage at any time through your browser's settings; doing so signs you out and the device identifier is created again the next time you use the app.
4. Who can see what inside your club
- Coaching staff see the club's training data, member contact details, absences, progress records and pending approvals.
- A linked parent sees their child's schedule, progress, match results, absences and the notebook entries the child has shared.
- All club members see the club roster (name, photo, role, level, coach) and the club's training schedule for the day — including who trains when, on every court. This mirrors the printed weekly grid on a club wall and rests on the club's legitimate interest in organising shared courts. If you do not want other players to see your name on the schedule, tell your coach — a per-player setting hides partner names. You can also object to this processing at any time (Art. 21(1) GDPR); once you object, your club must stop unless it can demonstrate compelling legitimate grounds that override your interests, rights and freedoms.
- Ordinary members can NOT see other members' email, phone number, family code, date of birth or device list.
- Your private notebook stays private unless you share an entry; a free note is never shared.
5. Children
Most players are minors. The core service (accounts, schedules, training, progress, messaging) is provided under the membership agreement your parents concluded with the club — the club confirms it holds the parents' signed forms for each minor member. Photo consent is separate (section 6). A child's private notebook notes are not shared with anyone unless the player shares them.
6. Photos
Photos in the club gallery and feed are posted on the basis of written consent collected by your club (parental consent for children under 16, per the GDPR and Romanian Law 190/2018, and art. 73–74 of the Romanian Civil Code). The club is responsible for collecting and keeping this consent, and for only posting photos of members whose consent it holds; this duty is written into the club's agreement with the operator. You (or your parents) can withdraw consent at any time by telling the club — the photos are then deleted. The uploader or club staff can delete any gallery photo directly in the app; a member's photos are deleted when they leave the club, per the retention schedule below.
7. Purposes and legal bases
| Purpose | Legal basis (GDPR) |
|---|---|
| Providing the club-management service: accounts, schedules, training, progress, messaging | Art. 6(1)(b) — performance of the membership agreement |
| Club gallery and feed photos | Art. 6(1)(a) — consent collected by the club (parental for under-16), withdrawable at any time |
| Club-internal schedule visibility (who trains when) | Art. 6(1)(f) — the club's legitimate interest in organising shared courts, with the objection route in section 4 |
| License protection through device binding, including the device storage described in section 3 | Art. 6(1)(f) — legitimate interest in preventing unlicensed use |
| Reading a photographed or imported schedule with AI (see section 8) | Art. 6(1)(b) / 6(1)(f) |
| Selling licenses, invoicing, support (website) | Art. 6(1)(b) and 6(1)(c) — contract and legal obligations |
Health information is not requested anywhere in the app. Free-text fields (such as an unavailability reason) must not be used for medical details, and absence reasons are visible only to you, your coaches and your linked parent.
8. AI schedule reading
When a coach chooses to import a schedule with the "Read with AI" feature, the text of that schedule — which may include player names — is sent to Anthropic PBC (USA), the provider of the Claude AI model, solely to convert it into a structured schedule. The transfer is protected by the EU Standard Contractual Clauses in Anthropic's data-processing agreement, and Anthropic does not use this data to train its models under its commercial terms. The feature runs only when the coach explicitly triggers it.
One honest caveat about that protection. Those Standard Contractual Clauses and the no-training commitment come from Anthropic's commercial terms, and they apply only if the key the head coach entered is a commercial Anthropic Console key belonging to the club or to the operator. The app has no way to check which kind of key was entered. Clubs are required by their agreement with the operator to use a commercial Console key; if a coach uses a personal or consumer key instead, the transfer protections described in this section may not apply to that club's imports.
9. Who receives your data
- Google Ireland Ltd / Google LLC (Firebase) — hosting of the app's database (Cloud Firestore, stored in the European Union — region europe-west1, Belgium) and login service (Firebase Authentication, which processes login data in the USA). Transfers are covered by the EU–US Data Privacy Framework and Standard Contractual Clauses.
- Anthropic PBC (USA) — only for the AI schedule-reading feature (section 8).
- Stripe — payment processing, once license purchases are enabled on this website. Card data is handled by Stripe, not us.
- Google LLC (Firebase Hosting) — serving this website and the web app.
We do not sell or share data with anyone else.
10. How long data is kept
The platform ships the default retention periods below. Your club can adjust them within fixed bounds in the app (Settings → Data & retention); the club's configured values are the ones that apply, and you can see them in the app at any time. Defaults:
| Data | Retention |
|---|---|
| Profile / account data | Deleted 2 months after membership ends (club-configurable: 1–6 months) |
| Grades, roadmaps, notebook | Deleted 2 months after membership ends, with an export to the family available on request beforehand (1–6 months) |
| Match results | Kept 12 months after membership ends, then anonymised (3–24 months) |
| Schedules and court hours | Kept for the club's lifetime as its operational record; a leaver's name is anonymised after 24 months (12–36 months) |
| Messages and community posts | Kept until you delete them; content you authored is deleted when your account is deleted; conversations everyone has left are pruned. A club can additionally set messages to be anonymised after 3, 6 or 12 months (default: off) |
| Photos (gallery/feed) | Deleted immediately when a member leaves, when consent is withdrawn, or when the author deletes them (club-configurable up to a hard maximum of 3 months) |
| Device records (license) | Deleted on device reset or license end |
| Operational logs | 2 months |
| If a club's license lapses | 60 days' grace with written notice and an export to the club, then the club's data is deleted |
| Purchase and invoicing records | 10 years (Romanian fiscal law) |
11. Your rights
Under the GDPR you can ask us or your club at any time for: access to your data, rectification, erasure, restriction of processing, portability (a copy in a machine-readable format), and you can object to processing based on legitimate interest or withdraw consent (for example, photo consent) without affecting past processing.
Being honest about the mechanics: erasure and export are currently performed manually by the operator using an administrative procedure, not by an in-app button. Send requests to ai.resynapse.official@gmail.com or to your club; we answer and complete justified requests within one month, as the GDPR requires. For a child, the request comes from a parent or legal guardian.
You also have the right to lodge a complaint with the Romanian supervisory authority: ANSPDCP, B-dul G-ral. Gheorghe Magheru 28–30, Sector 1, 010336 Bucharest, dataprotection.ro.
12. Security
All traffic is encrypted (HTTPS/TLS). Access to club data is restricted by per-club security rules enforced on the server; passwords are handled by Google's login service and are never visible to us; private messages are readable only by their participants. Security issues can be reported to ai.resynapse.official@gmail.com.
13. Changes
If this notice changes in a way that affects you, the app will ask you to review and re-accept the new version before you continue, and the change is announced on this page.