| VERSION | 1.5 |
|---|---|
| EFFECTIVE DATE | 26 September 2026 |
| STATUS | Public privacy information under the GDPR |
| OPERATOR | Petr Novák | Business ID 03741842 | Czech Republic |
Location data deserves special care
ArcRoute uses precise location to plan and follow routes and, when you actively start a ride, to record the ride in the foreground or background.
A ride history can reveal sensitive patterns such as home, work and regular destinations. Your rides and personal heatmap are private by default and are not sold or used for targeted advertising.
Privacy contact: support@arcroute.app
Document overview
| SECTION | WHAT IT COVERS |
|---|---|
| 1-3 | Controller identity, scope and key privacy points. |
| 4-6 | Data categories, purposes, legal bases, location data and subscriptions. |
| 7-9 | Service providers, international transfers and retention. |
| 10-13 | Account deletion, export, choices, GDPR rights and security. |
| 14-18 | Children, automated decisions, website cookies, changes and contact. |
1. Who is responsible for your data?
The controller of personal data processed for the ArcRoute Service is Petr Novák, an individual entrepreneur registered in the Czech Republic under Business ID No. 03741842, with registered office at Marie Podvalové 1041/8, 196 00 Praha-Čakovice, Czech Republic (“ArcRoute”, “we”, “us” or “our”).
| OPERATOR | Petr Novák, Business ID No. 03741842 |
|---|---|
| ADDRESS | Marie Podvalové 1041/8, 196 00 Praha-Čakovice, Czech Republic |
| support@arcroute.app |
ArcRoute is established in the European Union. We have not appointed a separate EU representative. Privacy and data-rights requests can be sent to support@arcroute.app.
2. Scope of this Notice
This Privacy Notice applies to the ArcRoute iOS application, your ArcRoute account, the cloud and routing services used by the App, support communications and the public website at arcroute.app. It does not replace the privacy notices of Apple, Mapbox or other independent services that you use in connection with ArcRoute.
This Notice describes the production configuration of the Service. We keep the App, App Store disclosures and operational practices aligned with it. If a new feature changes the processing materially, we will update the Notice before or when the feature is introduced, as required by law.
3. Key privacy points
| TOPIC | ARCROUTE APPROACH |
|---|---|
| Precise location | Used for the map, place search, route calculation, navigation and ride recording. Background location is used only while an active navigation or ride-recording session requires it. |
| Ride history | Saved routes and recorded rides may be stored on your device and synchronised to your private ArcRoute account. They include route geometry and ride metrics. |
| Advertising | ArcRoute does not sell personal data and does not use personal data for targeted advertising or cross-company tracking. |
| Payments | Apple processes App Store payments. ArcRoute does not receive payment-card details. |
| Website analytics | Google Analytics 4 is loaded only after website analytics consent. Refusing analytics does not prevent use of the website or App. |
| Account deletion | You can initiate deletion in the App. Account deletion and Apple subscription cancellation are separate actions. |
4. Personal data we process and why
The table below describes the main processing activities. “Contract” means processing necessary to provide the Service you request under Article 6(1)(b) GDPR. “Legitimate interests” means processing necessary for a stated operational or security interest under Article 6(1)(f), after balancing that interest against your rights. “Legal obligation” means Article 6(1)(c), and “consent” means Article 6(1)(a).
| ACTIVITY AND DATA | PURPOSE AND LEGAL BASIS | RECIPIENTS AND RETENTION SUMMARY |
|---|---|---|
| Account and authentication Apple user identifier; name and email or Apple private-relay email if Apple makes them available; ArcRoute user ID; authentication and session metadata. |
Create and secure your account, sign you in and synchronise account-based features. Basis: contract; legitimate interests in account security and abuse prevention. |
Apple and Supabase. Account data is kept while the account is active and removed from active ArcRoute systems when the account is deleted, subject to backup and legal retention described in Section 9. |
| Profile and avatar Display name, profile image selected by you, internal identifiers and profile settings. |
Provide and personalise your account. The avatar is optional. Basis: contract for requested profile functions; legitimate interests for secure storage. |
Supabase database and private storage. Retained until you replace it or delete the account. ArcRoute re-encodes profile images before cloud storage, which generally removes original photo metadata. |
| Subscription status Product identifier, monthly or annual plan, introductory-offer eligibility, entitlement status, renewal or expiry date and revocation information available through StoreKit. A limited paid-through status may be cached on the device. |
Show the correct paywall, activate ArcRoute Pro and respond to purchase status changes. Basis: contract; legal obligation where required for consumer claims. |
Apple processes billing and maintains transaction records under its own terms. ArcRoute does not receive payment-card details and does not send Apple transaction identifiers to the ArcRoute cloud database. |
| Live location, map and routing Precise latitude and longitude; timestamp; altitude; speed; heading or course; accuracy; selected waypoints; routing and avoidance preferences; map viewport or nearby-search area. |
Show your position, search near you, calculate routes, follow navigation instructions, match your position to a route and provide map functions. Basis: contract. Device location permissions control whether the App can access location. |
Processed on the device and, when necessary for the requested function, by Mapbox or ArcRoute-controlled GraphHopper infrastructure hosted with Hetzner in Germany. Transient service and security logs follow Section 9. |
| Saved routes, recorded rides and heatmap Route geometry; waypoints and place names; manoeuvres; route preferences; imported GPX content; start and end time; distance and duration; per-point time, speed and altitude; maximum speed; elevation; lean-angle estimates; map-matched geometry; deletion and synchronisation metadata. |
Save, display, synchronise and recover routes and rides; calculate statistics; build your private heatmap; improve route display and map matching. Basis: contract; legitimate interests in reliable synchronisation and data integrity. |
Stored locally in the App and, for signed-in cloud functions, in Supabase in the EU. Kept until you delete the item or account. Deleted-item handling and backup windows are described in Sections 9 and 10. |
| Place search and recent places Search query; precise or approximate proximity coordinates when used; selected result; place name, address, identifier and coordinates. The App keeps a limited recent-search list on the device. |
Return relevant places, create route waypoints and make recent searches convenient. Basis: contract. |
Mapbox receives search requests and may process them under its own privacy terms. The App stores up to seven recent places locally until they are overwritten, cleared or removed as part of account/app-data deletion. |
| Support, complaints and rights requests Name, email, message, attachments you choose to send, account or device details needed to investigate, and our response history. |
Provide support, handle complaints, withdrawals, refunds assistance and GDPR requests, and establish or defend legal claims. Basis: contract; legal obligation; legitimate interests in resolving issues and protecting legal rights. |
Processed by ArcRoute and the relevant communications provider. Normally retained for three years after the matter closes, or longer where a legal claim or mandatory recordkeeping period requires it. |
| Security and technical operations IP address; request time; endpoint; response status; authentication event; device/app version where supplied; error and abuse indicators. ArcRoute does not currently integrate a third-party mobile advertising or crash-analytics SDK. |
Protect accounts and infrastructure, diagnose failures, prevent abuse and maintain availability. Basis: legitimate interests; legal obligation where incident records are required. |
May be processed by Supabase, Hetzner and relevant infrastructure providers. Routine accessible logs are retained only for the documented operational window described in Section 9. We configure them not to contain complete ride payloads or credentials. |
| Website access and consent IP address, browser language and standard request data processed by the host; language and analytics-consent choices stored in your browser; Google Analytics identifiers and interaction data only after consent. |
Deliver and secure the website; show it in your language and remember that choice; remember your cookie choice; understand aggregate website use where you consent. Basis: legitimate interests for essential hosting/security and language selection; consent for analytics. |
Netlify hosts the website. Google Analytics 4 is used only after consent. Website retention and cookies are described in Sections 9 and 16. |
5. Precise location and ride recording
ArcRoute needs precise location for core navigation functions. When you start navigation or ride recording, the App may continue to receive location in the background so the session can continue while the screen is locked or another application is visible. ArcRoute does not use background location when no active function requires it.
Location permission is a device-level control, not a blanket GDPR consent. ArcRoute first requests location access when a feature needs it. When you start navigation or ride recording and background access is required, the App may request the higher-level “Always” permission in context. If iOS does not show the prompt or you decline it, you can manage the permission in iOS Settings; background continuation may be unavailable.
Ride recordings can reveal highly private patterns even though location is not automatically a special category of data. Keep your Apple device and ArcRoute account secure. Do not include another person’s location in a recording or uploaded route unless you have a lawful basis to do so.
6. Subscriptions and Apple
Monthly and annual ArcRoute Pro subscriptions, including the fourteen-day introductory trial for eligible users, are offered through Apple’s In-App Purchase system. Apple determines the storefront price, currency, tax treatment and introductory-offer eligibility and processes the payment under Apple’s own terms and privacy notice.
The App uses StoreKit to determine whether your Apple Account has a current ArcRoute Pro entitlement. ArcRoute uses the minimum status information needed to enable or disable Pro features. It does not receive your full payment-card number. Deleting the ArcRoute account does not cancel the Apple subscription; manage the subscription separately in Apple Account settings.
7. Service providers and other recipients
We disclose personal data only where needed to provide the Service, comply with law, protect the Service or handle a request. The principal providers are:
| PROVIDER | SERVICE AND DATA USE | LOCATION / ROLE |
|---|---|---|
| Apple | App distribution, Sign in with Apple, StoreKit subscriptions and Apple Account services. Apple acts under its own terms for those platform functions; ArcRoute receives only the information needed for the Service. | Apple may process data internationally under its published privacy and transfer arrangements. |
| Supabase | Authentication, EU-hosted database, private file storage and server functions. ArcRoute uses a Pro project in the EU-West region (Ireland). | Processor for ArcRoute. Core project data is hosted in the selected EU region, subject to Supabase support, security and subprocessors described in its documentation and DPA. |
| Hetzner / ArcRoute GraphHopper | Germany-hosted infrastructure used to calculate routes and map-match route or ride points under ArcRoute’s control. | Processor infrastructure in Germany. We send only data needed for the requested route or matching operation and minimise operational logging. |
| Mapbox | Map rendering, place search and related SDK functionality. Requests may include search text, selected place, map area, proximity location and technical SDK information. | Mapbox processes certain data under its own privacy terms, including SDK telemetry where enabled. The Mapbox attribution interface provides access to attribution and available telemetry controls. |
| Netlify | Hosting, delivery and security of the public website, including selecting the English or Czech version from the browser language. | Netlify may process standard website request logs, including IP addresses, under its own service and privacy terms, with EU-US Data Privacy Framework certification for transfers. |
| Google Ireland Limited | Google Analytics 4 for website measurement only after consent. | Analytics provider. Depending on the service and configuration, data may be processed by Google group companies outside the EEA under applicable safeguards. |
We may also disclose information to professional advisers, authorities or courts where necessary to comply with law, respond to a lawful request, protect users or establish, exercise or defend legal claims. If the ArcRoute business is transferred, relevant data may be disclosed to a successor subject to confidentiality and applicable data-protection law.
8. International transfers
ArcRoute is based in the Czech Republic and uses EU-hosted core account and ride storage. Some platform providers, including Apple, Mapbox, Netlify or Google, may process information in countries outside the European Economic Area.
Where the GDPR requires a transfer safeguard, we rely on the mechanism applicable to the provider and transfer, such as an adequacy decision (including the EU-US Data Privacy Framework where the recipient is validly certified), the European Commission’s Standard Contractual Clauses with supplementary measures, or another lawful mechanism. You may contact us for information about the relevant safeguard, subject to protection of confidential security and contractual information.
9. How long we keep data
We keep personal data only for as long as needed for the purposes described above, including to provide the Service, comply with law and resolve claims. We apply the following retention periods:
| DATA CATEGORY | RETENTION RULE |
|---|---|
| Account, profile and active cloud content | While the account is active. On account deletion, remove the data from active ArcRoute systems promptly, subject to limited legal records and backup expiry. |
| Saved routes and rides | Until you delete the item or account. When an item is deleted, remove its substantive route and telemetry payload from active systems after synchronisation. A minimal deletion marker may be kept for up to 30 days solely to propagate deletion across devices. |
| Supabase database backups | Residual database records may remain in isolated rolling disaster-recovery backups for up to seven days, after which the relevant backup is overwritten in the normal cycle. Backups are not used for ordinary product access. |
| Recent searches on the device | Up to seven recent items, until overwritten, cleared or removed with local app/account data. |
| Supabase platform and function logs | Routine accessible logs: up to seven days, subject to the configured Supabase plan and verified production settings. |
| ArcRoute routing and infrastructure security logs | Up to 30 days unless a shorter period is sufficient or a specific security incident or legal obligation justifies longer restricted retention. |
| Support, complaints, withdrawals and rights requests | Normally three years after closure; longer only where needed for an active claim, a statutory limitation period or mandatory recordkeeping. |
| Website analytics | GA4 event data: two months. GA4 user-level data: 14 months from collection, not extended by later visits. Google Analytics cookies may last up to two years unless deleted sooner. |
| Cookie-consent records | Normally up to three years to demonstrate and respect the choice, unless renewed or deleted sooner. |
If these settings change, we will update this Notice before applying a longer period. We may retain narrowly limited records longer where required by law or necessary for an active legal claim, and will restrict their use to that purpose.
10. Account deletion and data export
You can initiate permanent account deletion in the App. The account-deletion flow removes the ArcRoute authentication account, profile, private avatar, cloud-synchronised routes and rides from active systems, revokes the ArcRoute Sign in with Apple connection as required, signs the device out and removes account-linked local App data and caches. Residual database copies may remain in isolated backups for up to seven days as described above.
Account deletion and subscription cancellation are separate
Deleting the ArcRoute account does not cancel an App Store subscription. Cancel or manage the subscription separately in Apple Account settings before or after deleting the ArcRoute account.
Before deleting the account, export content you want to keep. Where self-service export is not available for a particular data set, email support@arcroute.app to request access or a portable copy. Depending on the request and technical context, route and ride data may be provided in a commonly used machine-readable format such as GPX or JSON.
We may retain limited information that must be kept for legal compliance, fraud prevention or an active dispute, but will not use it for unrelated product purposes. Account deletion is irreversible after active deletion and backup expiry.
11. Your choices and controls
-
Location permissions: change precise, while-in-use or background access in iOS Settings. Core navigation or recording functions may stop working.
-
Ride recording: begin and end recording deliberately. Delete an individual ride or the account when you no longer want it stored.
-
Recent searches: clear them through the App where the control is provided, or remove local App data.
-
Profile image: do not upload one, replace it, or delete the account.
-
Mapbox telemetry: use the attribution and privacy controls made available through the Mapbox map interface where applicable.
-
Website analytics: choose Reject or Allow on the website banner and change the choice later through Cookie settings.
-
Subscription: manage or cancel it in Apple Account settings.
12. Your GDPR rights
Subject to the conditions and exceptions in applicable law, you may request:
-
access to your personal data and information about its processing;
-
correction of inaccurate or incomplete data;
-
deletion of personal data;
-
restriction of processing;
-
a portable copy of data you provided where processing is based on consent or contract and carried out by automated means;
-
objection to processing based on legitimate interests, including an explanation of your particular situation;
-
withdrawal of consent at any time, without affecting processing carried out before withdrawal;
-
information about an applicable international-transfer safeguard.
Send a request to support@arcroute.app. We may ask for information reasonably needed to verify your identity and protect the account. We normally respond within one month, subject to any lawful extension for a complex or numerous request. Rights are generally free, but the GDPR permits a reasonable fee or refusal for manifestly unfounded or excessive requests.
You may complain to the Office for Personal Data Protection of the Czech Republic (Úřad pro ochranu osobních údajů, ÚOOÚ) or the supervisory authority in the EEA country where you live, work or believe an infringement occurred.
Czech supervisory authority: uoou.gov.cz.
13. Security
ArcRoute uses measures designed to protect personal data, including encrypted network connections, Sign in with Apple, access controls, row-level database security, private file storage, separation of production secrets, restricted provider access and backups for recovery. We limit access to people and systems that need it for a documented purpose.
No internet or mobile system is completely secure. Keep your device, Apple Account and passcode secure, install updates and contact us promptly if you suspect unauthorised access. Do not send passwords, complete payment-card details or unnecessary ride histories by email.
14. Children
ArcRoute is intended for users aged 16 or older and is not directed to children under 16. Users aged 16 or 17 may use the Service only with the approval of a parent or legal guardian, as described in the Terms of Service.
We do not knowingly permit children under 16 to create an ArcRoute account. If we learn that a child under 16 has created an account or provided personal data through the Service, we will take reasonable steps to delete the account and associated personal data, unless we are legally required to retain limited information.
A parent or legal guardian may contact support@arcroute.app regarding a minor’s account or personal data.
15. Automated decisions
ArcRoute does not use personal data to make solely automated decisions that produce legal effects or similarly significant effects about you. Route recommendations are functional navigation outputs based on your request and settings; you remain responsible for the riding decision.
16. Website cookies and analytics
The public website uses essential storage to remember your analytics choice and, if you switch language in the footer, the language you chose. The preference keys arcroute:analytics-consent and arcroute:analytics-consent-at and the cookie nf_lang are stored in your browser and are not used for advertising. Standard hosting logs may be processed by Netlify for delivery and security.
Google Analytics 4 is loaded only after you select Allow for analytics. When enabled, it may set cookies such as _ga and _ga_T3QWF37E10 and collect pseudonymous identifiers, approximate location derived from IP address, browser/device information and page or interaction events. ArcRoute uses these data to understand aggregate website use, not to build advertising profiles.
You can reject analytics without losing access. You can later change the choice through the website’s Cookie settings. Withdrawing consent stops future analytics loading and the website deletes ArcRoute-accessible Google Analytics cookies where technically possible. You can also remove cookies in your browser.
| STORAGE / COOKIE | PURPOSE | TYPICAL DURATION |
|---|---|---|
| arcroute:analytics-consent | Remember Allow or Reject choice in local browser storage. | Up to three years, after which the choice is discarded and the banner asks again. Sooner if you change it or clear browser data. |
| arcroute:analytics-consent-at | Record when the choice was made, so the three-year limit in Section 9 applies. | Discarded together with the choice it timestamps. |
| nf_lang | Remember the language you chose in the footer, so the host serves that version instead of guessing from your browser. Set only when you switch. | Up to 1 year. Sooner if you switch again or clear browser data. |
| _ga | Distinguish website visitors after analytics consent. | Up to 2 years. |
| _ga_T3QWF37E10 | Maintain and count website sessions after analytics consent. | Up to 2 years. |
More information about Google’s handling of Analytics data is available in Google’s privacy information.
17. Changes to this Notice
We may update this Notice when the Service, providers or law changes. We will publish the new effective date and, for a material change, provide an appropriate in-app, website or email notice before the change takes effect where required. If a new processing activity requires consent, we will ask for that consent rather than treating continued use as consent.
18. Contact
For privacy questions, rights requests or concerns about location and ride data, contact:
| OPERATOR | Petr Novák, Business ID No. 03741842 |
|---|---|
| ADDRESS | Marie Podvalové 1041/8, 196 00 Praha-Čakovice, Czech Republic |
| support@arcroute.app |