Privacy Policy

There is no account, no sign-up, no analytics, no advertising and no tracking. Your position, your steps and the map you build up by playing stay on your phone.

The app sends us one kind of request: a download of street maps. To draw the streets around you, the app asks our map host for the map squares near you, and that request shows roughly which area you are in. See Street maps.

Used on your phone, and only while you are using the app. Wisp reads your position to work out where you are in the game’s invisible world, which is laid over the real places around you. It does not ask for background location, and it does not read your position while you are not using the app.

If you have allowed only approximate location, Wisp may ask for your precise position when you start a survey, and again when you return to Wisp during one, because approximate location can be kilometres off. Each yes lasts until you leave the app, and you can say no.

Wisp never sends your coordinates to us or to anyone else. The map squares it requests show your rough area, and that is the only information based on your position that Wisp sends anywhere. What the game remembers can also be included in your own iCloud or computer backups (see What stays on your phone). Wisp needs location to play. You can turn it off for Wisp in iOS Settings at any time.

Wisp counts your steps, which power the instrument, and reads how you are holding the phone and which way it is facing. All of this is read from your phone’s motion sensors and compass and used on the phone. None of it is sent anywhere.

The app keeps the following in its own storage on your phone, and never sends any of it to us:

• your map: where you have walked and the places you have surveyed and lit
• the area the game treats as your home region
• the state of the game’s world
• your settings

Your map and home region are a record of where you have played, and your map records it street by street. They are ordinary app data. If your iPhone backs up to iCloud or to a computer, the backup includes them. Your phone makes the backup, and it is stored in your iCloud account or on your computer, where we cannot get to it. Deleting Wisp removes this data from the phone but not from backups already made, and restoring one of those backups brings it back.

Wisp also writes short diagnostic messages to the iPhone’s system log. Wisp never sends the log anywhere, but it can leave the phone if you create and share a diagnostic report, for example with Apple Support, or connect your phone to a computer that reads it. In the versions we distribute, including TestFlight builds, any place or game cell named in a message is shown there as “<private>”, unless a special Apple logging profile has been installed on the phone.

The streets and water on Wisp’s chart come from map files we publish, built from OpenStreetMap. The world is divided into fixed squares a quarter of a degree on each side, about 28 km north to south and narrower east to west away from the equator. The app downloads the square you are in, together with the squares around it, from tiles.claphamdigital.com. In most of the world that is nine squares: yours and the eight around it. Far to the north or south, where the squares are narrower, the block can include more squares east to west. We currently publish maps for North America. Elsewhere the app still asks for the squares around you, and the host answers that they do not exist.

What a download reveals. Which squares the app needs depends only on which square you are in, not where you stand inside it, so the host never learns anything finer than your square. A request never names a street, an address or your coordinates. The app asks only for squares it does not already have, or ones due for their weekly check, so over time the requests show which areas you have played in, which way you moved between squares, when you came back, and when each request was made.

Squares already downloaded are kept on your phone, in storage iOS may clear to free space and does not back up, and deleting Wisp removes them. A download happens only for squares the phone does not have yet, and a copy more than a week old is checked for an update the next time the app needs it.

The request carries no account and no cookies. Besides the map square, it carries only what an ordinary download does: the app’s name (“Wisp”), your phone’s language setting, and your phone’s IP address, which the host needs in order to send the file back. The map files are hosted by Cloudflare, which describes how it handles this data in its privacy policy.

We have not turned on Cloudflare’s request logs for map downloads. Cloudflare’s security systems still record a sample of requests on their own. A sampled record may include your IP address and which map file was requested, and we can view these records in our Cloudflare account. We do not use them to identify anyone or to track where anyone plays. Cloudflare decides how long it keeps them.

The app itself sends us no account, identifier or coordinates. We have not turned on request logging for map downloads. The only records are the sampled security records Cloudflare keeps, which we can view in our Cloudflare account (see Street maps). We do hold what TestFlight shares if you test Wisp (see below), and any email you send us. Ask us and we will delete what we can.

Deleting Wisp deletes everything it stored in its own storage on your phone, including downloaded map squares. Diagnostic messages already in the system log are removed by iOS on its own schedule. Turning Location off for Wisp in iOS Settings stops the app reading your position.

Questions or deletion requests: hello@claphamdigital.com.

When Wisp opens, it checks with Apple’s Game Center whether you are signed in, so that Wisp can appear in Apple’s Games app, including to your Game Center friends. If you are not signed in, Wisp does not ask you to sign in. Wisp has no leaderboards, achievements or scores, and it does not send your Game Center identity to us. This exchange is between your phone and Apple and is covered by Apple’s privacy policy.

If you test Wisp through Apple’s TestFlight, Apple gives us:

• your device model and device identifier, iOS version and language
• how many times the build was installed and opened
• crash counts and crash logs
• your name and email address, if you were invited by email (not if you joined through a public link)
• any feedback and screenshots you choose to send, with details such as your carrier, time zone and battery level

Install, session and crash data is collected automatically by iOS and TestFlight, not by code in Wisp. Feedback and screenshots are sent only when you choose to send them. Wisp’s screen shows your real surroundings, so a feedback screenshot may show where you are.

We use this only to fix and improve Wisp, and we do not share it. Apple says it keeps beta feedback for one year. Apple describes all of this on TestFlight & Privacy.

• No account or sign-up with us
• No analytics or usage tracking
• No advertising SDK and no ad identifiers
• No crash-reporting SDK of its own
• No selling or sharing of data

This website, including this page, is a separate thing from the app: see how the website counts visits.

If the data practices described here change, this page changes with them and the date below is updated. This policy covers Wisp specifically; other Clapham Digital apps are covered by the general policy or by their own.

Questions: hello@claphamdigital.com.

Last updated: 16 September 2026