Access control
- Every table has row-level security. The database itself enforces that people can reach only the data of organizations they belong to.
- No master key in the product. Neither the app nor its server functions hold a service-role database key. Even background builds run as the signed-in user who started them.
- Roles. Each organization has owners, admins and members. Only owners and admins can change the brand profile.
- Staff access. The people who operate Cue can reach the production database through our provider's admin tools for support and incidents. We keep this to what the task needs.
Protecting data
- Encryption. Data is encrypted in transit with TLS and at rest with AES-256 by Supabase, our database provider.
- Private files. Past decks and talk documents sit in a private bucket that only organization members can read.
- Public files. Logos and image library files sit in a public bucket, because slides on the audience screen must load them without signing in. Anyone with the exact file address can view them, so keep confidential material out of them.
- Audience links. Each talk has its own unguessable link, which you can replace at any time. An audience screen holds only the opening slide and each slide as it comes up, so slides that have not come up can't be read from it, even with a browser's inspect tools. Only members of the organization can change what audience screens show, and these pages tell search engines not to index them.
- Secrets. API keys are held as server secrets and never reach a browser. Our AI prompts run on the server only.
- In the browser. A content security policy limits where pages can load code from. Like every website, the code that runs in your browser can be read with inspect tools, so we keep nothing secret in it.
During a live talk
- Matching speech to slides runs in your browser, with no network hop for that decision.
- Cue never receives audio. Your browser's speech recognition returns text, and in Chrome that recognition is done by Google unless you choose to keep your voice on your computer. Our Privacy Policy explains this.
- Transcript text is saved with each slide decision so you can review the talk. Deleting the talk deletes it.
Website
Our public pages load no third-party scripts, analytics or trackers, and our fonts are served from our own site. The whole site is served over HTTPS.
What we do not have yet
Cue is an early product, and we would rather be clear about this than have you assume otherwise.
- Cue itself has no SOC 2 or ISO 27001 certification. Supabase, which holds our data, is SOC 2 Type 2 compliant, but that does not extend to Cue.
- Cue has not yet had an independent penetration test.
- Cue has no single sign-on (SSO) or SCIM yet.
- Deleting an organization or account is done by request, not yet in the product.
- Session transcripts are kept until you delete them. There is no automatic retention limit yet.
Report a security issue
If you think you have found a vulnerability, contact us. Please give us reasonable time to fix it before making it public, and do not access other people's data while testing. We will not take action against good-faith research that follows these rules.