Privacy Policy

This Privacy Policy explains how Panaride collects, uses, stores and shares information when you use the Panaride cycling app, public profile and share pages, account deletion pages, and related backend services.

Information We Collect

The exact data depends on the features you use. Panaride may process:

• account and profile information, including your sign-in identifier, email address, display name, username, avatar, language, region and profile visibility settings;
• ride and location data, including precise GPS points, route geometry, speed, altitude, accuracy, timestamps, start and finish coordinates (from which our server names the nearest town or village using the GeoNames gazetteer, without storing the name);
• health and fitness data when you choose to connect health features, including workouts, distance, speed, elevation, calories, heart-rate values, heart-rate zones, workout routes and device/source metadata;
• Bluetooth sensor data when you connect a heart-rate monitor or similar cycling sensor during a ride;
• photos, avatars, trip images, route photos, GPX files and other content you upload or generate in the app;
• device, diagnostics and usage data, including device identifiers, Firebase installation identifiers, FCM tokens, app version, operating system, crash logs, performance data, screen views and product events;
• public sharing data, including share tokens, public profile data, public trip/route pages, view counters and abuse-prevention signals such as IP address and User-Agent;
• social features data, including follows and follow requests, the audience you choose for each ride, likes, comments and comment photos, reports and blocks.

Sources of Personal Information

We collect personal information from the following sources:

• Directly from you — for example your email address when you sign in with a one-time email code, and information you provide when you create an account, edit your profile, upload photos or GPX files, or contact support;
• Automatically from your device and sensors — for example precise GPS location, motion/barometer-derived altitude inputs, Bluetooth heart-rate sensor readings, device identifiers, app version and diagnostics while you use the app;
• From your sign-in providers — when you use Sign in with Apple or Google sign-in, we receive the account identifier and, where you allow it, your email address and name;
• Generated by your use of the app — for example ride metrics, calculated statistics, achievements, share tokens, view counters and product usage events.

Location and Background Recording

With your permission, Panaride uses your location while you view map screens to show your position and help you plan a route. Opening a map does not start recording a ride. On Android, an in-app disclosure explains foreground and background location use before the system location permission request.

Panaride is a cycling ride recorder. When you explicitly start a ride, the app may collect precise location in the foreground and in the background so the route, distance, speed, elevation, GPX export and ride history remain accurate while the phone is locked, minimized or in your pocket. You can stop recording in the app and can change location permissions in your device settings. During route guidance the app may send your current location and direction of travel to our routing provider (GraphHopper, Germany) to build a path, also with the screen off. Location is not used for advertising.

Health, Fitness and Sensors

Health integrations are optional. If you connect Apple Health, Google Health Connect or a Bluetooth heart-rate sensor, Panaride uses the permitted data only for cycling, fitness, import/export, statistics and related app functionality. Health and fitness data is not used for advertising and is not sold to data brokers. You can disconnect health integrations in the app or in system settings.

How We Use Information

• to create and maintain your account and sync your ride history;
• to record rides, calculate metrics, show maps, import/export workouts and create GPX files;
• to provide public profile, follows, feed, comments, and trip and route sharing when you choose to use those features;
• to make the elevations of routes more accurate from the barometer heights of road sections in the rides of riders who keep that setting on (see “Road Elevations from Rides”);
• to send service notifications and push notifications where permitted;
• to protect the service from abuse, debug issues, improve performance and understand feature usage;
• to comply with legal obligations and process account deletion requests.

No Ads and No Sale of Personal Information

Panaride does not show ads and does not use an advertising SDK. We do not sell your personal information, and we do not share it for cross-context behavioral advertising. Your location, health and fitness data is never sold to data brokers or used to build advertising profiles.

Public Sharing and Social Features

Your profile has two visibility levels, chosen in the app settings: Everyone and Followers (the default; “Link only” in earlier app versions). Statistics visibility is a separate setting. With Everyone, anyone can open your profile and find it by username, and your web profile page (/u/{username}) opens without signing in and may be indexed by search engines; people follow you at once or after your approval, depending on “Confirm followers manually”.

With Followers, on your profile page people who do not follow you — in the app, by link, by QR code or by exact username — see only your display name, username, profile photo and a Follow button; every new follow request needs your approval. This setting does not hide your Everyone rides, comments or reactions, or data you have separately made available through a sharing link. The web page shows only your display name, username and photo; we mark it as not intended for search-engine indexing, which does not guarantee immediate removal of information previously stored by search engines.

Your current followers can access your profile content, subject to your other visibility settings. Existing follows are kept, including follows accepted automatically under earlier settings; they do not require approval again. The “Private” level of earlier app versions no longer exists since October 25, 2026: such profiles were moved to Followers, and people can now send them a follow request.

