Beta

Privacy

Updated 14 November 2026

Varg GPS privacy notice

Version privacy-v1. Data notice data-v1.

Operator and contact

Varg GPS is operated as an independent personal project. In this notice, “we” means the operator of Varg GPS. For support, personal-information requests or privacy concerns, email varggps-support@googlegroups.com. The official website is https://varggps.pages.dev.

Starting and riding offline

Accepting the app agreement and signing in with Google are required before first use. After activation and riding setup, local maps, navigation, recording and settings work offline. Download maps before losing signal. Expiry of an online session does not remove successful offline activation. Friends sharing needs a connection. Help, Agreement, Privacy and update/install recovery remain available before activation.

Maps, saved places and tracks stay on your device unless you choose to share, export or back them up. Sign-in does not create cloud backup or sync.

Accounts and purposes

Google verifies your sign-in. The phone sends Google proof to the Varg GPS account service for verification. Google may select a previously authorised account or show its chooser or consent screen. Varg GPS does not ask for your Google password or access Gmail or contacts.

The Varg GPS server keeps Google's account identifier, a separate internal account number, account creation and latest activity information, session expiry/revocation information, and hashes of Varg GPS session credentials. It does not save your Google email, name, avatar, password or Google sign-in token. Google proof can contain additional claims during verification; we do not retain those unnecessary claims. On the phone, account credentials and activation are protected using Android's secure storage and excluded from app backup.

We also keep the accepted agreement, privacy and data-notice versions and acceptance time against your account. The acceptance record has no internet address, location or token. These account and acceptance records are personal information.

We use account information to provide and manage account activation, sign-in, session recovery and deletion under the agreement. We keep acceptance records to record the agreement. Limited security and improvement processing serves our interests in protecting the service, finding failures and deciding which app features need work. We limit it as described below. Accepting the agreement does not turn required reporting into separate, freely optional consent, and Google's sign-in consent does not replace this notice. Applicable personal-information rights remain available through the contact above.

Limited improvement reports

When reporting is enabled, the phone combines feature counts, selected display settings, app versions, update outcomes and limited safe crash counts before sending them. Reporting may be disabled in a development or test build. Acceptance alone does not turn disabled collection on. There is no separate reporting onboarding or toggle screen.

Reports contain no account/session/Google, installation, daily phone or advertising identifier, email, name, search word, destination, track name, invite code, rider name or location. They are sent without account authorisation or cookies. A random reference identifies one message and its retries only; the server stores its hash and source day to prevent double counting. That reference does not connect different messages or an account.

The service adds fixed counters directly to combined tables. It keeps no raw report history or individual reporting profile. Counts and settings/version shares describe submitted contributions, not unique people or all riders. Separately, account operations produce combined sign-in, new-account and online-active-account counts. Online activity uses the account's latest active day without an account activity-history table. Offline riding is absent from these counts.

Crash reports cover safely captured Java failures only, with build, a fixed app-code category and a count. They do not include crash messages, full stacks, paths, logs, screenshots or location. Native crashes and other failure types are not covered. Reports you manually choose to share are separate and may contain more information.

This release collects no area reports, analytics tracks or account-linked ride locations. Friends positions are handled separately below. The app does not include a third-party advertising or analytics SDK, sell reports, or add public website analytics. Network transport and provider processing are not a guarantee of legal anonymity.

Retention and cleanup

Local usage/crash reports stop being eligible to send at midnight UTC after the day following collection, within 48 hours. The server accepts the current and previous UTC source day only. The message-reference deadline is the same. Older reports are discarded rather than backfilled. Expired files are removed when the app next runs cleanup; an app that is not running cannot erase its files.

Combined non-location improvement and account-operation totals cover up to 90 UTC days. Accounts and acceptance records expire after 12 months without account activity, or are removed on successful deletion. Offline riding and improvement reports do not extend the server account clock.

Online access credentials last 15 minutes. Refresh sessions expire after 30 days idle and at most 90 days overall. Used refresh hashes remain only while the same session family is live, to detect reuse; expiry or revocation removes that family's records through scheduled cleanup. These server limits do not periodically expire local riding activation. Sign-in challenges last five minutes.

