Data processing agreement
Under Article 28 GDPR (in German practice, an Auftragsverarbeitungsvertrag). Version 1, last updated November 16, 2026
How this agreement applies
- No signature needed. For business customers, this agreement is part of Cue's terms of service. It applies as soon as a company or other organisation uses Cue, and it covers the personal data in its workspaces.
- A signed copy, if you need one. Save this page as a PDF (your browser's Print, then Save as PDF), fill in the signature block at the end, sign it and email it to hello@pinkpantherlabs.com. We countersign it and send it back. The signed copy says the same as this page.
- Its annexes: Annex 1 describes the processing, Annex 2 the technical and organisational measures, and Annex 3 the subprocessors. The security overview sums them up in plain words.
1. Parties and scope
1.1 This agreement is between the business customer that uses Cue (the "Customer", the controller) and Zyad Abuzeid, trading as Pink Panther Labs, Prenzlauer Promenade 191, 13189 Berlin, Germany (the "Processor"). The Customer is the company or other organisation that runs one or more workspaces in Cue; the people who accept the terms of service for it accept this agreement for it too.
1.2 It covers the personal data that the Processor processes on the Customer's behalf while providing Cue under the terms of service (the "Agreement"): what the Customer's workspaces hold and the data about people who use or view them, as Annex 1 describes ("Customer Personal Data").
1.3 It doesn't cover data the Processor processes as a controller itself, as the privacy notice describes: people's Cue accounts and sign-in sessions, the website and its analytics, where sign-ups come from and first steps, request logs and rate limits that keep Cue secure, and correspondence with the Customer. Payments for paid plans are handled by Paddle as reseller and merchant of record, which is a controller of its own (see Annex 3).
1.4 Words such as "personal data", "processing", "controller", "processor", "data subject", "personal data breach" and "supervisory authority" have the meaning the General Data Protection Regulation (EU) 2016/679 ("GDPR") gives them.
1.5 Where this agreement and the terms of service disagree on the protection of personal data, this agreement prevails. Where standard contractual clauses apply, they prevail over both.
2. Subject matter, duration, nature and purpose
2.1 The subject matter is providing Cue to the Customer: writing, editing, branding, presenting and sharing decks, connecting data to them, and the features that go with them. The nature and purpose of the processing, the types of personal data and the categories of data subjects are in Annex 1.
2.2 The processing lasts as long as the Customer uses Cue under the Agreement and, after that, until Customer Personal Data is deleted as section 11 describes.
2.3 The Customer won't put special categories of personal data (Art. 9 GDPR) or data about criminal convictions and offences (Art. 10 GDPR) into Cue, as the terms of service's acceptable use rules say.
3. Instructions
3.1 The Processor processes Customer Personal Data only on the Customer's documented instructions, including with regard to transfers to a third country, unless EU or Member State law to which the Processor is subject requires it to process it otherwise. In that case the Processor tells the Customer of that legal requirement before processing, unless that law prohibits it on important grounds of public interest.
3.2 The Customer's instructions are the Agreement and this agreement; the way the Customer's members use and set up Cue (for example its settings, sharing a deck, connecting a data source or an app, or asking Cue's AI to write or translate); and further instructions a workspace owner gives in text form, such as by email, within the scope of the Agreement. Instructions beyond that scope are agreed separately.
3.3 The Processor tells the Customer immediately if, in its opinion, an instruction infringes the GDPR or other EU or Member State data protection law, and may hold off on following it until the Customer confirms or changes it.
3.4 The Customer is responsible for the lawfulness of the processing it instructs, including having a legal basis for it and informing the people concerned. Where Cue identifies readers of a private link, it tells them so before they read; a workspace's admins can turn that off.
4. Confidentiality
The Processor ensures that everyone authorised to process Customer Personal Data has committed themselves to confidentiality or is under an appropriate statutory obligation of confidentiality. Today that is only the Processor himself; anyone given access later commits to confidentiality in writing before getting it. The obligation continues after the Agreement ends.
5. Security of processing
5.1 The Processor takes the technical and organisational measures in Annex 2 to ensure a level of security appropriate to the risk, as Art. 32 GDPR requires.
5.2 The measures follow technical progress. The Processor may change them as long as the overall level of protection doesn't go down, and keeps Annex 2 up to date.
6. Subprocessors
6.1 The Customer gives the Processor general written authorisation to engage subprocessors. The subprocessors in Annex 3 are approved.
6.2 At least 30 days before a new or replacement subprocessor starts processing Customer Personal Data, the Processor tells the owners of the Customer's workspaces by email, saying who it is, what it will do and where, and adds it to Annex 3 with the date.
6.3 The Customer may object to the change in text form within that notice period on reasonable grounds relating to data protection. The parties then look for a solution in good faith. If they don't find one, the Customer may end the Agreement for the affected workspaces before the change takes effect, and the Processor refunds, through Paddle, what the Customer paid in advance for the time after that. Without an objection within the notice period, the change counts as approved.
6.4 If a subprocessor has to be replaced at shorter notice to protect Customer Personal Data or to keep Cue running (for example, because it stops its service or suffers a security incident), the Processor tells the Customer as soon as it can, and the Customer's right to object under 6.3 applies from that notice.
6.5 The Processor imposes on each subprocessor, by contract, data protection obligations that offer the same level of protection as this agreement, in particular sufficient guarantees for appropriate technical and organisational measures. The Processor remains liable to the Customer for its subprocessors' performance of those obligations.
6.6 Services that the Customer's members choose to connect or use with Cue aren't the Processor's subprocessors: the business apps and data sources they connect (for example Stripe, HubSpot, Google Drive and Sheets, Notion or another MCP server), the websites they import from, and the AI apps they connect to Cue's MCP server (for example Claude, ChatGPT or Cursor). Cue exchanges data with them on the Customer's instruction, and they process it under the Customer's own arrangements with them.
7. Where data is processed, and transfers
7.1 The Processor is in Germany. Cue's database is placed in Cloudflare's Eastern Europe region by a location hint, which Cloudflare doesn't guarantee; Cloudflare handles requests and runs live sessions in its data centres worldwide; OpenAI and Resend process data in the United States. Annex 3 says where each subprocessor processes data.
7.2 Customer Personal Data is transferred outside the European Economic Area only to the subprocessors in Annex 3, and only under Chapter V GDPR: an adequacy decision (for a recipient in the United States, its certification under the EU–U.S. Data Privacy Framework) or the European Commission's standard contractual clauses (module 3, processor to processor) in the subprocessor's data processing terms, with supplementary measures where they're needed.
7.3 If a transfer mechanism stops being valid, the Processor moves to another valid one or tells the Customer without undue delay, and section 6.3 applies.
8. Data subjects' rights
8.1 Taking into account the nature of the processing, the Processor helps the Customer, by appropriate technical and organisational measures and insofar as this is possible, to respond to requests from people exercising their rights under Chapter III GDPR. Cue's own controls cover most requests: members change their name and picture, admins remove members, editors delete decks, sources and pictures, admins turn off identifying readers, owners delete workspaces, and decks export as PowerPoint and PDF files. Where Cue has no control for a request (for example, removing a person's name from a deck's earlier versions), the Processor carries it out on the Customer's instruction.
8.2 If someone sends the Processor a request about Customer Personal Data, the Processor passes it to the Customer without undue delay and doesn't answer it itself beyond telling the person it has done so, unless the Customer instructs it to.
9. Assistance with security, impact assessments and consultations
Taking into account the nature of the processing and the information available to it, the Processor helps the Customer to meet its obligations under Art. 32 to 36 GDPR (security of processing, notifying personal data breaches, data protection impact assessments and prior consultation): with this agreement and its annexes, the privacy notice and the security overview, and by answering the Customer's reasonable questions about the processing.
10. Personal data breaches
10.1 The Processor notifies the Customer of a personal data breach affecting Customer Personal Data without undue delay, and within 48 hours of becoming aware of it, by email to the owners of the affected workspaces (and to the contact named in a signed copy of this agreement).
10.2 As far as it knows them, the notification describes the nature of the breach, including the categories and approximate number of people and records concerned; its likely consequences; the measures taken or proposed to address it and to mitigate its possible adverse effects; and a contact for more information. Where not everything is known at once, the Processor provides the information in phases, without further undue delay.
10.3 The Processor takes reasonable steps to contain and investigate the breach and to mitigate its effects, documents it, and helps the Customer notify the supervisory authority and the people concerned where the Customer has to.
11. Deletion and return
11.1 At any time, the Customer's members can export decks (as PowerPoint and PDF files) and delete what they hold in Cue. On request, before the Customer's workspaces are deleted, the Processor provides the rest of the Customer Personal Data in a common machine-readable format.
11.2 When an owner deletes a workspace, it disappears from Cue at once and can be restored for 30 days. After that it's purged with everything in it. Cue's database backups (Cloudflare D1's point-in-time recovery, called Time Travel) are kept for at most 30 days, so the workspace's data has left them within a further 30 days. Live sessions' data is deleted 24 hours after their last activity, and other data within the periods the privacy notice gives.
11.3 When the Agreement ends, the Customer deletes its workspaces, or the Processor deletes them as in 11.2 within 30 days of the Customer asking it to in text form, unless EU or Member State law requires the Processor to keep the data. On request, the Processor confirms the deletion in text form.
12. Information and audits
12.1 The Processor makes available to the Customer all information necessary to demonstrate compliance with Art. 28 GDPR: this agreement and its annexes, the privacy notice, written answers to the Customer's reasonable security questionnaires (one a year, and after a personal data breach), and its subprocessors' certifications and audit reports as far as they make them available.
12.2 If that information isn't enough to demonstrate compliance, or a supervisory authority requires it, the Customer, or an independent auditor bound to confidentiality who isn't a competitor of the Processor, may carry out an audit, including an inspection. The Customer announces it in text form at least 30 days ahead (less after a personal data breach), limits it to once a year (unless after a breach or at a supervisory authority's request), holds it during normal business hours in Berlin, and makes sure it doesn't disrupt Cue or expose other customers' data or Cue's security. The Processor runs no servers of its own, so an audit takes place remotely or at the Processor's office; its subprocessors are audited through their own certifications and reports. Each party bears its own costs.
12.3 The Processor keeps a record of processing activities under Art. 30(2) GDPR and cooperates with the supervisory authorities.
13. Liability
Art. 82 GDPR governs liability towards the people concerned. Between the parties, the liability rules of the terms of service apply, as far as the law allows.
14. Term, changes and final provisions
14.1 This agreement takes effect when the Customer accepts the terms of service, or signs it, and ends when the Agreement has ended and Customer Personal Data has been deleted. Sections 4 and 11 continue after that, as long as needed.
14.2 The Processor may change this agreement where the law requires it, or where the change doesn't lower the protection of Customer Personal Data, by telling the owners of the Customer's workspaces by email at least 30 days ahead. Changes to Annex 3 follow section 6. A signed copy keeps its version, except for Annexes 2 and 3, which follow sections 5 and 6.
14.3 The Processor isn't required to appoint a data protection officer. For questions about data protection, write to hello@pinkpantherlabs.com. The Processor's supervisory authority is the Berlin Commissioner for Data Protection and Freedom of Information (Berliner Beauftragte für Datenschutz und Informationsfreiheit).
14.4 Notices and instructions under this agreement may be given in text form, such as by email.
14.5 German law applies. If the Customer is a merchant, the place of jurisdiction is Berlin. If a provision of this agreement is invalid, the rest stays in force, and the parties replace it with a valid one that comes closest to its purpose.
Annex 1: Details of the processing
Categories of data subjects
- Members of the Customer's workspaces and people invited to them (typically its employees and contractors).
- Identified readers of the Customer's private links: members who are signed in, and guests at email domains the Customer allows who proved their address with a one-time code (typically the Customer's colleagues, clients and partners).
- Viewers of share links, and followers of live presentations and people who take part in them through their own AI assistant, who aren't identified.
- People named on a review's audience list or as a share link's recipient, and other recipients of emails Cue sends for a workspace.
- People who appear in the Customer's content: in its decks, speaker notes and data sources, in its brand kits' pictures, and in the details of the companies it makes decks for (its customers and prospects), as far as these hold personal data.
- People whose accounts at other services the Customer's members connect (the account name or email address the service reports).
Types of personal data
- Members: name, email address and picture as shown in the workspace, role and how they joined (including by the Customer's email domain), a presenter's open request for edit access, invitations, the people who left the workspace or were removed, and their actions: who made each version of a deck (a person, or an AI app acting for them) with the instruction behind it, the workspace's audit log of who did what and when, and how long each deck imported from its link kept a browser open.
- Content: decks and every version of them, speaker notes, imported presentations' text and pictures (for a deck imported from its link, only the link's host), brand kits with their logos, image libraries (pictures, where they came from, who added them, descriptions and tags) and characters, companies (name, website domain, logo, color, a paragraph on what they do), data sources and the values read from them, review series and their audience lists, share links with their labels and recipients, notifications, and translations of a deck's text.
- Connections to other services: which service, the account name or email address it reports, the read-only tools Cue may use, and access tokens or API keys, encrypted; for Google, the list of files chosen.
- Identified readers and guests: email address, when they opened a link and were last active, which version they saw and the seconds spent on each slide; for guests, a hash of their one-time code and of their guest pass, and an audit log entry that they got in.
- Share-link viewers: a hash of a random ID their browser keeps, when the view started and was last active, which version they saw and the seconds spent on each slide; readers' poll votes as counts with a keyed hash per poll and browser. No IP addresses or user agents.
- Live sessions: the follower ID the session issued, a salted hash of the follower's IP address (both kept only during the session's life), questions with an optional name, votes, upvotes and reactions, and on live activity slides the team a follower picked, their points and actions and shout-outs with an optional name; for people taking part through an AI assistant, a random pass instead of a follower ID and a salted hash of the address the assistant calls from (also kept only during the session's life); afterwards only poll results, questions with their upvotes and moderation, counts of followers, and each activity's totals, its teams' points and the shout-outs that were shown.
Nature of the processing
Storing and hosting; drawing decks in the browser, as PDF and as PowerPoint files; importing decks from files and, by opening their page in Cloudflare's browser, from their links; presenting live and sharing through links; reading connected data sources and services on the Customer's instruction; sending a deck's content to OpenAI to write, edit, import, describe pictures, make pictures and translate, when a member or reader asks for it; sending emails through Resend; counting views; and deleting.
Purpose
To provide Cue to the Customer under the Agreement, keep it secure and support the Customer's use of it.
Duration and retention
For the duration of the Agreement, and then until deletion under section 11. Within it, the periods in the privacy notice apply (for example: live sessions' data 24 hours after their last activity, one-time codes about a day, guest passes 30 days).
Annex 2: Technical and organisational measures
These are the measures Cue takes under Art. 32 GDPR. They describe what Cue's code and operation do today. Cue holds no certification of its own (see the security overview).
Organisation and people
- Cue is run by one person, Zyad Abuzeid, its operator. There are no employees. Only the operator has administrative access to Cue's production systems: the Cloudflare account (with the database, the Worker's secrets and its logs) and the accounts at OpenAI, Resend and Paddle.
- The operator looks at Customer content only to provide support the Customer asks for, to investigate security issues or abuse, or where the law requires it.
- The operator is bound to confidentiality (section 4). Anyone given access in the future commits to confidentiality in writing first and gets only the access their work needs.
- These measures are reviewed at least once a year and whenever Cue changes how it stores or sends data.
Physical access
- Cue runs no servers or data centres of its own. Its production systems run in Cloudflare's data centres, whose physical security Cloudflare is responsible for and has certified (including ISO/IEC 27001 and SOC 2 Type II reports, at Cloudflare's trust hub).
- The computer Cue is administered from has an encrypted disk.
Access to systems (sign-in)
- People sign in with Google (OpenID Connect with PKCE, checking the state and nonce) or with a single-use emailed link that expires after 15 minutes and is stored only as a hash. Sign-in emails are limited per email address and per IP address.
- A session is a random 256-bit ID in a signed cookie that is
HttpOnly,Secure,SameSite=Laxand carries the__Host-prefix, which pins it to Cue's host. The database stores only the ID's SHA-256 hash. Sessions end after 30 days or on sign-out, and people can see and end their sessions under Profile. - AI apps connect to Cue's MCP server through OAuth; Cue stores only hashes of their tokens, and a connection ends after 30 days without use. There are no shared API keys.
- Cue's own secrets (the session signing key, the key that seals connector tokens, API keys for its subprocessors) are stored as encrypted Cloudflare Worker secrets, never in its source code, which is kept in a private repository.
Access to data (authorisation)
- Every member has a role in a workspace: presenter, editor, admin or owner. Every API route checks the least role its action needs before it does anything, and MCP tool calls check the person's membership again on every call.
- Every record belongs to a workspace and every query names it; a deleted workspace is invisible to everything but restoring and purging it.
- A private link never opens anything by itself: it lets in the workspace's members and, where the Customer allows an email domain, guests who proved an address there with a one-time code (10 minutes, five tries, stored as a hash). Everyone else gets the same "ask for access" answer whether or not the deck exists.
- Links meant for anyone carry a random secret (at least 65 bits), can expire and can be revoked. Pictures in brand kits' libraries are served under 128-bit random keys.
- Cue calls only tools that read from the services people connect, decided on the server on every call. Google access is limited to the files a person picks (
drive.file); Stripe takes only restricted, read-only keys, and Cue keeps no customer names, emails or payment details from it.
Transmission
- Cue is served only over HTTPS (TLS) through Cloudflare: a request over plain HTTP is redirected to HTTPS, and browsers are told to use HTTPS only (HSTS). Cue sends data to its subprocessors over TLS.
- Requests to OpenAI are sent with storage turned off; under OpenAI's API terms, API data isn't used to train models.
- Addresses people type (data sources, websites to import from, connected servers) are fetched only on the public internet: every host and every redirect is checked against private and internal address ranges, including through a DNS lookup, with a time limit and a size cap.
- A Content-Security-Policy lets the app and website run scripts only from Cue, Google's file picker and Cloudflare's analytics (no evaluated code, and no inline script but one Cue allows by its hash), send data only to Cue and that analytics, and keeps every other site from framing Cue.
Encryption and pseudonymisation
- Cloudflare encrypts Cue's database, live sessions' storage and its key-value store at rest (AES-256).
- Tokens and API keys for connected services are additionally encrypted by Cue before they're stored: AES-256-GCM with a key derived (HKDF-SHA-256) from a secret only the Worker holds, a fresh IV for every value, and bound to the record it belongs to.
- Session IDs, sign-in links, one-time codes, guest passes, presenter and moderator tokens, MCP tokens and the secrets of claim links are stored only as hashes.
- Share links never identify who opened them: Cue keeps a hash of a random browser ID, and no IP addresses or user agents. Followers of live sessions are anonymous, and their IP addresses are kept only as a salted hash, inside the session, until its data is deleted. People who take part through an AI assistant need no account: they get a random pass, and the address the assistant calls from is kept the same way.
Data minimisation
- Cue uses no advertising or third-party trackers, and its website analytics sets no cookies.
- Presentations and files people import, and screenshots they upload for a product demo, are used for that request and not kept.
- Translation sends a deck's text, never its numbers, bound values or speaker notes. Importing a presentation sends the model its slides' text, never its pictures or speaker notes.
Input control
- Every change to a deck's content is a new version that records who made it (a person, or an AI app acting for them) and the instruction behind it. History is never rewritten; restoring is a new version.
- Changes to a workspace (members and roles, links, brand kits, settings, guests who got in, moves and deletions) are written to its audit log, which its admins can read.
Availability and recovery
- Cue runs on Cloudflare's network, which spreads load across its data centres and absorbs denial-of-service attacks.
- Cloudflare keeps point-in-time recovery for Cue's database (D1 Time Travel) for at most 30 days, and the operator marks a restore point before every change to the database's structure.
- Rate limits per IP address protect sign-in, live-session codes, guessed links, one-time codes, readers' votes, translations, AI assistants taking part in live sessions, the contact form and the website preview; monthly and daily caps limit AI use.
Separation
- Each customer's data is kept apart by workspace (logical separation in a shared database), as under access to data above.
- Development and automated tests run on local databases with made-up accounts and data, apart from production.
Testing and evaluation
- Every change to Cue's code runs automated test suites before it ships, including checks of roles, link access and the Content-Security-Policy.
- Each release follows a written routine: every suite, browser checks, a restore point before database changes, and checks against production after deploying.
Subprocessors
- Subprocessors are chosen for their security, bound by their data processing terms, and announced as section 6 describes (Annex 3).
Annex 3: Subprocessors
These companies process Customer Personal Data for Cue. A change to this list is announced to workspace owners by email at least 30 days before it takes effect, and dated below (section 6).
Cloudflare, Inc.
- What for: hosting and network (Workers), the database (D1), live sessions (Durable Objects), the MCP server's sign-in store (Workers KV), PDF export and importing decks from their links (Browser Rendering), logs, and website analytics.
- Data: everything Cue stores, and requests to Cue.
- Where: the database in Cloudflare's Eastern Europe region (by location hint, which Cloudflare doesn't guarantee); requests, live sessions and logs in Cloudflare's data centres worldwide. Company in the United States.
- Transfers: EU–U.S. Data Privacy Framework, and standard contractual clauses in Cloudflare's data processing addendum.
OpenAI
- What for: writing, editing and importing decks, drafting brand kits, describing and making pictures, writing demos, review copy and speaker notes, and translating decks for followers and readers, when a member or reader asks for it.
- Data: what each task needs (a brief or instruction, the deck's content, a website's text, pictures to describe, screenshots for a demo), as the privacy notice details. Sent with storage turned off; OpenAI may keep API data for up to 30 days to detect abuse and doesn't use it to train models.
- Where: the United States. OpenAI's contracting entity for customers in the EEA is OpenAI Ireland Ltd (Ireland), which processes with OpenAI's affiliates in the United States.
- Transfers: standard contractual clauses in OpenAI's data processing addendum.
Resend, Inc.
- What for: sending emails: sign-in links, one-time codes, invitations, change alerts, a share link's first open, review digests and notices to workspace owners.
- Data: the recipient's email address and the email's content.
- Where: the United States.
- Transfers: EU–U.S. Data Privacy Framework, and standard contractual clauses in Resend's data processing addendum.
Not a subprocessor: Paddle
Paddle.com Market Ltd (United Kingdom) sells Cue's paid plans as reseller and merchant of record. It collects the buyer's name, email address, billing address and payment details itself and handles payment, taxes and invoices as a controller of its own, under its own privacy notice. It receives no workspace content, and Cue never receives card details. Transfers to the United Kingdom rely on the EU's adequacy decision for it.
Also not subprocessors
- The services, data sources, websites and AI apps that the Customer's members connect or use with Cue (section 6.6).
- Google Fonts: Cue's pages and decks load fonts from Google's servers, so a reader's browser sends its IP address to Google when it loads them. Cue sends Google no Customer Personal Data.
- Google sign-in, when a person chooses it: Google tells Cue who they are, for their own account (section 1.3).
Changes to this list
- November 16, 2026: first version.
Signatures
Only needed for a signed copy. Without one, this agreement applies as part of the terms of service.
Customer (controller)
- Company
- Address
- Contact for notices (email)
- Name and role of signatory
- Place and date
- Signature
Processor
- Company
- Zyad Abuzeid, trading as Pink Panther Labs
- Address
- Prenzlauer Promenade 191, 13189 Berlin, Germany
- Contact for notices (email)
- hello@pinkpantherlabs.com
- Name and role of signatory
- Zyad Abuzeid, owner
- Place and date
- Signature