Privacy Policy

PaceWise · Last updated 21 September 2026

Data we collect

Your paces, times, personal bests, races and profile are never collected. They stay on your device, or in your own iCloud account if you sync (see the next section). PaceWise has no accounts, and no servers that hold your data.

The one thing PaceWise can send is anonymous usage analytics: a count of which features get used, so we know what's worth improving. These events are not tied to you: no name, no account, no device or advertising identifier, no location, and never any value you type unless you choose to send it (below). Your times, paces and personal bests are never sent to us. We use Aptabase, an open-source, EU-hosted analytics service that is anonymous by design: it identifies each install only by a random id that rotates daily and cannot be traced back to you or linked across apps.

One exception is yours to make. On iPhone, if you describe a race and rate how it filled in the form as wrong, PaceWise offers Send this example. If you confirm, it sends the line you wrote, what the app read from it, and your region, units and today's date, through the same anonymous analytics. It is never sent automatically, and never while analytics is off. We use it only to improve how PaceWise reads a described race.

This is optional. You can turn it off, or confirm it's off, any time from the privacy screen in the app (on iPhone, your profile → Privacy; on Android, Settings → Privacy). If you were already using PaceWise before analytics existed, it starts off until you choose to turn it on; on a new install it starts on, and the first launch shows a one-time notice saying so, with a button to turn it off there and then. It is always off, with the toggle hidden, for anyone whose profile indicates they are under 13.

One thing we want to be straightforward about: turning analytics off records that you turned it off. A single anonymous event notes the switch moved and which screen you moved it from, sent while analytics is still on. It carries nothing about you. We count it because knowing how many people opt out, and where, is the only honest way to tell whether the default is one people are happy with. After that, nothing is sent. It is the last thing PaceWise sends until you turn analytics back on. Turning it back on records that too. If analytics is already off, or the under-13 lock applies, nothing is recorded either way.

Data stored on your device

The information you enter into PaceWise is stored on your device. Apart from the optional features under Features that go online, and any example you choose to send, it is not sent to us or to any third party. Deleting the app removes this data from your device.

On iPhone and iPad, iCloud sync keeps your races, results, distances, profile, fuel and carb-load plans and preferences the same on every device signed in to your Apple Account. It starts on for a new install and off after an update, and it uses your own iCloud account. The data goes to Apple, not to us, we cannot read it, and Apple handles it under its own privacy policy. Your profile photo and weekly distance stay on each device. Sync includes any saved parkrun IDs, including ones added for other people.

Turn sync on or off in Profile, Sync and backup. To delete the copy in iCloud, open Sync details there and choose Remove data from iCloud. Deleting the app does not remove it. Turn sync off on your other devices first, or they will send their copy back.

PaceWise can back up your data to a file when you ask it to. The backup is created on your device and saved wherever you choose (for example the Files app, or a cloud folder you control). It is never sent to us. Where it goes is up to you. On iPhone the backup includes any saved parkrun barcodes, including ones you have added for other people, so a new phone does not mean re-finding everyone's athlete ID. Worth knowing before you share the file.

Features that go online

PaceWise's core features work offline. On iPhone and iPad, iCloud sync (above) and two optional features go online to do their job. Each sends only what is described here.

Race location search. When you type in a race's location field, PaceWise sends what you have typed to Apple Maps so it can suggest matching places. This happens only while you type in that field. It goes to Apple, not to us, and Apple handles it under its own privacy policy. PaceWise never asks for your location. Offline, the field keeps whatever you type.

parkrun pass for Apple Wallet. Wallet only accepts a pass that has been signed. When you tap Add to Apple Wallet on a parkrun barcode, PaceWise sends that barcode's athlete ID and the name saved with it to a signing service we run on Cloudflare. The service builds the pass, sends it back, and keeps nothing. It has no storage, and it does not log the ID or the name.

Device permissions