Combined administrator access/security records expire within 30 days. Day-only account-request security counters are cleared after UTC rollover. Day-only report-budget counters retain the current and previous UTC day, up to 48 hours. These bounded counters contain no person or account reference. Server removal uses scheduled cleanup, normally hourly; service endpoints close if cleanup health becomes stale. Expiry is not a claim that a failed cleanup job deletes data while it is broken.

Successful account deletion and inactivity cleanup retain an internal account-number-only deletion record for eight days, without Google's identifier or an analytics link, to prevent deleted accounts returning after recovery. Cloudflare's configured Free database recovery history can retain deleted database data for up to seven additional days. We do not make extra exported database backups. Recovery must preserve deletions before service resumes.

Sign-out and account deletion

Sign-out immediately disables this phone's activation and clears waiting improvement reports. It leaves maps and tracks. Protected credentials may remain solely to finish remote sign-out, including the existing encrypted account record until safe handover. Remote revocation is not immediate when offline. Retry eligibility ends 24 hours after sign-out; expired recovery data is removed when the app next runs cleanup.

Delete account in Account while connected. Deletion requires explicit confirmation and fresh verification of the same Google account; Google need not ask for a password. Successful deletion removes active account, session and acceptance records. This phone clears activation and waiting reports. It does not delete your Google account, maps, tracks, exported files, independent providers' copies, or stop Friends sharing. Stop sharing separately. Remote account changes are learned only when connected.

Signing out, deleting the account on this phone, clearing storage or installing afresh requires online Google sign-in before use again.

Data and permissions

Precise location shows where you are. A recording also saves the path and the times. Friends asks for location only when you tap Start new group or Join and share, after a short reason, and uses it only while sharing is on. You can see that from the Sharing chip on the map and, if you allow notifications, from the notification with Stop. The notification is optional. VargGPS does not ask to use location while the app is closed.

Picture-in-picture keeps the map in a small window over your dashboard. That is Android's name for the small window.

Display over other apps is optional. It shows the Varg App button on top of Google Maps, Waze, or Strava, so you can get back to the bike screen.

Usage access is optional. It shows the right button for the app in front. During a ride, VargGPS only checks which app is open. It does not read the screen or save a history of your apps.

VargGPS Auto-enlarge is a separate, optional helper. Its Accessibility switch lets it check that Google's window is the small map, then send one double-tap after you ask. Accessibility is a strong permission: it can see windows and tap for you. This helper does not read map text, does not take screenshots, and does not use the internet.

Ride with friends

Sharing is off until you tap Start new group or Join and share. It runs only while it is on. The Sharing chip shows that. If you allow notifications, a notification with Stop shows it too. It stops when you tap Stop, or after 4 hours. You choose the name friends see. Friends does not use your Google identity or phone number.

Your position, the time, whether you are moving, and your name are locked on your phone with the invite code. Locked means only someone with that code can read them. Anyone you give the code or the square code to can see you until you stop.

A pass-through service hosted by Cloudflare receives only that locked data, a random group and member identifier, a random key your phone makes to protect your spot in the group, and request information such as your internet address. It stores only a scrambled copy of that key, so only your phone can change or remove your spot. To slow down misuse, it counts requests per group and per internet address, one minute at a time. It keeps only each person's latest update in memory. It removes that update within 15 minutes, or as soon as you stop. It keeps no history. A group can have at most 10 people. Friends' positions are shown on your map only. They are not saved as places or tracks, and they disappear when sharing ends.

After you start or join a group, this phone saves the invite code, a group name you can edit, your display name, and when you last used it. That list stays on the phone. It is not uploaded. Remove from this phone deletes the code stored here.

To turn a permission off, open Android Settings, then Apps, then VargGPS. To remove the helper, turn off VargGPS Auto-enlarge under Accessibility, or uninstall the helper. You can still double-tap the small map yourself.

Providers, downloads and sharing

