Enterprise / Trust centre
What we store, how we protect it, and who can use it.
Written as statements about the product, not promises about intent. Where a commitment is a self-assessment, we say so.
Privacy
Three privacy modes, three ways of storing answers
Each session chooses what is written down. A fully anonymous session never stores a name or an account, so nobody can recover one later, whatever settings change.
Identified
- Nickname
- Yes
- Linked account
- Yes
- Presenter sees who answered
- Yes
- Name from an integrated platform
- Yes
- Contact-details questions
- Allowed
- Quiz teams
- Yes
Anonymous to the creator
- Nickname
- Yes, never shown
- Linked account
- No
- Presenter sees who answered
- No
- Name from an integrated platform
- Never stored
- Contact-details questions
- Refused
- Quiz teams
- Yes, members never shown
Fully anonymous
- Nickname
- Never stored
- Linked account
- Never stored
- Presenter sees who answered
- No
- Name from an integrated platform
- Never stored
- Contact-details questions
- Refused
- Quiz teams
- Refused
Retention and deletion
Keep results as long as you need, and no longer
Deletion removes the data, not just the view of it. In the console every destructive step asks you to confirm first, and session deletions, erasures, retention changes and exports are recorded in the audit trail.
A retention period you set
Owners and admins choose how long results are kept. Sessions that closed longer ago than that are deleted automatically. It is off until you set it, and a session still open is never swept.
Delete a session
A closed session goes with everything in it: answers, participants, board posts and votes, teams, and the webhook events about it, including any not yet sent.
Erase one participant
Take one person’s answers out of a session’s results, through the API. Their votes and posts go with them.
Export the whole workspace
Owners and admins download activities, sessions, answers, members and the audit trail as a zip. Anonymity rules apply to it as to any export, and no secret is ever included.
Delete the workspace
The owner deletes every session, activity and membership, and the audit trail, after typing the workspace name to confirm.
Delete your account
Anyone signed in can delete their own account; the only owner of a shared workspace must add another owner first. Work in shared workspaces stays with the workspace, and the audit trail keeps what was done under a pseudonym instead of the email.
Security practices
How the product is built to protect your data
No passwords to steal
People sign in through Panhari, Google, Microsoft, LinkedIn or your own OpenID Connect or SAML 2.0 provider. Murmle never stores a password.
Accounts linked only on a verified email
A new sign-in joins an existing account by email only when the address is verified, by the identity provider or by your workspace’s verified domain. An unverified match is refused, not linked.
MFA when you require it
A workspace can require multi-factor authentication from its SAML 2.0 or OpenID Connect provider. A sign-in without it is refused.
Every workspace kept apart
Every query is scoped to the caller’s workspace, and an automated test fails the build if a new table is not.
Secrets stored safely
API keys, provisioning tokens and participant tokens are stored only as hashes. Identity-provider, webhook and integration secrets are encrypted.
Keys shown once
A new API key is shown exactly once, limited to one workspace and the permissions you grant, and can be revoked at any time.
Signed webhooks
Every webhook is signed, so your system can verify it came from us. A delivery log shows what was sent and what came back.
Identities stay with the platform that sent them
An integrated platform’s identifier for a person goes back only to that platform, and only from identified sessions. Your other webhooks get results without it.
Abuse limits
Joining, answering and posting are rate-limited, with the limits held centrally so they hold across every server.
The server decides
Scores, correctness and timers are decided on the server. A participant’s device sends answers, never verdicts.
Embedding you control
A live activity can be framed only by the sites you list.
Where your data lives
Murmle runs on Microsoft Azure in the United States.
Accessibility
WCAG 2.2 Level AA, checked on every build
Automated checks run against every question type before and after it is answered, and a new type cannot ship until it passes. Our conformance statement is a self-assessment; it has not yet been independently reviewed, and we will say so until it has.
- Every question type answerable by keyboard, drawing included
- A data table behind every chart; correctness never shown by colour alone
- Captions and transcripts on video slides, and time limits a presenter can extend
- Reduced motion, from the device setting or a setting of its own
Questions from your security or procurement team?
Send them over. We will answer from the product as it is, not from a brochure.