The transition takes place on October 25, 2026 while the servers are updated (a few minutes). During that time the previous rules may still apply to profiles formerly set to Link only: the profile is shown in full, and follows of owners who accepted followers without approval are accepted at once. In earlier app versions, exact-username search for Followers profiles does not work, and information already loaded on screen may stay until the screen is refreshed or closed.

A profile open to a viewer can show your username, display name, avatar and game-status badge, join date, aggregate statistics, achievements, game statuses, the bikes you choose to show, routes you publish, daily distances for the last 12 weeks in the app and 28 days on the web profile, the rides open to that viewer, and lists of your followers and of the people you follow (to everyone who can open the profile if it is set to Everyone without manual approval; otherwise to you and your followers).

You choose the audience of each ride in the app's social features: Only me, Followers or Everyone. Your followers see your Followers rides. Everyone rides are shown to every app user in the All and Nearby feeds, with your display name and photo, at any profile level. Link sharing is a separate setting: if it is enabled, anyone with the link can open the ride data available on its web page, including the track and metrics, even when the ride's audience is Only me or Followers; changing the audience does not by itself disable the link.

A post shows the ride with your hiding settings applied: the track with enabled privacy zones applied and, if start and finish hiding is on, with the start and finish hidden (it is on by default, but you can turn it off for a ride; then those parts of the track may be visible), ride metrics, your caption, photos and videos, and your bike if you have enabled its display. The ride card and the sections opened from it may also show the ride's date and time, the town of its start (to other people only a town of at least 10,000 inhabitants, and nothing if the start is inside your privacy zone), distance from the viewer, and achievements and game-status promotions earned on that ride; this information follows the ride's audience regardless of access to the profile. Your bike's mileage and ride count, the “New roads” label (kilometres new to you) and the badge of your current game status next to your name are shown only to people your profile is open to (mileage and “New roads” only if your statistics are not hidden); the badge restriction applies to your current status, not to awards earned on the ride shown. Your display name and photo also appear next to your comments and likes. If your profile is set to Everyone and “Show me in “Riding near you”” is on, people riding nearby may see you, with the distance and the number of your public rides in the last 30 days.

If you make a trip or route visible by link or publicly, people with the link may see the information shown on that page, including your display name, username, cycling metrics, route geometry, photos and view count. Panaride supports privacy settings and start/finish hiding for shared rides, but you should share only content you are comfortable making visible to others.

Road Elevations from Rides

To make the elevation gain on routes in Panaride more accurate, we use the height of the road measured by the barometer in riders’ phones during rides recorded in the app. These heights are used only for routes: they do not change your own rides or their numbers.

What we take. From your rides recorded in the app where the phone measured air pressure — including rides that only you can see — only the height of individual road sections: a small map cell (about 20 × 20 metres), one of four travel directions, and the height above sea level in that cell. To calculate it we read the ride’s track file (GPX), which we already store. Rides imported from other apps or files, rides without a barometer and rides shorter than 3 km do not take part.

What we do not take and what others cannot see. The calculation does not include:

• your name, username, photo or any other information about you;
• the time and date of the ride, speed, heart rate, power or other metrics;
• the first and last sections of every ride (at least 200 metres from the start and the finish), the places where you usually start and finish rides, places you visit often, and your privacy zones — that is, the surroundings of your home;
• sections with a poor GPS signal, pauses and gaps in the recording, and sections ridden too fast for a bicycle.

Other users are not shown your ride, its route or the fact that you take part at all. What they see is only the resulting road heights inside a route — in the route’s elevation chart and elevation gain, with a note for the route as a whole that its heights were refined from riders’ rides — with no link to any person.

At least two riders, and three for saved routes. The height of a road section enters a route only if at least two different riders rode that section and their measurements agree. When a route is being built for you at that moment, your own rides are not counted: at least two other riders are needed. For routes that we save and that other people may open (your saved routes, public routes and links to them) we take only sections where at least three different riders rode, not counting the owner of the route. Your single measurement does not appear in a route on its own.

How it is stored. For each cell we store the height and a link to your ride, and through it to your account. This link is used only to count different riders, to leave your own rides out of routes built for you, and to remove the contribution when the ride is deleted, the setting is switched off or the account is deleted. It is not passed on to other users or third parties and is not used for anything else. A contribution is kept while the ride exists, the setting is on and the account is active.

How to switch it on and off. The “Improve road elevations from my rides” setting is under Settings → Privacy. It is on by default. If you switch it off, we stop using your rides and the cells already contributed are deleted: they stop taking part in new calculations at once and are fully deleted within a day. If you switch it on again, your rides are taken into account again.