Cloudflare hosts the website, account service and Friends relay. Google handles sign-in and GitHub hosts downloads. Providers receive network requests, such as internet addresses, device/browser information and requested URLs. Varg GPS does not add these details to improvement totals. Processing and provider recovery may occur outside your country; no particular hosting country is promised. The private totals dashboard requires separate administrator authentication; a rider account does not grant access. It has no rider profiles, individual tracks, person filter or account-location view. The public website adds no application cookies or advertising trackers; private administration uses necessary access cookies.

CoMaps and community map servers receive your IP address and the map files you request. Google Maps, Waze, and Strava run separately. VargGPS only opens Strava's record screen. It never starts a recording, reads Strava data, or sends your position to Strava. Strava receives only what you do inside Strava. Optional OpenStreetMap editing sends account authorisation and edits to OpenStreetMap.

Provider policies: Cloudflare https://www.cloudflare.com/privacypolicy/; Google https://policies.google.com/privacy; GitHub https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement; Waze https://www.waze.com/legal/privacy; Strava https://www.strava.com/legal/privacy; OpenStreetMap https://osmfoundation.org/wiki/Privacy_Policy. Stark, VargPilot and other independent apps handle their own processing under their policies.

Track exports and diagnostic reports go to the apps or people you select. Reports can include device, file, or location details. Review attachments and recipients before sharing. Inherited feedback links may still address CoMaps, which does not operate VargGPS.

Backup, local deletion and your requests

Android may back up saved bookmarks and settings according to your device configuration. Friends invite codes are not in that backup, because it only includes bookmarks and settings. Delete items in the app, or clear its storage to remove local data. Exported files and provider backups must be deleted separately. Saved places, maps and tracks remain until you remove them. Third-party retention follows the provider's policy.

Email varggps-support@googlegroups.com to request a copy/export of your personal account information, deletion or correction, or to raise a privacy concern or objection. We may need to verify account ownership. Do not email passwords, sign-in tokens or invite codes. Requests are handled manually; there is no automatic export service. Your message and any information you choose to include are also processed by the email service used to deliver and answer it.

Combined totals have no person-to-contribution lookup. This does not remove rights that apply to identifiable information. You may exercise applicable access, correction, deletion, restriction, portability, objection and complaint rights, including contacting the relevant data-protection authority where available. This notice does not waive legal rights or claim universal legal compliance.

Website-specific administrator cookies

The public website adds no visitor tracking. Private administration uses direct Google sign-in in the browser, restricted to the owner's approved Google account. A necessary session cookie lasts 30 minutes, is scoped to private administration and is HttpOnly, so page scripts cannot read it. These cookies are for private administrator access, not public visitor tracking.

First sign-in summary

Before your first ride

Sign in once with Google. After setup, you can ride offline. When enabled, Varg GPS sends combined feature, settings, version, update and limited crash counts to improve the app. Reports have no account or phone identifier. It does not send tracks or link ride locations to your account. Area reporting is unavailable. Set up while parked.

I accept the agreement and data notice.

Read the full agreement.

Varg GPS agreement

Version terms-v1. Data notice data-v1. Privacy notice privacy-v1.

About Varg GPS

Varg GPS is an independent personal project providing riding maps and navigation. In this agreement, “we” means the operator of Varg GPS. Contact us at varggps-support@googlegroups.com. The official website is https://varggps.pages.dev.

Set up the app while parked. Maps, routes, positioning, downloads and app switching can fail. Follow signs, local rules and the conditions in front of you. A suggested route gives no right to enter private land or closed trails. Do not operate the phone while riding or rely on Varg GPS for emergencies. Keep dashboard warnings visible and back up important tracks.

First sign-in and offline riding

Before first use, accept this agreement and sign in with Google while connected. Google services must be available on the device. Google may select a previously authorised account or show an account chooser or consent screen. Varg GPS does not ask for your Google password or access Gmail or contacts. Agreement, Privacy, Help and update/install recovery are available before activation.

After successful activation and riding setup, local maps, navigation, recording and settings work offline. Download your riding regions before losing signal. An expired online session does not remove activation or stop an ongoing ride. Friends sharing needs a connection. Sign-in does not back up your maps, tracks or settings.

