Privacy modes as policy
Each activity's creator chooses its privacy mode. For an organisation, the useful question is what each mode guarantees - because the guarantee is what you can put in a policy, a works council agreement or a data-protection assessment.
The guarantees
| Identified | Anonymous to the creator | Fully anonymous | |
|---|---|---|---|
| Anyone in the workspace can tell who gave an answer | Yes | No | No |
| Murmle can link a returning participant | Yes | One-way code, to stop answering twice | No |
| Nickname stored | Yes | Yes | No - discarded at join |
| Contact-details questions | Allowed | Refused | Refused |
| Individual leaderboard | Yes | No | No |
| Team mode | Yes | Yes, head counts only | Refused |
| Outcomes to integrated platforms | Yes | No | No |
These hold on every surface - the console, exports, the workspace export, the REST API, webhooks and the live connection to phones - because they are enforced when data is written and queried, not when it is displayed. An owner, an admin, an API key and the export all get the same answer: in an anonymous session, nobody.
Switching an activity from an anonymous mode to identified reveals nothing about sessions that already ran, because the link was never stored.
Defaults
New activities start anonymous to the creator, except quizzes, which start identified because a score is usually meant to be attributed. A creator can change the mode before publishing; each session keeps the mode it started with.
There is no workspace-wide setting that forces a mode. If your policy requires one - for example, "staff engagement surveys are always fully anonymous" - it is a rule for your creators to follow, and the session's mode is visible to anyone reading its results.
What to tell participants
Participants are told which mode applies in their own language. Two points are worth repeating in your own communications, because they are the ones people most often misunderstand:
- Anonymous to the creator is anonymous to your organisation, not to Murmle, which keeps a one-way code to prevent repeat answers.
- No mode stops someone identifying themselves in a written answer, being seen typing in the room, or being identifiable in a very small group.
The full statement of what each mode stores is in Privacy modes.