DriverTake Privacy Policy

1. Information DriverTake Handles

Location and trip movement

When you grant permission and an eligible trip is active, DriverTake can process and save precise latitude and longitude, time, horizontal accuracy, altitude, speed, course, recorded route points and segments, distance, trip start and end times, and pickup, drop-off, origin, destination, or planned-stop labels and coordinates.

DriverTake uses Core Location for mileage and route recording. When automatic drive detection is enabled, it can also use significant-location updates. Background location is used for enabled drive detection or an eligible active trip. A short-lived pickup-departure anchor can be stored to help reject false pickup completion.

Motion activity

With permission, DriverTake processes Core Motion activity classifications to decide whether movement is likely automotive. DriverTake does not collect raw accelerometer or gyroscope samples. It saves resulting trip timing and distance, not a motion-history profile.

Driver-entered records

DriverTake can store information you enter or import, including:

• Shifts, trips, work classifications, business purposes, platforms, and notes
• Earnings, payouts, currencies, fuel, tolls, maintenance, other expenses, vendors, and receipt images
• Vehicle nickname, year, make, model, optional license plate, and odometer
• Statement-import identifiers, report settings, and the backups, CSV files, or PDFs you choose to create

You decide what optional text, vehicle, financial, and receipt information to enter. Avoid entering rider names, rider contact information, or other unnecessary personal information about another person.

Preferences and app state

The app stores preferences such as onboarding completion, appearance, units, currency, default platform, notification choice, automatic-drive choice, and temporary guarded work state. iOS supplies permission and notification status. DriverTake does not use an advertising identifier or create a cross-app profile.

2. Apple Maps Share and the App Group Inbox

DriverTake receives an Apple Maps place, link, or address only when you explicitly choose Share or otherwise choose a supported import action. The Share extension can receive the place name, address, original Maps URL, and coordinate supplied by Apple. It validates the item, shows Add and Cancel choices, and, only after Add, writes one versioned envelope to DriverTake's App Group inbox. The inbox is limited to five pending items.

The Share extension does not open the main SwiftData or CloudKit store, start a trip, monitor Apple Maps, read the screen, take over live navigation, or launch DriverTake. The main app revalidates the item and requires separate Use and Save choices. A pending item is removed after it is successfully saved into a stop plan; unapplied items can remain until used or until the app and extension data are removed.

For a supported Apple Maps short link, the extension uses an ephemeral network session and follows at most one permitted redirect to https://maps.apple.com. It does not keep a general browsing history or browser cookie.

3. MapKit, App Intents, Controls, and CarPlay

Recorded route overlays are based on locally saved DriverTake data, while Apple supplies the MapKit basemap and related map services. When you explicitly open Trip Route for a destination with coordinates, DriverTake can ask Apple's MapKit service for one automobile route preview. The source and destination coordinates are sent to Apple to provide that request. The preview is not used as recorded mileage and is not stored as the driven route.

App Intents, Siri, Lock Screen controls, and the CarPlay scene use the same guarded DriverTake work session and action store. They can read current status and, after applicable confirmation and safety gates, request the same work-state changes as the iPhone app. Apple handles Siri speech recognition and system interfaces; ORYAN Studios LLC does not receive a copy of Siri audio through DriverTake.

CarPlay availability requires Apple's managed driving-task capability, compatible hardware, and a correctly signed release. Publication of this policy does not mean Apple has granted that capability or that CarPlay is available in a production vehicle.

The current build includes local OpenStreetMap-derived traffic-control data. Its production download URL is empty, so DriverTake does not currently download traffic-control data from an ORYAN server.

4. How DriverTake Uses Information

DriverTake uses information to:

• Record mileage and route evidence for active work trips
• Maintain your chosen shift, trip, earnings, expense, receipt, and vehicle records
• Detect likely drives and preserve guarded work-state transitions
• Prepare reports, backups, and exports you request from permitted core records
• Display reviewed destinations and optional MapKit route previews
• Synchronize supported records through your private iCloud database only in a cloud-configured build
• Protect data integrity, diagnose local persistence failure, and prevent duplicate imports

DriverTake does not sell information, serve advertising, use third-party analytics, track people across apps or websites, or use data for credit, insurance, employment, or eligibility decisions.

5. Local Storage and Optional Private iCloud Sync

Standard DriverTake release

Standard DriverTake Debug and Release configurations store records in the app's local SwiftData container and do not enable CloudKit. The Apple Maps App Group inbox is a separate local container shared only by the main app and its Share extension.

DriverTake Cloud or CloudRelease configuration

A dedicated cloud configuration can request synchronization through the private CloudKit database associated with your Apple ID and keep a local copy on the device. Simulator builds force CloudKit off. If CloudKit startup fails, DriverTake uses a local fallback rather than silently changing or discarding records. DriverTake does not offer a separate ORYAN account, and ORYAN Studios LLC does not operate a server that reads your private CloudKit records.