Signing out, deleting your account on this phone, clearing app storage or installing afresh requires online sign-in before use again. Sign-out immediately disables this phone's activation and clears waiting improvement reports. Maps and tracks remain. Protected credentials may remain only to finish remote sign-out, including the existing encrypted account record until it can be handed over safely. Retry eligibility ends after 24 hours; expired recovery data is removed when the app next runs cleanup. Remote changes can be learned only while connected.

Account information

We keep Google's account identifier, a separate internal account number, creation and latest activity information, and protected session records. We do not save your Google email, name, avatar, password or Google sign-in token on the Varg GPS server. We record the agreement and privacy/data-notice versions you accepted and the acceptance time against your account. These account and acceptance records are personal information. Acceptance records contain no location, internet address or sign-in token.

Improvement reporting

This agreement includes the following limited reporting when reporting is enabled. A development or test build may have reporting disabled. Accepting the agreement does not itself enable disabled reporting. There is no separate reporting choice screen.

The phone combines feature counts, selected display settings, app versions, update outcomes and limited crash counts before sending them. These reports contain no account, session, Google, installation, daily phone or advertising identifier. They contain no search words, destinations, track names, friends' names, invite codes or locations. A random reference belongs to one message and its retries only. Reports are sent without account credentials.

The service adds those counters to combined totals and does not keep a raw report history or individual activity profile. Usage contributions do not count unique riders or phones. Account sign-ins and accounts active online are counted separately; offline riding is absent from those account counts.

Crash reports cover safely captured Java failures only. They contain the build, a fixed app-code category and a count, without crash messages, logs, screenshots, file paths or location. Coverage is incomplete. This release does not collect area reports, analytics tracks or account-linked ride locations.

Friends and other services

Friends sharing is separate from your Google identity. Your phone locks your sharing name, position, time and movement status with the invite code. Anyone with that code can read shared updates. The Cloudflare relay holds only the latest locked updates, removes them within 15 minutes or when you stop, and keeps no track history. Sharing stops when you stop it or after four hours. Stop sharing separately when needed. See Privacy for permissions, saved groups and relay request handling.

Cloudflare hosts the service, Google handles sign-in and GitHub hosts downloads. These providers process network information, such as internet addresses and requested URLs. Sending a report over the internet is not anonymous transport. We do not attach network details to improvement totals, sell reports or send them to advertising services.

Maps and other apps have their own providers, terms and privacy policies. CoMaps, map contributors and included software retain their licences and attribution. Varg GPS is not affiliated with Google, Stark or the other named services. Exported files and independent services remain outside our deletion controls.

Retention, deletion and requests

Local improvement reports stop being eligible to send at midnight UTC after the day following collection, within 48 hours. Expired local data is removed when the app next runs cleanup. Server message references have the same deadline. Combined improvement and account-operation totals are kept for up to 90 days, with scheduled cleanup.

Accounts and acceptance records are removed on successful account deletion or after 12 months without account activity. Offline riding and improvement reports do not extend that account clock. Session credentials have separate limits described in Privacy; they do not periodically expire offline activation.

Delete account in Account while connected, confirm the deletion and verify the same Google account again. Google may not ask for a password. Successful deletion removes active account, session and acceptance records and clears this phone's activation and waiting reports. It does not delete your Google account, local maps or tracks, stop Friends sharing, or remove independent copies. An internal account-number-only deletion record is kept for eight days to protect against restoring deleted accounts. Cloudflare's configured Free database recovery history can retain deleted database data for up to seven further days.

Email varggps-support@googlegroups.com to request a copy of your personal account information, account deletion, a correction, or to raise a privacy concern or objection. We may need to verify that the account is yours. Do not send passwords, sign-in tokens or invite codes. There is no automatic export service. Combined totals have no person-to-contribution lookup. Rights available under applicable law, including complaint rights, remain available.

Fair terms

Varg GPS is provided as available, to the extent permitted by law. Nothing here excludes rights or liability that the law does not allow us to exclude. We will give clear notice of material changes. Your acceptance covers this agreement and its data notice; it is not described as separate, optional consent to required reporting. The Privacy notice explains the purposes, limits and request route.