Privacy and manual support

Private beta · updated 19 October 2026.

Who is responsible

Patrik Pecinka is the controller of personal data used to run Q-Golf. Contact: patrik.pecinka@gmail.com. This free private beta is for invited adults aged 18 or older living in Czechia: two initial testers, at most ten total. Access and password help are arranged individually.

Your account and golf

Guests can browse courses. Saving rounds, clubs and practice requires an account. Q-Golf uses your email, login identity, display name and distance units. Google login requests basic identity, email and profile access, without Gmail, Drive or contacts access. Optional profile details may be left empty. New ČGF membership numbers are not collected; an older saved number can be removed in Account.

Scores, clubs, carry distances, completed practice, notes, dates and manually recorded shot positions are stored on your phone and synchronized to your account. Older records may contain GPS metadata. Unfinished practice and practice/handicap preferences stay on this phone. Replaced conflict copies remain in a private local recovery folder, outside active statistics and sync. Other users have no public profile/feed for browsing your golf.

Original movies and recorded audio stay on the recording phone. Sync sends clip/session information, not the original movies. Internal recordings are excluded from routine device backup. An explicit export, private account archive or requested developer preservation copy can include originals, notes and locations. Choose a private destination; these copies have their own lifetime. A replacement phone restores synchronized records, not another phone's original movies.

Choices and help

Camera permission enables recording; microphone permission is optional. iPhone Settings controls permissions. Manual shot positions work without location permission. Ask people before recording or sharing them. External benchmark comparisons and benchmark-based practice ranking are excluded from this beta; personal statistics and drills remain.

Start support with the app's redacted summary and steps/version. The summary excludes your email, account ID, golf records, locations and videos. Share it only through a destination you choose. A private archive is requested only when needed for an explained recovery problem. Never send passwords or sign-in/reset links.

Identity is checked through the agreed private channel before access changes. Google recovery stays with Google. A Q-Golf password replacement and explicit global session revocation prevent refresh, but an existing access token may remain valid for up to one hour. They do not erase an offline phone.

Services and international processing

Supabase processes authentication and synchronized records for Q-Golf. The staging database/Auth/Storage region is Frankfurt, Germany; support, service logs, subprocessors and functions can involve other countries. Its DPA and transfer information describe processor duties and safeguards, including standard contractual clauses.

Apple supplies regular map imagery. The alternate aerial map uses Mapbox software and ČÚZK imagery. Requests disclose IP/map areas and technical information to these services. Mapbox also receives necessary SDK usage/accounting information when optional improvement telemetry is off. Optional location/usage telemetry starts off without a saved choice; change it in Help or map attribution. Mapbox acts as a controller for its own service purposes. Its policy describes international safeguards and generally 30-day IP retention, with security/legal exceptions. Mapbox, Apple Maps, ČÚZK.

Manual support uses the developer's consumer Gmail account. Encrypted operational database/Auth recovery copies can be stored in consumer Google Drive, with the unlocking password kept separately. Older manual phone copies in Desktop folders may also be managed by iCloud Drive; new preservation copies are kept in private local Application Support. These are separate from ordinary app sync. They are not covered by a claimed Google Workspace processor agreement. Google/Apple have their own service purposes and privacy terms. Google privacy, Google transfer safeguards, Apple privacy.

The hosted Auth service still has Brevo SMTP configured, although this beta hides email signup/reset/resend controls and uses manual help. If an administrative/security flow sends mail, Brevo and the recipient's mail provider receive the address, message/link and delivery data; provider tracking may apply. No tracking-free or short log-retention promise is made. Brevo documents indefinite default transactional log/preview retention unless changed. Brevo privacy, mail retention.

This notice site uses Cloudflare Pages. It contains no scripts, forms, analytics, remote fonts or tracking pixels. Hosting still processes IP addresses and request/technical information for delivery and security. Cloudflare's DPA and privacy policy distinguish customer processing from its own network purposes and describe international safeguards and purpose-based retention. Ask Patrik for applicable safeguards or further provider details.

Purposes and legal bases

Necessary account access, saving/restoring requested golf records and essential service support use GDPR Article 6(1)(b), for the individually agreed free beta service. Limited security, conflict recovery, fault investigation and related support use Article 6(1)(f): protecting private records and keeping the small beta usable. Access is limited to the developer; ordinary support avoids original recordings and unnecessary golf/location data. You may object. Handling mandatory rights/legal duties uses Article 6(1)(c). Optional improvement telemetry uses your choice/consent, which you can withdraw in Help without losing golf features. Eligibility, reading this notice and iPhone permissions are not blanket GDPR consent. No advertising or solely automated decision with legal or similarly significant effects is offered.

Retention and deletion

Active cloud records stay until you delete them or the account. Individual deletion removes record content but retains an account-scoped ID/type/version/time marker for sync; no scheduled marker purge runs. Account deletion removes its cloud record rows. Interrupted upload pieces become eligible for cleanup after seven days; actual cleanup needs a successful account sync, so this is not a seven-day erasure guarantee.

Account → Delete account removes Auth, profile and cloud golf records and this account's recordings on the deleting phone. Export first. Other offline installations, conflict copies, your exports and developer preservation copies need separate handling. Sign-out preserves private account-local files. Removing the app erases all its accounts' local data on that phone.

Support messages, private recovery copies and encrypted backups are retained only while needed to answer the request, verify recoverability or resolve a documented incident/legal need. Existing validation copies are currently preserved; there is no automatic purge or verified fixed maximum age. The developer reviews necessity after recovery validation, at case closure, on a deletion request and when the beta ends, removing copies no longer needed and recording any specific continued hold. Deleted accounts/records must be suppressed again before a backup restore is made available. Provider logs and recipient mail copies follow their own retention rules; app deletion does not instantly erase those systems.

Your rights

Edit your profile, export the phone's account archive or delete the account in the app. For access to cloud data, correction, erasure, restriction, portability where applicable, objection or withdrawing consent, contact Patrik. The local archive is not a complete server-side rights response. Reasonable identity checks protect your account. Requests are answered without undue delay, normally within one month; an eligible extension of up to two further months is explained during the first month. You can complain to the Czech Úřad pro ochranu osobních údajů. Material changes will be explained to beta users.