Privacy policy
Effective date: October 27, 2026
Who we are
Clutch Clicks LLC ("Clutch Clicks", "we") is a marketing agency for auto repair and body shops, based in Houston, Texas. Our contact is tech@clutchclicks.com.
What this policy covers
This policy covers our review request service and, for a shop that turns them on, our service reminders (together, the "Service"). A shop that is our client connects its shop management software to the Service. When a repair order closes, the shop's own CRM account sends that customer a review request.
We run the Service for the shop. The shop decides which customers it serves and what it sends them. In this policy, "shop" means our client, and "customer" means a person the shop served.
What we collect
About a shop's customers, from the shop's management software:
- First and last name.
- Mobile phone number and email address.
- Whether the record is a person or a fleet account.
- The repair order's number, status, total, payment state and close date.
- The type of each payment on the repair order, such as warranty or internal.
Only for a shop that turns on service reminders: the declined jobs of a closed repair order (the job's name and the vehicle) and the vehicle's odometer readings.
The software sends us each repair order and payment as its own record. We use only the fields above.
About a shop:
- The business name, and the names and work emails of the people we work with.
- The credential that lets the Service read the shop's repair orders, such as an API key.
- The settings the shop chooses for the Service.
How we use it
- To tell that a job is complete.
- To decide whether a request goes out. A fleet account gets none. A warranty or internal job gets none. A repair order under the shop's minimum total gets none. A customer who opted out gets none.
- To send one review request per repair order. A request may hold follow-up messages that the shop's sequence sets.
- To send the same phone number no more than one request in a period the shop sets (90 days by default).
- For a shop that turns on service reminders: to send up to two follow-up texts about recommended work the customer declined, and a reminder when that service is due.
- To create or update the customer's contact in the shop's own CRM account, and to start the shop's message sequence there.
- To keep a record of each request and its reason, so the shop and we can answer questions and fix errors.
We do not sell personal information. We do not share it for advertising. We do not use it for our own marketing or to train AI models. We write nothing back to a customer, vehicle or repair order record in the shop's software.
Text messages
- The shop sends each text from its own phone number, registered for business texting (A2P 10DLC). A number without that registration sends no text.
- Reply STOP to any message to opt out. The shop's CRM then marks the number Do Not Disturb, and the Service sends it no more texts.
- The Service starts a text only between 9 AM and 8 PM in the shop's time zone.
- Message and data rates may apply.
- The shop is responsible for the customer's consent to receive its texts.
Who receives the data
- The shop, in its own CRM account.
- Our service providers, who act on our instructions:
- HighLevel, the CRM platform that holds the shop's contacts and sends its messages.
- The messaging carrier of the shop's registered number.
- Hostinger, which hosts our server.
- Authorities, when the law requires it.
Where it is stored
The data is stored on our server in the United States, in a Hostinger data center in Boston. It is also stored in the shop's CRM account at HighLevel.
How long we keep it
- Our server keeps each record the shop's software sends, and each request record, for 90 days. Then it deletes them automatically.
- A request record holds the customer's name, phone and email only when a request is to be sent.
- A phone number the shop asked us never to text is kept, as the number alone, until the shop asks for its removal.
- A backup of our server is kept for 90 days. A deleted record leaves the last backup within 90 more days.
- The contact in the shop's CRM account is the shop's own record. The shop decides how long it stays.
- When a shop disconnects, we delete its credential and its webhook from our server at once. The credential leaves the last backup within 90 more days.
How we protect it
- Every transfer uses HTTPS.
- Where the shop's software signs its events, we check each signature and refuse an event that fails.
- A shop's credential is stored where only the Service's own process reads it. It is never shown again and never written to a log.
- Our staff sign in with company accounts. Access is given per person and recorded.
No method is perfect. If we learn of a breach of a shop's data, we tell the shop without undue delay.
Your choices
If you are a shop's customer:
- Reply STOP to stop the texts.
- Ask the shop, or us at tech@clutchclicks.com, to see, correct or delete your information. We act for the shop, so we pass your request to the shop within 5 business days and help it answer.
- Some states give you more rights over your personal information, such as California. We treat you the same whether you use them or not.
If you are a shop: you may pause or disconnect the Service at any time.
Children
The Service is not directed to children under 13. We do not knowingly collect their information.
Changes
We post each change on this page with a new effective date. We tell our shops by email before a material change takes effect.
Contact
Clutch Clicks LLC, Houston, Texas, United States. Email tech@clutchclicks.com.