Your activities. Your choices.

Updated 24 September 2026. TempusMeter is developed by Mathieu Barnachon.

The native iPhone and iPad app remains on iOS. A native Android app is in development and is not publicly released. The Android-specific information below describes its planned services and permissions; implementation and release disclosures still require verification.

Activity recording and your account

TempusMeter stores activities and routes on your device. Recording may include GPS coordinates, timestamps, distance, movement and elapsed time, splits and activity type. iOS recordings can also retain available weather snapshots; Android recordings do not save weather. With an account and cloud sync enabled, your activity library is stored in Supabase and linked to your account ID. Account authentication uses your email address and password. On iOS, session credentials are stored in the device Keychain. Android account storage and cross-platform sync are being implemented and must be verified before release.

Apple Watch companion

The optional Apple Watch companion receives the paired iPhone’s current activity summary, route name, guidance text and off-route distance/direction through Apple WatchConnectivity. The system may retain the latest summary for delivery. The Watch does not receive route geometry, account credentials or your activity library, and does not independently record GPS or heart rate. Watch pause/resume controls affect only the current iPhone recording; they never publish an activity. No additional developer-server collection is introduced.

Community

Joining Community is optional. Recording or importing never publishes an activity. Your profile can include a username, display name, picture, bio and optional location. Community stores your published activity summaries, selected route coordinates, separate route publications, optional shared completion records, captions, pictures, follows, likes, comments, notifications, blocks and reports. These are linked to your account and used to provide Community features and moderation.

New profiles are private, require follower approval and do not appear in search until you choose to enable discovery. New posts default to Only me. Each post has its own audience: Only me, Followers or Public. Public posts on public profiles can be read without signing in through a shared web link. Public content may be copied by others, including people you have blocked. These privacy defaults also apply to the Android development work; adding a platform does not make publication automatic.

Pictures and locations

You choose pictures through the system photo picker. The app compresses selected pictures and removes original metadata before uploading. Pictures are compressed and stripped of original metadata before upload. A post's route map is optional; start/end privacy areas remove nearby coordinates. Review the remaining map because it can still reveal a location.

Publishing a separate route shares its name, type, distance and map without the source activity’s time, date or pictures. Route publishing defaults to 0 m hidden at the start and end: exact endpoints and revisits are visible to the selected audience. You must review and acknowledge the map, or choose larger privacy areas. Sharing a route result is a separate opt-in that shares your profile identity and elapsed time with the route audience and counts you as a participant.

Services and sharing

Supabase provides account, database and image storage services. Nearby Community route search sends the selected coordinates and radius to Supabase to find visible published starts; the app does not store this search as a profile location or activity. Around me reuses the last activity location without requesting a GPS update.

On iOS, Apple Maps, Apple place search and WeatherKit provide maps, place results and weather. These features send the query or location needed to serve their requests. Available iOS weather conditions and forecasts can be saved with your session for later viewing.

On Android, the planned Google Maps + Places integration sends map-area coordinates and place-search queries to Google to retrieve maps and places. Weather requests send location coordinates through TempusMeter’s authenticated backend proxy to the Google Weather API to retrieve live local conditions and forecasts. Android weather requires a signed-in account and a configured proxy, even without cloud-library sync. These requests are separate from publishing to Community. Google API keys, billing and live service activation remain pending verification.

Android weather is live-only: weather snapshots are not saved in recordings or synced activities. iOS saved session weather is unchanged. Under Google’s service-specific terms, section 21.2.1, cached current conditions and hourly forecasts must be deleted after at most one hour. Other weather fields have different limits; this is not a blanket 30-day cache allowance. The Android client and proxy must respect the applicable limits rather than keeping a permanent weather archive.

Google processes service requests under its own terms and privacy policy. Read Google’s privacy policy and Apple’s privacy policy for provider information. This page does not claim that an unreleased Android implementation has completed a privacy or legal compliance review.

Cloudflare hosts this website. The website does not load Google Maps, Places or Weather, request your location, or include advertising tracking. Shared activity previews request only the public post from Supabase. Account-confirmation returns remove URL credentials without storing them or passing them to the app. Manually exported files, shared activity cards and copies sent to other services are controlled by those recipients. Manual GPX, TCX and FIT transfer is available in the iOS app; automatic Strava connection is coming soon.

GPS, motion and Android recording notifications

On iOS, continuous GPS updates start only for a started activity or a motion-detected activity. Manual pause, saving and discarding stop updates. Auto-pause keeps GPS available to detect resumed movement. Motion & Fitness permission supports activity detection. Weather requests a one-time location at app launch or when you tap its refresh icon, with your permission, and sends that location to Apple Weather. These fixes do not start an activity. Around me reuses the last activity location without requesting GPS; if none exists, search for a place or start an activity. Recording maps use the recorder’s location rather than a separate GPS request.

Android is being built with location permission for recording and one-time weather requests, and activity recognition permission for optional motion detection. Ongoing recording uses a foreground location service with a visible recording notification, including when the app is not on screen. Android notification permission and operating-system limits may affect that experience. The intended lifecycle is the same: manual pause, save and discard stop continuous location updates; idle browsing does not repeatedly request GPS. One-time weather fixes go to Google Weather, do not start an activity and remain separate from the cached activity location used by Around me. These Android permission and lifecycle behaviors still require device verification before release.

Removing information

On iOS, You → Delete account & cloud data downloads your cloud activities and saved routes to this device before permanently deleting your account, cloud backups and Community content, including photos and published routes. Community content is not retained in your local activity library. Cloud syncing pauses during deletion, and interrupted cleanup can be retried. The service retains only an opaque hashed deletion receipt and completion time after deletion, without your account identifier. Keep your device and app, or export activities to retain another copy. Account deletion requires internet.

Automatic lap detection uses the existing recorded GPS trace on your device. Spoken announcements do not record your voice or use the microphone. Activity-map wind direction uses session weather. The Community routes map requests current Apple Weather for the center of the map you are viewing. This sends that map coordinate to Apple Weather without requesting your GPS location or publishing it to Community.

Delete a Community post to remove its social content, or use Delete social profile to remove your posts and social relationships. Your private activity library remains separate. Remove saved activities from their activity details. Removing an original recording does not remove a separately published Community post; delete that post separately. The same applies to separately published routes and shared route results. Remove a shared result from its Community route; deleting a route publication removes its social likes and records.

Deleted image metadata stops new access immediately. Physical image cleanup retries when you next use Community if a network or storage error delays it. Previously issued image links may remain usable for up to 60 seconds, and downloaded or externally shared copies cannot be recalled. Local drafts remain on your device so you can resume interrupted uploads.

Safety controls

Report a profile, post, route or comment from Community. Block an account from its profile and manage blocked accounts from your social profile. Read the Community guidelines for content rules and moderation.