Privacy Policy

1. Data controller

The controller of personal data processed through the RideArrow application is:

2. Scope

This policy applies to the RideArrow application for iOS and Android, its cloud features, RideArrow accounts, and the related data-management portal. It does not govern third-party services used separately outside RideArrow.

3. Data we process

Account and authentication

• Firebase user identifier and whether the account is anonymous, linked to Apple or Google, or uses email sign-in,
• for Apple or Google sign-in, the name and email address made available by the provider and authentication data needed to verify the login,
• for an email account, the email address, verification state, and security data managed by Firebase Authentication,
• Free, Lite, or Full access tier.

RideArrow never receives your Apple or Google password. Email-account passwords are processed by Firebase Authentication in securely hashed form; neither the operator nor the app can read the original password.

Location, search, and navigation

• precise or approximate location, bearing, speed, altitude, and GPS accuracy,
• origin, destination, intermediate stops, search terms, and calculated route,
• navigation progress, maneuvers, off-route status, and arrival.

Location is processed during an active ride or navigation session. If a ride or navigation remains active while the screen is locked or another app is visible, RideArrow uses the operating system’s background-location mechanism. Android displays a persistent foreground-service notification; iOS displays its system location-use indicator.

Place search is presented through the official Google Places UI Kit. Google displays the place name, address, and required Google Maps attribution inside that component. After you select a result, RideArrow uses its place ID and coordinates to place a point on the RideArrow map. RideArrow stores your own search text as its label instead of copying the Google place name or address.

Selected destinations may be kept only in a recent-destinations list on that device. Search history is never included in RideArrow cloud backup. Each complete history entry—including the search text, place ID, and coordinates—is automatically removed 30 days after its last use, or earlier when you clear the list.

Shared destinations and routes

When you deliberately share a destination or planned route, RideArrow sends its title, points and geometry, and the preferences needed to recalculate it to Firebase and Google Cloud. RideArrow creates a random link that can be opened by anyone you give it to while it remains valid. The link does not contain your name or email address, but the route itself may reveal places you visited or plan to visit. Do not publish the link if you do not want those details available to others.

Ride Log and ride telemetry

When you save a ride, RideArrow may record timestamps, GPS track, distance, duration, speed, acceleration and g-force, lean angle, altitude, bearing, GPS accuracy and satellite count, battery status and device temperature, mobile network type and signal strength, and navigation state. We do not access call content, contacts, messages, your phone number, or call history.

Settings and layouts

We process your selected language, measurement system, appearance, voice preferences, widget configuration, saved layouts, and cloud-backup and diagnostics preferences.

AI planning, place explanations, and Narrator

RideArrow uses the OpenAI API to suggest trip programmes, explain places, and prepare route-aware Narrator stories. Before sharing data for these AI features, the app explains the recipient and data involved and asks for your explicit permission. This is separate from location, advertising, diagnostics, and cloud-backup choices. You can decline or later withdraw permission in the app’s AI data sharing controls. Without permission, these AI features are disabled; manual trip editing, map search, and route calculation without AI remain available under their normal access and permission requirements.

• Trip planning and AI edits: selected start, destination, intermediate and locked places, their names, identifiers and coordinates; trip themes or instructions; language, day count, return choice, visit durations, tempo, interests and road preferences; and relevant route distances, timings and reference geometry or sampled coordinates. When the requested feature uses them, the input also includes the existing programme, summaries of riding history, and liked or disliked places. Supplied map candidates and their factual information help the model choose supported places.
• Place explanations: the selected place’s identifier, name, category, requested language and verified factual context. RideArrow servers also receive the place’s coordinates to look up map facts; the explanation request to OpenAI does not add a separate coordinate field.
• Narrator: relevant places and verified facts along the route, route progress, distance and timing context, selected interests, language and storytelling style, and summaries of previously told stories to avoid repetition and maintain continuity. This is text-based story generation; microphone or intercom audio is not sent to OpenAI by this feature.

We do not add your sign-in email address, Firebase account identifier, account password, or purchase tokens to these AI inputs. Place labels, instructions and themes are your text and may themselves identify you or others; avoid including personal information that the feature does not need. Route and place choices can reveal where you live or plan to travel even without an account identifier.

