EngageBeat explained
A clear framework for confidential feedback.
Before participating, everyone should know who sees their feedback and where protection has its limits.
Trust grows when everyone knows before their first response who sees results and what the limits of protection are.
Who sees responses and comments?
Only authorised team owners see available results and comments; participant access does not show results.
Results and comments are shown to authorised team owners. Participant access is used to answer the check-in; it does not provide a separate results overview. Results remain hidden until the week closes. After that, there must be at least five valid responses for each question. This also applies to custom questions.
The team leader then discusses the available results with the team. Comments should be shared thoughtfully: wording, project references or events described may point to individual people. A conversation about the topic is often more helpful than publicly attributing a statement to someone.
Results for a survey week in progress remain locked in the admin area too. Afterwards, the minimum threshold applies to each individual question.
What organisation access shows
Organisation access brings together eligible aggregate values without revealing comments or individual team values.
Organisation-wide reporting is available at no extra charge for 3 or more teams in EngageBeat Team, EngageBeat Fokus and EngageBeat Enterprise and is set up optionally. People with explicit authorisation see aggregated values after the week closes. For each question, at least three teams must meet the release requirements and each included team must have at least five valid responses. Additional protection rules may hide further teams or the entire metric.
Authorised company admins or organisation leaders set up inclusion. It applies from the following Monday; team owners are informed, and separate consent from them is not required. The company admin role alone does not grant access to results. Participants are informed before submitting responses. Comments and individual team values do not appear in organisation access. Organisation reports cover no more than twelve completed weeks; affected reports are also removed when the underlying team data is deleted. These rules, too, do not guarantee absolute anonymity in the face of additional knowledge.
Organisation access shows aggregated weekly values. Different sets of teams are not connected by a line. Individual team values and comments are excluded.
Five responses are the minimum threshold
Each question needs at least five valid responses – including in small teams.
In a team of five people, with the usual one submission per person, all five must participate for results to become available. A team of six has similarly little margin. The threshold is not lowered for small teams.
Shared access and a limit per browser do not verify identities. Five valid responses are therefore not technical proof of five different people. Share access only within the intended team and agree on one submission per person.
Stored without names – with limitations
Responses contain no name fields; free text and contextual knowledge may still make people identifiable.
Response records do not contain names, email addresses, employee IDs or IP addresses. Employees do not need a personal account. This is not an absolute guarantee of anonymity: free text, small groups and knowledge from outside the system may allow identification. Technical access by the operator must be considered separately.
Operating websites and handling contact enquiries generates technical or personal data. The data processed on the sales website is explained in the Privacy policy. The web app is subject to its own privacy notices and the information provided by your organisation.
Hosting and retention
The app runs in Nuremberg; retention and deletion are deliberately defined for your use.
EngageBeat runs on a netcup server in Nuremberg. The contact mailbox uses IONOS Mail Basic without the AI assistant. This does not imply a guarantee that all technical communication and certificate data is processed exclusively in Germany. The services used and their roles are described in the privacy notices.
The twelve-week display in the app does not determine the deletion period. Team owners can select 13, 26, 52 or 104 completed weeks for response and weekly records; the current week is additional. The period must be deliberately configured. Question versions and plan decisions are retained until the team is deleted. Backups require their own deletion and restoration process.
An explanation for your team
Before the first response, make clear which data is stored and who can see it.
Want to know what happens to your responses before you participate? The page for employees explains stored data, access to results and identification risks clearly. Team leaders can share it before the first invitation and add their own participant information.
Clarify before the first invitation
Purpose, access and data protection must be clear before your trial actually begins.
Agree the purpose, authorised people, participant information and retention. Also clarify the data protection roles and required contracts with the service providers involved. Your organisation is responsible for its use with employees; workplace participation rights must be considered. Guidance is available on the page Works council involvement. Submitting an enquiry form does not replace these agreements.
About the 28-day trial: the 28 days begin when the first survey opens. Setup and preparation do not count towards them. As part of this, set a suitable time for your first shared review.
Is EngageBeat right for your team?
Choose the right starting point and resolve your questions before the trial.
Choose EngageBeat Team for everyday teamwork or EngageBeat Fokus for custom questions and change initiatives.
Try free for 28 days — with up to three teams. Can be ended at any time during the trial.
All terms