Who we are
CoatHQ is CRM and operations software for concrete coating and epoxy flooring contractors. It's run by [legal entity name], [registered address]. Send privacy questions to [privacy contact email].
What this policy covers
It covers two things. They need to be described apart, because our role is different in each one.
- This website. Data we collect when you browse coathq.com or ask for a demo.
- The CoatHQ application. Data we handle for a contractor who uses CoatHQ to run their business. That includes details about the contractor's own customers. Here the contractor is the controller of that data, and CoatHQ processes it for them. TO CONFIRM: whether a separate data processing agreement is offered to customers.
Information collected on this website
- What you send us. Your name, company, email and phone, plus anything else you type into the demo request form.
- Analytics. TO CONFIRM: GA4 is planned but not installed yet. Once it is, this section will name the provider and what it collects. It will also say how long the data is kept, and the lawful basis for keeping it.
- Cookies. TO CONFIRM: the site sets none right now. If we add analytics or a booking embed, list each cookie with its purpose and how long it lasts. Then add a consent banner that declines anything non-essential by default.
How information is used
- To answer a demo request and talk with you about the product.
- To run, secure and support the app for customers.
- TO CONFIRM: whether demo requesters are added to a marketing email list, and how they opt out.
We don't sell personal information to third parties.
Who else processes data
List every sub-processor with its role and region. Here's what we know so far, still to be confirmed. Hosting and database. Email delivery. Telephony. Payment processing through Stripe (a contractor connects their own Stripe account, so their customers' payment data goes to the contractor's account). Analytics, once it's added. TO CONFIRM: the full current list and each provider's region.
Retention, security and your rights
- Retention. TO CONFIRM: how long demo requests are kept, and what happens to a customer's data after their account closes.
- Security. Describe the real controls we use, not boilerplate.
- Your rights. Access, correction and deletion, and how to make a request. TO CONFIRM which regimes apply: US state privacy laws, state by state, and GDPR or UK GDPR if there are customers or staff in those regions.
Messaging consent
This gets its own section because the product sends messages for contractors. The app checks for consent before any automated send. The final policy should say plainly how consent is captured and how someone opts out. It should also say who is responsible for consent, CoatHQ or the contractor.
Changes to this policy
Put a date on the policy and keep the old version. Say how we'll tell people about material changes.
Questions
Until this is finished, the honest answer to a privacy question is to ask a person. Bring it up when you get started. Want to see what the product does with data day to day? The features page covers messaging, call tracking and payments. The terms of service cover who owns the data and how to export it.
Draft last updated October 2026. Not published, and not legal advice.