Cube

Privacy Policy

Innovube LLC · Effective November 11, 2026

This policy explains what personal information Cube handles, why, and the choices you have. Each section starts with a short plain-language summary; the full text of the section is what applies.

1. Who this policy covers

In short: It explains what information Cube handles, for the people who use it and for the people who appear in it.

Innovube LLC ("Innovube", "we", "us") provides Cube (the "Service") to businesses. This policy describes the personal information we handle when someone uses the Service or visits its pages.

There are two kinds of people in the Service. Users are the people in a customer company who have an account. Contacts are the people a customer talks to, emails or researches, such as prospects and meeting participants. For information about Contacts we act on the instructions of our customer, who decides what is collected and why; if you are a Contact, the company that contacted you is the right place to start, and we will help them answer you.

2. What we collect

In short: Account details, the content your team puts in or captures, connected-account data, and technical records such as sign-ins and IP addresses.

Account information: name, work email, company, role, password (stored only as a one-way hash), and settings such as an email signature.

Content your team creates or captures ("Customer Data"): meeting recordings and transcripts, notes and summaries, practice-call recordings, emails and campaign content, uploaded documents, company and contact records, and research the Service produces for you.

Information from accounts you connect: if you connect a calendar, mailbox, meeting platform or CRM, we receive the information needed for the features you use, such as meeting details, the emails the Service sends or reads for you, and the records it keeps in sync.

Information about companies and business contacts that the Service finds for you from public sources and from data providers you enable.

Technical and security records: sign-ins and sign-outs, failed sign-in attempts, the IP address and time of security-relevant actions, and a record of changes made in your workspace (the audit log).

Payment information: payments are handled by our payment provider. We receive confirmation of payment and a reference to it; we do not receive or store your full card number.

3. How we use it

In short: To run the Service for you, keep it secure, bill for it and support you.

  • to provide the Service: join and transcribe meetings, speak in them when you ask Cube to, produce notes, follow-ups, research and reports, and send the emails you approve (a person sends every email to a prospect);
  • to keep accounts and data secure, prevent abuse, and keep an audit record;
  • to measure usage against your plan's allowances and to bill you;
  • to answer your questions and tell you about important changes to the Service;
  • to understand which features are used so that we can improve the Service;
  • to meet legal obligations and enforce our agreements.

We do not sell personal information, and we do not use Customer Data to train artificial intelligence models of our own.

4. Artificial intelligence

In short: AI providers process your content to produce results for you. They work on our behalf.

Many features use artificial intelligence, including speech recognition, a voice model for Cube, and language models for notes, research and drafting. To produce results, the relevant content (for example meeting audio, a transcript, or the details of a company being researched) is sent to AI providers that process it on our behalf.

AI results can be wrong. Please review them before relying on them.

5. Email you connect for context (read-only)

In short: If you connect "Gmail — Read" or "Outlook — Read", Cube reads only relevant threads to prepare you for calls, keeps short extracts, and never changes your mailbox.

These connections are separate from the mailbox used to send campaign emails. They ask Google only for read-only Gmail access (gmail.readonly) and Microsoft only for read-only mail access (Mail.Read). Cube refuses a connection that grants more.

What Cube reads: only email threads with contacts and companies already in your Cube workspace, or only the one label or folder you choose, within the look-back period your workspace sets. It never reads your whole inbox. Threads matching your administrator's exclusions (for example HR, legal, medical or personal topics, or chosen domains and senders) are never read, and you can exclude any thread yourself.

Why: to prepare you for calls. Cube shows the latest emails with an account, open commitments and unanswered questions, and cites them (for example "from Joe's email on Nov 13"). Cube only suggests; it never drafts, sends, replies, forwards, deletes, archives, labels, marks as read or changes anything in your mailbox.

What Cube keeps: short extracts with sensitive details masked (summaries, key facts, commitments, questions and references to the messages), never full mailboxes, for the retention period your workspace sets. Disconnecting deletes everything Cube kept from that mailbox, and the deletion is recorded. Your email context is visible only to you and the people your administrator allows. Every read, use and deletion is recorded in the audit log, without email contents.

Google user data: Cube's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace APIs is not used to create, train or improve artificial intelligence or machine learning models, and people at Innovube do not read it except with your permission, for security, or when the law requires it.

6. Who we share it with

In short: Only the service providers needed to run the product, the accounts you connect, and authorities when the law requires it.

We share personal information only as follows:

  • with service providers that help us run the Service, under contracts that limit what they may do with it: cloud hosting and storage, AI providers, the payment provider, email delivery through the mailbox you connect, and data providers you enable for research;
  • with the third-party accounts you choose to connect, such as your meeting platform, calendar, mailbox or CRM, to do what you asked;
  • within your own company: admins of your workspace can see their team's activity in it, including sign-in history;
  • when the law requires it, or to protect the rights, safety and property of our customers, the public or us;
  • with a successor, if our business is merged or sold, subject to this policy.

Each customer's data is kept separate from every other customer's.

7. How long we keep it

In short: For as long as your company has an account, with shorter periods for recordings, and for a limited time afterwards.

We keep Customer Data for as long as your company has an account, so the Service can work. Stored call recordings are deleted automatically after 90 days. Your admin can delete records in the Service, and you can ask us to delete information.

After an account is closed, we delete or de-identify its Customer Data within a reasonable period, except where we must keep something to meet a legal obligation, resolve a dispute or enforce our agreements. Security and audit records may be kept longer for those purposes.

8. Security

In short: We protect your information, and we ask you to protect your account.

We use measures designed to protect personal information, including encrypted connections, storing passwords only as one-way hashes, sealing the credentials of connected accounts, separating each customer's data, optional two-step sign-in, and an audit record of security-relevant actions. No system is completely secure; if we learn of a breach affecting your information we will tell you as the law requires.

9. Cookies

In short: We use a cookie to keep you signed in. We do not use advertising cookies.

The Service uses a cookie that keeps you signed in; it is necessary for the Service to work. We may also use product analytics to understand how features are used, configured so that on-screen text is masked. We do not use advertising or cross-site tracking cookies.

10. Your choices and rights

In short: You can ask to see, correct or delete your information. Start with your admin, or write to us.

Depending on where you live, you may have the right to ask for access to your personal information, to have it corrected or deleted, to receive a copy, or to object to or limit certain uses. You will not be treated differently for using these rights.

If you are a User, your workspace admin can help with most requests, and you can write to us at info@innovube.com. If you are a Contact, please first contact the company that used the Service to reach you; we will support them in responding, and you may also write to us. We may need to confirm who you are before acting on a request.

Every campaign email sent through the Service includes a way to stop receiving them.

11. Where information is processed

In short: In the United States, and wherever our service providers operate.

We are based in the United States and process information there and in other countries where our service providers operate. Where the law requires it, we use appropriate safeguards for transfers of personal information between countries.

12. Children

In short: The Service is for businesses and is not meant for children.

The Service is not directed to anyone under 18, and we do not knowingly collect personal information from children.

13. Changes and contact

In short: We will tell you about important changes. Write to us with any question.

We may update this policy. When a change is material we will show the new version in the Service and ask you to accept it. The date at the top shows when this version took effect.

Questions or requests about privacy: info@innovube.com.

Privacy Policy · Cube