Built for anonymous honesty

Anonymity is structural, not a setting

Survey responses are anonymous by design: the platform never collects or stores respondent names or email addresses. A response carries only the building, optional self-reported role/team/tenure/supervisor fields, and the answers themselves.

Every reported number — dashboards, comparisons, trends, layer breakdowns, printed packets, and shared pages — enforces a minimum group size of five. Any group smaller than five respondents is withheld everywhere, so no individual can be identified from an aggregate.

Your data belongs to you

Each organization’s data is isolated by organization ID at every read and write path, and administrator accounts are additionally scoped to specific buildings where configured.

Full CSV exports of scores, responses, trends, and themes are available to authorized administrators at any time. On contract end, your organization’s data is deleted on request — deletions cascade through administrations, responses, and analysis artifacts.

Access & authentication

Administrator passwords are stored as bcrypt hashes and held to a length-and-complexity policy. Sessions are httpOnly, same-site cookies that can be revoked server-side (password changes invalidate existing sessions). Google single sign-on is available so districts can rely on their existing Workspace controls.

Roles and per-building scoping limit what each administrator can see; permission checks run on the server on every request, not just in the interface.

Platform & subprocessors

The application runs on Vercel with TLS on every connection. Data is stored in Supabase (managed Postgres) with encryption at rest. Transactional email is delivered via Resend. Open-text analysis uses the Anthropic API; responses sent for analysis carry no identifying fields, and Anthropic does not train on API data.

State-changing requests are origin-checked (CSRF), endpoints are rate-limited, and public share pages expose only privacy-gated aggregates behind unguessable, revocable, expiring tokens.

Questions

Security reviews and data-processing questions: mda.experience@gmail.com. We’re glad to walk your IT team through the architecture.