Skip to main content

Privacy modes

The question this page answers:

When a session is fully anonymous, can any person or credential - creator, admin, owner, API key, live connection, log reader - determine who said what?

The answer is stated as storage, not as intent. A claim backed only by what the interface shows is a claim a later change could quietly withdraw; a claim about what is never written down cannot be.

Three modes, three storage shapes​

IdentifiedAnonymous to the creatorFully anonymous
Nickname storedYesYesNo - discarded at join
Integrated-platform identity of a launched participantKeptA salted one-way hash only, to recognise a returning personNot stored
Platform-supplied name of a launched participantKeptNot storedNot stored
Anyone in the workspace can see who answered whatYesNoNo
Contact-details questionsAllowedRefusedRefused
Quiz teamsYesYes - head counts only, no member listsRefused - never stored
Outcome events naming a learnerSent to the launching platform onlyNot sentNot sent
A later switch to identified reveals past answers-NoNo

The last row is the one a display-time implementation always gets wrong. Anonymity applied when data is shown evaporates the moment someone edits the setting. Here it cannot, because the link was never written.

What a fully anonymous session stores​

A participant record exists, because a session has to count its participants and recognise a person's own answers for the length of the session. It holds:

  • a hash of a session token, meaningless once the session ends and derived from no identity;
  • an empty name - the nickname supplied at join is discarded, so no feature can later be built that accidentally shows it;
  • no account link and no external identity - someone who arrived through single sign-on or a course launch is stored exactly like someone who did not.

Answers themselves carry no identity in any mode.

The same rules on every surface​

Each of these applies the session's mode, and is covered by automated tests organised by reader - because an anonymity rule that holds in the export and fails on the leaderboard is not a rule:

  • Results and the console. No names outside identified sessions; board posts show "Anonymous", to moderators too.
  • Exports, per session and for the whole workspace: every participant is "Anonymous"; no participant identifier is in the file.
  • Leaderboards. The individual leaderboard is empty outside identified sessions, and so is the closing slide's podium, which is built from it.
  • Answer cards. Free-text answers and drawings shown to the host and on the wall carry the answer and when it arrived - never the participant or a name, in any mode. A host's decision to approve or hide a card is audited by its outcome, never with the words.
  • The finished screen and a participant's own answers. A phone is given its own answer count, score and place, and its own earlier answers - nothing about anyone else, in any mode. A place is a number among numbers, withheld when the activity shows no leaderboard; score and place wait for the session to end, so a running total cannot reveal the answer key.
  • The REST API, which uses the same export and results code.
  • Webhooks and outcome events. No event carries an answer or contact details; an event naming a learner exists only for an identified session and goes only to the platform that launched them.
  • The live connection to phones carries identifiers and counts, not who did what; board post notifications carry no text.
  • Requests for more time are stored as a count with no participant link, in every mode.
  • Telemetry and logs do not record answers, free text, contact fields or participant identifiers.

What is deliberately not claimed​

A guarantee with unstated limits is marketing. These are the limits:

  • Correlation in the room. Someone watching people type can associate an answer arriving with a person typing. No storage decision prevents that.
  • Small numbers. A session with one participant identifies them by arithmetic, and with three it often takes little more. That is true of publishing any aggregate.
  • Free text. A participant who writes their own name into an answer has identified themselves. Anonymity governs what Pollinator stores about them, not what they choose to say.
  • Infrastructure. Someone with direct administrative access to the database is outside what an application-level guarantee can address; that is a matter of operational controls.
  • Anonymous to the creator is not anonymous to Pollinator. It keeps a one-way code to stop people answering twice, and participants are told so.
  • Erasure needs the person to find their own answers. In either anonymous mode nobody in the workspace can tell which submission is whose, so an erasure request can only be met if the person can identify their own submission. Retention and session deletion still remove everything.
  • Linked pictures, videos and audio - in image questions, on content slides and as a question's own media - are loaded by participants' browsers from wherever the creator hosts them, so that host sees the devices' network addresses. An uploaded image is served by Pollinator instead. YouTube and Vimeo videos are embedded in privacy-enhanced mode, which sets no tracking cookie until someone presses play; after that the provider's own policy applies. Nothing plays by itself.

Corrections​

Earlier versions did not fully meet this statement. Each gap was fixed, and data stored under the old behaviour was erased:

  • Nicknames in fully anonymous sessions. Until 5 October 2026, a fully anonymous session that also asked for a nickname stored it. The mode now always discards it, and nicknames stored earlier were erased.
  • Contact questions in anonymous sessions. Until 5 October 2026, a contact-details question could run in a session that was anonymous to the creator. It is now refused there, and contact answers collected in such sessions were deleted.
  • Launched participants in anonymous sessions. Until 5 October 2026, a launch from a learning platform stored the student's platform identity and name whatever the mode. Anonymous sessions now store neither, and those stored earlier were erased.