Privacy Policy

Groundbook
Last updated: October 10, 2026
Effective: October 10, 2026

1. Who we are

Groundbook ("we," "us," "our") is a personal match-attendance log for soccer fans. This policy explains what personal data we collect when you use the Groundbook iOS app and the website at groundbook.app ("the Service"), how we use it, and the choices you have.

2. What data we collect and why

2.1 Account data

When you create an account we collect:

• Email address: to identify your account and send transactional messages (verification, password reset, data export). If you sign in with Apple and choose to hide your email, Apple provides a private relay address in the form xxx@privaterelay.appleid.com; we treat it the same way and display it in Settings as "Hidden by Apple."
• Password hash: if you choose email/password sign-in. We never store your password in plain text. Apple-authenticated accounts do not have a password on our side.
• Display name: the name shown on your profile to accepted friends.
• Avatar photo (optional): if you upload one, the app shows it only to your accepted friends. The image file is stored at a public web address, so anyone who has that exact address could open it. Do not upload an image you would not want seen outside your friends.

2.2 Match attendance log

The core of Groundbook is your personal log. For each match you add, we store:

• Clubs (home and away), competition, date, stadium, and score
• Your seat section, row, and number (optional)
• Your personal notes about the match (optional)
• A personal rating (optional)
• Companions you list (optional, free text)
• Your own correction to a score, if you make one (optional)
• Whether you attended or missed the match, and if missed, why

This personal context (notes, rating, seat, companions, score corrections) is private to you. It is never shared with friends, and it does not appear in any friend-facing view. The only match data visible to your accepted friends is the objective match fact: which clubs played, the score, the date, the stadium, and whether you were there.

2.3 Matches, clubs and stadiums you add by hand

If a match is not in our fixture data, you can enter it yourself. The match, and any club, stadium or competition created along with it, becomes part of a shared catalogue that other users can find when they search. These records contain facts about the match only (teams, date, stadium, competition, score). They do not show who added them. Your attendance at the match stays private as described above.

2.4 Home location

During onboarding you may optionally set a home location. We store a city name and a latitude and longitude. If you type a city, the coordinates are for that city. If you choose "Use current location", we store the coordinates your device reports, which may be precise. We use this to power distance-based stats and a locale-aware experience (for example, a relevant popular-clubs list). Home location is never shared publicly or with friends. You can update or remove it at any time in Settings.

2.5 Friend graph

If you choose to connect with friends:

• We store a record of each accepted friendship (your user ID and your friend's user ID).
• We generate single-use invite links so you can invite someone to connect. Each link expires after 72 hours. Once used, an invite is marked as used and cannot be used again.
• Your accepted friends can see the match facts in your log, including upcoming matches you have added. They cannot see your notes, rating, seat, companions, or score corrections.
• There are no public profiles. No one outside your accepted friends can see your match list.

2.6 Season ticket data

If you use the "Add a season" feature, we store the club, season, seat details, and the list of included competitions. This data is private to your account.

2.7 Technical data collected automatically

• Crash and error reports: when the app crashes or hits an error, a report is sent to Sentry, our crash-reporting provider. A report contains the error and its stack trace, your device model and operating system version, recent app log messages, and your Groundbook user ID so we can connect a report to a support request. Email addresses, sign-in tokens and coordinates are removed before a report is sent.
• Server logs: standard request logs, retained for up to 30 days for security and debugging.

We do not use product analytics, advertising, or tracking software in the app.

2.8 The website

The website at groundbook.app is hosted by Cloudflare. Like any web host, Cloudflare processes the requests your browser makes, including your IP address, in order to deliver the pages. The website does not use cookies, advertising, or tracking scripts.

3. How we use your data

We do not use your data to serve advertisements. We do not sell your data to third parties. We do not build advertising profiles.

4. Data sharing

We share data only in the following circumstances:

• Supabase: our database, authentication, and file storage provider. Your data is stored in Supabase's managed Postgres database and Supabase Storage. Supabase processes data as our data processor under its Data Processing Agreement.
• Sentry: our crash-reporting provider. It receives the crash and error reports described in section 2.7.
• API-Football (API-Sports): we query this service for match fixture data (clubs, scores, dates, stadiums). We send search terms such as club names, competition names, and dates. We do not send personal data about you. Club and competition logos shown in the app are loaded directly from this provider's image server, which, like any web server, receives your device's IP address when an image loads.
• Resend: our transactional email provider. Your email address is passed to Resend when we send you a verification email, password reset, or data export link.
• Apple: when you sign in with Apple, Apple processes your identity authentication. The app also uses Apple's maps to draw your Journey map and Apple's geocoding service to place stadiums and your home location on it. Geocoding sends Apple the stadium name or city you entered, or your device's coordinates if you choose "Use current location".
• Cloudflare: hosts the website, as described in section 2.8.
• Legal requirements: we may disclose data if required by law or to protect the rights, property, or safety of Groundbook, our users, or others.

We do not share your data with any other third parties.

5. Data retention

• Active accounts: data is retained while your account is active.
• Deleted accounts: when you delete your account via Settings, your personal data is deleted from our database: your attendances, notes, ratings, friendships, invites, and season ticket data. Your sign-in record is removed immediately afterwards, and your avatar and any data export files are removed from storage. Matches, clubs and stadiums you added to the shared catalogue remain, with no link to you.
• Invites: links expire after 72 hours. Invite records are kept, marked as used or expired, until you delete your account.
• Data export files: the download link we email you works for one hour.
• Server logs: retained for up to 30 days.
• Crash reports: retained for up to 30 days.

6. Your rights and choices

Access and export: You can export your personal data in JSON format at any time via Settings → Account → Export your data. We email you a link to download the file; the link works for one hour. You may request one export per 24-hour period.

Correction: You can update your display name, email address, avatar, home location, and favorite club in Settings at any time. Match attendance records can be edited or deleted individually.

Deletion: You can delete your account and associated data at any time via Settings → Account → Delete account. Deletion is permanent and cannot be undone.

Crash reporting: Crash reporting cannot currently be turned off, because it is essential for diagnosing and fixing problems.

If you are in the European Economic Area or the United Kingdom, you have additional rights under the GDPR or UK GDPR respectively, including the right to object to processing, the right to data portability, and the right to lodge a complaint with your supervisory authority. To exercise these rights, contact us at the address below.

7. Security

• All data is transmitted over TLS/HTTPS.
• Database access is governed by Row Level Security policies in Supabase Postgres. Your attendance records can be read only by you; friends read match facts through a separate, restricted view.
• API keys (including the API-Football key) are never shipped in the app. They are held on our servers and used server-side only.
• Invite tokens are generated with a cryptographically secure random number generator, are single-use, and expire after 72 hours.
• Email/password accounts require a verified email address before access is granted.

8. Children

Groundbook is not directed at children under the age of 13. We do not knowingly collect personal data from children under 13. If you believe we have inadvertently collected data from a child under 13, please contact us and we will delete it promptly.

9. Changes to this policy

We may update this policy as the product evolves. For material changes, we will notify you via email or an in-app notice before the change takes effect. The "Last updated" date at the top of this page reflects the most recent revision. Continued use of the Service after a change takes effect constitutes acceptance of the updated policy.

10. Contact

Questions about this policy or your data:

Groundbook
contact@groundbook.app

For data rights requests (access, deletion, portability), use the in-app tools in Settings first, as they are faster. If you need further assistance, email us at the address above.