DBL Mando

Privacy Policy

Last updated 2 October 2026

DBL Mando is a disc golf scorecard. It collects as little as it can get away with, and most of the time that is nothing at all.

The short version


What is stored on your phone

Rounds you score are written to your device first and kept there. This is what makes the app work on a course with no signal. Stored on the device are your rounds, the scores in them, the names of the people on your card, and the courses and layouts you have played.

This data is yours. It is not read by us, and deleting the app deletes it.

What is collected when you sign in

Signing in is optional and uses Sign in with Apple. If you choose to sign in, the following is stored on our servers:

From Apple

From you

The lock screen

While a round is in progress the app can show it on your lock screen: the course, the hole you are on, and the scores on your card. This is drawn on your phone by the app itself. Nothing about it is uploaded, and it disappears when the round ends. You can turn Live Activities off for DBL Mando in iOS Settings.

Notifications

Notifications are off until you turn them on. The app only asks after you tap Turn On next to an explanation of what they are for, never when it opens, and only while you are signed in.

Notifications are delivered by Apple Push Notification service. What they say is sent to Apple to deliver, and to nobody else.

Your location

Location is optional, and works like this:

One exception, and only one: the weather card. To show current conditions on the home screen, the app sends a rounded position — two decimal places, about a kilometre — to Apple Weather. That is deliberately too coarse to say where you are standing, and it is enough for a forecast. Apple states that it does not associate this with your Apple Account or device, does not store it, and does not link requests together. Nothing else about you is sent with it. If you never grant location access, no position is sent: the home screen offers to show conditions instead, or says they are off and how to turn them back on.

Coordinates attached to a course are a separate thing: they describe where that course is, not where you are, and they are set by searching for a place by name or address.

What is never collected

DBL Mando contains no advertising SDKs and no third-party analytics. Crash reports, described below, are the only diagnostics it sends, and they go to our own database. It is not used to track you, in the sense Apple's App Tracking Transparency means.

Course information in the app

DBL Mando ships with a list of real courses — names, towns, positions and hole counts — supplied by DiscGolfAPI, with coordinates for a handful of courses from OpenStreetMap. That list is bundled with the app and read on your phone. Browsing it, searching it, or adding a course from it sends nothing to anyone. Both sources are credited on the Courses tab.

Crash reports

When DBL Mando crashes, or freezes long enough that you would force-quit it, iOS records what happened. The next time you open the app — usually the following day, because that is how often iOS hands these over — the app sends that record to our database so the crash can be fixed.

A crash report contains the kind of crash, the call stack (a list of the functions the app was running), the app version, your iOS version, and your device model, such as iPhone16,1. It contains nothing about you, your rounds, your friends, or your location. Your account id is attached so a crash that only affects one person can be answered.

These reports are only sent while you are signed in. If you have never signed in, the app never sends one.

The records come from MetricKit, which is part of iOS. There is no crash-reporting SDK from another company in the app, and the reports go to our own database rather than to a third party. Deleting your account detaches your account id from any crash reports it sent; the technical details are kept, because at that point they describe the app and not you.

Who else handles this data

Nobody else. The data is not sold, rented, or shared with advertisers or data brokers.

What other people can see

Only what you choose to share:

You can remove a friend, block anyone, or report them, from your profile screen. Blocking is immediate: a blocked person cannot find you in search, cannot send you a request, and is not told that you blocked them. You can unblock from the same screen.

How long it is kept, and how to delete it

Data is kept until you delete it.

To delete your account, open DBL Mando, go to Profile and choose Delete Account. This is immediate and cannot be undone. It removes your profile, your handle, your friend connections, and every round synced to your account. It also tells Apple to disconnect your Apple ID from the app.

One thing worth knowing before you do it: rounds you hosted are deleted for everyone who played in them, because the round belongs to the card it was scored on. Rounds hosted by somebody else survive; only your entry in them is removed.

Rounds stored on your phone are separate and are not touched by account deletion. Deleting the app removes those.

Children

DBL Mando is not directed at children under 13, and we do not knowingly collect data from them.

Changes

If this policy changes in a way that affects what is collected or who it is shared with, the date at the top will change and the new version will be published here before the change takes effect.

Contact

Questions about this policy, or about data held about you: andrewjpar@gmail.com