Data-processing addendum
Effective date: October 27, 2026
This addendum is part of the terms of service between Clutch Clicks LLC ("Clutch Clicks") and the shop that uses the review request service (the "Client"). On data protection, it controls over the terms.
1. Roles
The Client decides why and how its customers' personal information is used. Clutch Clicks processes that information only on the Client's instructions. The instructions are the terms, the settings the Client chooses, and the Client's written requests.
2. The processing
| Item | Detail |
|---|---|
| Subject | Review requests sent to the Client's customers after a repair order closes; service reminders, if the Client turns them on |
| Purpose | To tell that a job is complete, to decide whether a text goes out, and to start the Client's message sequence in its own CRM account |
| Duration | While the Client uses the Service, and 90 days after |
| People | The Client's customers |
| Data | Name, mobile phone, email, customer type (person or fleet); the repair order's number, status, total, payment state and close date; the type of each payment. For service reminders only: the declined jobs of a closed repair order, the vehicle and its odometer readings |
| Sensitive data | None is asked for and none is used |
3. What Clutch Clicks does
- Instructions only. It uses the data only to provide the Service. It does not sell the data or share it for advertising. It does not combine it with data from another source for its own purposes.
- Confidentiality. Each person with access is bound to keep the data confidential.
- Security. It keeps the measures of Annex 2.
- Sub-processors. It uses only those of Annex 1. It tells the Client 30 days before it adds one, and the Client may object. It stays responsible for each one's work.
- Requests from individuals. It passes a customer's request to the Client within 5 business days, and helps the Client answer.
- Breach. It tells the Client without undue delay, and within 72 hours after it confirms a breach of the Client's data. The notice says what happened, which data, and what was done.
- Deletion. Its server deletes each record after 90 days. A phone number the Client asked it never to text is kept, as the number alone, until the Client asks for its removal. When the Client disconnects, it deletes the Client's credential and webhook from its server at once. A backup is kept for 90 days, so a deleted record or credential leaves the last backup within 90 more days. On the Client's written request, it deletes the Client's records within 30 days.
- Proof. Once a year, on request, it answers the Client's reasonable security questions in writing.
- Unlawful instructions. It tells the Client when an instruction seems to break the law.
4. What the Client does
- It has a lawful reason to hold its customers' information and to share it with Clutch Clicks.
- It has its customers' consent to receive its text messages.
- It gives its customers the privacy notices the law requires.
5. Where the data sits
Clutch Clicks's server is in the United States. Annex 1 gives each sub-processor's place.
Annex 1: sub-processors
| Sub-processor | What it does | Place |
|---|---|---|
| HighLevel | The CRM platform: it holds the Client's contacts and sends its messages | United States; its support team also works from India |
| The messaging carrier of the Client's registered number | It delivers the text messages | United States |
| Hostinger | It hosts Clutch Clicks's server | United States (Boston) |
Annex 2: security measures
- In transit: every transfer uses HTTPS.
- Events: where the shop software signs its events, each signature is checked. An event that fails, or one older than 5 minutes, is refused.
- Credentials: a Client's credential is a file that only the Service's own process reads. It is never shown again and never written to a log.
- Sign-in: staff sign in with a company Google account. Access is given per person. The app stores no password.
- The server: remote login takes a key only, through a private tunnel. From outside, only the web ports answer. Repeated refused sign-ins block the caller's address.
- Records: each sign-in and each access is recorded, and the record is kept 90 days.
- Deploys: the server runs only signed code from one private repository.
- Backups: daily, readable by the server's administrator account only, with an encrypted copy off the server, kept 90 days.
- Deletion: events and request records are deleted automatically after 90 days. The never-text list is kept.