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.
This Policy applies wherever you use Trace, and section 11 explains the rights that depend on where you live. It 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, the time you confirm you are 18 or older (not your date of birth), and, if you answer, how you heard about Trace | Sign-in, account security, profile, support, legal records, and learning how people find Trace |
| Drive and sensor data | Precise location, route points, timestamps, accuracy, speed, distance, elevation, motion and fitness signals, derived driving events, recording state, a drive title made from the street or area names where it starts and ends, and any Business or Personal tag you add | Record, recover, map, summarize, and privately preserve drives, and build mileage logs you request |
| Places and privacy zones | The Home, Work and other named places you save, your 20 most recent destinations (name, address and coordinates), saved when you open directions to a place, and the privacy zones you add (name, center and radius) | Directions and shortcuts on your iPhone and in CarPlay, and keeping live drives, shares and heatmaps away from those places |
| Live drive sharing (on unless you turn it off) | While you record or navigate a drive: your precise position 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, your arrival time, and the meetup you are driving to; plus who each share went to (friends, or clubs you chose) and when it started and ended. Trace shares your speed only while you navigate to a meetup you take part in, and only with your friends in that meetup. Trace also keeps the 3D vehicle you last shared a live drive with on your profile, where anyone who can see your profile can see it. | Show your drive to the friends and clubs you choose while it happens, and record when you arrive at a meetup |
| Garage and user content | Vehicle year, make, model, trim, color, nickname, odometer, modifications, maintenance, notes, social links, selected photos or videos, 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, meetups and arrival times, leaderboard participation, the drives and routes you share with friends, public vehicle-card settings, referrals, notification choices, 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, including the subscription records RevenueCat keeps for Trace | Offer, verify, and keep records of Trace Pro |
| Device and service data | App version, device or installation identifiers, push notification tokens, permission state, language, settings, diagnostics, performance measurements, security events, and feature interactions | Operate, secure, debug, and improve Trace |
| Product analytics (while it is on; see section 04) | The Mixpanel usage events described in section 07, and summaries of drives you record while it is on: distance, durations, stops, elevation, turn and braking counts, average and top speed, and g-force, under a research ID. They omit your name, photos, and exact route. | Understand how Trace is used and improve its features, including its driving analysis and recording quality |
| 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, directly or through RevenueCat, 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, starts on for new accounts; it sends your position only to the friends and clubs it allows, only while you record or navigate a drive, and you can turn it off at any time. 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.
- Private account persistence. Eligible completed drives, routes, metrics, vehicle records, Garage history, private 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. A drive appears in your friends' activity feed only when you share it with them from the drive page.
- Live drives with friends begin on for new accounts. Trace no longer asks first; turn them off anytime in Settings › Account › Privacy & Data. Each club is a separate choice and begins off. An account created before this version keeps its earlier choice.
- Profile and aggregate Stats. New profiles and aggregate Stats can begin visible to other Trace users. You can change them to Private in Settings › Account › Privacy & Data.
- Garage build visibility. A newly created vehicle can begin with Public selected in the vehicle editor. Review the visibility before saving. Private odometer, notes, routes, raw photos, maintenance, and modification history are not part of the current public-card payload. A build page, described in section 08, adds the mods you list and outlines of drives you shared.
- Heatmap contribution and product analytics begin on for new accounts. Global and friends heatmap contribution begins on everywhere, the EEA, the UK, and Switzerland included; turn it off anytime in Settings › Account › Privacy & Data › Heatmaps. Product analytics, which includes Trace's internal research on drive summaries, begins on except in the EEA, the UK, and Switzerland, where it begins off and the permissions page asks once. Change it anytime in Settings › Account › Privacy & Data. An account created before this version keeps its earlier choices. Trace goes by your App Store country or region, or by your iPhone's region when that isn't available, and asks whenever it can't tell.
- No Mapbox telemetry. Trace turns off Mapbox's telemetry on every iPhone, so there is no Mapbox sharing switch. Necessary map requests still occur when you use maps, as section 07 describes.
Heatmap
The global heatmap is aggregated, de-identified data, and you can turn your contribution off.
Global heatmap addendum, effective October 5, 2026 (heatmap-global-permanent-v3). The global heatmap is aggregated, de-identified data: it lights coarse hexagonal areas, about 0.7 km² each, in one of four brightness levels, blended from the drives of many drivers. It shows no names, usernames, photos, vehicles, speeds, dates, times, counts, or single routes. Contributed history has no age-based expiry. Global enrollment from before that date was reset rather than carried into it. From version 5, a new account's global contribution begins on under this addendum everywhere, and you can turn it off at any time; an account created before version 5 keeps its choice. Friends heatmap sharing remains a separate choice under its existing rules.
Private drive recording works with global heatmap contribution off. While global contribution is on, Trace leaves out drives you keep private (recorded in Ghost mode or marked Keep this drive private), deleted drives, passenger and other trips that aren't drives, trips excluded from your stats, imported trips, and trips replaced by a correction. It also leaves out every area inside or touching your privacy zones and every area within about 500 meters of where a drive started or ended, which in practice is about 1 km around each end, and Trace's servers check each contribution against your saved drive before it counts. From the rest it 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 only once at least three different drivers drove through it on the same day; each area then appears once, without a date, at the brightest level it reached. Only signed-in members who accepted the current terms can view the map. 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 Settings › Account › Privacy & Data › Heatmaps. Turning it off deletes your retained global contributions at once and takes the areas they touched off the map; those areas are rebuilt from the remaining drivers within about a minute, and an area left with fewer than three drivers stays off. Keeping a drive private, deleting or correcting it, changing your privacy zones, or resetting your heatmap also removes its contribution. Turning contribution back on adds only drives you upload from then on. Contribution deletion and account deletion also retract the affected history. Changing global contribution does not change your friends heatmap choice. 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.
Friends heatmap contribution is a separate choice in Settings › Account › Privacy & Data › Heatmaps, and it begins the same way as global contribution. Only routes you include when you share a drive with selected friends add coarse areas, with start and finish areas hidden. An area appears after 24 hours and only where at least two friends contribute, and contributions expire after 30 days.
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, meetups, group drives, leaderboards, reports, blocks, referrals, public cards, live drives, and selected share features;
- send the notifications you allow, such as friend requests, accepted requests, and meetup invitations;
- check public text automatically before others see it, and send photos and flagged text to a person for review;
- keep the Business or Personal tags you add and build a mileage log when you ask for one;
- process heatmap contributions and product analytics (which includes internal research on drive summaries) while they are on;
- present and verify purchases and entitlements when Trace Pro is offered, choose which plans the Pro screen lists, and keep subscription records;
- 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.
Product analytics and internal research. Product analytics is on by default for new accounts, except in the EEA, the UK, and Switzerland, where it begins off until you turn it on; you can change it in Settings › Account › Privacy & Data. While it is on, Trace sends the allow-listed usage events described in section 07 to Mixpanel and uses summaries of your new drives, under a research ID, for its internal evaluation of driving analysis and recording quality. The summaries omit your name, photos, and exact route but stay privately linked to your account. This version makes no AI model calls, trains no models, and shares no research with outside organizations. Turning it off stops new sharing on your iPhone at once and, once the change syncs, invalidates research downloads and queues their deletion. Copies already downloaded for authorized internal use cannot be recalled remotely, and turning it off does not remove your drive history.
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, automatic content checks, live drive relay, notification queue, exports, deletion, heatmap processing, research datasets, 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 |
| RevenueCat | Subscription records, purchase and renewal tracking, the plans and offer tests shown on Trace's own Pro screens, and copies of Apple's subscription notifications forwarded to Trace | Trace account ID; Trace Pro product and transaction records; purchase, renewal, expiry, and refund dates; price, currency, and storefront country as reported by Apple; and ordinary app and device request data such as app and iOS version, device model, locale, and IP address. No location, route, vehicle, contact, or analytics data. |
| Mapbox | Map display, styles, geocoding, directions, and related map functions | Map requests needed for the chosen map function: the map area you view, search text with your position rounded to about 100 meters, and the exact start, stops, and destination of directions you ask for. Trace turns Mapbox telemetry off and sends Mapbox no account or drive identifier; the Mapbox SDK still reports the monthly active users that Mapbox counts for billing |
| Apple Maps | Place names for the start and end of each drive, CarPlay place search, and the map behind Share Studio images and videos | The coordinates where a drive starts and ends, CarPlay search text and your approximate area, and the map area of a route you turn into a share image or video; Apple handles these under its own privacy policy |
| Mixpanel | Product analytics, while it is on | Account UUID; a random device ID and the device details Mixpanel's SDK adds, such as device model and iOS and app version; plan type, onboarding state, including how you heard about Trace (its category and any platform you picked, never text you typed), selected settings, and allow-listed interaction or first-drive measurements. IP-based location is turned off. No raw route, contact list, 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 for years, makes, and models; no VIN, account, or location information |
| NASA GIBS | Map imagery used by selected map experiences | Ordinary imagery requests needed to render the selected map layer |
| Apple platform services | iOS permissions, push notifications and Live Activities when enabled, Photos actions, and device services | Information required by the selected Apple feature, such as a push token and the notification text |
| 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.
RevenueCat. Trace's own Pro screens use RevenueCat as a subscription back office. Trace still makes every purchase with Apple StoreKit and still decides Pro access from Apple-signed records bound to your account; an update from RevenueCat only tells Trace which subscription to check again with Apple. If Trace's server cannot be reached, the app may show Pro on your iPhone for up to 24 hours from RevenueCat's last signed record of your Apple purchase; cloud sync and other server features still wait for Trace's own check. RevenueCat identifies you by your Trace account ID, which is also the identifier Apple carries on every Trace purchase. The SDK runs with attribution identifiers and SDK diagnostics off, no customer attributes are set, and no RevenueCat integration such as an analytics or advertising network is connected. RevenueCat's offerings and offer tests choose which Trace Pro plans the Pro screen lists, their order, and the plan selected first; they cannot change the product you buy, and Apple's purchase sheet shows its price and terms.
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.
Where your information is processed. Vex is based in the United States, and Trace's account database and private storage are hosted with Supabase in the United States. When you use Trace from another country, your information is sent to and processed in the United States, and the providers above may also process it in other countries where they operate. Privacy law in those countries may differ from the law where you live. Where your country's law requires a safeguard for these transfers, we rely on the European Commission's standard contractual clauses, with the additions the United Kingdom and Switzerland require, as included in our providers' data processing terms, or on another transfer basis your country's law recognizes. Vex is not certified under the EU-U.S. Data Privacy Framework. You can ask support@builtbyvex.com for a copy of these safeguards.
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 |
| Drives you delete | The route is deleted from our servers at once: the recorded route, a GPX import's route, previews shared with friends, and the sync service's copies. Other details (times, distance, notes, title, vehicle) are erased 30 days later, the Recently Deleted window. After that we keep only a record that the drive was deleted and when, so your other devices delete it too and an old device can't bring it back. Copies an out-of-date device sends after deletion are refused and erased within the same 30 days |
| Vehicles you delete | The sync service's copies (odometer included) go at once. The vehicle's remaining details and its card go 30 days later, and so do its photos on our servers (its cover and any earlier covers), which are deleted from our storage; then only its id and deletion time remain. Within those 30 days, a sync from one of your devices that still has it, such as restoring it from Recently Deleted, brings it back; after that it can't be restored |
| Recently Deleted on your iPhone | A copy of a drive or vehicle you delete stays on your iPhone, in Settings › Account › 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 |
| Share Studio images and videos | Trace's working copies on your iPhone are deleted when you leave Share Studio, or, after an interruption, the next time you use it or when iOS clears Trace's cache; copies you save to Photos or share are kept by you or the recipient |
| Business mileage tags and logs | Each tag is kept with its drive for as long as the drive exists. Trace's copy of an exported log is removed from your iPhone after sharing. If sharing is interrupted, a leftover copy stays in Trace's cache until your next export or until iOS clears it |
| 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 |
| Sync service change records | Our sync service keeps a full copy of each change your devices send for 30 days after processing it, applied or refused. After that it keeps only a record that the change happened (identifiers, type, outcome, times and version numbers), not the values you entered (notes, titles, times, distances, odometer) |
| Earlier photos and calculations | Cover photos you replace on a vehicle you keep, and earlier profile photos, are kept until your account is deleted. Each published version of a public vehicle card is kept until the card is removed. Earlier calculations of a kept drive's measurements stay with the drive |
| Saved places, recent destinations, and privacy zones | Until you remove them or delete your account; only the 20 most recent destinations are kept. A home Trace detects, and the suggestions you dismiss, stay on your iPhone until you delete your account or remove Trace |
| 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, with any group-drive speed, 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, stopped, or expired, and which friends or clubs could see it) | Deleted 30 days after the share ends |
| Meetup arrival records | Shown to friends in the meetup for six hours after the arrival; kept with your meetup participation, which is removed when the meetup or your account is deleted |
| Notification devices and queued notifications | Trace stops using a device's push token when iOS replaces it, when you sign out, when your account is deleted, or the next time Trace opens after you turn off notifications for Trace. An unused token is then deleted, normally within about 30 days, and at once when you delete your account. Records of friend and meetup notifications are deleted eight days after they are sent or expire |
| Live Activity start records and tokens | A start record (when a drive's Live Activity was requested, and whether Apple accepted it) is deleted 30 days after its last update. A Live Activity push token is deleted 30 days after it is revoked, or 90 days after the app last confirmed it |
| Referral records | Your invite code, the referrals you made or confirmed, and the Pro weeks they earned stay until your account is deleted; a referral also goes when the other account is deleted. A code you open but don't confirm expires after 30 days |
| Product analytics research summaries | Research datasets expire after seven days. Consent and contribution records stay linked to your account until it is deleted; minimal deletion records remain so erased files do not return |
| Private global heatmap contributions and receipts | Account-linked coarse cells with their day and distance, each contributed drive's start time, end time, and distance, receipt 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 contributions from at least three different drivers remain. A withdrawn or deleted contribution is removed at once, and affected areas are rebuilt from the remaining drivers within about a minute. 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 |
| RevenueCat subscription records | While your Trace account exists. Deleting your account asks RevenueCat to delete its customer record, which RevenueCat completes on its own schedule; Apple keeps its own purchase records under Apple's policies |
| Support and website messages | For the period reasonably needed to respond, maintain support history, prevent abuse, and meet legal obligations |
Backups roll off on our hosting provider's schedule, so deleted data can remain in a backup for a while after it is deleted from active systems. 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 › Account › Privacy & Data, and choose each club separately on the club's screen or in Settings › Account › Privacy & Data › Club live drives;
- hide other people's live drives from your own map in Map Layers › More layers › Friends › Live drives;
- keep detailed drives and raw routes private, and share a drive with the friends you choose from its page, or stop sharing it;
- turn heatmap contribution and product analytics (including internal research) on or off at any time in Settings › Account › Privacy & Data, leave contact discovery off, and use “Turn off contact discovery” in Social › Add friends;
- add privacy zones, including the ones Trace suggests, in Settings › Account › Privacy & Data › Privacy zones;
- rename, move or delete Home, Work and your other saved places, including a home Trace detected, in Settings › Saved Places;
- turn friend-request and meetup notifications on or off in Settings › Notifications › Friends, or turn off notifications for Trace in iOS Settings;
- turn business mileage tracking on or off in Settings › Mileage Tracking, and tag or re-tag drives;
- 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.
Trace offers these rights to every user, wherever you live and whether or not a particular 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 Settings › Account › Privacy & Data › Export Account Data.
- Withdraw consent. Turn off an optional choice, such as live drive sharing, heatmap contribution, product analytics, or an iOS permission, at any time. This stops future processing for that choice; it does not undo processing that happened before.
- 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 privacy laws. Trace processes it only after you grant location permission, and only to provide the features you use, such as recording, maps, directions, drive titles, live drives and heatmap contribution while they are on, and internal research on drive summaries while product analytics is 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, email support@builtbyvex.com with the subject “Privacy request,” or write to the mailing address in section 15. 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 where the law allows; we may still ask you to confirm your identity directly. We respond within one month, or sooner where the law where you live requires it. If a request is complex, we may extend that time where the law allows, and we will tell you why before the first period ends.
Appeals. If we decline a request, we will tell you why. You can ask us to reconsider by replying with the subject “Privacy appeal,” and we will respond within 60 days. You can also complain to an authority, as described below.
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.
United States. Several U.S. states give residents rights over their personal information; the rights above include them. If you disagree with the outcome of an appeal, you may contact your state attorney general.
European Economic Area, United Kingdom, and Switzerland. Vex Technologies Inc. is the controller of your personal data. We use it on these legal bases:
- Contract: to provide your account and the features you ask for, such as recording, sync, Garage, friends, clubs, live drives with friends, the shares you choose, Trace Pro, export, and deletion;
- Consent: for product analytics (including internal research on drive summaries), which begins off in the EEA, the UK, and Switzerland until you turn it on, for live drives with a club, contact discovery, and notifications, and for the iOS permissions you grant;
- Legitimate interests: to keep Trace and its community safe and secure, check public content, prevent fraud and abuse, fix problems, answer messages, and build the global heatmap as aggregated, de-identified data and the friends heatmap from routes you share with friends, both of which you can turn off at any time, where your rights do not override those interests; and
- Legal obligation: to keep tax and accounting records, answer lawful requests, and meet other legal duties.
You also have the rights to restrict our processing and to object to processing based on legitimate interests; turning off live drive sharing, heatmap contribution, or product analytics in Settings › Account › Privacy & Data stops that processing. To create an account, you must provide a sign-in identity and confirm that you are 18 or older, and recording needs location; everything else is optional, and leaving it out only turns off the feature that uses it. The automatic text check described in section 08 only lets text appear right away or holds it for a person to review. It never removes content or restricts an account by itself, so Trace makes no decision based solely on automated processing that has legal or similarly significant effects on you. You have the right to lodge a complaint with a data protection supervisory authority, in particular in the country where you live or work or where you believe your rights were infringed; in the United Kingdom, that is the Information Commissioner's Office.
Other countries and regions. If you live elsewhere, such as in Canada, Brazil, Japan, South Korea, or Australia, you also have the rights the privacy law where you live gives you. Use the steps above to exercise them; support@builtbyvex.com is Trace's privacy contact for every country. If you are not satisfied with our answer, you can complain to the data protection authority where you live.
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 in place, and complete deletion is still being 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 testing is complete.
Before you begin. While safely parked, open Settings › Account › Privacy & Data › 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 Settings with the profile button on the map, then select Delete Account at the bottom of the page. It is also under Account › Details.
- 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, meetups and arrival records, blocks, reports where deletion is lawful, drives and route records, saved places, recent destinations and privacy zones, live drive share records, Garage and vehicle data, hosted media, public vehicle cards, heatmap submissions, referral codes and records, notification devices and queued notifications, research consent and contributions, feature state, provider tokens, eligible analytics identity, and the subscription-processor (RevenueCat) customer record associated with the account. RevenueCat completes its deletion on its own schedule. Local cleanup removes the account namespace, Recently Deleted copies, live drive and research choices, 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 for a while in restricted backups, which roll off on our hosting provider's schedule. 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
- Mailing address
- 5124 Avenue N, Brooklyn, NY 11234, United States
- Privacy, security, and rights requests
- support@builtbyvex.com, or by mail to the mailing address