Privacy notice

Provider and club responsibilities

Padel Score is provided by duonon GbR, Morsestraße 1, 40215 Düsseldorf, Germany, represented by Alexander Kassymow, Daniel Kohnert and Artur Sept. Contact: padelscore@duonon.de; support: support@duonon.de.

The club identified on a form determines its activities, admission and publication. Contact it about these decisions; contact duonon about platform accounts and technical operation. Controller/processor responsibilities and any required agreement with a club must be established before productive use. Creating a workspace does not verify a real-world club. Public registration under a club name requires separate manual operator approval. Teams can organise privately.

Club and competition applications

Forms process your display name, selected club/event, a verified email for guest self-registration, optional team label, registration status and changes, and the version/time of your terms acceptance and privacy acknowledgement. No postal address, birth date, health or payment data is needed. Acknowledgement is not general consent to all processing.

Club administrators review club applications; authorised organisers review competition applications, places and withdrawals. Pending or rejected applications and contact details are not public. Public registration does not grant management or scoring rights. Open guest competitions need no app or account; new club workspace requests require a Padel Score account and do not create membership in the actual club. Internal competitions may require an eligible account or approved workspace access. A private browser session keeps access to their own applications; verified guests can reopen access with a new code sent to the same address. Older unverified participation may still require a personal receipt or identity checks and help from the club.

Doubles, personal passes and club verification

A doubles entry also stores the second display name. Authority to register another player is recorded separately from their personal acceptance. Every partner confirms their own participation using an account or their own verified guest email. Restricted competitions require the corresponding eligible account; entering a name does not prove eligible workspace access or authorise online access.

Guest passes contain a public reference and a separate access code, stored only as a hash. A pass can restore personal access on another device; rotating it invalidates old codes. Linking a guest participation to an account requires explicit confirmation. Keep codes private.

Club review stores club name and location, representative name and role, official contact email, optional website or register reference, bounded notes, workspace type, status, time, operator identifier and a bounded review note with an evidence reference. No identity document uploads are provided. Club administrators cannot approve themselves. Retention and review procedures require operator and legal approval before production.

Profiles, sign-in and roles

Optional profiles use Apple sign-in, configured Google sign-in or email sign-in codes. Provider sign-in verifies the signed provider subject, audience and nonce. Provider identities are never merged solely by an email address. Creating an email account requires a display name, current terms acceptance and privacy acknowledgement. Codes expire after ten minutes, are single use and have limited attempts. Only a keyed hash is stored. Existing link sessions remain supported. We process internal IDs, display name, optional announcement name, profile connections, friends/requests, invitations, synchronised match records and session metadata. Apple identifiers are pseudonymised. Email addresses are used to deliver requested authentication links, not to subscribe to marketing. The configured email provider and region must be documented before activation.

Club roles, staff invitations, expiry, acceptance and revocation are recorded. Staff invitations require a signed-in account, separate code and explicit acceptance. Participation claims do not grant management rights. Names alone do not merge identities.

Matches, results and public visibility

Competition data includes names, teams, fixtures, courts, schedules, scores, results and correction/approval records. A linked account can connect a participation to personal history. Rankings and exports use display names; phonetic names serve speech only.

Club competitions start privately. Explicit publication can make display names, teams, fixtures and results available to viewers. Clubs must inform participants and establish the permitted basis. Applying alone is not general permission to publish a personal profile, contacts or fitness data. Live scores are provisional until confirmation. Controller ownership, handovers and corrections are recorded for reliability and disputes. Public links are read-only; personal access is scoped to assigned participation and live input needs separate authority.

Cookies and local storage

Necessary sessions maintain sign-in and registration ownership. The registration cookie is HttpOnly, Secure in production and SameSite=Lax, with a maximum lifetime of 180 days. Account and competition access has separate expiry and revocation. Cookies go to the configured same-origin application.

Devices can store settings, recent competitions, match/workout history and pending synchronisation records. Native credentials use protected storage. Closing a view is not withdrawal. The platform uses no advertising networks or cross-app advertising tracking. See the actual storage inventory, including legacy private-score access stored in the browser. Public help search runs locally without sending search queries to an external search service.

Optional usage analytics and diagnostics

Prepared usage analytics and technical diagnostics are off by default. They require a separate operator review, technical activation and your voluntary choice for each category. Rejection or withdrawal does not limit the app. Optional processing relies on consent under Article 6(1)(a) GDPR and optional device access on section 25(1) TDDDG. Necessary storage for expressly requested functions is subject to section 25(2) TDDDG.

The interface accepts predefined screen/event or technical error codes, without names, email addresses, health data, scores, free-form errors, access tokens or complete URLs. Records are not linked to your account. A daily random session identifier can still be a personal-data pseudonym; we do not describe this processing as automatically anonymous. A self-hosted operations platform is prepared with separate projects per app: Umami for usage statistics and GlitchTip for fixed diagnostic events. Sharing the service does not connect users across apps. Proposed upper limits are 90 days for usage events and 14 days for diagnostics; separate availability checks without visitor identity are retained for 30 days, infrastructure logs for 7 days and encrypted backups for 30 days. These are deployment drafts requiring approval. Actual location, recipients, access rights, contracts and automated deletion must be verified and implemented before activation. No optional transfer takes place without this release.

Choices apply per browser and origin; native apps and other domains have separate choices. Do Not Track and Global Privacy Control disable optional categories. Change privacy settings.

Apple Health, workouts and Strava

Optional workout data can include duration, energy and heart rate according to your device permissions. Local records stay on the device unless you use a function synchronising selected match/workout records or exporting a workout. Depending on that feature, selected records and metadata can be processed by the backend. A club role provides no access to private health/workout data. Apple Health permissions can be changed in system settings.

