Privacy Policy

We collect only the data needed to operate, secure, and improve the service.

• Account data such as name, email address, authentication records, and consent evidence.
• Billing identifiers and subscription status from Dodo Payments; BallPeek does not store full payment-card details.
• Telegram identifiers and alert preferences if you link Telegram in a future alerting flow.
• Product usage, paywall interactions, request identifiers, device/browser diagnostics, and security logs.

We use account data to authenticate users, provide requested features, project paid entitlements, deliver opted-in communications, prevent abuse, diagnose failures, and understand whether product boundaries are useful.

We do not sell personal data or use it to place wagers or execute trades.

Data may be processed by infrastructure and product providers needed to run the service, including Cloudflare, database hosting, Sentry, Dodo Payments, and Telegram when you choose to link it. Each provider handles data under its own terms and role.

Deleting your account removes the local user, sessions, linked accounts, profile, registration-consent record, local billing projection, and linked communication data that exists at deletion time. Retained operator records are anonymized where they contain your user identifier or email.

Dodo Payments transaction records remain with Dodo as Merchant of Record where required for tax, payment, dispute, fraud, or legal obligations, but account deletion is blocked until a renewable Pro subscription is canceled. Limited logs and backups may remain temporarily until their normal expiry cycle.

We use authenticated sessions, signed tokens, access controls, encrypted transport, and operational logging. No system is risk-free; protect your credentials and report unexpected account activity promptly.

You can review account settings, manage paid access through the hosted customer portal, unlink optional communication channels when available, and permanently delete your local account. Registration is optional, but authenticated features require the account data described here.

When this policy materially changes, the effective version changes. New registrations must accept the current version; existing-user re-consent may be required when a change affects how personal data is handled.