Última actualización: 16 June 2026
1. Responsable y contacto
Gustav GutscheSchlossplatz 166482 ZweibrückenGermanyEmail: support@tournamentcraft.comA data protection officer has not been appointed for TournamentCraft at this stage. Privacy requests can be sent to the email address above.
2. Scope and product model
This privacy notice applies to tournamentcraft.com, the operator dashboard, server-side APIs, public tournament pages, and backend processing used by the native TournamentCraft apps.
Native apps remain offline-first. Local tournaments stay on the device unless an operator signs in and explicitly syncs or publishes tournament data.
3. Hosting, security logs, and analytics
TournamentCraft is hosted on Vercel. Technical access data is processed to deliver the website, protect it from misuse, diagnose incidents, and keep the service reliable.
TournamentCraft uses cookieless Vercel Web Analytics for aggregated page views and normalizes public tournament URLs before analytics events are sent.
4. Operator accounts and sessions
Operator accounts are managed through Firebase Authentication. Depending on the sign-in method, Firebase and TournamentCraft may process account identifiers, email address, display name, provider information, ID tokens, and session data.
Technically necessary cookies and local storage are used for sessions, login state, CSRF protection, abuse prevention, and privacy preferences.
5. Private sync and public publishing
Private cross-device sync stores editable tournament payloads for signed-in operators with an active monthly or yearly publishing subscription.
Public tournament pages are created only after an explicit publish action and expose only published tournament data such as schedules, standings, teams, fields, results, public URLs, and update timestamps.
6. Payments and entitlements
Paid publishing is processed through Stripe Checkout. Stripe processes payment and billing data; TournamentCraft does not store full card numbers.
Stripe webhooks are the source of truth for paid entitlements and are used to grant, maintain, expire, or remove publishing access.
7. Rights, retention, and changes
Data subjects may request access, rectification, erasure, restriction, data portability, objection, and withdrawal of consent where applicable.
Records are retained as long as needed for account operation, security, billing, support, legal obligations, and public page integrity. This notice will be updated when features, providers, or processing activities change.
Más detalles sobre almacenamiento están disponibles en la Política de cookies.