Data Processing Addendum
v1.0.1Last Updated: November 2026
Version 1.0 · Effective October 4, 2026
This Data Processing Addendum ("DPA") forms part of the agreement between 404 Innovationz LLC d/b/a MECH Inspect ("Provider") and the customer that uses the MECH Inspect Service under it ("Customer"). That agreement (the "Agreement") is either:
- the Terms of Service Customer accepted; or
- a written service agreement Customer signed with Provider, if there is one.
The DPA applies automatically, without a separate signature, whenever Customer submits personal data to the Service. Capitalized terms not defined here have the meanings given in the Agreement.
1. Roles
1.1 Customer is a repair shop. Where Customer is an automotive repair business using the Service for its own shop or shops:
- Customer is the Controller of the personal data submitted to or generated in the Service ("Customer Data").
- Provider is the Processor. It processes Customer Data only to provide the Service and on Customer's documented instructions. Those instructions consist of the Agreement, this DPA, and Customer's use of the Service's features.
- Where Customer operates more than one shop location, instructions given by Customer's administrators through the Service are Customer's instructions for every location in its account.
1.2 Customer acts for separate shop entities. Where Customer manages the account for one or more shop locations that are separate legal entities (each a "Member Shop"):
- (a) each Member Shop is the Controller of the Customer Data in its own location;
- (b) Customer is a Processor acting for each Member Shop, and Provider is Customer's Sub-processor;
- (c) Customer represents and warrants that it is authorized by each Member Shop to submit that shop's data to the Service and to give Provider the instructions in Section 1.1, and that it will pass on to Provider any instructions from the Member Shop that bear on the processing; and
- (d) Provider's obligations in this DPA run to Customer, for the benefit of each Member Shop.
1.3 Provider will notify Customer if, in Provider's reasonable opinion, an instruction infringes applicable data protection law.
2. Scope of Processing
- Subject matter: provision of the Service.
- Duration: the term of the Agreement, plus the post-termination period in Section 8.
- Nature and purpose: reading repair order, vehicle and service history information from Customer's shop management system; AI-assisted drafting of technician notes, diagnostic summaries, customer talking points and service recommendations; generating service recommendations from maintenance schedules and service history; hosting photos, scan reports and templates Authorized Users upload; customer-facing explainer video pages; transactional email; and payment status handling. In each case this is as directed by Customer's use of the Service.
- Categories of data subjects:
- owners, service advisors, technicians and other Authorized Users;
- employees of Customer or of a Member Shop;
- Customer's customers (vehicle owners and drivers);
- visitors to the customer-facing video pages Customer sends out.
- Categories of personal data:
- account data of Authorized Users: name, email address, role, and sign-in metadata such as IP address, device and approximate location;
- repair order content: vehicle identification numbers, license plates, odometer readings, repair order numbers, service descriptions and prices, technician notes, photographs and scan reports;
- a customer identifier assigned by Customer's shop management system, with visit counts and spend totals used for service recommendations;
- vehicle history report data obtained on Customer's instruction, held no longer than 24 hours;
- customer-facing video page events: a link token, the event type, playback position and device type;
- correspondence sent through the Service.
- Special categories: none are intentionally collected.
- Provider does not store Customer's customers' names, home addresses, email addresses or telephone numbers from the shop management system, and does not require them. Such information may still appear incidentally in technician notes or photographs. Customer should avoid submitting government identification numbers, financial account numbers, or health information.
- Full payment card numbers and bank account numbers are never held by Provider; they are collected and processed by Stripe.
3. Customer Obligations
Customer will:
- (a) have the right to submit Customer Data to the Service, and give any notices to its customers and others that applicable law requires;
- (b) keep Customer Data reasonably accurate, and not submit data prohibited by Section 2;
- (c) decide who in its organization, or outside it, may access Customer Data, using the Service's roles and access controls, and remain responsible for those Authorized Users under the Agreement;
- (d) give only instructions that comply with applicable law; and
- (e) where Customer sends a customer-facing video page or report to a vehicle owner, do so in compliance with the Agreement and applicable messaging law.
4. Provider Obligations
Provider will:
- (a) process Customer Data only in accordance with Section 1;
- (b) ensure that persons authorized to process it are bound by an obligation of confidentiality;
- (c) implement and maintain the security measures in Section 6;
- (d) assist Customer with data-subject requests, and with Customer's own security and breach-notification obligations, to the extent Customer cannot address them through the Service itself. This takes into account the nature of the processing and the information available to Provider; and
- (e) on Customer's reasonable written request, make available the information reasonably necessary to demonstrate compliance with this DPA. No more than once in any twelve-month period, on reasonable notice and at Customer's cost, Provider will also allow for and cooperate with a reasonable assessment of its compliance. The assessment is conducted by Customer, or by an independent assessor agreed by the parties and bound by confidentiality. Provider may satisfy an assessment by providing a written description of its security controls, or a current third-party security audit report where one exists.
5. Sub-processors
5.1 Customer authorizes Provider to engage the sub-processors listed below.
- Provider imposes data-protection obligations on each one that are at least as protective as those in this DPA.
- Provider remains responsible to Customer for its sub-processors' performance.
- Where a sub-processor is listed by category rather than by name, Provider will identify it to Customer on written request, subject to the confidentiality terms of the Agreement.
| Sub-processor | Purpose | Data it receives |
|---|---|---|
| Lovable Labs Incorporated | Managed backend platform through which the database, file storage, authentication and server functions run, under Lovable's Data Processing Agreement, which prohibits use of Customer personal data to train or develop AI or machine-learning models | All Customer Data |
| Supabase (Lovable's sub-processor, engaged through Lovable) | Database, file storage, authentication and server functions | All Customer Data |
| Netlify, Inc. | Hosting and delivery of the web application and website | Request logs, including IP address and browser information, for pages Authorized Users and video page visitors load |
| Google (Gemini API) | AI drafting and analysis | Technician notes, diagnostic codes, scan-tool reports, vehicle descriptions, photographs and documents submitted for analysis |
| Resend | Transactional email delivery | Recipient name and address, message content |
| Stripe, Inc. | Payment processing | Customer billing contact, payment method details (held by Stripe only), invoices and payment status |
| AutoNetTV Media, Inc. | Hosting and playback of explainer videos on customer-facing video pages (only if Customer uses the video add-on) | Viewer IP address and browser information, the video and shop location identifiers, and Customer's business name, address and telephone number at setup |
| CARFAX, Inc. | Vehicle history reports through the CARFAX Shop Loyalty Program (only if Customer has activated vehicle history reports) | The vehicle identification number and the shop location identifier used to request a report |
| Google Analytics 4 | Website usage analytics, loaded only after cookie consent on the public website | Website visitor interactions; no Customer Data |
5.2 Changes.
- Provider will give at least thirty (30) days' notice before adding or replacing a sub-processor that will process personal data. Notice is given by email to Customer's account administrators and by updating the list on this page.
- Customer may object on reasonable data-protection grounds within that period.
- If the parties cannot resolve the objection, Customer may terminate without penalty and receive a refund of prepaid fees for the unused portion of the term, notwithstanding any no-refund term in the Agreement.
5.3 Customer's shop management system. Customer's shop management system (for example Shop-Ware) is Customer's own system, operated under Customer's own agreement with that vendor. Provider reads data from it and writes notes and photos to it only on the instruction of an Authorized User. It is not Provider's sub-processor.
6. Security
6.1 Provider maintains commercially reasonable technical and organizational measures appropriate to the risk, including:
- encryption of data in transit (TLS) and, by the infrastructure provider, at rest;
- authentication through a managed identity provider, with optional multi-factor authentication;
- role-based permissions (owner, administrator, technician), set by Customer, limiting what each Authorized User can view and change;
- database row-level security isolating each shop and each group of shops from other customers;
- private storage for technician photographs and scan reports, served only through short-lived signed links. Shop logos and the media Customer places in its own library are public because they appear on customer-facing pages;
- deletion of third-party vehicle history report data, and of anything derived from it, within 24 hours of receipt;
- audit logging of authentication events, and rate limiting of sign-in attempts;
- automated database backups retained for a limited rolling period.
6.2 Provider does not warrant absolute security. No method of transmission or storage is completely secure.
7. Personal Data Breach
7.1 Provider will notify Customer without undue delay and in any event within seventy-two (72) hours of confirming a personal data breach affecting Customer Data.
7.2 The notification will describe, to the extent known:
- the nature of the breach;
- the categories and approximate number of data subjects and records affected;
- the likely consequences; and
- the measures taken or proposed.
Provider will supplement it as more information becomes available. Where Customer acts for Member Shops, Customer is responsible for informing each affected Member Shop.
7.3 Provider will not make any public statement or notification identifying Customer or a Member Shop in connection with a breach without Customer's prior written consent, unless required by law.
8. Data-Subject Requests; Deletion and Return
8.1 Data-subject requests. The Service gives Customer tools to view and remove much of its Customer Data.
- Where Customer cannot fulfil a data-subject request through the Service, Provider will provide reasonable assistance at no additional charge.
- If a data subject contacts Provider directly, Provider will refer them to Customer and will not respond substantively on Customer's behalf.
8.2 Deletion and return.
- For sixty (60) days after termination of the Agreement, Provider will, on Customer's written request, make available a copy of the Customer Data held in the Service in a commonly used format.
- After that, Provider will delete or irreversibly anonymize Customer Data within a commercially reasonable time and in accordance with the retention schedule in the Privacy Policy, except where retention is required by law.
- Backup copies are deleted on Provider's ordinary backup rotation, and remain subject to this DPA until they are.
- Provider will confirm deletion in writing on request.
9. No Sale of Data; No Model Training
9.1 Provider does not sell personal data and does not process Customer Data for advertising or for any purpose unrelated to providing the Service.
9.2 Customer Data is not used to train Provider's models. Provider engages its AI sub-processor on terms that do not permit Customer Data to be used to train that sub-processor's general models. Provider accesses the Google Gemini API as a paid service, under terms under which Google does not use prompts or responses to improve its products.
9.3 Vehicle history report data is never submitted to an AI model. Service recommendations drawn from it are computed by Provider's own rules-based software.
10. Location
Customer Data at rest, including stored photographs and documents, is hosted in the United Kingdom (London) through Provider's infrastructure provider. The sub-processors in Section 5.1 process Customer Data in the United States and other countries, under their own terms, to provide their services.
11. Liability; Order of Precedence; Changes
11.1 Each party's liability under this DPA is subject to the limitations and exclusions of liability in the Agreement, including its provisions for claims arising from a personal data breach.
11.2 If this DPA conflicts with the Agreement with respect to the processing of personal data, this DPA controls.
11.3 Provider may update this DPA, as the Agreement allows for its own terms. A change that reduces Customer's protection will not apply to Customer without at least thirty (30) days' notice. Sub-processor changes follow Section 5.2.