Privacy Policy
Information Incrementum processes
- Account information: Email address, authentication identifier, display name, and selected empire color. Passwords are handled by Supabase Auth and are not readable by the app developer.
- Activity summaries: Activity type (walk, run, or bike), start and end times, active and paused durations, total distance, eligible standard-distance record times, and territory/game outcomes.
- Derived location information: Identifiers for H3 map cells affected by an activity. These are not latitude/longitude coordinates or a route polyline, but they can indicate fine-grained areas visited.
- Shared game information: Display name, empire color, public player identifier, territory ownership, reinforcements, and defense values.
- Operational information: Service providers may process ordinary network metadata such as IP address, request time, device or client information, security cookies, and error logs to deliver, operate, and protect the service.
Information kept only on the device
While an activity is recording, accepted GPS samples are kept in a temporary private cache so the app can calculate distance, route geometry, territory effects, and records. The route remains local through the Save-or-Delete review. Saving submits or queues only the derived data described above, then deletes the raw route cache. Deleting the activity removes the raw route without submitting it.
A small route thumbnail may remain privately on the device for activity history. Pending derived submissions and privacy acknowledgments may also be stored locally.
How information is used
Information is used to create and secure accounts, restore sessions, calculate and display private progress, synchronize activities, operate the shared territory game, prevent duplicate submissions, provide account deletion, diagnose failures, and protect the service.
Incrementum does not use advertising SDKs, does not sell personal information, and does not track users across other companies' apps or websites.
Service providers
Incrementum uses Supabase for authentication, database storage, server functions, and related backend services. On iOS, standard maps are provided through Apple's mapping services. This website is delivered through Cloudflare infrastructure. These providers may process information under their own terms and privacy policies while supplying their services.
Retention and deletion
Server-side account, activity, record, and territory data is retained while the account exists. Hiding an activity from the Progress list does not reverse territory effects or delete a personal record earned by that activity.
The in-app Delete account and data control permanently deletes the authentication account and cascades through the profile, activity history, personal records, territory, and related game data. It also removes account-scoped queued activities, route thumbnails, and disclosure state from that device.
Raw route data remains only until the user saves or deletes the pending activity, subject to crash-recovery storage needed to preserve that decision.
Security and choices
Incrementum uses encrypted network connections, account-bound authorization, private database policies, and device-protected session storage. No system can guarantee absolute security.
Users can decline location permission, stop using the app, hide individual history entries, sign out on one device, or permanently delete the account in the Account screen.
Children
Incrementum is not directed to children under 13. A parent or guardian should not create an account for a child under 13 during this beta.
Changes and contact
This policy may be updated as the beta changes. The effective date above will be revised when material changes are made.
For privacy questions or support, see the Incrementum Support page.