How Padel Ping handles your data.

This page reflects the way the current app works: account based access, alert storage, push notifications, consent-gated product analytics, technical error monitoring, Pro subscription tiers, account deletion, and booking handoff to external provider pages.

Last updated: April 4, 2026

Summary

Padel Ping stores account, alert, favorite club, subscription tier, and recent match data needed to operate the app.
Push notifications rely on device push tokens and notification event records so the service can deliver alert pings.
The app uses optional, consent-gated product analytics powered by PostHog. Analytics is off by default and only activates when you opt in.
The app also uses Sentry for technical error and crash monitoring. Sentry is separate from product analytics and is not part of the analytics-consent flow.
Booking happens on external provider pages outside Padel Ping, and those third parties have their own policies.
The app uses Supabase for auth and core data storage, Firebase/APNs for mobile push delivery, PostHog (EU region) for product analytics, and Sentry for technical error monitoring.
You can delete your Padel Ping account from inside the app. Deleting your account does not cancel any App Store or Google Play subscription.

1. Scope of this policy

This Privacy Policy explains how Padel Ping collects, uses, stores, and shares information when you use the Padel Ping mobile app and related services.

Padel Ping is built to monitor padel court availability across supported venues, match that availability against your alerts, send push notifications, and hand you off to an external booking page. Padel Ping does not complete bookings inside the app.

2. Information we collect

The app and backend architecture currently support account authentication, alert creation, favorite clubs, recent slot matches, premium subscription tiers, account deletion, and mobile push notifications. The information collected is limited to what is needed to run those features.

Account information, such as your email address, display name (if provided via your authentication method, e.g., Google Sign-In), account identifier, authentication provider (email/password, Sign in with Apple, or Google Sign-In), and subscription tier.
Alert and preference information, such as alert names, selected clubs, release and cancellation settings, court type, and Padel Ping Pro precision filters including days of week, watch windows, and minimum lead time.
Club and favorites information, such as which clubs you have saved as favorites from the supported venue list.
Notification and device information, such as device platform, push token, token timestamps, notification delivery status, and recent alert matches.
Availability match information, such as the clubs, courts, times, and booking links associated with slots that matched your alerts.
Payment and entitlement information needed to reflect whether your account is on a free or Pro tier. Billing itself is handled through the Apple App Store or Google Play rather than inside Padel Ping. Subscription receipts are verified server-side before Pro access is granted.
Technical error-monitoring data, such as crash reports, stack traces, internal app user identifier, subscription tier tag, device and app runtime context, and limited diagnostic metadata attached to selected failures in billing, booking handoff, and notification routing flows.

3. Product analytics

Padel Ping includes optional product analytics to help us understand how people use the app and where we can improve sign-in, alert, and booking flows. Analytics is powered by PostHog and is hosted in the EU region.

Analytics is off by default. It only activates if you choose to opt in through an in-app consent prompt that appears after you first sign in. You can change your choice at any time from the Account screen in the app.

When analytics is enabled, the app records anonymous usage events such as screens viewed, alerts created or edited, paywall interactions, and booking link taps. These events are associated with an anonymous identifier before you sign in, and with your Padel Ping user identifier after you sign in, so we can understand user journeys across sessions.

We do not use Apple App Tracking Transparency, IDFA, or any cross-app or cross-website advertising identifiers. This is first-party product analytics only.

Analytics events include: app opens, authentication flow steps, alert creation and editing, paywall views, upgrade completions, notification taps, and booking link opens.
Analytics does not collect your email address, booking URLs, raw third-party error messages, or provider payload data.
PostHog autocapture, session replay, heatmaps, and web analytics features are all disabled.
When you deny or revoke analytics consent, no events are captured or sent to PostHog.
If you delete your Padel Ping account, your analytics consent preference is removed along with all other profile-owned data. Any previously sent analytics events that are no longer linked to your identity may be retained in anonymised or aggregated form.

4. Error monitoring

Padel Ping uses Sentry for technical crash and runtime error monitoring. Sentry is used to help us detect app failures, diagnose issues, and improve reliability in high-value flows such as billing, booking handoff, and notification routing.

Sentry is separate from PostHog product analytics and is not part of the analytics-consent flow. It is enabled only when the app is configured with a Sentry DSN, and it is used for reliability and security purposes rather than analytics or advertising.

Sentry captures uncaught Flutter and Dart exceptions and selected handled failures that we explicitly report from the app. For signed-in users, Sentry user context uses the internal Padel Ping user id only. It does not intentionally send raw email for new users. The app also tags the current subscription tier.

Handled Sentry events currently include selected failures in billing upgrades, restore purchases, manage subscription launch, booking handoff, malformed notification routing, and recent-slot refresh during notification-open handling.
Depending on the error, diagnostic metadata sent to Sentry can include technical context such as stack traces, internal slot ids, club or court names, source and court type tags, booking URLs, notification payload keys, message ids, and error messages.
Sentry is not used for advertising, cross-app tracking, or product analytics.

5. How we use your information

We use the information we collect to provide and operate the service you asked for, keep the app functional, and improve reliability around alert detection and delivery.

