Privacy Policy

What data can the application process

• The access account may include a verified email or the stable identifier provided by Google or Apple. Password credentials are hashed; GrupetApp does not receive your password from Google or Apple.
• The profile may include display name, cycling discipline, pace range, wheel settings and authorized Bluetooth sensor metadata. Readings are stored locally and may be sent in a FIT file if you enable a voluntary upload feature.
• During an active bike ride, the device can send location, capture time, speed, heading, accuracy and altitude when offered by the navigator.
• Groups, invitations, requests, blocks, content reports, route reports and SOS notices generate control and security data according to the action that the user chooses.
• For internal usage statistics, when you open the app with an account, the platform, the general type of device and, if available, the region configured in your language are recorded at most once a day. The region is approximate and may differ from the country where you are located. No model, device ID, additional IP address, or location are sent for this measurement.

How to share location

• Radar visibility is turned off outside of an active bike ride.
• Public Radar uses a degraded representation of distance and direction; It does not provide exact coordinates.
• The precise location is delivered to authorized members of the same temporary group bike ride or, in Solo mode, to people the rider has authorized to view that bike ride.
• At the end of the bike ride, the live presence is revoked and late updates should not reactivate it.

Purposes and suppliers

If you voluntarily connect your Strava account, GrupetApp sends FIT files from new rides to Strava when online. These files may include your precise GPS route and sensor data. The GrupetApp API forwards them without retaining the file; it stores encrypted authorization tokens and the status of each upload. Disconnecting Strava stops future uploads but does not delete activities already published in your Strava account.

The data is used to authenticate the account, operate the chosen bike ride, display the Radar according to the selected range, coordinate temporary groups, process security actions and maintain the session. Authentication can use Google, Apple or email. Resend processes verification and recovery emails. The API, PostgreSQL and Redis infrastructure is hosted on Railway. The map loads OpenFreeMap resources and OpenStreetMap data when used. Each provider processes only the data necessary to provide its part of the service under its own conditions.

A private administrative dashboard displays aggregated account numbers, bike rides, duration, and sensor preferences saved in profiles. Does not show sensor names or routes. Platform, device, and region data is associated with the account to count active users and is deleted when you delete the account.

In web browsers, the session is maintained with an HttpOnly and Secure cookie in production. This cookie contains the session credential, not coordinates. Location is processed separately during an active bike ride based on the permissions and controls you choose. In mobile apps, the credential is saved in the device's secure storage.

On the public pages of the site we use Google Analytics 4 to measure visits and general usage. Google may process technical navigation data, such as the page viewed, the browser and the device, using cookies or similar identifiers. This measurement is not uploaded to the app, invitations, or beta forms. Consult the Google privacy policy.

When a mobile release enables Google Analytics for Firebase, usage analytics starts automatically on Android and iOS unless you disable it. These analytics measure GrupetApp usage independently of iOS advertising tracking permission; Meta keeps that permission separately. We measure app opens, first-experience steps, authentication outcomes and ride starts/completions. Google processes its own installation identifiers and technical data, such as platform, version and approximate country. We do not send your account, email, name, coordinates, routes, groups, sensor readings or audio to these analytics. You can disable them in Profile → Privacy with “Do not allow analytics”. Previous decisions not to allow them are preserved. Disabling stops new events without automatically deleting those already sent, and does not change your Meta authorization.

Releases that enable Firebase Remote Config may request first-experience configuration even without Analytics consent. This service uses an installation identifier and technical data to assign an experience, and keeps local configuration when offline. It does not require access to location, microphone, Bluetooth or contacts. The demonstration uses sample data and does not start a ride or share your location.

FIT backup is optional. If you enable it in Account, existing and future FIT files on this device will be uploaded, including precise GPS routes and available sensor data. Files are encrypted before storage in a private Railway bucket and only your account can retrieve them. Disabling backup stops new uploads; you can delete cloud copies in Account. Deleting a copy or your account revokes access immediately; object deletion runs in the background, normally after one hour, with retries if Railway is unavailable. Local and downloaded copies remain.

GPX routes

In Solo, an imported GPX is stored on the device for that activity. In a group, its creator can share the GPX name and geometry with members: we store that private plan until it is replaced, removed or the group is deleted. It is a planned path, not a location history, and it is not sent to Meta.

Optional ad measurement on iOS

In iOS versions that include ad measurement, only if you allow tracking through Apple’s permission (ATT), the Meta SDK sends app activations, ride starts, installation information and technical device data, including the advertising identifier, to measure campaigns. Meta also receives the connection’s IP address. We do not send Meta emails, names, routes, coordinates, groups or sensor readings. You can decline permission and keep using the app, or revoke it in iOS Settings to stop new event submissions from this integration. Data already sent is governed by Meta’s policy. Meta privacy policy.

Conservation, revocation and deletion

Live GPS presence is ephemeral and uses Redis with TTL; The application does not intend to maintain a public history of exact coordinates. Group history stores control metadata, not public GPS samples. The user can turn off the Radar, end a bike ride, block or unblock users and delete the account from Profile. Deletion stops presence, revokes sessions, deletes the profile and associated data, and dissolves managed groups. If the account is linked to Apple, GrupetApp attempts to revoke the Apple token as well; If this is not possible, the app indicates that it must be revoked manually in the Apple ID settings.

Rights and contact

For support you can write to [email protected] without logging in.