Privacy

Last updated: 2026-09-03

Blaze is a map app for iPhone. It carries maps you already have, it uses your location to draw you on them, and it collects nothing. This page says exactly when your location is used, exactly what is kept, and exactly what leaves the phone — which is nothing about where you have been.

Location: used, kept, and sent are three different things

Used — while you are looking at the map

Blaze reads your location to put the blue dot on the map and to keep the map pointed the way you are facing. Nothing about it is written down for that, and nothing about it goes anywhere.

Kept — only for a track you start

Start a recording and Blaze writes your positions to the phone, so you have the track afterwards. Waypoints you mark are saved the same way. This is the only circumstance in which your location is stored, it is stored on your phone, and stopping the recording stops it.

In the background — only while recording

Background location runs only while a recording is active, so a track keeps going with the phone in your pocket. It is switched on when you start the recording and off when you stop it.

Sent — never

There is no server that receives your position, your track, your waypoints, or a list of anywhere you have been. Not on a delay, not in summary, not anonymised. The app has nowhere to send it to.

The one way a track leaves: you export it

A recorded track can be exported as a GPX file. Where that file then goes is entirely your doing — AirDrop, a message, a folder in iCloud Drive, another app. Blaze does not send it anywhere on its own and does not keep a copy anywhere but your phone.

What the app asks the network for

Two things, and neither one says anything about you. The basemap: a manifest of which tiles exist and where, and then the tiles themselves. And the catalogue that lists where free maps can be downloaded from — if you download one, it comes from whoever publishes it, a government mapping agency say, rather than from us.

Asking a server for a map or a tile is an ordinary web request, and that is worth being plain about: the server on the other end sees the request and the address it came from, the way it does for every website you visit. That is the honest limit of "sends nothing" — what it never contains is your location, your track, your waypoints, or any identifier belonging to you or your phone. Everything you have already downloaded is read off the phone with no request at all.

What is not collected

There is no account and no sign-in. There is no device registration and no token identifying your phone. There is no analytics SDK, no advertising identifier, no crash reporter that leaves the device, and no third-party tracker of any kind. Blaze does not ask for your name or your email, and does not have a way to store them if you offered.

Because none of that exists, there is no data of yours held anywhere to request, correct, or delete. Deleting a track or a map on the phone is the whole of it.

What stays on your phone

• Maps you imported — Blaze's own copy of each
• Basemap tiles the app has already fetched
• Tracks you recorded, and waypoints you marked
• Your settings

Deleting the app removes what it holds. A map file you also keep elsewhere — in Files, or on a computer — is untouched, because Blaze took its own copy on import and never writes to the original.

What the earlier version did

Blaze began as a trail-conditions app. That version sent hazard reports, the list of trail stretches a recorded walk covered, and held a random token in the keychain so an anonymous device could be rate-limited. It also had an off-by-default setting that uploaded raw recorded walks.

All of it is gone: the reports, the uploads, the token, and the service that received them. Nothing has replaced them, and this page describes what is left. The app's privacy manifest now declares no collected data types at all, and the App Store privacy label says the same — three statements of one truth, and if they ever disagree, that is a bug worth reporting.

Children

Blaze is not directed at children and collects nothing that would identify anyone, of any age.

Changes

If this ever changes materially, the date at the top changes and the app says so before anything new is sent. This page and the app's own wording are kept in step deliberately — if they ever disagree, the app is wrong and that is a bug worth reporting.

Contact

See Support.