Privacy
Privacy Policy
Effective date: 2026-08-10.
Note: Legally variable information is maintained centrally in private/config.php. Configuration values marked [RECHTLICH PRÜFEN] must be completed and reviewed before publication.
1. Controller
2. Website processing
Hosting and server logs
The hosting server processes technically necessary connection data such as IP address, time, requested resource, HTTP status, transferred volume, referrer and user agent to deliver, stabilise and secure the site.
No web analytics or marketing cookies
The website uses no web analytics, marketing cookies, externally loaded fonts, JavaScript frameworks or CSS frameworks. No technically necessary cookies are currently planned.
Email contact
When contacting support, the sender address, content, metadata and attachments are processed to answer the request. Do not send passwords, complete payment details, private keys or complete purchase tokens.
3. Processing in the DartPulse app
Local game data
Profiles, games, history, statistics, hit analysis and settings are stored locally on the device in version 1.0. Normal play does not require a DartPulse account. Version 1.0 exposes no DartPulse cloud, club or LAN feature.
Advertising and consent
The Free version may use Google Mobile Ads SDK and Google User Messaging Platform. Depending on consent, region, device and ad configuration, Google or ad partners may process device, advertising, diagnostic and usage information. The app provides access to applicable privacy options. Local DartPulse house ads do not make an external ad request.
Google and Apple in-app purchases
Google Play or Apple process payments, store accounts and purchase history. DartPulse does not receive complete card or bank details. Official privacy information: Google and Apple.
4. Server-side purchase verification
To securely unlock dartpulse_pro_lifetime, the app sends purchase evidence to the DartPulse backend. Data may include platform, product ID, transaction and original transaction IDs, encrypted Google purchase tokens or Apple-signed transaction data, purchase/refund/revocation status, verification timestamps, a random pseudonymous installation ID, request ID, nonce hash, app version and security logs without complete tokens.
Purposes are verification, entitlement management, restoration, refund and revocation handling, replay/fraud prevention and system security. The backend checks the purchase directly with Google Play or the App Store Server API. This is the explicit exception to local-only app data; gameplay and statistics remain local.
Legal basis
[RECHTLICH PRÜFEN] Rechtsgrundlage für Kaufverifikation, Betrugsprävention und Berechtigungsverwaltung festlegen
International transfers
[RECHTLICH PRÜFEN] Aktuelle Empfänger, Garantien und Transfermechanismen bei Google/Apple festlegen
5. Retention and deletion
Indefinite storage without a defined purpose is not intended.
6. Security
Planned measures include HTTPS, strict validation, encrypted Google purchase tokens, secret isolation, minimised logs, access control, rate limiting, replay protection, signed entitlement evidence, backups and log rotation.
7. Data-subject rights
Depending on applicable law, rights may include access, rectification, erasure, restriction, portability, objection and complaint. Because the backend has no DartPulse account and does not identify a natural person, an appropriate purchase reference or pseudonymous identifier may be necessary.
[RECHTLICH PRÜFEN] Verfahren zur Zuordnung und Bearbeitung von Betroffenenanfragen festlegen
8. Supervisory authority
[RECHTLICH PRÜFEN] Zuständige Aufsichtsbehörde eintragen
9. Changes
This policy will be updated when the app, backend, advertising or store integration changes.