Create and manage your account and sign-in session.
Store and apply your alert settings, selected clubs, favorites, and Pro filters.
Enforce alert limits based on your subscription tier. Free accounts can save up to 3 alerts; Pro accounts can save unlimited alerts.
Match newly detected availability against your alerts and show recent matches in the app.
Send push notifications to your registered device when a relevant slot is detected.
Verify subscription purchases server-side with Apple or Google before granting or maintaining Pro access.
Process restore-purchase requests to recover your Pro entitlement on a new device or after reinstallation.
Process account deletion requests and remove your authentication record and profile-owned data.
Understand how the app is used through anonymised product analytics, where you have opted in, to improve sign-in, alert, and booking flows.
Detect, investigate, and diagnose crashes and technical failures through Sentry error monitoring.
Maintain security, prevent abuse, investigate failures, and keep the monitoring and notification systems reliable.

6. Legal bases and permissions

Where applicable, we process your information because it is necessary to provide the service you request through the app, because you have chosen to enable features such as push notifications or analytics, because we have legitimate interests in running and securing the service, or because we need to comply with legal obligations.

Product analytics processing is based on your explicit consent, which you can grant or withdraw at any time from the Account screen in the app.

Technical error monitoring through Sentry is not part of the analytics consent flow and is processed on the basis of our legitimate interests in keeping the app secure, stable, and reliable.

If you allow push notifications, that permission is managed by your device operating system and can usually be changed later in your device settings.

7. Sharing and service providers

Padel Ping relies on third party infrastructure to run the product. We share information only as needed to provide the service, process subscriptions, or meet legal obligations.

Supabase, which provides authentication, database storage, edge functions for subscription verification and account deletion, and core application data services.
Firebase Cloud Messaging and Apple Push Notification service, which are used to deliver mobile push notifications.
PostHog (EU region), which processes anonymous product analytics events when you have opted in. PostHog does not receive your email address or booking URLs.
Sentry, which processes technical crash and runtime error-monitoring events and related diagnostic metadata when Sentry is configured in the app. Sentry user context uses the internal app user id rather than raw email for new users.
Apple and Google, to the extent needed for app distribution, platform billing, Sign in with Apple, Google Sign-In, server-side subscription verification, and subscription management.
External provider endpoints or related booking pages when you choose to open a booking link from the app.
Professional advisers, regulators, law enforcement, or counterparties where disclosure is required by law or reasonably necessary to protect the service or our users.

8. Data retention

We keep information for as long as it is reasonably needed to operate the service, maintain your account, support alert delivery, enforce our terms, and satisfy legal, security, or accounting obligations.

Different categories of data may be kept for different periods. For example, account and alert records may remain while your account is active, and push token or notification records may be retained until they are invalidated, no longer needed, or removed as part of account cleanup.

Analytics event data sent to PostHog while you were opted in is retained according to PostHog's standard data retention policies. Withdrawing consent stops future event capture but does not retroactively delete previously sent events.

Error-monitoring events sent to Sentry are retained according to Sentry's configured retention settings. Disabling analytics does not affect Sentry, because Sentry is separate from the analytics-consent flow.

9. Account deletion

You can request deletion of your Padel Ping account at any time from inside the app. Open the Account settings screen and choose Delete account. The app will ask you to confirm before proceeding. Once confirmed, the deletion is processed immediately.

Your authentication record is permanently removed.
Your profile, including email address, subscription tier, and account metadata, is permanently removed.
All alerts you created, including alert names, selected clubs, enabled monitoring types, court type settings, and any Pro precision filters, are permanently removed.
Your favorite clubs list is permanently removed.
Your device push tokens and notification event history are permanently removed.
Your slot alert match history is permanently removed.
Your subscription verification records stored in Padel Ping are permanently removed.
Your analytics consent preference is permanently removed.
Detected slot data is not deleted because it is not owned by any individual user account. Detected slots are shared availability records tied to clubs, not to your profile.
Previously sent analytics events that are no longer linked to your identity may be retained in anonymised or aggregated form by PostHog.
Previously sent Sentry error-monitoring events may be retained by Sentry according to configured retention settings and may still include the internal app user id, subscription tier, and technical diagnostic context captured at the time of the event.
Aggregated or anonymised operational logs that are no longer linked to your identity may be retained for security, abuse prevention, or service reliability purposes.
Deleting your Padel Ping account does not cancel any active App Store or Google Play subscription. You must cancel your subscription separately through the relevant platform's account settings before or after deleting your Padel Ping account.

10. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or object to certain processing of your personal information, and in some cases to request a copy of it in a portable form.

You can also manage some information directly in the app, such as alert settings, notification permissions, and analytics preferences. If you want help with a privacy request, use the support contact details published for Padel Ping at the time you make the request.

You can sign out of the app at any time.
You can change or delete alert configurations and favorites through the app.
You can enable or disable product analytics from the Account screen in the app.
You can disable push notifications in your device settings.
You can delete your Padel Ping account as described in section 9 above.
If you are in the UK, you may also have the right to complain to the Information Commissioner's Office.

11. External links and third party pages

Padel Ping can open booking links in an in-app browser or external browser. Once you leave Padel Ping and visit a third party page, that third party is responsible for its own content, privacy practices, and terms.

12. Changes to this policy

We may update this Privacy Policy from time to time to reflect product changes, legal updates, or operational needs. The latest version will be the version published on the Padel Ping website or otherwise made available through the service.