Security
Last updated November 16, 2026
What your privacy, security and procurement teams usually ask about Cue, in plain words. The documents behind it:
- Data processing agreement (Art. 28 GDPR): part of the terms for business customers, with a copy to sign if you need one.
- Technical and organisational measures (its Annex 2): every measure in detail.
- Subprocessors (its Annex 3): who processes data for Cue, where, and how changes are announced.
- Privacy notice: everything Cue stores, why and for how long.
Who runs Cue
Cue is made and run by one person: Zyad Abuzeid, trading as Pink Panther Labs, Prenzlauer Promenade 191, 13189 Berlin, Germany. Only he has administrative access to Cue's production systems. Cue has no servers of its own: it runs on Cloudflare.
Where your data is
| What | Where |
|---|---|
| The database: workspaces, decks and their versions, brand kits and their pictures, data sources, accounts | Cloudflare D1, placed in Cloudflare's Eastern Europe region by a location hint. A hint isn't a guarantee: Cue hasn't restricted the database to the EU. |
| Its backups | Cloudflare D1's point-in-time recovery, kept for at most 30 days |
| Live presentations | A Cloudflare data centre near where the presentation started; deleted 24 hours after its last activity |
| Sign-ins of AI apps connected over MCP | Cloudflare Workers KV, replicated across Cloudflare's network; tokens only as hashes |
| Requests and logs | The Cloudflare data centre nearest the visitor; logs kept by Cloudflare for a few days |
| AI features | OpenAI, in the United States, with storage turned off (OpenAI may keep requests for up to 30 days to detect abuse, and doesn't train on them) |
| Emails | Resend, in the United States |
Transfers to the United States rely on the EU–U.S. Data Privacy Framework or on standard contractual clauses, per subprocessor.
How Cue protects it
- Sign-in: with Google or a single-use emailed link that expires in 15 minutes. Session cookies are
HttpOnly,Secureand host-only (__Host-), and the database keeps only a hash of each session ID. You can see and end your sessions. - Roles: presenter, editor, admin or owner, checked on every request, including every tool call from a connected AI app.
- Encryption: Cue is served only over HTTPS (TLS), and browsers are told never to use plain HTTP (HSTS); Cloudflare encrypts stored data (AES-256); tokens and keys for the apps you connect are encrypted again by Cue (AES-256-GCM).
- Links: a deck's private address lets in only members, and guests at email domains you allow who confirm their address with a one-time code. Links for anyone carry a random secret, can expire and can be revoked.
- Connected apps: Cue only ever calls tools that read. Google access covers only the files you pick; Stripe takes only restricted keys.
- History: every change to a deck is a version recording who made it, and a workspace's audit log records who did what.
- The browser: a strict Content-Security-Policy: scripts only from Cue, Google's file picker and Cloudflare's cookieless analytics, and no other site may frame Cue. No advertising or third-party trackers.
- Fetching: addresses people type are fetched only on the public internet, never from private networks, with time and size limits.
- Abuse: rate limits on sign-in, codes, guessed links and votes; caps on AI use.
What Cue doesn't have
- No certification: Cue holds no ISO/IEC 27001 certificate, SOC 2 report or similar attestation of its own. The GDPR doesn't require one; Cloudflare's own certifications cover the data centres Cue runs in.
- No outside penetration test.
- No EU-only hosting guarantee: see where your data is, above.
- No service level: Cue makes no uptime commitment.
- No sign-in through your company's identity provider (such as SAML): people sign in with Google or an emailed link.
Deleting data
An owner can delete a workspace in Settings. It disappears at once, can be restored for 30 days, and is then removed with everything in it; backups roll off within a further 30 days. To delete your account, email us. The privacy notice gives every other retention period.
Security questionnaires and a signed DPA
Send your questionnaire, or ask for a countersigned data processing agreement, to hello@pinkpantherlabs.com.
Reporting a vulnerability
If you think you've found a security problem in Cue, email hello@pinkpantherlabs.com with what you found and how to reproduce it. We'll confirm we got it within three working days and tell you when it's fixed.
Please test only with accounts and workspaces of your own, don't read or change other people's data beyond what you need to show the problem, don't disrupt Cue (no denial-of-service or spam), and give us reasonable time to fix it before you tell anyone else. We won't take legal action against research that follows these rules. There's no bug bounty.