Cube
Security
Innovube LLC · Effective November 11, 2026
How Cube protects your data, stated as it is. Each badge on our pages links here.
1. Encryption (256-bit)
In short: Encrypted in transit and at rest; secrets you connect are sealed with AES-256.
- In transit: every connection to Cube uses HTTPS (TLS). Services talk to each other over Google Cloud’s private network.
- At rest: the database, backups and stored files are encrypted with AES-256 by Google Cloud.
- Connected-account secrets (CRM tokens, mailbox credentials, Apollo keys) are additionally sealed with AES-256-GCM before they are stored, with a key held only by the services that need it.
- Passwords are never stored: only a one-way bcrypt hash. Two-factor secrets are sealed with AES-256-GCM.
2. Each workspace is kept apart
In short: One company can never see or use another company’s data.
Every record belongs to one workspace. The database itself enforces this (row-level security, forced on every table), and the application connects with roles that cannot bypass it. Your business profile, offerings, contacts, research, Cube’s knowledge and your data-provider keys are used only inside your workspace.
3. Access control
In short: Strong sign-in, roles, and the option to require two-factor for admins.
- Two-factor authentication (authenticator app) for every user; admins can require it.
- Single sign-on with Google or Microsoft.
- Sign-in lockout after repeated failures, rate limits, and a password policy that rejects known-breached passwords.
- Roles (admin, manager, AE, SDR, viewer) decide who can see and change what.
4. Audit trail
In short: Every change and every automated decision is recorded and cannot be edited.
Changes in your workspace and every decision Cube’s agents make are written to an audit log that cannot be edited or deleted, and each entry is linked to the one before it (a hash chain), so any alteration shows. Admins can verify the chain and export the log.
5. Your data and GDPR
In short: Tools to export or erase a person’s data, honour opt-outs, and limit how long data is kept.
- Export everything held about a contact, or erase it (right to be forgotten), from the admin pages.
- Every outreach email carries a one-click opt-out; opted-out people and domains are never contacted again.
- Recording consent and retention settings for meetings; unsent drafts expire and are deleted after a retention period.
- For contacts’ data we act on our customer’s instructions (as a processor). A data processing agreement is available on request at info@innovube.com.
Cube is hosted in the United States (Google Cloud, us-central1). “GDPR ready” means these tools and commitments are in place; meeting GDPR remains a shared responsibility with each customer.
6. Infrastructure and backups
In short: Google Cloud, a private database network, and daily backups.
The database has no public address and is reachable only from Cube’s own services. Backups are taken daily and kept for 14 days, with point-in-time recovery for the last 7 days.
7. AI with a person in the lead
In short: Agents prepare the work; a person sends each email to a contact, or switches on sending for a campaign they chose.
Research, drafting and fact-checking are automated, but no email reaches a contact unless a person sent it or switched on sending for that campaign. Admins can pause any agent instantly (kill switches) and see why each automated decision was made.
8. Compliance status: SOC 2 audit not yet completed
In short: Controls are built and mapped to SOC 2; we do not claim a certification we do not hold.
Cube runs security controls mapped to the SOC 2 Trust Services Criteria (and ISO 27001, NIST CSF and the OWASP ASVS), reviewed in the admin's Security & compliance page. An independent SOC 2 audit has not been completed, so Cube is not SOC 2 certified; we will say so here, with the auditor's name, when it is. Control documentation is available on request at info@innovube.com.
9. Read-only connections to your systems
In short: Cube reads your email and company database; it cannot change them.
- Email context uses separate read-only connections (Gmail read-only, Outlook Mail.Read). Cube never drafts, sends or changes email through them.
- Company-database answers connect with an account that must prove it cannot write; every query runs inside a read-only transaction that is always rolled back, and only questions your data owner approved are answered.
10. Innovube support sees your workspace only if you allow it
In short: Read-only, for the time your admin chooses, and every view is listed for you.
Innovube staff cannot open a customer’s workspace on their own. If you ask us for help, your admin can allow support access for 1 hour, 24 hours or 3 days. During that time support can only look: changes, sending, connecting accounts and exports are refused, and the database itself rejects writes. Every area support opens is listed with the time on your Innovube support access page and in your audit log, and your admin can end access at any moment.
11. Reporting a security issue
In short: Tell us and we will respond quickly.
Email info@innovube.com with "Security" in the subject.