Effective 2 August 2026 · Last updated 15 August 2026
Pickleball Event Manager (“the app”, “we”, “us”) runs a live playing queue at pickleball venues. This policy explains what it collects, why, and what you can do about it.
Contact: cs@pickleballeventmanager.app
To run a queue, the app needs to know who is waiting, who is on court, and what the results were. That is essentially all it collects.
We do not collect your precise location, contacts, photos, microphone audio, health data, browsing history, or payment card details. We do not sell personal information, and we do not share it with data brokers.
Organizers hold an account (email and password) and create events.
Players usually do not. Joining an event by QR code or join code is anonymous — you enter a display name and nothing else. No email, no phone number, no sign-up. Advertising is the one thing that works differently for everyone, account or not: see section 6.
| Data | Why |
|---|---|
| Email address | Sign-in, password reset, essential service notices |
| Password | Sign-in. Stored only as a salted hash by our authentication provider; we never see it |
| Username and display name | Identifying you in the app |
| Gender (male / female / undisclosed) | Optional gender-balancing rules for matchmaking |
| Phone number (optional) | Optional. So an event organizer can reach you about events you join — see 3.2. You can add, change or remove it at any time in your account settings |
| Membership tier, status and expiry | Enforcing free and paid plan limits |
| Account administration records | Security and support — a log of changes made to accounts by administrators |
| Data | Why |
|---|---|
| Display name | Showing you in the queue and on court. It can be a nickname; it need not be your legal name |
| Gender | Optional gender-balancing rules, when the organizer enables them |
| Phone number | Contacting you about that event: whether you are playing, when your court is up, results, and sharing event information and your own record. Collected only when the organizer of that event has turned on the requirement, or you choose to give one. Visible to that event’s organizer only — never to other players and never on a display screen |
| Skill level and rating | Optional, organizer-enabled — used for balancing teams |
| Queue position, playing status, team | Running the queue |
| Match results and scores | Standings, brackets, and your own win–loss record |
| A device identifier | So your phone can find your row without an account (see 3.3) |
The first time you use the app it generates a random identifier and stores it on your device. This is not your advertising ID, phone number, IMEI, MAC address or any manufacturer identifier, and it is not derived from anything about your device or about you.
It exists so an anonymous player can return to their own queue entry. It cannot be linked to you outside this app, and deleting the app deletes it.
Clearing the app’s data or uninstalling removes these.
Your chosen language is also stored on your device. If you have an account, it is additionally recorded on that account — see 3.7. If you do not have an account, it stays on your device only.
The app uses the camera for one purpose: scanning a QR code to join an event. Frames are processed on your device to read the code. No image or video is recorded, stored or transmitted, and the camera is inactive outside the scanning screen.
The app requests no microphone permission and cannot record audio.
When the app crashes or hits an error, it sends a diagnostic report to Sentry so the fault can be found and fixed. A report contains the error and the code path that produced it, plus the device model, operating system version and app version — which is how we tell a fault affecting one phone model apart from one affecting everybody.
If you have an account, we record on that account: your country, your device platform (iOS or Android), your device language and time zone, the app version, and when you last used the app. This tells us which languages and devices to support.
Country is worked out from your network connection when the app talks to our server. We do not store your IP address, and we do not use location services — the app has no location permission and cannot read your position. A VPN or mobile roaming will change the answer, because it describes the network, not you.
We also keep, for each event, a statistical summary: which settings the organizer chose, how many games were played, and how many people took part. It contains no event name, no player names and no results.
If you join an event without an account, we collect none of this about you. The only thing recorded is that one more person joined, counted in one of four groups — someone signed in, someone using the website, someone using the app, or a name the organizer typed in. Which group you fall into is worked out from the request your device already makes; it is a count, not a record about you, and it is deleted with the event.
Precise or background location · your device’s contacts or address book · calendar · photo library · microphone or audio · health or fitness data · SMS or call logs · installed-app lists · payment card numbers · biometrics.
A phone number you type in yourself is collected as described in 3.1 and 3.2. We never read it from your device, and we never access your contacts to find it.
An event is a shared, semi-public activity, so some information is visible by design:
Anyone holding an event’s join code or QR code can view that event’s queue and results. Treat the join code as semi-public; organizers can hide it from display screens in event settings.
Advertisements are shown in two places, both supplied by Google: Google AdMob in the mobile app, and Google AdSense on the website. Paid plans are ad-free in the app.
To serve ads, Google may access technical information such as IP address, device type and coarse region. In the app it may also access your device’s advertising identifier; on the website it may instead store cookies or similar identifiers in your browser. This is collected by Google, not by us — we receive only aggregate earnings figures and never see who saw which ad.
Ads are not shown on the venue display board, and never on the pages used to join an event or on these legal pages.
Paid plans are sold only through in-app purchase on the App Store or Google Play. Your payment is handled entirely by Apple or Google — we never see or store your card details.
We use RevenueCat to manage subscriptions. It receives a pseudonymous account identifier for you, together with purchase events from the store (a purchase, a renewal, a cancellation, a refund). We store, against your account: your plan, its status, its renewal date, and the amount and currency the store reports for the purchase.
If you enter a referral code when subscribing, we also record which code you used, so we can pay the partner who referred you. A referral code identifies the partner, not you: partners are told how many subscriptions their code produced, and are never given your name, email or any other personal information.
Cancelling and requesting refunds is handled by the store, not by us: use your App Store or Google Play account settings.
Where the UK/EU GDPR or similar law applies:
Data is stored with our hosting provider Supabase (which runs on Amazon Web Services) in Singapore (AWS ap-southeast-1). If you are outside that region your data is transferred there, protected by the provider’s standard contractual clauses.
Retention:
You can request access to, correction of, or deletion of your personal information, object to processing, or ask for a copy in a portable format. Contact cs@pickleballeventmanager.app; we respond within 30 days.
Deleting your account: the app has a built-in Delete account control in Account settings. It permanently deletes your account and profile — it is immediate and cannot be undone.
If you joined anonymously as a player you have no account to delete. Ask the event organizer to remove you, or wait for the automatic deletion above. If you cannot reach the organizer, contact us with the event name and date and we will remove your entry.
Residents of the EEA and UK may also complain to their data protection authority.
Residents of US states with comprehensive privacy laws — including California (CCPA/CPRA), Virginia, Colorado, Connecticut, Utah and Texas — have rights of access, correction, deletion and portability, and may not be discriminated against for exercising them. We do not sell personal information. Because we request non-personalized ads only, we do not share personal information for cross-context behavioural advertising as those laws define it.
If you are in another country, the rights described here are offered to you as well, whether or not your local law requires them.
The app is not directed to children under 13, and we do not knowingly collect personal information from them. A child may appear in an event as a player entered by an organizer or parent, in which case only a display name is recorded. If you believe a child’s information has been collected improperly, contact us and we will delete it.
Data is encrypted in transit (HTTPS/TLS) and at rest by our hosting provider. Access is restricted by database row-level security so that organizers reach only their own events, and anonymous players can only read and modify their own entry. Passwords are stored only as salted hashes.
No system is perfectly secure. If a breach affects your personal information we will notify affected users and any regulator as the law requires.
| Provider | Role | Policy |
|---|---|---|
| Supabase | Database, authentication, hosting | supabase.com/privacy |
| Apple / Google | App distribution and payment processing | Their own policies |
| RevenueCat | Subscription management | revenuecat.com/privacy |
| Google AdMob | Advertising (mobile app) | policies.google.com/privacy |
| Google AdSense | Advertising (website) | policies.google.com/privacy |
| Sentry | Crash and error diagnostics (mobile app only) | sentry.io/privacy |
Each acts under contract and may not use your information for their own unrelated purposes, except as described for advertising above.
We will post any change here and update the “Last updated” date. Significant changes will be announced in the app before taking effect.