HubCoach privacy policy

Account and authentication

The official HubCoach web app can ask the extension to confirm its presence and version in this browser. This reply contains no account, session token or CRM data and does not confirm that you are signed in or have portal access.

We process your email, account identifier, profile details, organization, role and access grants to authenticate you and determine which content and portals you may use. Credentials entered in the extension are sent over HTTPS to Supabase Authentication. The extension stores session access and refresh tokens in Chrome local extension storage; it does not persist the password you enter.

The extension does not collect your HubSpot password. HubSpot connection tokens are managed by the server and stored encrypted. Signing out removes the local HubCoach session; uninstalling the extension does not delete your organization’s server data.

HubSpot context and CRM data

On supported HubSpot pages, the extension reads page context and visible record identifiers, such as portal, object type and record ID. It sends that context to the HubCoach backend, which reads authorized CRM properties and associations through the HubSpot API to evaluate your organization’s rules and show relevant guidance. Depending on the configured rules, these properties can include contact details, company information, deal information and ticket information.

We process the record identifiers, rule results and relevant evidence needed to display and explain a notice. Observations and related activity can be stored in your organization’s workspace. This is not a general browsing-history collector: the extension is designed to work on HubSpot application pages and does not inspect unrelated websites.

Team content and activity

We store the knowledge cards, guides, processes, rules, plans, announcements and media that your organization creates, together with assignments, revisions, favorites, completed steps, acknowledgements and feedback you submit. Operational events such as opening the panel or content are recorded to provide recent activity and usage reports.

Authorized organization members and administrators can access content, progress and reports according to their roles and portal permissions. A completed step is a progress record, not an automatic assessment of employee performance or CRM data quality.

Service providers and optional AI

Supabase provides authentication, databases, storage and backend processing. HubSpot supplies the connected CRM data. Netlify hosts the companion website. These services receive information needed to provide their respective functions; requests and infrastructure logs may include technical information such as IP addresses, timestamps and error details.

The companion web application uses PostHog for product usage and error analytics. Its configured session recording masks input fields; interface content and interaction metadata may still be processed according to the active recording configuration. This web analytics integration is separate from the Chrome extension’s operational events.

When you explicitly use Markdown import or the AI assistant in the web application, DeepSeek receives the submitted text and relevant authorized property metadata; Markdown import can also send existing content needed to compare suggestions and avoid duplicates. HubCoach retains the import fingerprint, reviewable suggestions and short supporting excerpts rather than the full uploaded Markdown. Assistant conversations and suggestions may be retained in your workspace. Opening a HubSpot record does not automatically send its content to DeepSeek.

If your organization adds external images, videos or links, loading them can send your IP address and normal request information to their hosts, including embedded media services. Their own privacy policies also apply.

Use, sharing and security

HubCoach follows the Chrome Web Store User Data Policy, including its Limited Use requirements. Information obtained through Chrome is used only to provide, maintain and secure the guidance features described here. Revenue Hub personnel may read specific user data only with the user’s consent, for security investigations, to meet legal requirements, or as aggregated and anonymized information for internal operations.

We use this information to provide the features you and your organization request, enforce access controls, keep the service reliable and respond to support requests. We do not sell personal data or use it for advertising profiles, creditworthiness or lending decisions. Transfers to service providers are limited to providing these functions; information may also be disclosed where legally required.

Client-server traffic uses HTTPS. Authorization checks restrict access by organization, user, portal and record; session storage is restricted to trusted extension contexts. All executable extension code is packaged with the extension. Remote responses provide data and content, not downloaded executable extension code.

Retention and your choices

Workspace content, assignments and operational records remain on the server until removed through available product controls or an authorized deletion request. Signing out or uninstalling the extension does not erase shared workspace records. Backup and infrastructure-log retention follows the relevant service provider’s configuration; we do not promise a universal automatic deletion interval.

You may sign out, uninstall the extension, ask your organization administrator to revoke access, or contact privacy@revenuehublatam.com to request access, correction or deletion. We verify identity and authorization before acting on shared organization data. Some records may need to be retained to meet legal obligations or resolve disputes.

Contact and changes

For privacy questions, contact Revenue Hub Latam SpA at privacy@revenuehublatam.com. Processing may take place in countries where our service providers operate. This page will be updated when HubCoach’s data practices change, with the revision date shown above.