Skip to content

Solution Security

This page describes how the HubSpot CTI Connector is deployed and how it handles data, for security and compliance reviewers evaluating the product.

Tenancy model

The connector is single-tenant: each customer runs their own dedicated deployment, inside their own AWS account, provisioned via the CloudFormation template in the Deployment Guide. There is no shared application server or shared database between customers — your deployment, your infrastructure, your data.

Data handling

Data Where it lives
Contact cache (phone number → HubSpot contact ID, used to speed up screenpop lookups) DynamoDB, in your AWS account
Connector configuration (toggles, dispositions, screenpop rules) DynamoDB, in your AWS account
Call recordings Your existing Amazon Connect S3 recording bucket — the connector references it, it doesn't copy recordings elsewhere
Call transcripts Generated by Amazon Connect Contact Lens and written directly to the matching HubSpot call/communication record
Credentials and secrets (HubSpot tokens, JWT signing key, license key) AWS Secrets Manager, in your AWS account

The connector does not send call, chat, or WhatsApp content to any Octave Bytes-operated system. HubSpot record data, call metadata, and message content flow between your AWS account, HubSpot, AWS Connect, and (for WhatsApp) your WhatsApp provider — the systems you already use and control access to.

Transport security

  • All traffic to the connector is served over HTTPS, using a certificate you request and validate through AWS Certificate Manager as part of deployment.
  • The Chrome extension never calls HubSpot, AWS Connect, or any external API directly — every request is proxied through your connector deployment.

Authentication

Layer Mechanism
HubSpot access OAuth 2.0 — the connector requests only the scopes it needs (contacts, deals, tickets, companies, calls, communications) and you approve them during install
Agent login Verified against your live AWS Connect agent identity, plus your Octave Bytes license (customer, portal, seat count, expiry)
Agent sessions Short-lived signed tokens, tied to a specific agent and Connect instance
Admin portal Separate password-based login, independent from agent authentication

Licensing

Each deployment is bound to an encrypted license key that enforces the customer, HubSpot portal, seat count, and expiry agreed with Octave Bytes. Admins can view current license status and update the key from the admin portal's License Details page.

Questions

If your security or procurement team needs more detail than is covered here — architecture diagrams, a completed questionnaire, or a call with our team — contact sales@octavebytes.com.