Security and privacy
This section is for anyone assessing Pollinator: security reviewers, data-protection officers, accessibility leads and procurement. Every statement here describes how the product behaves today. Where something is a self-assessment or has a known limit, it says so.
Privacy modesThe three modes as three storage shapes, what each stores, and the limits we do not claim to solve.Security practicesTenant isolation, authentication, secrets, the server deciding what matters, and logging.Accessibility conformanceWCAG 2.2 AA, self-assessed, with what is enforced automatically and what is not yet done.Data location and retentionWhere data is hosted, how long it is kept, and how it is deleted.
In brief
- Anonymity is storage, not display. A fully anonymous session never stores a name, account or external identity with answers, so no person, credential or later setting change can recover one.
- The server decides everything that matters - identity, permissions, correctness, points and timing. A phone sends answers, never scores.
- Workspaces are isolated. Every query is scoped to the caller's workspace, which comes from their credential and never from the request.
- No passwords. Sign-in is through identity providers, including your own OpenID Connect or SAML provider, which can be required to prove multi-factor authentication.
- Secrets are shown once and stored hashed or encrypted.
- An append-only audit trail records security-relevant actions, without copying content.
- Data can be deleted as well as collected: retention limits, session and participant erasure, workspace export and deletion, account deletion.
Legal documents - terms of service, privacy policy, data processing agreement - are not published on this site.