PaceWise works offline and needs no permissions for its core features. A few optional features use device permissions; each is off until you use it, and everything they touch stays on your device. Add to Calendar on a dated race uses your device's calendar. If you choose to use it, PaceWise adds a single all-day event for your race to the calendar you pick, and may update or remove that same event when you change or delete the race. PaceWise reads your calendar only to find the event it created (so it can keep it in sync rather than adding duplicates); it does not read, store, or transmit any of your other calendar data. You can deny or revoke Calendar access at any time in your device's Settings (iOS or Android), and the rest of PaceWise keeps working. This all happens on your device. Nothing is sent to us.

On iPhone, some optional features use Apple Health. All of them are read-only. PaceWise never writes back to Health, and everything it reads is processed on your device. Nothing is sent to us. If you grant Health access, PaceWise reads your running workouts for two things: Import from Health on the Personal bests screen (finding your fastest 5K, 10K, half, and full marathon times and offering them as Personal bests; only the race times you choose to save are kept), and the Weekly distance view and its home-screen widget (your recent weekly running volume, refreshed when you use the app). By default PaceWise never reads Health in the background; if you turn on “Update widget in the background” (off unless you enable it), it also checks for new runs in the background so the widget stays current after a run. Separately, if you tap “Fill age & sex from Apple Health” in the athlete profile, PaceWise reads your date of birth and biological sex once, to set up age-graded times, never in the background, and it reads no other health data. You can deny or revoke Health access at any time in the iOS Settings or Health app, and the rest of PaceWise keeps working. On Android, the equivalent import reads from Health Connect. See the next section.

Two more optional features use device permissions in the same on-device way. A profile photo in the athlete editor can use your camera or photo library; the photo is stored only on your device, alongside the rest of your PaceWise data. And as described above, Add to Calendar touches only the race-day events PaceWise itself creates.

On iPhone and iPad, Describe the race in Add race fills in the form from one line you type or say. It is optional and marked Experimental. Apple Intelligence reads the line on your device. PaceWise does not store the line or use it to train any model, and you check the form before anything is saved. The microphone button uses your microphone only while you dictate, and your speech becomes text on your device. Nothing is recorded. The line leaves your device only if you choose Send this example, described above.

Health Connect (Android)

On Android, PaceWise can read your recorded running workouts from Health Connect, the on-device encrypted health store, to find your fastest recorded times. This is entirely optional and off until you ask for it.

What we read. With your permission, PaceWise reads your exercise sessions (running and treadmill runs) and their distance from Health Connect. It uses these only to identify your fastest recorded 5K, 10K, half marathon, and marathon, which you can then choose to save as Personal bests.

When we read it. Only when you tap Import from Health, or, if you have already granted permission, to show how many new results are available. PaceWise never reads your health data in the background.

What we never do. PaceWise never writes anything back to Health Connect, never sends your health data off your device, and never shares it with us or any third party. All of this happens on your phone. We keep only the personal-best entries you explicitly choose to save, stored locally on your device.

Your control. You can grant or revoke PaceWise's access to Health Connect at any time in Settings → Health Connect (or the Health Connect app). Revoking it hides the import feature; nothing else changes.

Third-party services

PaceWise integrates no advertising or cross-app tracking services, and nothing that profiles you. Its only analytics service is Aptabase, the anonymous usage analytics described above. It receives only anonymous feature-usage counts, and only while you leave analytics enabled, plus the single event that records you turning it off and any example you choose to send. Nothing else you enter is shared with it. The two features under Features that go online reach Apple Maps and a signing service hosted on Cloudflare, and send only what that section describes.

This website

Everything above describes the PaceWise app. This website, pacewise.doughworks.dev, counts page views using Cloudflare Web Analytics. It sets no cookies and stores nothing on your device, which is why you have not been asked to accept anything. It does not fingerprint your browser and cannot follow you to other sites. What it records is the page you viewed, the site you arrived from, your country, and your browser and device type. Never your IP address, and nothing that identifies you.

Children's privacy

PaceWise does not knowingly collect information from anyone, including children under 13. It collects nothing personal from anyone, and the optional usage analytics is off, with its toggle hidden, whenever a profile indicates the person is under 13.

Changes to this policy

If this policy changes, we will update this page and revise the date above.

Contact

Email support@doughworks.dev.