Data Processing Addendum
Last updated November 21, 2026
This Addendum is part of the Subscriber Terms of Service between Westerners Automotive (Westerners Automotive LLC, "Processor", "we") and the Company ("Business", "you"). It is accepted at signup with the Terms and recorded on the Company record.
1. Definitions
"Personal Information", "Business", "Service Provider", "Consumer", "Sell", "Share", "Business Purpose" and "Commercial Purpose" have the meanings in the California Consumer Privacy Act as amended (Cal. Civ. Code §1798.100 et seq.) and its regulations (11 CCR §7000 et seq.); equivalent terms in other state privacy laws ("controller", "processor", "personal data") are read the same way. "Company Data" means Personal Information you or your team enter into the platform, or that your customers enter in connection with your shop.
2. Roles
You are the Business (controller) for Company Data. We are your Service Provider (processor). For data we collect directly for our own account (your owner and team sign-in accounts, customer-app accounts, billing), we are the business, as described in our Privacy Policy. The Vehicle Service History copies described in §3 item 7 are held by us as the business once made.
3. Specific business purposes
We process Company Data only for these purposes, on your documented instructions as given through the platform:
- Hosting, storing, backing up and syncing Company Data to your team's authorised devices.
- Running the shop-management features you use: bookings, repair orders, inspections, estimates and authorizations, invoices, receipts, payments recording, scheduling, parts, time clock, payroll prep, loaners, towing, promotions, campaigns, hiring and onboarding, reports.
- Sending transactional notifications and, where you have consent on record, marketing messages to your customers on your behalf.
- Providing support you request, under a support-access grant.
- Security, fraud prevention, debugging and keeping the service working.
- Complying with law.
- At your instruction, making a copy of each completed repair order, keyed to the customer record and, for a customer without a linked account, to a keyed hash of the email on that record, and providing it to that customer, and only to them, in the Vehicle Service History described in the Subscriber Terms (§4), compiled with that customer's own repair orders from other Companies.
- Where your plan includes it and an owner has turned it on, answering your team's questions in the Assistant (named Wes in the apps): the question and the Company Data needed to answer it (only what the asking team member's role can already see) are sent to the AI sub-processor in Annex B, which returns the reply. Company Data is not used to train AI models, by us or by the sub-processor.
- Sending your customers the reminders described in the Subscriber Terms (appointments, service due, safety recalls) on your behalf.
4. What we will not do (11 CCR §7051(a))
We will not: (a) sell or share Company Data; (b) retain, use or disclose it for any purpose other than the business purposes above or as the CCPA permits; (c) retain, use or disclose it outside the direct business relationship between you and us; (d) combine it with Personal Information we receive from another Company or collect ourselves, except as the CCPA regulations allow for the limited purposes of security, debugging or performing the service, and except that a customer's own completed repair orders are compiled with that customer's own repair orders from other Companies for the Vehicle Service History (§3, item 7); (e) use it to build profiles or train models; (f) grant access to any person except as needed to perform the services under confidentiality obligations.
5. Our compliance duties
We will comply with the CCPA and other applicable state privacy laws and give Company Data the same level of protection they require of you. We will notify you within 5 business days if we determine we can no longer meet our obligations under this Addendum, and you may then direct us to stop processing and return or delete the affected data. We will tell you promptly if an instruction, in our view, violates the law.
6. Your right to assess (11 CCR §7051(a)(8))
You may take reasonable steps to ensure we use Company Data consistently with your obligations: once every 12 months (or after a confirmed breach) you may request our written security description, the sub-processor list, and answers to a reasonable security questionnaire, and we will respond within 30 days. You may remediate any unauthorised use by directing us to stop it; we comply within 5 business days.
7. Consumer requests
Customers may submit requests to know, delete, correct, opt out or limit through the customer app, our web form or email; team members through the team app and HR screens. Requests about Company Data are routed to your owner console (Privacy) the same day with the 10-business-day acknowledgement and 45-day response timers shown. The console gives you Export (one JSON/CSV bundle per person), Delete/anonymise (respecting the retention minimums in Annex A) and Correct. If a request reaches us directly, we forward it to you within 2 business days and tell the requester we have done so. We will not respond substantively on your behalf unless you ask us to.
8. Sub-processors
Our sub-processors are listed in Annex B. We bind each by written contract to obligations no less protective than this Addendum and remain responsible for them. We give you at least 30 days' notice by email to owner accounts before adding or replacing a sub-processor; if you object on reasonable data-protection grounds and we cannot resolve it, you may terminate the affected service and receive a pro-rata refund of prepaid fees.
9. Security
We maintain the technical and organisational measures in Annex C, appropriate to the nature of Company Data, and update them as the service develops. Annex C states the measures in place today.
10. Breach notification
If we confirm unauthorised acquisition of Company Data, we notify your owner account within 72 hours of confirmation, by email and in the console, with: the date and time of discovery; what happened; the categories of data and the approximate number of people affected, by state of residence where we can determine it (from ZIP codes on file); what we have done to contain it; a named contact; and the information you need for your own consumer notices and regulator filings (Washington's 30-day consumer and attorney-general deadlines; California's 30-day consumer notice and 15-day attorney-general sample; others as applicable). We update you as facts develop and cooperate with your notices. Where the breach affects data we hold as the business, we make our own notifications.
11. Return and deletion
During the term you can export Company Data at any time. On termination you have 90 days to export; we then delete Company Data from live systems within 30 days and from backups as they roll off (90 days), except records we must retain by law, which we keep isolated and delete when the duty ends. On request we certify deletion in writing. The Vehicle Service History copies made under §3 item 7 are not returned or deleted on termination; we keep them as our record for the customer until the customer deletes their account or asks us to delete them, and delete the repair orders you delete, and those of customers you delete or anonymise, during the term.
12. Audit of our own compliance
We keep records of processing activities and of every support-access session, and make summaries available to you on request under §6.
13. Term
This Addendum lasts as long as we hold Company Data. Sections 4, 10 and 11 survive.
Annex A — Details of processing
| Item | Detail |
|---|---|
| Subjects | Your customers and their household members named on bookings; your team members and applicants; your suppliers' contacts |
| Categories | Identifiers; commercial information; vehicle identifiers; audio/visual (inspection media); professional/employment information; for payroll, government identifiers and financial account numbers (restricted) |
| Sensitive PI | Payroll and I-9/W-4 data for team members (restricted to the owner and permitted managers); none for customers beyond log-in credentials |
| Retention minimums that override deletion requests | Estimates and invoices: 1 year WA, 3 years CA; tax records: 5 years WA; payroll: 3 years; time cards: 2 years; applicants: 1 year; I-9: later of 3 years after hire / 1 year after separation; STOP requests: 5 years |
| Default retention | Inactive customer accounts anonymised after 24 months; inspection media 24 months; chat 12 months; presence and push 90 days; Vehicle Service History copies: until the customer deletes their account or asks us to delete them, or you delete the repair order or delete or anonymise the customer |
| Location | United States |
Annex B — Sub-processors (as of 2026-11-21)
| Sub-processor | Service | Data | Location |
|---|---|---|---|
| Akamai Technologies, Inc. (Linode) | Hosting, storage, backups | All Company Data | United States |
| Cloudflare, Inc. | DNS, the proxy and certificates in front of our domain, backup storage (R2) | All Company Data (in transit through the proxy; encrypted backup copies) | United States (backups); its network worldwide for traffic in transit |
| ActiveCampaign, LLC (Postmark) | Transactional email delivery (SMTP) | Email addresses and message content | United States |
| Apple Push Notification service; Firebase Cloud Messaging (Google); Mozilla push | Push delivery to the apps and browsers | Push tokens and notification text | United States |
| Google ML Kit (Android apps only) | On-device barcode reading for VINs | Device and app diagnostics, on Google's terms; no Company Data | United States |
| National Highway Traffic Safety Administration (vPIC) | VIN decoding | VIN only (no customer identifiers) | United States |
| National Highway Traffic Safety Administration (recall lookup) | Safety recalls for a model | Model year, make and model only (no VIN, no customer identifiers) | United States |
| Anthropic, PBC | The AI model behind the Assistant, only for Companies that turn the Assistant on, and for customers who use it in the app | The messages of a chat and the records the Assistant reads to answer: order, vehicle and inspection details and customers' names; never passwords, payment card data, or customers' email, phone or address | United States |
| komoot GmbH (Photon, OpenStreetMap data) | Address suggestions as you type | The typed address text and an approximate location (no customer identifiers) | Germany |
| U.S. Census Bureau geocoder | Address checks and map pins | Address text only (no customer identifiers) | United States |
Card payments at shops that take them go through the shop's own account with Stripe, Inc. (United States), under the shop's agreement with Stripe; Stripe processes for the shop as merchant and is not our sub-processor. Not currently used: text-message provider, analytics. Any new sub-processor is added here with 30 days' notice before use.
Annex C — Security measures
- Passwords stored as salted, peppered Argon2id hashes (scrypt fallback), never in plain text; NIST 800-63B-style password rules; rate limits and lockout on sign-in.
- Server-side sessions in an HttpOnly cookie (Secure on HTTPS); "Sign out everywhere"; device list; new-device and password-change emails.
- Two-step sign-in (authenticator app plus recovery codes) available to all; required for Westerners Automotive administrators; a fresh second step is required to approve support access.
- Each Company's records in its own data store; every API request checked against the signed-in person's Company, role and permissions; records written by clients re-stamped with the Company id on the server; technician, advisor and recovery devices never receive payroll or sensitive HR documents.
- The Assistant reads Company Data only through the asking person's own role and permission checks, sends customers' names and vehicle details but never their email, phone or address to the AI sub-processor, and cannot change a record: a proposed task is carried out under the person's own session only when they confirm it. The sub-processor's key is held on the server and is never sent to a browser.
- File uploads scoped to the Company and access-checked on download; sensitive HR documents (I-9, W-4, direct deposit) restricted to the owner and managers with the sensitive-documents permission.
- Support access only by owner-approved, time-boxed grants, read-only by default, written to the Company's audit log.
- Audit log of sign-ins, security changes and administrative actions.
- Nightly backups with restricted file permissions on a host with full-disk encryption.
- Security headers (frame denial, content-type sniffing off, strict referrer policy) and an enforced Content-Security-Policy; HTTPS and HSTS on the hosted service.
- No card numbers collected or stored; receipts show the last 4 digits only.