Privacy Notice
This notice is the information that GDPR Articles 13 and 14 require. It applies to the SurveyBeat website, the app and the answer page. Effective 20 November 2026.
Who is responsible
SurveyBeat runs surveybeat.app. The legal name and postal address of the operator are not published on this page yet. For anything about privacy, including requests under the GDPR, write to privacy@surveybeat.app.
SurveyBeat has two roles, and they decide who answers your request. The next section explains them.
Two roles: processor and controller
Your Organization is the controller of the data about its People, Teams, Pulses, Rounds and Submissions. It decides why and how that data is used. SurveyBeat is its processor under Article 28 and acts only on its instructions, set out in the Data Processing Agreement. If you are asked to answer a Pulse, your Organization is the controller for your data, and you should send requests about it to your Organization. SurveyBeat helps it answer them.
SurveyBeat is the controller for signing in, for keeping the service secure and preventing abuse, for the SurveyBeat website, and for the sign-in emails it sends to you.
What we process, why, and for how long
Each row names the data, the purpose, the legal basis under Article 6(1) and how long the data is kept. For data held for an Organization, the Organization chooses the legal basis, usually legitimate interests (point f) in understanding how its Teams are doing, and the row shows the basis it normally relies on.
| Data | Purpose | Legal basis | Kept for |
|---|---|---|---|
| Sign-in: your email address, the one-time code or sign-in link we send, the session (IP address, browser user agent, expiry) and a passkey's public key if you add one. SurveyBeat is the controller. | Let you sign in, keep your session safe and detect abuse. | Point b, to provide the service you use. Point f, legitimate interests, for security and abuse prevention. | A code for 10 minutes. A sign-in link for 5 minutes. A session for 30 days, refreshed while you use the app. The sign-in record while you belong to an Organization, and until it is deleted after that. |
| People and Teams: email address, role, Team Membership, time zone and language, whether you turned off reminders for a Pulse, and the Invitations sent to you (stored as a hash, never the link). The Organization is the controller. | Run Teams and Pulses, send Invitations and reminders, and count how many people took part. | Point f, legitimate interests of your Organization. | While you are a Person in the Organization. Removing a Person ends their Membership, deletes their Participation records, and revokes their Invitations. The Person record and Membership history stay, and erasing that record is not available yet. The Organization's Teams keep their Results. |
| Participation records: that a Person answered a Round. They hold no answers and no time. The Organization is the controller. | Count the response rate and stop a second Submission from the same Person. | Point f, legitimate interests of your Organization. | While the Person is in the Organization. Removing the Person deletes their Participation records. |
| Answers and comments in anonymous Submissions. They carry no Person and no time. Comments have names of People, email addresses, phone numbers, handles and links removed before they are stored. | Show a Team's combined Results, trends and comment themes to the people allowed to see them. | Anonymous Submissions are not personal data (see the next section). Where a comment still identifies someone, point f applies. | The policy default is 24 months for raw Answers and comments. A per-Organization period is not available yet. Automatic deletion on that schedule is not in place yet. Until it is, they stay with the Pulse, except that cancelling a Round deletes that Round's Answers, Submissions and Participation records. Aggregated Results may be kept longer. Backups are kept for 30 days. |
| Results, Lead's Notes and Actions: scores, response rates, comment themes, the Lead's Note and Actions with an owner and a due date. The Organization is the controller. | Let a Team talk about its Results and agree what to change. | Point f, legitimate interests of your Organization. | While the Organization keeps the Pulse. Results show nothing below the minimum group size. |
| Email: the recipient address, the message and its delivery state for Invitations, reminders, Results and added-to-Team notices (Organization controller), and for sign-in messages (SurveyBeat controller). | Deliver the message and show a Lead which sends failed and why. | Point f for Invitations and notices. Point b for sign-in messages. | Delivery records while the Organization exists. Sign-in codes expire after 10 minutes. Sign-in links expire after 5 minutes. |
| Technical logs: IP address and request details seen by the app's Worker, in a sample Cloudflare keeps. The Submission Worker, which receives anonymous answers, keeps no logs at all. SurveyBeat is the controller. | Keep the service running and secure. | Point f, legitimate interests in security and reliability. | A short period set by Cloudflare's log retention, measured in days. |
| This website: static pages only, with no analytics, no advertising and no tracking. Cloudflare sees your IP address to deliver the page. | Deliver the page. | Point f, legitimate interests in running the website. | SurveyBeat keeps nothing from a visit. |
Anonymous Submissions are not personal data
An anonymous Submission stores its Round, its Answers and a hash of an Edit key. It stores no Person, no Invitation and no time at all, not even the day. The Participation record, which says that a Person answered, is kept apart from it. We cannot match one to the other, and neither can your Lead or your Organization's admins.
A stored Submission has no column that names a Person, so the tables do not link it to you. Where the Answers and comments do not identify you, they are anonymous data under Recital 26 of the GDPR and not personal data. A comment that still identifies its author is personal data. Removing you deletes your Participation records. It does not erase the Person record or the Membership history, and that erasure is not available yet. It does not remove the Submissions you gave.
We do not claim to defend against everything. Database backups are kept for 30 days so that we can recover from a disaster. Restoring one replays every write, including the one transaction that writes a Participation record and a Submission together. Only named SurveyBeat operators can start a restore, and no Organization admin or Lead can. We also cannot read Cloudflare's own edge logs. An operator who changes the code to start logging is outside this claim too.
Pulses run in anonymous mode only. If SurveyBeat offers a mode that stores a name with an answer, it will say so here and on the answer page before anyone can use it.
Comments and AI processing
A comment is redacted when it is stored: names of People in the Organization, email addresses, phone numbers, handles and links are replaced with placeholders. The original text is not kept. Redaction follows patterns and cannot promise that free text never identifies anyone, so leave out anything that could identify you.
AI processing is off until an Organization admin turns it on. While it is on, a request can include the Question text, each Question's dimension, score, change and whether that change is larger than usual, the same figures for each Dimension, redacted comment text tied to a Question position, and the redacted titles of open Actions. The request has no dedicated field for a name, a Person, a Team, a Round or a time. Question text is sent as written and is not redacted, so a name, an email address, or a Team or Organization name in a Question is included. The service runs in the EU, keeps no prompts or output, and cannot fall back to another provider. If it is unavailable, the request waits and is retried. The answer page and the Invitation tell members when AI processing is on. The AI service only summarises. Nothing about a Person is decided by it.
Where the data comes from, and whether you must provide it
Your email address and Team Membership come from your Organization, which added you, as Article 14 requires us to tell you. Everything you answer comes from you.
You are never required to answer a Pulse through SurveyBeat. To sign in you must give an email address, and without one you cannot sign in. Whatever your Organization expects of you beyond that is its own matter.
SurveyBeat makes no decision about you based only on automated processing that has legal or similarly significant effects (Article 22).
Who receives data
Your Organization's Leads and admins see what their role allows. A Lead sees combined Results, never who answered what. Being an Organization admin does not grant access to any Team's Results. An admin sees a Team's Results only if they have a Membership in that Team.
SurveyBeat uses processors to run the service: Cloudflare, Inc. for hosting, storage and email delivery, and, only when an Organization admin turns on AI processing, OpenRouter, Inc., which routes the call to Google Cloud (google-vertex/europe) or Amazon Web Services (amazon-bedrock/eu-west-1). The Sub-processors page names each one, with its purpose, location and transfer basis.
Transfers outside the EU and EEA
Cloudflare is a US company and runs a global network, so data it hosts for us can be processed outside the EU and EEA. We rely on the EU Standard Contractual Clauses in its data processing terms and, where the recipient is certified, on the EU–US Data Privacy Framework.
Comment text for AI processing is sent only to endpoints in the EU. OpenRouter's own account and abuse-monitoring data can be processed in the US, and comment text is not part of it. A copy of the safeguards is available from privacy@surveybeat.app.
Cookies and browser storage
SurveyBeat sets one cookie and uses browser storage for a few functions you ask for. It uses no advertising, tracking or analytics cookies. Everything below is strictly necessary for a function you requested, so no consent banner is needed.
| Name | What it is | Kept for |
|---|---|---|
| __Host-surveybeat-session (cookie) | Keeps you signed in to the app. It is HttpOnly, Secure, SameSite=Lax and only for the app's own host. | 30 days, refreshed while you use the app, or until you sign out. |
| sb_edit_… (browser local storage) | Your Edit key for a Round, a random secret kept in this browser so you can change your anonymous answers. The first Answer sends only a hash of it. Later Answers and edits send the Edit key to the Submission Worker over HTTPS. The server stores only the hash. | Until you clear site data. If you lose it, your answers can no longer be changed. |
| sb_answers_… (browser local storage) | The answers and comments you gave, for your private history page. They stay on this device, and comments are kept as you typed them. | 1 year. You can clear them any time with Clear my answers on this device on the My history page. |
| sb_token (browser session storage) | Your Invitation token while the answer page is open in a tab, so reloading the page keeps working. | Until you save your answers or close the tab. |
Your rights
Under Articles 15 to 22 of the GDPR you have the right to:
- get access to your personal data and a copy of it (Article 15)
- have wrong data corrected (Article 16)
- have your data erased (Article 17)
- have its use restricted (Article 18)
- receive it in a common format and have it passed on (Article 20)
- object to processing based on legitimate interests (Article 21), and not be subject to a decision based only on automated processing (Article 22)
You can do some of this yourself. The My history page lists the Rounds you took part in and clears your answers from this device. Your Organization's admins can remove you. For everything else, write to privacy@surveybeat.app or to your Organization. If your Organization is the controller, we pass your request to it without delay and help it answer. We answer within 30 days. If a request is complex we tell you why and when you will get the answer, within the period the GDPR allows.
Anonymous Submissions cannot be found, exported or deleted for one Person, because nothing links them to you. That is the point of the design.
We do not rely on your consent for any processing, so there is no consent to withdraw.
Complaints
You can complain to a data protection supervisory authority, in particular in the EU Member State where you live or work or where you think the GDPR was breached. The European Data Protection Board lists the authorities at edpb.europa.eu. We would like to hear from you first, so we can put it right.
Security
Each Organization's data sits in its own Durable Object, and Organizations never share records. Invitation tokens and Edit keys are stored only as hashes. Traffic is encrypted in transit and storage is encrypted at rest by Cloudflare. Nothing below the minimum group size is shown. It is 4 by default and an Organization can raise it, never below 3. The Data Processing Agreement lists the measures in full.
Changes to this notice
When we change this notice in a way that matters to you, we update the date above and tell Organization admins by email before the change takes effect.
Questions about this page? Write to privacy@surveybeat.app.