Privacy notice
Protection health.
Not surveillance.
Realist Inc. operates MileMute (working name). Core drive detection and blocking run on your phone, and we designed the beta to work without collecting where you drive or what you say.
What stays on your phone
The current local-only mobile builds process safe/blocked app choices, iOS Screen Time tokens, guardian edit-lock credentials and attempt throttling, Android foreground-app identity during a block check, vehicle/motion signals, selected-car local identifiers, protection state, overrides, and completed trip summaries on the device. The iOS code stays in this-device-only Keychain; Android stores only a salted PBKDF2 hash. Neither code is transmitted to us.
Completed summaries are limited to start/end time, protected duration, activation-source class, parked-test status, and passenger/emergency outcome. Each phone retains at most 100 summaries. No route, destination, speed, message, contact, URL, foreground app name, or vehicle identifier is included. You can clear completed history in the app without interrupting an active trip.
Information you give us
Founding-family application
We collect email, applicant role, phone platform, driver age band, vehicle connection type, city or region, an optional trust note, safety acknowledgement, consent version, and submission time. Please do not put routes, health details, messages, contacts, or other sensitive content in the note.
Support and privacy requests
We collect the email, optional name, request category, phone platform, message, consent version, status, and submission time needed to answer the request. The form returns a reference number.
Optional family beta
The family backend is not connected to the current mobile builds. Before it is enabled, guardian and driver will receive a separate notice and consent choice. The design permits account and household identifiers, membership role, protection readiness/reason codes, check-in time, and consented coarse trip summaries. It rejects location, speed, communications, contacts, URLs, app identities, and typed content. Withdrawing family sharing will not disable the on-device safety core.
Why we use information
- Provide, secure, and troubleshoot the requested product or beta.
- Select and support a representative phone-and-vehicle test group.
- Measure activation reliability, false locks, overrides, and safety defects using minimal records.
- Respond to access, correction, deletion, support, and complaint requests.
- Meet legal obligations and address fraud, abuse, security, or an immediate safety threat.
We will seek fresh consent before using personal information for a materially new purpose.
Disclosure and service providers
We disclose only what is necessary to infrastructure providers that host the site and database, authorized household members for separately consented family features, professional advisers bound by confidentiality, authorities when legally required, or a successor in a corporate transaction subject to appropriate safeguards. We do not sell or rent personal information and do not share it with ad networks or data brokers.
Providers may process information outside your province or country, where local law can apply. The current site uses OpenAI Sites and Cloudflare-hosted infrastructure. Production app processors and regions will be listed before family networking is enabled.
Retention
| Record | Default maximum |
|---|---|
| Unenrolled waitlist application | 18 months after last contact |
| Support or privacy request | 24 months after resolution |
| Local completed summaries | 100 most recent, until cleared or app data is removed |
| Future family trip summaries | 12 months unless deleted earlier |
| Security/membership audit events | 24 months |
We may retain a record longer when law requires it or it is needed for a documented dispute or security investigation, and will explain an applicable exception.
Security and youth
We use access controls, narrow data allowlists, encrypted transport, secret management, and privacy-minimal storage. No method is perfectly secure. The beta is intended for licensed or learning drivers age 16 or older and their guardians; it is not directed to children under 13. A guardian must participate where legally required, while the young driver receives an understandable notice.
Your choices and rights
Depending on where you live, you may request access, correction, deletion, information about disclosures, or withdrawal of consent. Use the privacy request form. We verify requests without asking for unrelated sensitive information. Marketing messages will provide an unsubscribe route. You can also clear local history or remove local app data through the app and operating-system controls.
Changes, complaints, and safety limits
We will post the current effective date and present material changes before they take effect when new consent is required. Questions or complaints go to the Privacy Officer through the secure support form. Canadian residents may also contact the Office of the Privacy Commissioner of Canada after giving us a reasonable opportunity to respond.
MileMute is a supplemental safety aid. Detection or restriction can fail or be disabled. It does not guarantee legal compliance, prevent collisions, or replace attentive driving. Pull over safely before using a phone.