Withdrawing permission stops future AI sharing and automatic AI place-explanation requests. It does not recall requests already sent, delete earlier generated content or usage records, or cancel an in-flight request already accepted by the server. See sections 5, 7 and 8 for storage and deletion.

Subscriptions

We process the product ID, transaction or purchase token, subscription state and expiry, and a pseudonymized account identifier. We do not receive card details or full payment information; Apple processes App Store payments and Google processes Google Play payments.

Diagnostics and performance

If you enable “Share diagnostics” in Profile, Firebase may process app interactions, aggregate ride measurements, performance, crashes, error details, app version, device model, operating-system version, network information, and installation identifiers. Our diagnostic events never include coordinates, destination names, search text, or route geometry. This setting is disabled by default.

Advertising and consent

Anonymous and Free tiers may display Google AdMob banners. Depending on your consent, Google may process advertising identifiers, IP address, network-derived approximate location, ad interactions, and diagnostics to serve, measure, and possibly personalize ads. RideArrow does not send precise GPS tracks, destinations, or Ride Log data to AdMob. Where required in your region, advertising choices can be changed in Profile. Lite and Full do not display ads.

Application security

Firebase App Check, Apple App Attest, and Google Play Integrity may process technical information and integrity tokens to confirm that requests come from a genuine application, protect APIs, and prevent abuse.

4. Purposes and legal bases

• Providing the service and performing a contract: account, dashboard, ride recording, route calculation, navigation, synchronization, and subscriptions.
• Your consent: sharing the described data with OpenAI for optional AI features, location permission, optional diagnostics, cloud backup, and personalized advertising where consent is required. AI sharing consent can be withdrawn in the app; other permissions can also be changed in the applicable iOS or Android settings.
• Legitimate interests: service security, fraud prevention, troubleshooting, and protection of our systems where your rights do not override those interests.
• Legal obligations: information we must retain under accounting, tax, or other applicable laws.

5. Local and cloud storage

Ride records, preferences, and search history are first stored on the device. Search history remains device-local, is excluded from RideArrow cloud backup, and expires after 30 days. Android system backup for RideArrow is disabled; on iOS, local app data may be included in the user’s encrypted device backup according to their Apple settings. Signed-in users can disable RideArrow cloud backup in Profile. Signed-in accounts synchronize settings and layouts; Lite and Full may also synchronize saved rides, GPS tracks, and detailed telemetry. RideArrow cloud backup runs at most once per day.

Cloud backups, subscription records, shared routes, and AI planning records use Firebase and Google Cloud, including an SQL database in europe-central2. Some supporting Google services may process data outside the European Economic Area subject to applicable transfer safeguards.

The editable unsaved trip draft is stored on the device. AI generation also sends the described planning data to RideArrow servers and OpenAI. Before you explicitly save a trip, RideArrow may already store the generated programme and its original candidate places, coordinates and factual context in a server-side cache linked to your account. This lets the same generation action replay without another paid AI request. The cache can also retain generated AI edit proposals before you accept them or save the trip, so the same edit action can replay its original proposal without another paid AI request. Planning and place-explanation usage records identify the account, action and date; planning records may also contain trip identifiers, request fingerprints, processing state and AI cost information. This processing is separate from daily ride backup and saved-trip synchronization.

Saved multi-day trips are synchronized with your signed-in account in private Cloudflare R2 storage. This includes itinerary places and coordinates, planned road geometry, trip preferences, descriptions and completion state. The phone keeps a local cache for offline use and queues changes until it can synchronize. This synchronization follows explicit trip saving and editing and is separate from the daily ride-backup setting. Deleting a saved trip removes its R2 content; it does not by itself remove the separate AI generation cache or usage records. Deleting your account removes the associated saved-trip and AI planning records.

Narrator also keeps account-linked story-memory and playback records on RideArrow servers to avoid repeated stories and remember your feedback. The app and server may cache generated text so that it can be reused without generating it again.

6. Recipients

We do not sell personal data. The following providers may process data where necessary:

