Baanli privacy notice

Effective 10 November 2026.

Who is responsible

Baanli is operated by LPS Group B.V., KVK 97190136, Vrouw Avenweg 131, 2493 WT Den Haag, Netherlands. LPS Group B.V. is responsible for the personal data processed to provide Baanli. Contact support@bcworks.net for privacy questions or requests. Our telephone number is +31 6 2719 7896.

Your account and tennis records

We use your verified email address, account identifier and display name to provide your account, send sign-in codes and restore your Baanli data. The current beta uses email-code sign-in. Apple sign-in is not currently enabled.

Baanli stores match setups, player names, scores, scoring events and their times, playing visits, results, saved players and presets. App-generated phone and Watch identifiers help keep the correct devices, account and match records connected. These are app identifiers, not an advertising identifier.

Your phone and Watch keep local app data. Account-backed match records and saved players/presets are also sent to Baanli's service for backup, restoration and connected play. A player name you enter may describe another person; enter only information appropriate for your match. We may receive a name and match record involving you from the person keeping score or another participant.

People with access to a shared match can see the match information intended for them, including recorded player names and results. Following a score does not give someone access to your personal Health readings. Invitation links should be shared only with intended recipients. There is no public player directory or public Health feed in this beta.

Apple Health and optional workouts

You can keep score without recording a workout. If you choose workout recording and grant permission, Baanli uses Apple Health on your devices to record tennis workouts and active energy, and to read permitted workouts, heart rate, steps and active energy. The personal workout view uses permitted Health information to show your activity alongside the match.

Baanli does not send Health readings or derived personal workout charts to its account service, other players or its deletion journal. They are processed on your devices. Match scores and playing times are separate account-backed tennis records. Workouts may contain Baanli match, visit, player and account identifiers so the correct personal workout can be found again.

You control Health permission in Apple's settings and can turn off future workout recording in Baanli. Turning recording off does not remove workouts already saved in Apple Health. Deleting Baanli history or its profile does not delete those Health workouts. Manage them in Apple Health. Apple manages any Health synchronization or backup you enable under its own settings and terms.

Security, service records and support

Our service providers process network and account-security information such as IP addresses, client information, sign-in events and request/error records to authenticate requests, prevent abuse and operate the service. This is different from advertising tracking. The app does not include an advertising or behavioral analytics SDK, request your advertising identifier, or record your screen/taps for a separate analytics feed.

If you contact support, we process your message, contact details and any material you choose to send. We may ask for your app version, device model, operating system version, approximate problem time and a description. Never send passwords, sign-in codes or complete private invitation links. Do not send Health records unless we have agreed on a specific need and a safe way to provide them. Assisted recovery copies are handled separately and only for the recovery/support purpose you request.

During TestFlight testing, Apple automatically collects crash reports and usage information and shares them with us. This includes device and OS details, installation and session counts, and may include your name and email address. You cannot opt out of this automatic collection while testing through TestFlight. If you choose to send feedback, Apple also shares your comments and any screenshots you attach with us. We use this information to investigate and fix app problems. This beta-testing process is separate from Apple Health permissions.

Why we use this information

We use account details and tennis records to provide the service you request, including sign-in, scoring, saved history, restoration and invited connected play. Our legal basis for that processing is performance of our service agreement.

We rely on legitimate interests in operating a secure, reliable service, maintaining the integrity of shared match results and answering support requests. This includes limited information entered by other players. We consider those interests alongside the people affected and their rights. For optional Health processing, we rely on your choice and consent, including the relevant Apple Health permission. You can withdraw that choice for future processing. We also process information when needed to meet legal obligations, including handling privacy requests.

We do not sell your personal data, use it for targeted advertising, or use Health information for advertising. Baanli does not make automated decisions that produce legal or similarly significant effects about you.

Service providers and international processing

We use Supabase for account authentication, the database and related app services; Cloudflare for sign-in email and protected deletion-recovery storage; and email services for support correspondence. Apple provides device/Health services and TestFlight or App Store distribution under its terms. Authorized people supporting Baanli can access information necessary for their work. We may disclose information when legally required.

The Baanli database is hosted in Frankfurt, Germany. Its independent encrypted deletion-recovery storage uses Cloudflare R2's EU jurisdiction. These storage choices do not mean every authentication, email, support or provider operation occurs only in the EU. Providers and their subprocessors may process information in other countries. Their published data-processing agreements include EU Standard Contractual Clauses for applicable restricted transfers. Contact us for information about the safeguards relevant to your data.

Retention and deletion

We keep account information and tennis records while needed to provide your account and the history you retain. There is no automatic inactive-account deletion period in this beta. Hiding a match keeps it available to restore; it is not permanent deletion.

The app's Delete Baanli account flow requires fresh account verification and confirmation. Once the service confirms deletion, it removes your Baanli sign-in identity and linked sign-in methods, revokes its sessions, and erases your display profile, personal match payloads, presets and saved-player payloads. This cannot be undone. A deletion request awaiting confirmation is not yet a completed deletion; reconnect to let the app check its status.

Other participants can retain their match results and scoring events. Names linked to your account are replaced with Deleted player in retained shared history and its service-held copies. Someone may have entered your name without linking it to your account; those entries cannot automatically be identified as yours. Contact support@bcworks.net for help with such entries or a broader privacy request. We retain limited record identifiers and match relationships needed for shared-result integrity and deletion enforcement; replacing a name does not make every retained record anonymous.

Confirmed cleanup is applied to the app's local account data and sent to its paired Watch. An offline Watch and other disconnected installations need to reconnect before receiving confirmed deletion or updated shared records. Deletion does not remove your Apple Health workouts or copies another person has independently exported or recorded. Uninstalling the app or signing out is not an account-deletion request.

We retain minimal identifiers, deletion types and deletion times to prevent an old device or recovery copy from bringing deleted data back. These markers currently have no automatic expiry. Protected backup and recovery copies can retain earlier data, including previous account details and names, until safely retired. Confirmed deletions must be reapplied before a recovered service is opened for use. Removing the active sign-in identity does not erase every historical email-delivery, authentication-audit or security log. The configured database backup plan has a seven-day standard window, but this is not a seven-day erasure promise for every log, authentication record, recovery copy or recipient's history. Scheduled recovery-copy cleanup is not currently active; we do not promise that every residual copy is erased within 30 days. Retention for operational/security and support records depends on the purpose, provider controls and any legal need; we review requests to remove information no longer needed.

Your choices and rights

You can ask us to access, correct or erase your personal data, restrict its use, provide a portable copy where applicable, or object to processing based on legitimate interests. You can withdraw consent where we rely on it without affecting lawful earlier processing. Rights have conditions and exceptions. We may need proportionate proof that a request concerns your information; we will not ask you to email a password or current sign-in code.

Write to support@bcworks.net. We normally respond to a privacy-rights request within one month; where the law permits more time, we will explain why within that month. You can also complain to the Dutch Autoriteit Persoonsgegevens or another competent data-protection authority. See your GDPR rights.

If you are a parent or guardian with a concern about a child's information in Baanli, please contact us. We do not ask for a date of birth in the current app.

Changes to this notice

We will update this notice when Baanli's data practices change. Material changes will be brought to your attention through an appropriate channel. Optional features that change data use require the relevant choices and permissions.