Contents
Who we are
Vex Technologies Inc. operates Trace.
This Privacy Policy applies to the Trace iPhone application, Trace account services, public Trace sharing pages, and the Vex website pages that link to it. “Trace,” “Vex,” “we,” “us,” and “our” refer to Vex Technologies Inc., a New York corporation.
Trace is currently intended for an initial United States App Store release. This Policy describes the current release and the connected services configured for it. It does not apply to a third-party service you visit or use under that provider's own terms and privacy notice.
Questions and privacy requests may be sent to support@builtbyvex.com.
What we collect
Trace processes account, drive, vehicle, social, and service data.
| Category | Examples | Why it is used |
|---|---|---|
| Account and identity | Apple or Google provider identifier; or, if you sign in with email, your email address, your password (stored only as a one-way hash by our authentication provider) and the time you confirmed the address; name, email address or relay address, username, profile photo, account settings, policy acceptance, and the time you confirm you are 18 or older (not your date of birth) | Sign-in, account security, profile, support, and legal records |
| Drive and sensor data | Precise location, route points, timestamps, accuracy, speed, distance, elevation, motion and fitness signals, derived driving events, and recording state | Record, recover, map, summarize, and privately preserve drives |
| Live drive sharing (only after you turn it on) | While you record or navigate a drive: your precise position, speed and direction, a short trail of recent positions, whether you are driving or navigating, the 3D vehicle you drive with, and, while you navigate, the route ahead, its remaining distance and your arrival time; plus who each share went to (friends, or clubs you chose) and when it started and ended | Show your drive to the friends and clubs you choose while it happens |
| Garage and user content | Vehicle year, make, model, trim, color, nickname, VIN, odometer, modifications, maintenance, notes, selected photos or videos, car cut-outs made on your iPhone, and share designs | Maintain the vehicle record and create features you choose |
| Social and sharing | Profile visibility, aggregate Stats visibility, Ghost mode periods, friend relationships, blocks, reports, club activity, leaderboard participation, selected route shares, public vehicle-card settings, referrals, and optional contact-discovery data | Provide the social or sharing action you request and protect the community |
| Commerce | Product, transaction, renewal, expiration, refund, revocation, entitlement, and purchase-validation records | Offer and verify Trace Pro when available |
| Device and service data | App version, device or installation identifiers, permission state, language, settings, diagnostics, security events, and feature interactions | Operate, secure, debug, and improve Trace |
| Support and website data | Name, email, organization, inquiry type, message, correspondence, ordinary request logs, and a short-lived abuse-prevention hash | Respond to requests and protect the website and service |
Trace saves your 18-or-older confirmation and the applicable policy version with a server timestamp; it does not ask for a date of birth for this confirmation.
Trace receives information directly from you, from your iPhone and permissions, from Apple or Google when you sign in with them, from Apple when you purchase or manage a subscription, from people who interact with you in Trace, and from the providers listed below.
Location
Complete drives may require precise background location.
Manual recording uses precise location and motion while a drive is active. If you enable automatic recording and grant the required permissions, Trace may use precise location in the background, including while the screen is locked or another app is open, and Motion & Fitness signals to distinguish vehicle travel from walking or stationary time.
The automatic-recording preference may appear enabled for a new account, but monitoring does not begin until you grant Always and Precise Location, Motion & Fitness, and the required device authorization. You can turn automatic recording off in Trace or change permissions in iOS Settings. Force-quitting Trace and iOS background limits can prevent recording.
Exact routes can be stored on your device and privately in your verified account. They are not made public merely because a drive was recorded. Live drive sharing, described in section 08, sends your position to other people only after you turn it on, and only while you record or navigate a drive. GPS, motion, elevation, distance, speed, and derived performance values are estimates and may be delayed, incomplete, or wrong.
Storage
Local records and private account persistence are separate from public sharing.
- Verified account required. Trace uses Sign in with Apple, Sign in with Google, or an email address and password. An email account works only after you enter the code we send to confirm the address, and we send a code again if you reset your password. Trace does not provide a guest account.
- Local first. Active and completed drive records, Garage information, selected media, and settings can be stored in an account-scoped area on your iPhone. Drives and Garage changes save there first, then sync to your account when a connection is available.
- Car cut-outs stay on your iPhone. When you add a vehicle photo, Trace can lift the car out of the background so it can be shown on its own, for example in Garage, on share cards and in the Garage widget. This uses Apple's on-device Vision framework. The cut-out is saved next to the original photo in Trace's storage on your iPhone, is excluded from iCloud backup, and a smaller copy is kept where the Home Screen widget and Live Activity can read it. Cut-outs are not uploaded to Trace or sent to Apple, and are not used to identify people. A cut-out is deleted with the photo it was made from, or when Trace's data on the device is deleted.
- Private account persistence. Eligible completed drives, routes, metrics, vehicle records, Garage history, private VIN and ownership fields, and selected sanitized media may be stored with Supabase so the verified owner can recover them. This is a standard account feature, not a Trace Pro benefit.
- Plan limits do not delete history. A plan can limit which drives you can open, not what Trace keeps. Older drives stay saved in your account, and export and deletion are account rights, not Trace Pro benefits.
- Detailed drives and raw routes are private. Recording does not publish the detailed record or route. However, when your profile and Stats visibility allow it, accepted friends can receive activity facts for eligible completed drives—completion time, distance, duration, and an available public vehicle summary—without a separate per-drive feed switch.
- Live drive sharing begins off. Trace asks before sharing a drive live with friends, and each club is a separate choice.
- Profile and aggregate Stats. New profiles and aggregate Stats can begin visible to other Trace users. You can change them to Private in Privacy Controls.
- Garage build visibility. A newly created vehicle can begin with Public selected in the vehicle editor. Review the visibility before saving. Private VIN, odometer, notes, routes, raw photos, maintenance, and modification history are not part of the current public-card payload.
- Product analytics begins off. Mixpanel processing begins only after you opt in.
- Mapbox telemetry begins off. Optional Mapbox telemetry is a separate control. Necessary map requests still occur when you use maps.
Heatmap
Global heatmap contribution is off until you choose it.
Global heatmap addendum, effective October 5, 2026 (heatmap-global-permanent-v3). This optional feature now permits a cell to appear with one eligible contributor and keeps contributed history without an age-based expiry. It requires a new, explicit global heatmap choice in the app; accepting the general policy or an earlier heatmap choice does not enable it. Earlier global enrollment is reset rather than carried into this policy. Friends heatmap sharing remains a separate choice under its existing rules.
Private drive recording works with global heatmap contribution off. If you expressly enable the current global choice, Trace removes at least the first and last 60 seconds and 500 meters along the route. It also excludes cells that touch the 500-meter departure or destination privacy areas, including when the route returns to those areas. Trace converts the remaining path into H3 resolution-8 route cells on your device before submission. The private contribution remains associated with your Trace account and is privacy-reduced, not guaranteed anonymous.
A cell is eligible for the public global heatmap only after at least 24 hours from submission and when at least one eligible contributor has shared it. Public output omits account identity, raw coordinates, raw routes, exact contributor count, vehicle identity, and speed. Trace retains private account-linked coarse cell contributions, receipt timestamps, and idempotency records so it can remove your contributions later; the global contribution payload does not contain raw route coordinates. Eligible public cells and these private receipts do not expire merely because they are old.
You can turn global contribution off in Privacy Controls. Turning it off deletes your retained global contributions and immediately invalidates their affected public cells; cells contributed by other eligible people can be rebuilt from their independent contributions. Contribution deletion and account deletion also retract the affected history. Changing global contribution does not change your friends heatmap choice, and Ghost mode does not change it either. Trace's viewer cache uses a short server lease capped at 60 seconds; permanent storage does not grant indefinite access to a withdrawn contribution through Trace. Trace cannot recall a screenshot or external copy already created.
How we use it
We use information to provide, secure, and support Trace.
- authenticate the correct account, including sending email confirmation and password-reset codes, and keep account data separated;
- record, recover, finalize, map, organize, and privately preserve drives and Garage records;
- apply privacy, sharing, social, safety, notification, and subscription choices;
- provide friends, clubs, leaderboards, reports, blocks, referrals, public cards, live drives you turn on, and selected share features;
- process an optional heatmap contribution or optional product analytics only after the applicable choice;
- present and verify purchases and entitlements when Trace Pro is offered;
- produce a requested account export or deletion workflow;
- prevent fraud, abuse, unsafe use, and security incidents; comply with law; and enforce our terms; and
- answer support, privacy, safety, and website inquiries.
Trace does not sell personal information, share it for cross-context behavioral advertising, display targeted advertising, or use identified drive, location, or vehicle records to train a general-purpose artificial-intelligence model.
Providers
Selected providers process only the data needed for their role.
| Provider | Role | Typical information |
|---|---|---|
| Supabase | Authentication, database, private storage, server functions, policy acceptance, social controls, live drive relay, exports, deletion, heatmap processing, and entitlement state | Account identifiers and the private account or feature data described in this Policy |
| Apple and Google | Supported account sign-in | Provider identity assertion and account details you authorize |
| Apple App Store and StoreKit | Products, purchases, renewals, refunds, subscription management, and transaction verification | Product and transaction evidence; Vex does not receive your full payment-card number |
| Mapbox | Map display, styles, geocoding, directions, and related map functions | Map requests and approximate or precise location needed for the chosen map function; optional telemetry only when enabled |
| Mixpanel | Optional product analytics | Account UUID, plan type, onboarding state, selected settings, and allow-listed interaction or first-drive measurements; no raw route, contact list, VIN, or vehicle detail |
| Superwall (retired integration) | Historical paywall presentation in earlier builds; absent from build 24 | Earlier builds could send the Trace account identifier and plan or subscription context. Earlier server forwarding could also send signed Apple purchase notifications. Disabling the integration does not erase historical provider records. |
| NHTSA vPIC | Vehicle make and model discovery | Catalog queries; Trace does not currently send VINs to vPIC |
| NASA GIBS | Map imagery used by selected map experiences | Ordinary imagery requests needed to render the selected map layer |
| Apple platform services | iOS permissions, notifications when enabled, Live Activities, Photos actions, on-device Vision processing, and device services | Information required by the selected Apple feature |
| Netlify and Resend | Website hosting, isolated subscription verification, network delivery, contact-email delivery, account confirmation and password-reset email for email sign-in, and moderation alerts | Ordinary request logs, bounded subscription-verification requests, contact-form fields, your email address and one-time codes for account email, and aggregate moderation queue counts |
Operational clarification, October 5, 2026. Build 24 uses Trace-owned paywalls and Apple StoreKit; it does not initialize the Superwall SDK or send account identity or plan attributes to Superwall. Trace retired server forwarding to Superwall on October 3, 2026. Older installed builds may retain their original SDK behavior. Historical provider records require separate erasure confirmation; removing the integration is not confirmation that those records were deleted. Contact support@builtbyvex.com for a request concerning historical processing.
Settings › About › Acknowledgements lists the open-source software, fonts and data sources Trace is built with, and their licenses. The list is part of the app and loads without contacting anyone. If you tap a source, it opens that organization's website in your browser, under that site's own practices.
Providers may process information under our instructions and their own security and legal obligations. Independent destinations you choose—such as a social network, messaging app, or a person who receives a share—operate under their own practices.
Retention
Retention follows the feature, your choices, and legal needs.
| Information | Retention approach |
|---|---|
| Local drives, routes, Garage records, and media | Until you delete the record or account data, clear app data, or uninstall, subject to Apple-controlled backup and Keychain behavior |
| Recently deleted drives and vehicles | Removed from your Trace account when you delete them. A copy stays on your iPhone, in Settings › Privacy & Data › Recently Deleted, for 30 days so you can restore it, then it is removed. Deleting your account or Trace's data on the device removes it at once. Merged or split trips, and drives without a recorded route, are not kept |
| Car cut-outs | On your iPhone until the photo it was made from is deleted, or Trace's data on the device is deleted; excluded from iCloud backup; not stored by Trace's servers |
| Exported share images and films | Trace's working copy on your iPhone is removed within 24 hours; copies you save to Photos or share are kept by you or the recipient |
| Ghost mode periods | On your iPhone for the account; each affected drive keeps its hidden-from-friends mark for as long as the drive exists |
| Private hosted account records | While your account or the record remains active, then deleted through the applicable record or account process, subject to security, legal-hold, and backup limits |
| Raw recovery checkpoints | Normally removed after a drive successfully finalizes; an interrupted checkpoint can remain until finalized, discarded, or deleted |
| Live drive positions | Kept on Trace's servers only while the share runs; each position expires two minutes after its last update and is then deleted, so a car that stops updating disappears from other people's maps |
| Live drive share records (when a share started and ended, and which friends or clubs it went to) | Until your account is deleted. A person's audience entry is removed at once if you unfriend or block them, and a club's entry when you leave the club or turn its sharing off |
| Private global heatmap contributions and receipts | Account-linked coarse cells, timestamps, and idempotency records have no age-based expiry while the contribution remains active; removed through contribution deletion, global opt-out, or account deletion. No raw route coordinates are included in this contribution payload. |
| Public global heatmap cells | No age-based expiry while at least one eligible contribution remains. Withdrawal or deletion invalidates affected cells; independent contributions may be rebuilt. Viewer leases expire within 60 seconds. |
| Selected friend route shares | Configured to expire after 30 days; the shared preview removes endpoint areas |
| Diagnostics | Configured for up to 30 days where the diagnostic path is enabled |
| Account export archive | Configured to expire after seven days; temporary download links are short-lived |
| Purchase, fraud, security, moderation, and legal records | For the period reasonably needed to validate transactions, protect the service, resolve disputes, meet legal obligations, and document requests |
| Support and website messages | For the period reasonably needed to respond, maintain support history, prevent abuse, and meet legal obligations |
Deletion from active systems and expiration from backups may occur at different times. We use retention criteria that consider the feature requested, account status, user choice, security and fraud prevention, dispute resolution, and legal or accounting obligations.
Your choices
Privacy Controls separate recording, visibility, analytics, maps, and sharing.
- change profile and aggregate Stats visibility;
- turn on Ghost mode to keep drives you record out of what friends and other drivers can see, without stopping recording;
- turn live drive sharing with friends on or off in Settings › Privacy & Data, and choose each club separately on the club's screen or in Settings › Privacy & Data › Live drives in clubs;
- hide other people's live drives from your own map in Map Layers › Friends › Live drives;
- keep detailed drives and raw routes private, while recognizing that eligible completed-drive activity facts can appear to accepted friends when profile and Stats visibility allow;
- leave heatmap contribution, contact discovery, product analytics, and optional Mapbox telemetry off; use their separate controls to disable them later, including “Turn off contact discovery” in the Friends contact-discovery panel;
- manage automatic recording and iOS Location, Motion & Fitness, Contacts, Photos, and notification permissions;
- join or leave eligible leaderboards and clubs, revoke a public vehicle card, stop an eligible route share, and block or report accounts;
- request an account export of eligible hosted records and separately preserve local-only records;
- restore a drive or vehicle you deleted in the last 30 days from Recently Deleted, which puts it back on your iPhone and in your Trace account; and
- start account deletion in the app, as described in section 12, or contact support if the control or a processing step is unavailable.
Your rights
You can access, correct, export, and delete your information.
Several U.S. states give residents rights over their personal information. Trace offers these choices to every U.S. user, whether or not a particular state's law applies to Vex:
- Know and access. Ask what personal information we hold about you and receive a copy.
- Correct. Fix inaccurate information in the app where you can edit it, or ask us to correct it.
- Delete. Delete your account and associated information as described in section 12.
- Portability. Export eligible account data in a portable format from Profile → Account → Export Account Data.
- Opt out. Trace does not sell personal information, share it for cross-context behavioral advertising, use it for targeted advertising, or use it for profiling that produces legal or similarly significant effects, so there is nothing to opt out of today. If that changes, we will ask first or offer an opt-out as the law requires.
Sensitive information. Precise location is sensitive information under several state laws. Trace processes it only after you grant location permission, and only to provide the features you use, such as recording, maps, directions, and live drives you turn on. It is not sold, used for advertising, or used to infer other sensitive characteristics. You can withdraw location permission in iOS Settings, which stops the features that need it.
How to make a request. Use the in-app controls where they exist, or email support@builtbyvex.com with the subject “Privacy request.” We verify requests by asking you to confirm control of your Trace account or email address, and we will not ask for more information than we need. An authorized agent may submit a request with your written permission; we may still ask you to confirm your identity directly. We respond within 45 days and may extend that once by up to 45 more days where the law allows, telling you why.
Appeals. If we decline a request, reply to our decision with the subject “Privacy appeal,” and we will respond within 60 days. If you disagree with the outcome, you may contact your state attorney general.
No discrimination. We will not deny service, charge a different price, or provide a different quality of service because you exercised a privacy right. Trace does not disclose personal information to third parties for their own direct-marketing purposes.
Account deletion
A request is complete only after Trace confirms completion.
Current status. Trace includes an account-deletion flow, and the connected cleanup process is designed to remove account data across active Trace systems and applicable providers. Those connected services are still being activated and tested. A submitted or pending request is not proof of deletion: until successful end-to-end completion is verified, a queued, pending, signed-out, or locally cleared state is not proof that hosted data or provider records have been erased. Rely only on the status shown in Trace or a completion confirmation from support. No completion period is published yet; we will publish one after end-to-end activation and testing are complete.
Before you begin. While safely parked, open Profile → Account → Export Account Data and verify the downloaded archive when the export feature is available. The server archive covers enumerated server-held records; it may not contain an active checkpoint, pending media, or another local-only item on this iPhone. Finish, discard, save, or separately preserve local-only work before deletion or uninstalling. Deletion is intended to be irreversible after completion.
Start in Trace.
- Open Trace and sign in to the account you want to delete.
- Open Profile, then Account, then Delete Account.
- Select Begin Account Deletion.
- When asked, confirm it is you by signing in again with the same method you use for Trace: Apple, Google, or your email and password.
- Read the scope and Apple subscription reminder, then confirm only when ready.
The in-app path is the primary method because it binds the request to the verified account. If you cannot sign in or the control does not work, email support@builtbyvex.com with the subject “Trace account deletion help,” the app version, your sign-in method, and the step that failed. We must verify account ownership before acting on an email request, and an email alone is not proof that deletion occurred. Do not send a password, one-time code, authentication token, full Apple receipt, or raw route.
What completion covers. The completed workflow is designed to remove or de-identify the Trace authentication user, profile, visibility and privacy settings, contact-discovery state and hashes, social relationships, clubs and Territory records, blocks, reports where deletion is lawful, drives and route records, live drive share records, Garage and vehicle data, hosted media, public vehicle cards, heatmap submissions, feature state, provider tokens, and eligible analytics identity associated with the account. Local cleanup removes the account namespace, Recently Deleted copies, and app-held session or feature state on the participating device. Apple-controlled backups, Keychain behavior, another device, and copies outside Trace can follow separate lifecycles.
What may remain. Vex may retain the minimum records reasonably needed to document and complete the request, prevent fraud and abuse, resolve disputes, protect security, comply with tax or accounting rules, respond to lawful process, and honor a legal hold. Deleted data can also remain temporarily in restricted backups until those backups age out under ordinary cycles. Public or friend copies, screenshots, exports, files sent through another app, social-network posts, and other material already held by another person are outside Trace and cannot be recalled.
Apple subscriptions. Deleting a Trace account does not cancel an Apple subscription or automatically create a refund. Manage or cancel Trace Pro separately through Apple Subscriptions; Apple handles cancellation and refund requests under its rules.
Pending, failed, and complete. A request may remain pending while active Trace records, private storage, authentication, analytics identity, or provider tokens are processed. A request is complete only after the authoritative workflow reports completion and Trace or support provides a completion confirmation. Contact support@builtbyvex.com for the status of a request, preferably from the address associated with your account.
Age
Trace is for adults age 18 and older.
Trace is not directed to children and does not offer a child or parental-consent account. New and existing members must explicitly confirm that they are 18 or older when accepting the updated agreements; we retain the confirmation and server timestamp, not a date of birth. You must be at least 18 years old to create or use a Trace account. If we learn that a person under 18 provided personal information, we may close the account and delete the information as required by law. A parent or guardian may contact support@builtbyvex.com.
Security
We use layered safeguards, but no system is perfectly secure.
Trace uses measures such as account-scoped local storage, Keychain session storage, encrypted network transport, row-level database rules, private storage authorization, server-side validation, reduced public projections, and purpose-limited provider access. No method of storage or transmission is completely secure, and we cannot guarantee uninterrupted availability or absolute security.
If you believe your account or Trace data is at risk, contact support@builtbyvex.com. Do not email passwords, one-time codes, authentication tokens, complete payment details, or raw route files unless support gives you a secure way to provide specifically requested information.
Changes & contact
Material changes receive notice and a new review.
We update the date and policy version when this Policy changes. For a material change, Trace asks you to review and accept the new version in the app before you continue using account features, and we may also give notice on the website, by email, or through another appropriate channel. Where consent is required for a new purpose, we will request it separately rather than treating continued use as consent. Earlier versions are available on request.
- Operator
- Vex Technologies Inc.
- Formation
- New York, United States
- Privacy, security, and rights requests
- support@builtbyvex.com