Golfdar privacy policy

Your footage. Your choice.

Effective 5 October 2026 · Golfdar for iPhone, including the TestFlight beta.

The essentials

Ball recognition runs on your iPhone. Donating footage is optional, and its sole purpose is to train and validate Golfdar's golf-ball recognition model. We do not sell your personal data, use advertising trackers or upload microphone audio. Donated footage is deleted from our working storage after the training run using it has completed and been verified. You may request earlier deletion.

support@elyrion.nl · Golfdar support

1. Who is responsible

Elyrion Development is the developer and operator responsible for Golfdar's beta services. Contact support@elyrion.nl for support, privacy questions or requests concerning your data.

2. What stays on your phone

Core capture and ball recognition do not require an account. Camera access provides the live view, silent shot recordings and optional training images. Motion readings support camera orientation and stability. Optional microphone access processes impact sounds transiently; microphone audio is not saved or uploaded.

Shot records, recordings, settings and individual training samples stay in the app's storage unless you choose to share them. Golfdar does not request location, contacts or photo-library access. Device backups may include app files according to your Apple settings.

3. What you can choose to send

Shot uploads. A tester sign-in and an Upload action send shot metadata to the Golfdar evidence inbox. This can include club and ball details, notes, capture dates, device and camera information, motion samples and performance diagnostics. Include video also sends the silent shot movie. Uploaded material is linked to your tester identity. Tester records contain the name and email supplied for access; passwords are used to authenticate and stored as password hashes on the server.

Saved finds. Save finds for training keeps up to 30 seconds of sampled camera frames and saves them when you tap Found it. The images and search details can be sent to the paired Mac, directly on local Wi-Fi or through temporary storage on the Golfdar server. Phone and delivery identifiers let the system route the footage and confirm receipt.

Pairing and transfer are separate choices in the privacy update. Earlier beta builds enabled automatic transfer on pairing; turn automatic transfers off or disconnect if you do not want to send saved finds. Camera frames may show people or private surroundings, so avoid including them.

Buddy. Phones you approve exchange device names, an app-generated identifier, shot tracks and calibration information over an encrypted local connection. Buddy does not send video to the Golfdar server.

Manual sharing and support. The iOS share sheet sends selected files to a recipient you choose. Support and TestFlight feedback may contain your contact details, screenshots and diagnostic information you submit.

4. Why we use it, and who receives it

We collect donated footage solely to train and validate Golfdar's golf-ball recognition model, based on your consent. Real-world examples supplement existing training material with different grass, lighting, distances and camera views. Reviewing detection errors and checking model performance are part of that training purpose; we do not keep a separate footage archive for general app diagnostics or unrelated uses. This applies to donated search frames and optional uploaded shot videos.

Uploading does not automatically train or update the model: footage first needs human review and accurate labels, and model changes need testing. We do not use a predicted ball position as a verified training label.

Authentication, delivery and support information is used to provide the beta service. Limited operational information is also processed for our legitimate interest in security and reliability. We do not use the data for advertising or cross-app tracking.

Access is limited to the developer and the operator of the Mac you select, plus hosting and email providers where needed to operate the service. Apple separately operates TestFlight and its feedback services under Apple's privacy terms. A recipient you choose through the share sheet handles that copy under their own arrangements. Contact us for information about a recipient or any applicable international-transfer safeguards.

5. How long we keep it

Donated training footage: we keep it only while it is awaiting review and use in a training run. After that run has completed and been verified, the source footage and working image copies used by that run are deleted. Rejected or unusable footage is discarded rather than kept for unrelated use. You can withdraw consent and ask for deletion before training.

Remote delivery: the server's image archive is deleted as soon as the receiving Mac confirms safe receipt, often before any training. An incomplete transfer expires after 24 hours. A completed transfer waiting for an offline Mac remains pending until receipt, cancellation by the operator or a deletion request; it is not evidence that training has happened.

Records without footage: small delivery receipts and model-lineage records can remain to prevent duplicate uploads and account for a model version; these do not contain the images. Tester access, technical service information and support correspondence remain while needed to operate the beta, handle a request or meet a legal obligation. Donated shot videos follow the same training-and-deletion rule as donated search frames.

Deletion is from active storage, not a guarantee that a model forgets a particular example. Trained model parameters can remain after source files are removed. If a request also concerns a model or a restored backup, we assess that separately and explain the outcome; deleted footage must not be returned to active use through a restore.

6. Stop sharing and remove data

Disable training collection to stop saving new examples. Disable automatic transfers or disconnect the Mac to stop future search transfers; Stop transfer cancels an active one. In the privacy update, Cancel pending uploads or Sign out stops pending shot uploads. Data already received is not recalled by these controls.

Delete local samples in Capture settings or remove individual folders in Files → On My iPhone → Golfdar. Removing the app removes its local files; manage device backups separately in Apple's settings.

For copies received by Elyrion, email support@elyrion.nl with your tester email or relevant shot/find reference and approximate date. No password, pairing code or identity-document copy is needed in the initial request. We may ask for proportionate verification and coordinate removal from the receiving Mac and working training exports. If you selected somebody else's Mac, contact that operator too.

7. Your privacy rights

You may request access, correction, deletion, restriction and a portable copy where applicable, and object to processing based on legitimate interests. You can withdraw consent for optional training use without affecting earlier lawful processing or ordinary on-device use.

We respond to privacy requests within one month. If a permitted extension or exception applies, we explain it. You may complain to the Dutch Data Protection Authority or your local supervisory authority.

8. Changes

We update this page when Golfdar's data use changes, with a new effective date. Material changes to optional collection will be explained before asking for a new choice. Contact support@elyrion.nl if you need an earlier version or have a question.