Privacy

Last updated 17 November 2026

Apprehension is played outdoors, so it has to know where you are. This page says what it does with that, and with everything else it touches. The short version: your runs stay on your handset unless you choose to send one, the app has no ads and no analytics service, and nothing is sold.

Who is responsible

Apprehension is published under the name Duskglade by Daniel Hollands, who is the data controller for the personal data described here. For anything on this page, email .

Apprehension is for adults

The game is for players aged 18 and over. We don’t knowingly collect data from anyone younger, and if you think a child has sent us something, email us and we’ll delete it.

Your location

The game needs your precise location while you play, including when the screen is off or the app is in the background, because the game carries on in your pocket. It only tracks you while a game is running; the rest of the time the app doesn’t ask for your position. Your handset asks your permission first, and you can change it in your handset’s settings at any time.

While you play, your run shows on your handset’s lock screen: the mode, your score, the clock and what you’re heading for, but never your position. Anyone holding your locked handset can see it. It’s drawn by your handset from what the app tells it, and it isn’t sent anywhere. Your final score stays for a few minutes after a run, then clears. You can turn it off in your handset’s settings: Live Activities on an iPhone, or the app’s notifications on Android.

Each run is recorded on your handset: your positions, alongside what the game was doing at the time. That record is what draws your run history and your route afterwards. It stays on your handset until you delete it, which you can do one run at a time or all at once, and uninstalling the app deletes every run.

A run only leaves your handset when you send it yourself:

  • Exporting a route. You can export a run as a GPX file and share it wherever you like, such as a fitness app. Once shared, it’s in the hands of whatever you shared it with.
  • Sharing a run’s log. You can share a run’s raw log the same way.
  • Answering the question at the end of a run (see below).

If your handset backs up app data to iCloud or Google, your runs can be included in that backup, held by Apple or Google under your account.

Routes you import

One mode, Pursuit, is played along a route of your own instead of a park. You choose a GPX file that’s already on your handset, and the app reads the route out of it: its points and its name, which you can change. Nothing else in the file is kept. The route is saved in the app’s own storage on your handset, and it’s never uploaded, published or offered to anybody else.

A run played on an imported route records the whole route in its log, alongside your positions, so the log can be drawn again later. It stays on your handset like any other run, and it goes wherever you send that run: an export you share, or the question at the end of a run. A route can start at your front door, so bear that in mind before you send one.

You can delete an imported route from the list of routes in the app. That removes the route itself; runs you’ve already played on it keep their own copy until you delete them, and uninstalling the app deletes both. Like your runs, routes can be included in an iCloud or Google backup of your handset.

A paired watch

If you play with a watch paired to your handset, the handset sends it your position and what the game is showing: the map’s markers, your score, the clock and, in Pursuit, your route. In one mode, Blind Search, the watch sends the direction its compass is pointing back to the handset. All of this stays between your own two devices, and the watch keeps none of it once the run is over.

An Apple Watch asks you for two permissions. It asks for Health so that the game can keep running with your wrist down, which Apple only allows during a workout; it saves nothing to Health and reads nothing from it. It asks for location for its compass, which turns the map to face the way you are.

The map

Map images are downloaded from a map provider while you play: MapTiler, or the OpenStreetMap Foundation’s servers. Like any web request, this tells the provider your IP address and roughly which area of the map you’re looking at. We don’t send them your position or anything else about you.

An Apple Watch draws its own map, with images from Apple instead, which sees the same two things.

Venue files

The app downloads venue files, the layouts of the parks it plays in, from venues.duskglade.co.uk, which is hosted on GitHub Pages. Like any web request, this tells the host your handset’s IP address, so it can send the file. Nothing else goes with the request: no account, position, device details or identifier. The same address also has pages you can open in a browser, a list of the parks and a map of each; those are covered under This website.

Crash reports and diagnostics

The app sends diagnostics to Sentry, a service that collects them for us, so we can find and fix what goes wrong: crash and error reports, how often the app is used and how quickly its screens load, and short notes of what it did, such as a run starting or finishing. They can include your handset’s model and operating system, the kind of connection it is on, the app’s version, which permissions it has, and the park, mode and score of your run. They never include your position, your name, your email or a screenshot.

Sentry stores this in its European Union data region, in Germany, keeps it for 30 days and doesn’t store your IP address. We send it because we have a legitimate interest in the app working.

Feedback you send us

