Privacy Policy — Climb GTM Console
The Climb GTM Console is a revenue-operations dashboard operated by Climb Consulting for its clients. This policy covers what the console and its scanning engine collect, how it is used, where it rests, and what control you have. It is written to be checked against the system, not to sound reassuring.
What we collect, and why
- Account data. Your email address and a password hash, held by our authentication provider (Supabase), used only to sign you in and decide which client's data you may see.
- CRM business data. With each client's authorization, our engine reads their CRM (HubSpot) on a weekday schedule to compute pipeline, forecast, funnel, and data-quality metrics. Access is read-only.
- Connection tokens. If you connect your own HubSpot login to edit deals from the console, your refresh token is stored encrypted (AES-256-GCM); the decryption key is held only in the server runtime, never in the database.
- Edit receipts. When you edit a deal through the console, we record who changed which field, from what value to what value, and when.
We use no advertising trackers and no third-party analytics. The console sets no marketing cookies; your session lives in your browser and ends with it.
The unusual part: identity does not rest with us
By design — we call it the leave test — the names in a client's CRM (company names, deal names, people, emails, phones) are never stored in our database or reports. What rests with us is shape (amounts, dates, counts, durations, configuration) and pointers (CRM record ids). Names are resolved live from the client's own CRM at the moment they appear on screen, cached only in your browser tab for the session, and never written to our servers. If Climb's systems were opened tomorrow, they could not name a single customer, prospect, or partner of any client.
Where data lives and how it is protected
- Data rests in a managed Postgres database (Supabase) with row-level security: every query is evaluated against who you are, in the database itself, not in application code.
- All transport is TLS. Credentials and tokens live only in server environment configuration, never in code, never in the browser.
- Each user sees only the clients they are granted; operators are separated from client users by database policy.
Retention
- Identity: never at rest — see above; there is nothing to retain or delete.
- Shape and pointers are retained for the duration of the engagement to power trends, baselines, and the daily record.
- On engagement end or on a client's request: connection tokens are deleted immediately, and CRM-derived data (snapshots, pointers, receipts) is deleted within 30 days. Climb may retain de-identified aggregate measurements — numbers that describe no identifiable company or person — as its engagement record.
Sharing
We do not sell or share client data. One client's data is never used to benefit another without that client's express written permission. Subprocessors: Supabase (database and authentication), Vercel (application hosting), GitHub (engine automation). Each sees only what its role requires.
Your choices
- Disconnect your personal HubSpot connection at any time from Settings, or by revoking the app in HubSpot — either kills the console's ability to write as you.
- Ask us to delete your account or your organization's data: diego@climbconsulting.io.
Questions about this policy: diego@climbconsulting.io. Material changes will be dated at the top of this page.