Effective date: 2026-09-30
SameDrive is provided by Dvelop42 ("we," "us," or "our"). This Privacy Policy describes how information is handled when you use the SameDrive iPhone and iPad app and contact us for support.
SameDrive helps you review and compare your existing driving history. Its current version processes that history on your device and offers optional synchronization through your Apple iCloud account. You do not create a separate SameDrive account.
When you connect Tessie, the app requests information directly from Tessie using the access token you supply. Depending on the records available, this includes:
Vehicle identifiers, including the vehicle identification number (VIN), and vehicle names.
Drive identifiers, departure and arrival times, trip distances, energy consumption, battery usage, and recorded temperature.
Departure and arrival coordinates, address labels, and recorded GPS paths. This information can reveal precise locations, including places you visit regularly.
Names you assign to places and paths, selected or hidden routines, and other preferences.
Derived information, such as routine and path groupings, historical comparisons, and monthly summaries.
Local operational records needed to resume an interrupted import, avoid duplicate notifications, and synchronize changes.
SameDrive reads historical location information supplied by Tessie. It does not request access to your device's current location or independently record your movements. The app does not send vehicle-control commands.
Your Tessie access token is stored in the device's Keychain using a device-only accessibility setting. It is sent to Tessie over HTTPS to authorize requests. SameDrive does not include the token in its iCloud synchronization or send it to Dvelop42. The permissions associated with the token itself are determined by Tessie.
The app uses this information to import and display your history; recognize journeys and similar recorded paths; calculate comparisons and summaries; apply your names and preferences; resume imports; synchronize information when enabled; and provide notifications when authorized.
Routine and path classifications are generated on your device. They may be incomplete or inaccurate and are intended to help you explore your own records, rather than make decisions with legal or similarly significant effects about you.
Imported history, downloaded paths, local import checkpoints, and synchronization state are stored in the app's private storage. These files use iOS file protection and are marked for exclusion from ordinary device backups. A separate, protected copy of user-created place and path names, selected or hidden routines, and related edit metadata is eligible for device backup. This copy includes the identifiers and place coordinates needed to associate your edits with restored driving history, but does not contain downloaded drive records, full GPS paths, or your Tessie access token. It can be included in an iCloud or computer backup according to your Apple device and backup settings, independently of whether SameDrive's optional iCloud synchronization is enabled. Preferences such as distance units are stored separately in the app's settings. Device security, backup availability, and restoration also depend on your passcode, operating system, and account settings.
If you enable iCloud synchronization, the app sends saved drives, downloaded paths, vehicle information, place and path names, and routine choices to an Apple-hosted private CloudKit database associated with your Apple Account. This allows your other devices using that account to synchronize that information. Network and synchronization metadata needed for the service are also handled by Apple.
Tessie tokens, notification preferences, and distance-unit preferences are not part of SameDrive's CloudKit synchronization. Turning synchronization off stops further synchronization on that device; it does not delete copies already stored locally or in iCloud.
Dvelop42 does not operate a server that receives your driving library. This does not mean that data never leaves your device: Tessie requests, optional iCloud synchronization, and Apple map requests involve the providers described below.
Tessie: The app communicates directly with Tessie to retrieve vehicles, drives, and recorded paths. Requests include your access token and the relevant vehicle identifiers and time ranges. Tessie can receive network information such as your IP address. Its own handling of your Tessie account and original vehicle records is described in the Tessie Privacy Policy.
Apple: Apple supplies iCloud, CloudKit, Keychain, notifications, the App Store, and map services. Displaying maps can send the requested map area and technical request information to Apple. SameDrive does not request your current location for these maps. Apple's services are described in the Apple Privacy Policy and Apple Maps privacy information.
Support: If you contact Dvelop42, we receive the contact details, message, and any attachments you choose to send. We use these to respond and investigate the issue. Our communication provider may process them to deliver and store the correspondence. Please remove unnecessary location details and never send access tokens or passwords.
Platform diagnostics: Apple may provide developers with crash reports, diagnostics, or App Store statistics under its platform settings and policies. SameDrive has no separate third-party analytics or crash-reporting SDK.
Legal obligations: We may disclose information in our possession when legally required, or when reasonably necessary to respond to a security incident or protect lawful rights. This does not give us access to a driving library that we do not possess.
The current app has no advertising SDK, advertising identifier access, cross-app tracking, or third-party analytics SDK. We do not sell personal information, share it for cross-context behavioral advertising, or use your driving history for advertising or AI model training. Providers also have responsibilities under their own policies and applicable law; this policy describes the processing performed by SameDrive and Dvelop42.
Saved history: The app keeps your imported history and edits until you remove them. In Settings, Delete local history removes the saved library and downloaded paths on that device, clears its drive notifications, and pauses imports and iCloud synchronization. It also initiates removal of local import checkpoints and synchronization caches. It does not revoke or remove the Tessie token, delete other devices' copies, erase the iCloud copy, or alter the original Tessie records.
Tessie connection: Disconnect Tessie removes the stored token from that device and stops its imports and drive notifications. Saved history and iCloud synchronization are retained. To invalidate the credential itself, revoke it in Tessie; to remove tokens stored on other devices, disconnect those devices too.
iCloud data: You can manage and delete SameDrive's iCloud data through Apple's iCloud storage controls, where available. Before removing the cloud copy, turn synchronization off on all devices so an existing local library does not upload again. Deleting cloud data does not automatically delete every local copy. Apple's retention and deletion processes apply to its systems.
Original Tessie records: Manage or delete these through Tessie. Actions in SameDrive do not delete or modify them.
Notifications: Disable drive notifications in SameDrive or use iOS notification settings. Notifications can display place names and comparison details on the lock screen; use iOS preview settings to control their visibility.
Support and diagnostics: We retain information we receive only as needed to resolve requests, maintain necessary support or security records, and meet applicable legal obligations. When those purposes no longer apply, we delete or de-identify it, subject to any remaining legal retention requirement and the applicable provider's backup lifecycle.
Disconnect before uninstalling if you want to remove the Keychain token. Uninstalling alone should not be relied upon to revoke a token, erase iCloud data, or remove information held by Tessie. Restoring or importing again can recreate a local copy of records that remain with those services.
Depending on where you live, you may have rights to request access, correction, deletion, or a portable copy of personal information; restrict or object to certain processing; withdraw consent; or complain to a data-protection authority. Contact us using the details below. We may need proportionate information to verify and respond to a request. We will not discriminate against you for exercising an applicable privacy right.
We can respond concerning information we actually hold, such as support correspondence. For information stored only on your devices or in your Apple or Tessie account, we can explain the available controls or direct you to the relevant provider. SameDrive does not currently provide a general in-app data export function.
Where applicable law requires a legal basis, processing depends on the activity: providing features you request, your authorization or consent for optional services, legitimate interests in responding to support requests and maintaining security, or compliance with legal obligations. Withdrawing consent does not undo processing that was lawful before withdrawal.
Apple, Tessie, and communication providers may operate in countries other than yours. Their international transfers are governed by the arrangements and safeguards described in their policies and applicable law.
We use the platform protections described above, but no device, network, or storage system can be guaranteed completely secure. Protect your device and Apple Account, keep your software updated, and revoke exposed Tessie tokens promptly.
SameDrive is not directed to children under 13 or a higher minimum age required by local law. We do not knowingly solicit their personal information. If you believe a child has supplied personal information to us, contact us so we can address information in our possession and help identify the appropriate device or provider controls.
We may update this policy as the app or its data practices change. We will update the effective date and provide notice of material changes through the app or another appropriate channel. Where required, we will obtain consent before applying a new use of personal information.
Privacy questions and requests: Dvelop42 — dvelop42@gmail.com.
External websites opened from the app have their own data practices. This policy describes the app and our support handling; any additional website cookies, analytics, or hosting logs must be covered by the notice applicable to that website.