There are two ways to send feedback from inside the app, and both go to Sentry in the same way as crash reports. Both are your choice each time; nothing is sent until you press Send.

  • The question at the end of a run. Answering sends what you type and that run’s log, which records where you played and the route you took, and for a run on a route you imported, the whole of that route. Skipping sends nothing.
  • The feedback form in the app. It sends what you write, plus your name and email if you choose to give them.

We use feedback to fix and improve the game, and delete it once it’s no longer needed for that; Sentry deletes it after 30 days in any case.

What the app doesn’t do

  • No ads, and no advertising or tracking code of any kind.
  • No analytics service. The diagnostics described above go to Sentry to keep the app working, and never include your position.
  • No accounts. You don’t sign in, so there’s nothing about you held on a server.
  • Nothing is sold. We don’t sell or rent any data, to anyone.

This website

This website, duskglade.co.uk, sets no cookies. It’s hosted by GitHub, as are the venue pages below, and GitHub records the IP address of every visit to keep the sites secure, as any web host does; see GitHub’s privacy statement. We don’t see or use those records.

To see which pages get read and how people find this site, we use Umami, an open-source analytics tool we host ourselves. When you visit a page, it records the page, the site that linked you here, your browser, operating system, device type, screen size and language, and your approximate location (country, region and city).

It sets no cookies and stores nothing on your device. Your IP address is used briefly to work out your approximate location and to group the pages you view into one visit, but it is never stored. Visits are grouped using a code that changes every month, so we can’t link your visits from one month to the next, or identify you from them.

We do this on the basis of our legitimate interest in understanding how the site is used. The data is held on our own server in London (Oracle Cloud, UK South). It isn’t shared with anyone, and it isn’t used for advertising. Encrypted backups are kept with Dropbox in the United States; that transfer is covered by the UK–US Data Bridge, under which Dropbox, Inc. is certified. The statistics are kept indefinitely, because they can’t be traced back to any individual.

You can stop this by blocking pythia.limeblast.co.uk/omen.js in your browser or with an ad blocker; the site works the same without it. Apart from that script, the site loads nothing from anyone else until you ask for one of its sign-up forms.

The venue pages at venues.duskglade.co.uk set no cookies either, and use the same Umami analytics, held and blocked the same way. Apart from that, the list of parks loads nothing from anyone else, but a park’s own page draws its map with two outside services as soon as it opens. The map library, Leaflet, comes from Cloudflare’s cdnjs, which sees your IP address. The map images come from MapTiler, the same provider the app uses, which sees your IP address and roughly which area of the map you’re looking at. See Cloudflare’s privacy policy and MapTiler’s.

A venue page can also remember, in your browser, which map layers you switched off. It never leaves your browser.

If you email us, we keep the email for as long as it’s needed to answer it.

If you sign up to hear when the beta opens, the form is run by EmailOctopus, a UK company that keeps the list in Ireland. It loads fonts from Google, and Google’s reCAPTCHA, which checks you aren’t a bot. None of it loads until you open the form; see EmailOctopus’s privacy policy and Google’s. We use your address for two emails, one when the beta opens and one at launch, and nothing else. Every email has a link to leave the list, or email us and we’ll take you off.

If you sign up to join the alpha, that form is run by EmailOctopus too, and loads the same things from Google when you press the button to open it. It asks for your first name, the email for your Apple ID or Google account, which handset you play on, and your local park and its town. We use it to set your park up in the game and to email you how to install it.

Once you’ve confirmed your address, your first name, handset and park are copied into a private to-do in our issue tracker, on GitHub, so we remember to set you up. Your email address isn’t. To send you the game, we give that address to Apple or Google, whichever your handset uses, so they can invite you to the test. They handle it under their own policies, Apple’s and Google’s.

When the alpha ends, your name and email move onto the beta list above, for its two emails, and the rest is deleted, the to-do included, and we remove you as a tester at Apple or Google. We keep a note of how the alpha went for each tester, under a number rather than your name, and once the to-do is gone nothing links that number back to you. Every email has a link to leave, or email us and we’ll take you off.

Your rights

Under UK data protection law you can ask for a copy of the personal data we hold about you, ask us to correct it, ask us to delete it, or object to how we use it. Most of what Apprehension holds is on your handset, where you can delete it yourself. For anything you’ve sent us, email us and say what you’d like; we’ll reply within a month.

If you’re unhappy with how we’ve handled your data, you can complain to the Information Commissioner’s Office at ico.org.uk.

Changes to this page

When what the app collects changes, this page changes first, and the date at the top says when it last did.