DriveX is operated by Lee Andro. Contact support@drivex.party about your information or this notice.
01Account and profile
DriveX uses your email and account identifier for authentication. Your profile may include a display name, biography and vehicle details. Supabase provides authentication and account storage. Resend delivers account confirmation and password-reset emails and processes the recipient address, email content and delivery information.
02Location and drive recording
With your permission, DriveX uses precise location and Motion & Fitness to detect and record drives. Automatic detection can use location in the background, including while waiting for a drive. Routes include coordinates, timestamps, speed, distance and related trip details. iOS permissions and background execution affect detection and recording.
Personal drives are initially stored on your iPhone. If you enable Private trip backup, explicitly saved personal GPS drives are uploaded to your account. Other participants’ Party tracks are excluded from that private backup.
03Drive Party sharing
Joining and sharing is a separate choice. Authorized Party participants can receive your display name, location, speed, shared route preview and Party history for replay. Stopping sharing stops future updates. It does not recall copies or exports already received by others. Offline devices may retain previously received information.
04Photos, exports and optional Tesla connection
Landmark photos and generated replay videos remain on your iPhone unless you save, export or share them. Your selected destination and operating-system backup service apply their own policies.
If you connect Tesla, authentication takes place with Tesla. DriveX’s Cloudflare backend stores encrypted authorization tokens and requests vehicle information for the enabled features. Tesla access is separate from your DriveX account. Disconnecting this device does not revoke independent connections on other devices. You can manage third-party access through your Tesla account.
05Support correspondence
Support emails and diagnostic files you voluntarily provide are retained while we address your concern and deleted from our support inbox and downloaded working copies within 30 days after resolution. This cleanup is handled manually. Provider backup retention is separate from our working-copy deletion.
When a device owner authorizes a development backup for an app update, we delete that backup within 30 days after verifying that the update succeeded and the trips remain intact. These development copies are separate from optional private trip backups in your DriveX account.
06Retention and deletion
Unsaved local trips are eligible for removal seven days after the trip ends. Saved trips and protected or interrupted recordings are preserved. Local driving totals may retain trip identifiers, distance and duration after an unsaved route expires.
Deleting a local trip does not delete an existing private cloud backup. Use the cloud-backup controls to remove a cloud copy. Disabling future backups leaves existing backups in place.
Delete your account from Drive → Profile → Delete account. This removes the account and its associated active DriveX account data, ends hosted Parties and preserves other participants’ own records. On the deleting iPhone, account-owned trips and recovery drafts, plus unassigned routes, landmark photos, clubs and progress, are removed. Other accounts’ trips remain. A random deletion-confirmation receipt containing no email, account identifier or trip content is retained to recover interrupted deletion.
Account deletion does not remotely erase local files on other devices, exported files or recipients’ copies. Provider backups and operational logs have separate retention; deletion from the active database does not promise immediate removal from every backup. Contact us for retention questions.
Resend currently documents 30-day retention for email and log data on its Free plan, with backups retained for seven days. Its Tokyo sending region determines where mail is sent from; stored data is held in the United States. See Resend’s security and retention information. These provider retention periods are separate from deleting a DriveX account.
DriveX currently uses Supabase Free. Its dashboard confirms that scheduled project backups are not included. Supabase’s published Free-plan limits list one day of API/database logs and one hour of Auth audit logs. These limits describe those specific services, not a promise that all provider-held information is erased within that time. See Supabase’s plan details.
DriveX’s deployed Cloudflare Worker currently has Workers Logs and Workers Traces disabled. Cloudflare may still process platform, security, routing and aggregate usage information. This setting does not mean that Cloudflare holds no operational data.
07Service providers and your choices
Supabase provides account, database and Party services; Cloudflare hosts the website and backend and forwards support mail; Resend delivers account emails. Apple provides platform location, motion and native map services. Browser Party maps may request map tiles from OpenStreetMap. These services receive the information needed to handle requests, which can include network addresses and operational metadata. Support emails are forwarded to an owner-managed Gmail inbox; replies may come from that inbox.
You can manage location, motion, Photos and notification permissions in iPhone Settings, stop Party sharing, manage private backups or delete your account. For access, correction or deletion assistance, email support@drivex.party. Do not email passwords, reset links or authentication codes.