Privacy

Last updated 12 September 2026

1cue helps salespeople prepare for conversations. Doing that means handling records about the people you sell to, and material from your Google account. This page says exactly what is collected, why, and what is never touched.

What we collect

• Your account. Name, email address and profile picture from Google, used to sign you in and to identify you to colleagues in your organisation.
• Your records. Companies, people, deals, meetings, notes and anything you paste or upload. This is the material 1cue reasons over.
• Google Calendar. Event titles, times and attendees, used to work out which meeting is next and which company it concerns.
• Gmail. Messages involving people already in your records, used to assemble context for those accounts. Your wider mailbox is not read.
• Operational logs. Request timing, errors and usage volume.

What we never collect

• Reference folders. Any local folder you point 1cue at — a codebase, product documents — is read on your machine and never uploaded. Only a distilled summary you choose to publish leaves it.
• What we send the AI, in our logs. The text 1cue sends to the AI model carries your customer records, so our logs record only how long it was and an identifier for the request — never the text itself.
• Payment details. Handled by a payment provider, never by us.

How it is used

To prepare briefs, answer questions about your own records, draft messages you send yourself, and write summaries of your calls. Your content is sent to our model provider solely to produce those results for you. It is not used to train any model, and it is not sold, rented or shared for advertising.

Google user data

1cue’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Concretely: Google data is used only to provide features you can see, never for advertising, never sold, and never used to train models.

Storage and security

• Records are stored in an encrypted database, hosted in the United States.
• Access tokens for Google are encrypted at rest, so routine database access does not expose them.
• Call recordings and transcripts are encrypted at rest.
• Every row belongs to one organisation, and that boundary is enforced at the database layer rather than left to individual queries.

Who can see your records

People in your organisation, according to their role. Managers see metadata — stage, value, next step, activity counts — by default. Reading a call transcript is a separate, logged action, and that log cannot be suppressed by an administrator.

Your control

• Disconnect Google at any time from your Google account permissions, or from within 1cue. Access stops immediately.
• Export or delete your records by writing to the address below.
• Deleting your account removes your records; backups age out within 30 days.

Contact

Questions, exports, or deletion requests: hello@1cue.ai.