Deletion. The contribution of a ride is deleted together with the ride. When you delete your account, all your rides are deleted and the contribution with them. If you edit a ride’s track or your privacy zones, the contribution is calculated again: from the part of the track you kept and without the sections inside your current zones.

What remains after deletion. In a route that is already saved, the height of a section is an anonymous statistic over several riders (at least three different people), not a record of your ride. If you delete a ride, switch the setting off or delete your account, your contribution disappears from our road-height data and new calculations do not use it, but elevation profiles of routes that were already calculated and saved are not recalculated: they may keep a statistic result that included your measurement. It contains neither your name, nor a time, nor any trace of your ride, and it does not tell whose measurement went into it.

Sharing with third parties. We do not share these data with anyone. Heights from rides are added to a route on our server and are not sent to our routing provider (GraphHopper). For the base heights of routes we use the open Copernicus DEM GLO-30 terrain model; your data is not sent to it.

For any questions about these data, contact the operator, Panaride Sport Limited, at info@panaridesport.com.

Service Providers and Processors

Panaride uses service providers ("processors") to operate the app. Depending on the features you use and your region, these may include:

• Hosting, database and storage — DigitalOcean (managed compute, managed PostgreSQL and object storage in a European Union region, Frankfurt, Germany). During a limited migration window (no longer than 60 days) backup and archival copies may also remain with our previous providers (Yandex Cloud, Russia; DigitalOcean, US region) and are deleted afterwards.
• Authentication, analytics, diagnostics, configuration and push — Firebase / Google (Sign-in, Analytics, Crashlytics, Performance, Remote Config and Cloud Messaging).
• Sign-in and health platforms — Apple (Sign in with Apple, HealthKit) and Google Health Connect. The app reads or writes health data only after you grant permission.
• Maps — Mapbox (maps and static map images). The Mapbox maps SDK built into the app also sends Mapbox its own location and usage data (Mapbox telemetry) under Mapbox's terms. You can turn it off in the attribution menu of the map (the "i" button) and, in app versions that have it, with the "Mapbox telemetry" switch in Settings → Privacy.
• Place names — we name the town or village of a ride's start and finish ourselves, on our server, from a reduced copy of the open GeoNames gazetteer (CC BY 4.0); no coordinates are sent to third parties for this. Addresses that Mapbox derived from coordinates before October 28, 2026 are no longer used or shown and are deleted from our servers no later than November 30, 2026.
• Street of your own ride — your phone shows the street of your ride's start and finish: the app sends the coordinates of the ride's ends to the phone's system geocoding service (Apple on iPhone, Google on Android) when you open your ride or save it as a route, keeps the answer only in memory while the app is open and does not store it on the device or on our servers. Apple or Google process these requests under their own terms.
• Routing, map matching and address search — GraphHopper (Germany, hosted by Hetzner), reached through our server: route planning, address search, and matching a recorded track to the road network (map matching) with elevation data. GraphHopper keeps these requests for up to 5 weeks. When you start route guidance on a saved route, the app may ask GraphHopper again for the turn instructions of that route. The points of that route are sent for this. When the app builds a path during a ride — by itself after you leave the route, or when you ask (“Back to route”, “Back to the start”, “To the route start”, “To a point”, “Straight to the finish”) — it sends your current point, direction of travel and the destination to the GraphHopper routing service (Germany) via our server. We don't keep the coordinates of these requests: a service log without coordinates is kept for 30 days, and the ride itself is saved to your history as usual. GraphHopper keeps requests for up to 5 weeks. To stop automatic paths, choose “Ask me” or “Only notify”.
• Push delivery — Apple Push Notification service and Firebase Cloud Messaging.
• Email — our email provider, used to send account-deletion and security emails.

Server data is primarily hosted in Germany (European Union). Data may also be processed in the United States (Google, Apple, Mapbox), the European Economic Area, Hong Kong (operator), and, during the migration window described above, Russia. Providers may act as our service providers or contractors and are permitted to use your data only to provide their services to us.

Storage and Deletion

Panaride stores account, ride, route, media and operational data for as long as needed to provide the service, maintain security, meet legal obligations and support the choices you make in the app. You can request account deletion in the app or on the web at panaride.app/account/delete. Account deletion removes the main account and associated backend records according to the deletion flow, while some logs, analytics events, backups or provider records may remain for limited operational or legal periods. Per-category retention periods are set out in the "Categories of Personal Information We Collect" table below.

Automated Decision-Making

Panaride does not use automated decision-making technology (ADMT) to make decisions that produce legal or similarly significant effects about you. Automated processing is used to calculate ride metrics (such as distance, speed, elevation, calories and heart-rate zones), statistics, achievements and game statuses, to calculate the road heights for routes described in “Road Elevations from Rides”, and to select and order rides and suggest riders nearby in social features; the applicable access settings are applied when information is shown. We do not use this processing to profile you for advertising, eligibility, pricing or similar consequential decisions.

