Docs

What we read, and never read

Definitions, not records: the exact reads each connection makes.

The collector reads what your automations are, never what they hold.

HubSpot

Workflows with their triggers, enrollment criteria, branches and actions. Forms and the properties they write. Lists and their filters. Property definitions, groups, pipelines and stage orderings. The six scopes the private app needs are all read scopes, and none of them grants access to a record.

GitHub

The files in the repositories you connect, read with a token that has Contents: read on those repositories and nothing else. The scan looks for the names of CRM fields the graph already knows.

Google Cloud

The scheduled jobs, functions and services in the project you grant, and the messaging that connects them. No code, no data.

Never

No contact, company, deal or ticket is ever requested. Nothing in the product has a place to put a person's data.

Where it runs

On your machine, the app binds to localhost, the graph is a SQLite file in a folder you choose, and every token stays in an env file beside it. Hosted, the graph lives in a database with row-level security that follows membership, the collector runs on a schedule, and we hold your tokens in a secret store the collector reads and nothing else can. The Studio plan runs the collector on your side and sends us only the graph.

This site

Loads no third-party script, no analytics, no fonts from a network. The pictures are rendered from an invented portal.