• Google Firebase and Google Cloud — authentication, cloud functions, SQL backup, optional diagnostics, and security,
• OpenAI — the optional AI planning, place explanations and Narrator processing described above, after your explicit sharing permission. OpenAI receives requests from RideArrow servers and may process them outside the European Economic Area. Its API data controls and retention documentation explains provider-side handling, including security monitoring and temporary caching,
• Google Maps Platform — place search through the official Places UI Kit; use of Google Maps Platform is subject to the Google Maps Platform Terms and Google Privacy Policy,
• OpenStreetMap contributors, Protomaps, MapLibre, Valhalla, and Cloudflare R2 — RideArrow map rendering, map-data delivery, route calculation, and account-scoped saved trip storage,
• Google AdMob and User Messaging Platform — ads and consent management for Anonymous and Free tiers,
• Apple — App Store distribution and subscriptions, Sign in with Apple, and App Attest integrity verification on iOS,
• Google Play — Android distribution, subscriptions, and integrity verification.

We may disclose information to public authorities where legally required or where necessary to protect users, our rights, and our systems.

7. Retention

• local data remains on the device until you delete it, clear app storage, or uninstall RideArrow,
• cloud settings, layouts, and rides are retained while the account exists or until deleted; search history is not sent to this cloud storage,
• AI programme and edit-proposal caches and usage records linked to a trip have no fixed automatic expiry in the current service. They remain until account deletion or an applicable deletion request is fulfilled. The seven-day cleanup of ordinary planning or place-explanation usage records without a trip identifier does not apply to those trip-linked records. Withdrawing AI permission or deleting only the saved trip does not erase them,
• account-linked Narrator memory, playback and feedback records can remain until account deletion or an applicable deletion request is fulfilled; expiry of a playback reference does not mean all related memory has been deleted,
• every local search-history entry is automatically removed 30 days after its last use,
• a shared route remains available through its link for no longer than 30 days and expired records are removed regularly; deleting an account also removes its active shared routes,
• technical deletion markers without ride content may be kept temporarily to synchronize deletions,
• diagnostic and advertising data follows your settings and the applicable Google service retention rules,
• minimum purchase or security records may be retained for legally required periods or as necessary to prevent fraud and resolve disputes.

RideArrow’s OpenAI requests set store: false, so we do not ask OpenAI to retain a retrievable response for later API use. This is not a promise of zero provider retention. OpenAI’s published API policy says content is not used for model training by default unless the customer opts in; security-monitoring logs may retain prompts and responses for up to 30 days by default, with legal or safety exceptions, and temporary prompt caching may also apply. Provider retention follows the applicable API controls and terms, separately from RideArrow’s own caches. See the OpenAI API data controls.

8. Your rights and account deletion

Subject to applicable law, you may request access, correction, portability, restriction, objection, or deletion and may withdraw consent. You may also lodge a complaint with the Slovak Data Protection Authority or your local supervisory authority.

You can delete your RideArrow account and associated cloud data through the app or the secure portal. This includes saved trips in R2, RideArrow’s AI planning caches and usage records, and account-linked Narrator memory, playback and feedback records. Withdrawal of AI sharing permission is a separate control and does not itself delete that data. For an access or deletion request concerning data already sent to OpenAI, contact us; provider-side handling remains subject to the applicable retention and legal requirements. Account deletion does not automatically cancel an App Store or Google Play subscription; cancel automatic renewal in the applicable store before deleting the account.

Open account deletion

You can also email info@jsoft.sk. We may request reasonable identity verification to protect the account.

9. Security

We use HTTPS encryption in transit, Firebase Authentication, App Check, Apple App Attest, Google Play Integrity, account-scoped authorization, and server-side storage for secret API keys. Cleartext traffic is disabled. No system can nevertheless be guaranteed entirely risk-free.

10. Children

RideArrow is not directed to children, and we do not knowingly collect data from children below the age at which they can independently consent under the laws of their country.

11. Changes and contact

We may update this policy when features or legal requirements change. The current version and date will remain available here. Contact JSoft s.r.o. at info@jsoft.sk with privacy questions.