What we collect, and what we do not.

Information you send us

If you submit a form on this site we receive the fields you filled in — typically your name, company, email or phone, and any figures you entered into the estimator. We use them to reply to you and to prepare the breakdown you asked for. We do not sell, rent or share them with third parties for marketing.

Estimator inputs are processed in your browser. Nothing is transmitted unless you choose to submit the form, at which point your inputs travel with it so we do not have to ask you for them again.

If you arrived from an advertisement

When you arrive from a paid advertisement, the link carries a click identifier — for example Google's gclid — along with any campaign parameters. We keep that identifier in your browser's session storage and attach it to your submission if you choose to send us one, so that we can tell which advertising is worth paying for.

What that means in practice, stated precisely:

• No advertising pixel or tracking script runs on this site. There is no Google tag, no Meta pixel, no analytics script, and no third-party JavaScript of any kind. The only script we load is a small first-party file that copies the click identifier from the address bar into the form.
• Nothing is sent anywhere unless you submit a form. If you read the site and leave, no advertising network hears anything from us about your visit.
• The identifier is stored in session storage, not a cookie, and it is discarded when you close the tab. It cannot be read by any other site.
• Conversion reporting happens on our server, after the fact — we tell the ad platform that a click it sold us resulted in an enquiry. We do not send it your name, your email, your company, or anything you typed into the estimator.

If you would rather not carry the identifier at all, remove everything after the ? in the address bar before you browse, or open the site in a private window.

Client call data during an engagement

This is the part that matters, so it is spelled out.

• Caller phone numbers are hashed on arrival. The raw numbers are discarded at the point of ingest and are never written to disk, never stored in our systems, and never appear in any report. Hashing is salted per engagement, so hashes cannot be compared across clients.
• We do not need call recordings or transcripts for the diagnostic, and we do not ask for them.
• Client data is never committed to source control. This is enforced mechanically, not by policy — a repository hook rejects it.
• Anything published as a benchmark is anonymized and aggregated — vertical, revenue band, CSR count, and rate distributions. No client is identifiable from a benchmark record, and we do not name clients without written permission.
• Data is returned or destroyed at the close of an engagement on request, and in any case within twelve months.

Where it is held

This site is served by Cloudflare Pages. Form submissions are written to our own records system, which we control. Analysis of client call data runs on systems we control. We use no third-party form service, no advertising or analytics pixels, no session recording, and no cross-site tracking. Conversion reporting to advertising platforms happens server-side, as described above.

Cookies

This site sets no cookies of its own. Web fonts are loaded from Google Fonts, which means your browser makes a request to Google's servers to fetch them; we receive no information from that request.

Your choices

You can ask us what we hold about you, ask for it to be corrected, or ask for it to be deleted, and we will act on that within thirty days. California residents have specific rights under the CCPA, including the right to know and the right to delete; we extend the same handling to everyone regardless of where you are.

Contact

Questions about this notice, or a request about your data, can be sent through the contact form. We will reply to the address you give us.

This notice describes current practice and is not legal advice. It has not been reviewed by an attorney.