rootcheck.diag·Overviewnot connected
Optional · Permissions detail

What RootCheck reads, in plain English.

Extra reassurance if you want it. You don’t have to read this to start. The connect button on the main RootCheck page does the same thing.

read-only on your HubSpot · email saved · kept until you ask

rootcheck.needs
what RootCheck needs
  • Read contacts, companies, and deals

    To see the shape of your CRM data and score hygiene.

  • Read pipelines and lifecycle stages

    To check whether your process matches how your team actually sells.

  • Owner names and emails, if you allow it

    Optional. The scan still runs if you skip this. We use it to see who owns a record.

rootcheck.never
what RootCheck does not do
  • RootCheck never changes your CRM. No writes, no merges, no deletes.
  • RootCheck never emails your contacts. It does not read message bodies.
  • Connecting saves the HubSpot user's email and an encrypted access key, and it creates a sign-in for that email.
  • We may add that email and your scores to our own HubSpot so we can follow up. That is separate from The Garden Party.
how your diagnostic is used

We store an encrypted HubSpot access key, your portal name, the connecting person’s email, and your results on our servers. Connecting also creates a sign-in for that email. We do not resell your data.

To draft the report wording, we send a summary of scores and findings to an outside writing service. A Deep Report summary can also include pipeline totals and owner names. Contact records are not included.

Disconnect stops new scans. It does not erase what we stored, and it does not revoke the HubSpot connection. We keep this until you email oscar@blossomautomation.com and ask us to delete it. More is on the privacy page.

encrypted key · sign-in created · kept until you ask