Privacy Policy
Last updated ·
This Privacy Policy explains what data the CapDrive iOS app (the "App") handles, why, and the choices you have. The provider responsible for the App is named at the end of this page. If you have any questions, write to support@capdrive.app.
You do not need to register manually. Trips remain on your iPhone and are not automatically uploaded. To provide Plus, CapDrive creates a random guest account and sends its identifier, a device identifier, app and system versions, language and signed requests to our subscription server. RevenueCat processes the guest identifier and App Store purchase information to verify and restore subscriptions. Network services also receive the connection IP address. This subscription flow does not send driving locations or sensor recordings. We do not receive payment card details. Contact support@capdrive.app for requests about your subscription account data. See RevenueCat’s privacy policy.
Advertising measurement
CapDrive uses the Meta SDK to measure the effectiveness of its Facebook and Instagram app-install ads. Meta receives installation, app-open and session events, app/device identifiers, app and operating-system versions, device information and the connection IP address, and may receive SDK diagnostic data. At launch, CapDrive requests iOS tracking permission if you have not already made a choice. With your permission, Meta may use the advertising identifier (IDFA) for advertising measurement and personalization. If you decline or tracking is restricted, IDFA collection stays off and events reflect that status. Automatic purchase-event logging stays off. You can change tracking permission in iOS Settings. Driving locations, routes, or sensor recordings are not sent by this integration. Meta processes the data under its Privacy Policy; its retention and international-processing practices apply. For questions or data requests, contact support@capdrive.app.
CapDrive also sends its account UUID to Meta to associate app-usage events with the CapDrive account, whether tracking is allowed or declined. This UUID does not change the tracking-permission status. The association is updated when the account changes and cleared when the local account session ends.
To link subscriptions with advertising measurement, CapDrive shares its account UUID, the Meta SDK's anonymous installation ID, vendor/device identifiers and the recorded tracking-permission status with RevenueCat; IDFA is available only when iOS permits it. RevenueCat may forward verified trial starts, paid subscriptions, trial conversions, renewals and lifetime purchases to Meta, even while the App is closed. Events may include product and order identifiers, revenue and currency; reporting amounts may be converted to US dollars. Purchase events use one reporting source to avoid duplicate counting. Cancelled or restored purchases are not new purchases, and sandbox activity is kept separate from production advertising measurement. This flow includes no payment card details, driving locations, routes or sensor recordings.
Location
CapDrive needs access to your precise location. It uses location to show your speed, recognize when you are driving, draw your route, estimate distance and help determine the car's heading.
CapDrive requests location access while using the App, not Always access. An ongoing recording may continue in the background or while locked, with the iOS location indicator. Permissions, iOS and sensor availability can interrupt recording.
The App processes location data (coordinates, altitude, speed, course, their accuracy and the time) on your iPhone and stores it there as part of your trips. It sends location data to us only when you explicitly confirm a problem-report upload.
Motion and compass
While recording, CapDrive requests motion samples (acceleration, rotation, gravity and orientation) at about 100 Hz; actual delivery can vary. Compass updates arrive separately at the rate provided by iOS. Both are processed locally for G-force, mounting recognition, events and heading, and retained as part of trips as described below.
OBD, custom instruments and downloads
When you enable OBD, CapDrive uses Bluetooth to read a compatible vehicle adapter. Device identifiers, parameter settings, scripts and instrument resources are stored on your iPhone. Recorded vehicle inputs can be included in trips and in a full trip report you explicitly upload; connecting an adapter does not automatically upload its readings.
Custom instrument scripts process selected readings on your iPhone. The App maintains shared, already-acquired data in memory for the latest 30 seconds of the current trip, with at most 151 entries, and supplies samples according to each instrument’s input configuration. This history is independent of whether an instrument is open or its script runs, and resets when the trip ends or changes or the operating mode changes. Temporary script storage is isolated by instrument instance and current trip, and is cleared when the trip ends or changes or the runtime is recreated.
The native content library sends search text, App version and pagination to our catalog service, separately from account authentication. Instrument covers, packages and parameter files download from Alibaba Cloud OSS; these services receive request details and IP addresses, but library browsing does not send your trip readings or instrument source. Catalog requests also include the App’s current display language.
Exported .instrument files contain instrument code, image resources and input parameter definitions, including defaults, ranges and options. They exclude locally entered input values, OBD device bindings, temporary runtime state and trip records. Default text is still exported; check it for personal information before sharing. Remote editing exposes the current draft, resources, interface descriptions and editing logs over unencrypted local HTTP, without a separate login password. Devices able to reach that local-network address may read or modify the current draft. Allow local network access as needed and enable it only on a trusted network. Turning off remote editing, leaving the editor or moving the App to the background stops the session.
What a trip contains
A trip contains its start and end time, the route, the positions and speeds recorded, the calculated readings such as G-force and heading, the driving events with their scores, and raw sensor data.
A trip is kept in History only if it contains saved valid measurement data; there is no 60-second minimum. A recording with no valid measurement data is deleted when it ends or on the next launch. Later calibration interruptions do not remove a qualifying trip. Deletion and problem reports require the trip to have ended.
Raw sensor data is kept throughout the recording, including periods without valid orientation calibration. Valid GPS route points are saved independently of calibration; missing route sections are shown as gaps. Motion readings and GPS-dependent statistics still require valid measurements.
After orientation is calibrated, valid G-force and attitude data can still be displayed and recorded without valid GPS. Unavailable speed or position stays unavailable; it is not replaced with zero. Events and acceleration timing still require GPS that meets their quality conditions.
Trips are kept in the App's private storage on your iPhone, which other apps cannot access, and are excluded from iCloud and computer backups. iOS encrypts this storage; so that recording can continue while the screen is locked, the App can read it once you have unlocked the iPhone after it was last restarted.
The App also stores your settings (units, appearance, language, dashboard layout and whether you have seen the introduction) and map images of your routes on your iPhone.
Manual calibration settings are also stored locally. Calibration actions and parameters may be included in the trip's diagnostic recording and in a report file you choose to send.
Display mode, HUD brightness/HDR preferences and whether the HUD guide has been shown are stored on this iPhone. HUD changes presentation only; it does not upload trip data.
When you open a completed trip, CapDrive may filter motion readings judged anomalous and related events when sufficient evidence is available, and estimate missing pitch or roll when the recorded data supports it. This processing happens on your iPhone and does not change the original recording or export. Review readings, peak G and displayed events may therefore differ from the live dashboard or original export. An angle stays unavailable if the evidence is insufficient; not every anomaly can be identified.
Review adjustments are cached locally to speed up later viewing. They are separate from the original recording and are removed when you delete the trip or App. A manual calibration applies only to the current trip and is cleared when the trip ends or the App restarts.
Sharing a trip
Share trip creates images locally from the route, start date and time, statistics and, depending on the card and available data, peak-reading locations. Map backgrounds use Apple Maps. The system share sheet passes the image to the app or destination you select; it does not send the raw trip recording. Saving to Photos may require permission to add images.
Export trip generates a KML, GeoJSON or GPX route file on your iPhone containing recorded precise GPS coordinates, timestamps and available elevation; GeoJSON also includes the local trip identifier. It excludes raw motion or compass data, OBD parameters, events and scores, and is not a restorable archive of the complete trip.
Images and route files pass through the system share sheet to the app or destination you select. Export itself does not automatically upload them to us; recipients handle copies under their own rules. Deleting a trip or the App does not withdraw copies already saved or shared. Check locations, dates, times and other personal details before sharing.
Live Activity
For a Live Activity, CapDrive passes a local trip identifier, driving status and app language to iOS to show on the Lock Screen and supported Dynamic Island. It contains no route, speed or raw sensor data and uses local updates without remote push notifications.
The displayed status may be visible to others who can see your screen. You can control Live Activities in iOS; dismissing one does not stop trip recording.
Maps
The App uses Apple Maps to show maps: the position card, route thumbnails and the map in the drive review. To draw them, your iPhone downloads map data for the areas shown from Apple, so Apple may learn which areas are displayed. Apple handles this under its own privacy policy, and we do not receive it.
While recording a trip, or when generating a route map if its country code is still missing, the App may send one recorded location from that trip to Apple’s reverse-geocoding service to identify its country or region. The resulting country code is stored with the trip on your iPhone and reused for route maps and thumbnails.
Maps inside custom instruments may likewise request map data for their displayed areas from Apple.
Problem reports
From a trip’s More options menu, choose Report a problem. In Upload trip data?, choose:
- Send feedback directly opens an email draft without uploading trip data or adding a file UUID.
- Upload and send feedback requires an internet connection and uploads the complete trip, including precise locations and sensor data, to private Alibaba Cloud OSS storage in Singapore. After a successful upload, an email draft includes the file UUID as a reference, not a ZIP attachment.
Both email drafts include the trip’s start date and time in the subject. Neither attaches a trip file; only the upload option adds a file UUID.
The report file contains the trip's full recording: its start and end time, the route with precise positions and times, speeds, raw motion and compass data, the calculated readings, events and scores, and technical details such as the version of the App's algorithms.
When you send the email, we receive your email address, the subject with the trip’s start date and time, and whatever you write. If you chose to upload, the email also includes the file UUID. We use reports only to investigate and fix the problem you describe and to improve the App's measurements. With location and other identifying details removed, we may keep short excerpts of sensor data to test future versions of the App.
The upload happens before you send the email. Keep the file UUID in the draft so we can find the report. Cancelling the email or deleting the trip or App does not delete an uploaded report. To request its deletion, contact support@capdrive.app with the file UUID.
Contacting us
When you write to us, we receive your email address, your message and anything you attach, and use them to answer you. Email is not always encrypted end to end, so only send information you are comfortable sending by email.
Apple services
The App is distributed through the App Store, which Apple operates under its own terms and privacy policy. We do not receive your Apple Account, name or payment details. If you have chosen in iOS to share analytics with app developers, Apple may provide us with crash reports and aggregated usage statistics that do not identify you directly. You can change this in Settings › Privacy & Security › Analytics & Improvements.
Why we process data
The App processes location and motion data on your iPhone to provide the features you use: measuring, recognizing driving, and recording and showing your trips. We can access only trip reports you explicitly upload, even if you do not send the email.
We process data that you send us, such as problem reports and emails, to reply to you, to investigate and fix problems and to improve the App.
Where the law requires a legal basis, we rely on the performance of our agreement with you to provide the App, on your consent when you allow location access or choose to send us a report or email, and on our legitimate interest in keeping the App working correctly. We do not sell your data. Driving records are not used for advertising or profiling; app advertising measurement is described above.
We also process guest account identifiers and purchase information to provide, verify and restore Plus access and protect the subscription service against misuse.
Who receives data
We do not share your data with others, except with:
- Apple, which provides maps and the App Store and, if you have enabled it, crash reports and analytics, under its own terms;
- the email provider that hosts our mailbox and receives the reports and emails you send us, and your own email provider, which sends them;
- authorities, where the law requires us to disclose data, or where this is needed to protect the rights and safety of users or others.
- RevenueCat — CapDrive Plus (Privacy Policy).
- Meta Platforms — Meta SDK (Meta Privacy Policy).
- Alibaba Cloud OSS, which privately stores the complete trip reports you choose to upload in Singapore, including precise locations and sensor data;
- the apps or destinations you select to share images, routes or instrument files, which handle received copies under their own rules;
How long we keep data
Deleting a trip or the App does not delete server-side guest or purchase records, or cancel an Apple subscription. For requests about these records, contact support@capdrive.app. Apple and RevenueCat process purchase records under their own policies.
Saved trips remain until you delete them or the App. Deleting a trip removes its database records, raw data and cached route images. Preparing a report also creates temporary export files; these are replaced at the next export or may be cleared by iOS, and are removed when you delete the App. Deleting a trip does not recall copies saved in mail drafts, sent emails or recipients' mailboxes. Contact us to request deletion of a copy you sent us.
We keep problem reports and emails only as long as we need them to handle your request and to investigate and fix the problem, and then delete them. Excerpts kept for testing contain no location or other identifying details.
The same retention standard applies to uploaded reports even when no email is sent. You can request deletion at support@capdrive.app using the file UUID.
Route export creates a temporary file locally, which is cleaned up when its share sheet closes or you leave the review. Copies saved by recipients are unaffected.
International transfers
We are established in the country named at the end of this page, where the reports and emails you send us are processed. Our email provider may also process them in other countries. Where data protection law applies to such transfers, we rely on the safeguards that law provides.
Uploaded trip reports are stored by Alibaba Cloud OSS in Singapore and may be accessed by us from our place of establishment to investigate your report. This can involve transferring trip data outside your country or region.
Your choices and rights
When you are not driving, pull down and release the dashboard to pause recording; repeat to resume. Stop ends the current trip and allows automatic recording to continue. In Settings, you can prevent new trips from starting in the background; an ongoing trip continues recording.
- You can change location access and Precise Location in iOS Settings for CapDrive. Turning them off limits readings and recognition; it does not necessarily stop all motion processing. Close the App to stop recording.
- You can stop recording at any time by closing CapDrive in the App Switcher.
- You can delete a trip in its drive review, and all trips by deleting the App.
- You decide whether to send us a report or email, and what it contains.
Depending on where you live, you may have the right to access, correct or delete your personal data, to receive a copy of it, to object to or restrict its processing, to withdraw your consent and to complain to a data protection authority. Your trips stay on your iPhone, where you can view and delete them yourself. We can access only trip reports you explicitly upload, even if you do not send the email. For data you have sent us, write to support@capdrive.app. We may ask for details, such as the address you wrote from and roughly when, to find it, and we will reply within the time the law requires.
Children
The App is intended for drivers and is not directed at children under 13 years of age, or the higher age required where you live. We do not knowingly receive data from children. If you believe that a child has sent us data, contact us and we will delete it.
This website
When opened from the App, a support link may contain your guest UUID. It stays in the URL, follows help/legal links and pre-fills support-email drafts; it is not saved in browser storage. The website host may receive it in request URLs. Preparing a draft does not send an email.
Our help and legal websites do not set cookies or load advertising analytics or tracking scripts. The help site stores your light/dark theme preference locally in your browser; it contains no guest UUID and is not used for advertising measurement. Help language follows browser preferences or the language URL you choose; legal language follows browser preferences. Help search runs in your browser against a downloaded language index, without sending search text to our search service.
Help and legal links in the App open in Safari. The page host may retain technical access logs, such as request IP addresses and times, for security. The browser's own data handling depends on its settings and rules. Email links open your own mail app.
Changes to this policy
We may update this Privacy Policy when the App, our providers or the law change. The date at the top of this page shows when it was last updated. Material changes are announced on this page or in the App before they take effect.