6. Exports, Backups, and Sharing

Backups, recovery copies, CSV reports, PDFs, and shared files leave DriverTake's sandbox only when you choose a destination or recipient. Depending on what you export, they may contain routes, destinations, financial data, vehicle information, notes, and receipt images. After export, the selected Files location, recipient, backup service, or other app controls its copy.

DriverTake does not automatically upload an export to ORYAN Studios LLC. Do not send passwords, authorization tokens, full backups, database files, route histories, or receipt images through ordinary email unless ORYAN support gives you a secure, case-specific method.

If provider isolation cannot be verified during startup, a recovery share contains only a diagnostic report and omits the raw database and CloudKit sidecars.

7. Disabled Uber Pre-Alpha Boundary

DriverTake is not affiliated with or endorsed by Uber. DriverTake is not currently connected to Uber, has no current Uber API access, and provides no live Uber authorization, import, or account connection. Uber networking and live OAuth are disabled and unimplemented, and public Release builds do not include the pre-alpha Uber setup screen.

Developer tests use synthetic Uber-shaped fixtures only to verify mapping and isolation behavior; those fixtures are not live Uber data and are not persisted as user records. Safely identifiable legacy imported Uber records are quarantined into a separate local archive excluded from system backup. They do not enter the main SwiftData store, private CloudKit, App Groups, combined totals, charts, reports, exports, full backups, suggestions, widgets, App Intents, or Controls. Ambiguous linked legacy data blocks the operation rather than guessing. A record you manually enter and label Uber remains your user-authored DriverTake record.

Any future Uber feature would require Uber approval, an updated notice and policy, explicit user authorization, reviewed scopes and fields, and completed security and acceptance testing before live data is used.

8. Retention and Deletion

• Core records remain until you edit or delete them, use Delete All Data, remove the app's data, or a legal requirement applies.
• In a cloud configuration, deletions are submitted to your private CloudKit database and may require time and connectivity to synchronize.
• Preferences remain until changed, reset by app behavior, or app data is removed.
• The pickup-departure anchor is cleared on cancel, expiry, completion, state mismatch, or app-data removal.
• Pending Apple Maps items remain until successfully saved or app and extension data are removed; the inbox is capped at five.
• Copies exported outside DriverTake remain under the control of you, the recipient, or the selected service.
• DriverTake currently retains no Uber token or live Uber data. Quarantined legacy Uber records remain in the isolated local archive until Delete All Data or app-data removal.

Delete All Data is available after the active work session ends. It removes the isolated Uber archive and shifts, trips, routes, stops, earnings, expenses, receipts, vehicles, and related SwiftData records from the current store. It does not remove app preferences, pending Maps Share items, iOS permission state, or copies already exported. Removing the app and its data removes its local containers subject to iOS and backup behavior.

DriverTake has no ORYAN product account to close.

9. Disclosure and Security

DriverTake discloses information only to Apple as needed for enabled Apple services; to a destination or recipient you select; when reasonably necessary to protect users, investigate abuse or a security incident, comply with law, or respond to valid legal process; or to a successor entity subject to this policy if the product or company is transferred.

DriverTake uses the iOS app sandbox, SwiftData, an explicit App Group entitlement, bounded input and file-size validation, atomic inbox writes, HTTPS-only network gates, and fail-closed integration flags. No system or transmission method is perfectly secure.

10. Choices and Privacy Rights

You can deny or change Location, Motion, and Notification permissions in iOS Settings. You can disable automatic drive detection and background stop notifications in DriverTake. Disabling a permission can limit the related feature.

Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or objection for personal information controlled by ORYAN Studios LLC. Most DriverTake records are controlled directly on your device or in your private iCloud account. For an ORYAN-controlled support or incident record, email support@oryanstudiosllc.com. We may need to verify your identity.

11. Children and International Use

DriverTake is intended for adults legally permitted to drive and use the services for which they keep records. It is not directed to children, and ORYAN Studios LLC does not knowingly collect children's personal information through DriverTake.

DriverTake supports certain currencies and units, but you are responsible for local driving, recordkeeping, tax, privacy, and platform rules. ORYAN Studios LLC will use safeguards required by applicable law for any ORYAN-controlled personal information transferred internationally.

12. Changes and Contact

ORYAN Studios LLC may update this policy when DriverTake's features, release configuration, service providers, legal duties, or integrations change. The effective date will be updated. Material changes will be presented through an appropriate public or in-app notice when required.

ORYAN Studios LLC
Redkey, Indiana, USA
Email: support@oryanstudiosllc.com
DriverTake support: oryanstudiosllc.com/drivertake/support/