Strava connection and export are voluntary. Connection credentials are stored encrypted; selected workout information, export metadata and the returned activity ID are processed when you use export. Disconnecting prevents future exports. Data already sent is also subject to Strava’s privacy policy.

Infrastructure, purchases and optional speech

API, database, push and audio infrastructure run on our managed VPS at netcup GmbH. Cloudflare provides DNS and, depending on hostname settings, connection delivery/protection. The operator has confirmed data processing agreements with netcup and Cloudflare. Necessary technical connection data can include IP address, request time/function and security/error logs. New quota identifiers are pseudonymised; sensitive request bodies and access credentials must not be logged.

Apple handles sign-in and App Store purchases. We receive entitlement information, not card/bank details. Optional speech generation can send required names/text and language to ElevenLabs when enabled. Club application data is not sent to ElevenLabs, Strava or an AI service. Invitations are shared by the user; there is no automatic invitation email/messenger delivery.

Provider information: netcup, Cloudflare, Apple, ElevenLabs. Depending on enabled services, processing outside the EU/EEA may occur. Provider regions, safeguards and contractual arrangements require separate review before activation.

Purposes and legal basis

Purposes are requested platform functions, club competitions, secure operation and dispute handling. Depending on the function, contract-related processing, legitimate interests in operation/security or separately requested consent may be relevant. Optional health processing requires separate assessment. The concrete legal basis for club processing and public results must be documented by responsible parties before release.

There is no advertising profiling and no exclusively automated decision with legal or similarly significant effects. Admission remains subject to the club’s rules and review. Optional Apple Health, Strava, speech and account functions are not necessary for basic guest participation.

Retention, erasure and access

The cleanup process can remove rejected/withdrawn applications without retained participation links after 90 days and expired sessions; the operator must schedule it. Active participation references require controlled removal or anonymisation. After a draw, withdrawal creates a request instead of deleting played results. Match and audit history are not all erased by withdrawing.

Your private access allows withdrawal or erasure of an unused application. Authorised club administrators can export an individual application including acceptance metadata or remove eligible requests. Account deletion, broader access, correction or erasure can be requested through the app/support and, where applicable, the club. Entitlement is checked before disclosure; club exports must not include unrelated private or health records.

Purpose-specific retention for competitions, audit, logs and encrypted backups must be established before production. Restores must respect prior erasures. No fixed log/backup retention is promised without that operator configuration. Local records can be removed through the app/device controls.

Rights, complaints and updates

Subject to the applicable requirements, rights include access, rectification, erasure, restriction, portability, objection and withdrawal of consent for the future. Contact padelscore@duonon.de. You may complain to a supervisory authority, including LDI Nordrhein-Westfalen. Changes to purposes, providers and functions require renewed information and review.

Verified guest access without an account

New guest self-registration requires verification of your own email address. An eight-digit one-time code expires after ten minutes and permits at most five failed attempts. Codes are stored as purpose-bound HMACs. The subsequent proof is limited to one form and private browser session, lasts up to 30 minutes and is consumed on registration. This does not create a Padel Score account.

The address connects this participation to your personal recovery access; it is not used for advertising. The code email also includes the normal public registration link. Reopening participation requires a new email code; the public link or knowledge of the address alone grants no access. Older receipts remain valid, and an old unverified email alone cannot claim a participation. Each doubles partner confirms their own identity and participation.

Technical cleanup removes expired verification proofs and code records more than 24 hours past expiry. The operator must run the cleanup worker. Personal participation and email records follow the competition retention and erasure process.

Partner invitations and tournament operations

For fixed doubles, a private partner invitation can be shared, or a player can explicitly register as looking for a partner where offered. The hashed invitation code expires within 14 days and can be used once to join. It does not grant access to another person’s participation or club management. Each invited partner enters and confirms their own details. Authorised organisers can pair two players who explicitly requested partner assignment before the draw.

Operations process attendance, date and court proposals, responses, time-limited waitlist offers, and recorded withdrawal or replacement decisions. Personal updates require the relevant account or participation access. These features do not send email or messenger messages automatically. Do not include health information or unnecessary confidential details in free text.

After complete loss of guest access, a club admin may issue new personal access following an independent identity check and recorded reason. The previous personal guest access is revoked. No identity document copy or number is required. Account-owned participation requires account recovery instead.

Technical maintenance removes read personal updates after 90 days and retry receipts after 180 days. Retention for unresolved sporting cases and competition history requires separate agreement and legal review before productive use. Deletion markers for synchronised personal match records retain the internal match identifier and deletion time to prevent stale devices from restoring deleted records; account deletion removes them.

Public club identity and image storage

Authorised club administrators may prepare a logo, optional cover, colour, description, venue, website, public contact email and club privacy link. Drafts and private image previews require authorised access. Explicit publication by an administrator of a verified club exposes this identity and public competitions on its club page and related forms. It does not publish private applications, roles, contacts or notes.

PNG/JPEG uploads are checked for file size and dimensions and rewritten as PNG. Original filenames, EXIF and location metadata are discarded, but visible image content remains. Prefer a club logo and venue photos without identifiable people. The publishing club must hold image rights and any necessary permissions from depicted people, confirmed before publication. This acknowledgement does not replace an applicable legal basis or required consent.

A competition may use its own image. Public image access requires a currently published and eligible reference. Unpublishing ends that access but cannot recall copies already retained by third parties. The previous profile version can be restored as a draft for up to seven days. Unused assets may be explicitly deleted and are removed after at least seven days by the scheduled cleanup worker. The operator must run this process. Further publication and backup deletion follow separately established retention procedures.