Security

We use reasonable technical and organizational measures to protect your information. These include encryption of data in transit (TLS), access controls and authentication for our systems, and hosting in a European Union (Frankfurt) region of our infrastructure provider. No method of transmission or storage is completely secure, so while we work to protect your information, we cannot promise absolute security.

Your Choices

• change or revoke device permissions for location, Bluetooth, health, photos, camera and notifications;
• change profile, statistics, ride-audience and sharing visibility settings in the app;
• switch off “Improve road elevations from my rides” in Settings → Privacy;
• disconnect health integrations and delete imported health data where the app provides that control;
• delete your account through the app or web deletion flow;
• contact us to request access, correction, deletion or clarification.

Your California Privacy Rights

This section applies to residents of California and describes your rights under the California Consumer Privacy Act, as amended by the California Privacy Rights Act (CCPA/CPRA). It supplements the rest of this policy.

Notice at Collection — Categories of Personal Information We Collect

The table below maps the information we collect to the statutory CCPA categories, and states the business purpose and retention period for each category. We collect these categories from the sources described in "Sources of Personal Information" above.

In addition to the periods above: database backups are retained for up to 7 days; notification-delivery history is kept for audit purposes, with the personal association removed when you delete your account. Where a category currently has no fixed limit, we keep it only as long as needed for the stated purpose and plan to set explicit limits.

Sensitive Personal Information

Precise geolocation and health/fitness data are treated as Sensitive Personal Information (SPI) under the CCPA/CPRA. We use SPI only to provide the service you request — recording and showing your rides, metrics, maps and health features — and to maintain and improve the quality of that service: the barometer heights of road sections in recorded rides, with homes, starts and finishes cut away, make route elevations more accurate, as described in “Road Elevations from Rides” (you can switch this off in Settings → Privacy). We do not use SPI to infer characteristics about you, and we do not use it for any purpose beyond those permitted for providing and improving the requested service. Because of this, the CCPA/CPRA does not require us to offer a separate "Limit the Use of My Sensitive Personal Information" link, and we do not provide one. If we ever use SPI for a secondary purpose that triggers this requirement, we will provide that link and update this policy.

Your Rights

If you are a California resident, you have the right to:

• Know / Access — request the categories and specific pieces of personal information we have collected about you, the sources, the business purposes, and the categories of third parties with whom we share it;
• Delete — request deletion of personal information we have collected from you, subject to legal exceptions;
• Correct — request correction of inaccurate personal information;
• Opt out of the sale or sharing of your personal information (see below — we do not sell or share it);
• Limit the use of your Sensitive Personal Information (see above — not applicable, as we use SPI only to provide the requested service);
• Non-discrimination — you will not receive discriminatory treatment for exercising any of these rights.

How to Submit a Request

You can submit a request using either of these methods:

• email us at info@panaridesport.com; or
• use the in-app privacy controls and the account deletion flow, in the app or on the web at panaride.app/account/delete.

We will acknowledge your request within 10 business days and respond within 45 calendar days. If we need more time, we may extend the period by up to another 45 days and will let you know. We will act on a valid opt-out request within 15 business days. We may need to verify your identity before completing certain requests, and an authorized agent may submit a request on your behalf with proof of authorization.

Do Not Sell or Share; Global Privacy Control

We do not sell your personal information and do not share it for cross-context behavioral advertising, as those terms are defined by the CCPA/CPRA. Because we do not sell or share your personal information, no opt-out of sale or sharing is required. Some browsers or extensions send a Global Privacy Control (GPC) signal; since we do not sell or share personal information, there is no sale or sharing to opt out of, and receiving a GPC signal does not change how we handle your data. If our practices ever change, we will honor GPC signals as an opt-out preference and update this policy.

Non-Discrimination

We will not discriminate against you for exercising any of your California privacy rights. We will not deny you our services, charge you a different price, or provide you a different level or quality of service because you exercised your rights.

Children

Panaride is not intended for children under 13, and we do not knowingly collect personal information from children under 13. If you are under the age of majority in your jurisdiction, use Panaride only with permission from a parent or guardian. If you believe a child under 13 has provided us personal information, contact us at info@panaridesport.com and we will delete it.

Changes to this Policy

We may update this Privacy Policy from time to time. We will notify you of material changes before they take effect, through the app or another means available to users, including release notes in the app store. The notice will state when the changes take effect. We will also update the "Effective date" at the top of this page. Your continued use of Panaride after an update becomes effective means you accept the updated policy.

Contact

For privacy questions or data requests, contact us at info@panaridesport.com.