Privacy policy

1. Information used for the service

A request contains the contact name, email and phone number, service address and access notes, vehicle details, requested services, and preferred visit window. Reviewed service specifications, quote and payment references, visit status, completion checks, and any service photographs become part of the visit record.

An account adds sign-in information and the account profile. Provider applications and workspaces include business and contact details, service capabilities, qualifications, insurance information, schedules, assigned work, and payout records. Security and administration records may include request metadata, access events, and changes made to a visit.

2. Why this information is used

Motrive uses the necessary information to check address and vehicle eligibility, calculate an estimate, review service specifications, match a provider, prepare and complete a visit, process payment or a refund, communicate service updates, and resolve a support request. Account and security data support sign-in, access control, fraud prevention, and operational auditing.

The pricing rules consider the services, supported vehicle details, address zone, and eligible services at the same stop. Oil fitment and unsupported requests require human review. You can correct request information before accepting an offer and contact Motrive about a reviewed specification or price.

3. Who can access it

Customers can access visits through their authorized account or guest access. Providers receive information relevant to eligible job offers; detailed customer contact and address information is restricted to authorized assigned work. Authorized operations staff can review the information needed to manage requests, providers, payments, and support.

The implementation uses Supabase for authentication, database and private storage; Vercel for the website; and, when configured, Stripe for payment processing, Postmark for authentication and service email, Resend for previously queued service email, Turnstile for abuse prevention and Expo for app notifications. These services receive the information needed for their function. The Supabase project is configured in Canada Central and the Vercel server runtime in Montréal; static content delivery uses a global network. This does not mean all processing stays in Québec or Canada. The operator must complete the processing arrangements and applicable transfer assessments before operational launch.

When Google Maps address suggestions are enabled, the text entered for suggestions is sent through Motrive's server to Google Maps to find a Canadian street address and its location. We do not attach account, contact or vehicle fields to these lookup requests. Choose Enter address manually to stop suggestions and complete the address without this lookup. Google's terms and privacy policy apply to its processing. Suggestions and map-pin metadata stay temporarily in page memory; the selected street address becomes part of the normal request if you submit it.

Full payment-card details are entered through Stripe-hosted Checkout or Stripe’s PaymentSheet interface in the native app. Motrive’s booking forms and service APIs store payment references, amounts, and status rather than full card numbers. Service photographs are stored privately and retrieved through authorized, short-lived links. Avoid including unrelated people, documents, or sensitive information in photographs or access notes.

4. Browser and mobile-app access

The website uses necessary sign-in and guest-access cookies. A guest visit’s browser cookie is HttpOnly so page scripts cannot read the access credential. The focused website does not store private booking data or access tokens in localStorage or sessionStorage. Clearing cookies can remove that browser’s guest access.

The optional light/dark display preference is stored in localStorage under motrive-theme as light or dark. It contains no account or visit information; you can change it using the theme control or clear it through your browser. If storage is blocked, the default is dark and the current-page control still works.

If operational diagnostics are enabled, a small sample of visits sends numerical loading, interaction and request timings and generic app-error counts to Motrive’s own service. These diagnostic payloads omit names, contact details, addresses, record identifiers, full URLs and error messages. They do not use tracking cookies or persistent device identifiers. Browser diagnostics respect Do Not Track and Global Privacy Control; hosting access logs and retention are governed by the operator’s disclosed processing settings.

When Sentry error monitoring is configured, it receives sanitized technical error types and stack locations, with original error messages replaced by generic descriptions. The configured filter removes user, request, cookie, body, header, breadcrumb and extra context. Replay, tracing, session tracking and SDK log collection are disabled. The configured ingestion endpoint is in the United States; exact storage location and retention remain to be verified before operational launch. Private source maps are used for diagnosis and are not served as public website files.

The native app stores sign-in and guest-access credentials using the device’s protected SecureStore. Photo selection, camera access, and notifications depend on the feature used and device permission. The initial service uses the address you enter and visit status updates; it does not require continuous background location tracking.

You can recover eligible guest visits by signing in with the verified email used for the booking. Explicitly claiming a visit links it to the account and revokes the previous guest credential. Keep access to your email and device secure, and use sign-out on a shared device.

5. Retention and deletion requests

Information is retained for the service purpose and applicable transaction, accounting, dispute, security, and legal obligations. The operator’s retention approach for deployed services and backups is disclosed below. If it has not yet been configured, this policy remains a prelaunch draft and does not claim an established retention period.

A verified account holder can submit an account-deletion request and follow its review status. Submission does not immediately erase the account or all visit records. The team reviews open visits, refunds, provider obligations, and records that must be retained, and records the decision. A pending request may be withdrawn through the same screen.

6. Questions, access, and corrections

Use the privacy contact below to ask about personal information, request access or correction, raise a concern, or discuss withdrawing consent where applicable. Identity verification may be needed to protect the record. Some information is necessary to fulfill a visit; removing it may prevent the service from proceeding.

Changes to this policy will be published with an updated version and review date. Material changes to the purposes or handling of information must be communicated and any required consent obtained before that new use. The published policy does not limit your rights under applicable privacy law.