Built to protect
the people who
trust you.
Anonymous by default. The platform is built to protect community members' privacy and to keep your organization's data secure.
Limited PII collection
We do not collect names, contact details, or identifying information through standard participation.
Anonymous by default
Community submissions are anonymous from the moment they are shared. No account required, no trace left.
Voluntary and consent-based
Contact details and demographics are collected only when participants choose to join a panel. Plain-language consent is always presented first.
Purpose-limited use
Data is used to generate insights for participating organizations. It is never sold or shared outside that scope.
Standards we meet,
not just reference.
Our compliance posture is built around the actual regulatory obligations of the organizations we serve, and the communities they work with.
SOX-style internal controls
Encrypted credentials, complete audit trails, and role-based permission structures across all platform access.
PCI-DSS via Stripe
Payment data for panel compensation is handled entirely by Stripe. PCI-DSS Level 1 certified. No payment data is stored on our infrastructure.
GDPR — anonymous submission exception
Community submissions qualify for the anonymous submission exception per Recital 2 of GDPR.
CCPA — anonymous submission exception
Community submissions fall under the similar exception per 1798.144.5(a)(5) of the California Consumer Privacy Act.
OWASP Top 10
Best practices compliance across all OWASP Top 10 protections, including parameterized queries and XSS/CSRF defenses.
Authentication & Access Control
- Industry-standard password hashing with 12+ stretches in production, with reset token expiry
- Role-based access control: User, Admin, and Platform Owner permission levels
- SSL/TLS encryption enforced on all connections
- Session-based authentication with CSRF protection
Data Protection
- All third-party service credentials encrypted with AES-256
- Strong parameter filtering and validation on all endpoints
- reCAPTCHA verification to prevent automated abuse
- Logging filtered to exclude passwords, tokens, and sensitive fields
Data Retention & Privacy
- Automatic expiration of pending participant invitations after 72 hours
- Consent management system with customizable privacy notices per organization
Third-party providers
and their certifications.
We rely on certified, audited infrastructure providers. Their credentials are a condition of our partnership, not an afterthought.
All payment processing for panel compensation. No payment data stored on MoV infrastructure.
Used for theme and analysis generation. Zero data retention policy in place for all embeddings.
All media (uploaded files, audio, etc.) stored on SOC Type II certified infrastructure and exposed through URLs only. Content type validation present on all file uploads.
Communication delivery for panel recruitment and notifications. SOC 2 compliant communication infrastructure.
What happens to
community data.
Anonymization before storage
Identifying information is stripped from submissions before they enter the platform database. This is automated, not reliant on manual review.
Centralized, access-controlled repository
Stories are stored in a centralized location with role-based access controls. Organizations access only their own data. Spam and duplicate submissions are automatically filtered.
Insight generation only — never shared externally
Data generates insights for the organizations that collected it. It is never sold, shared with advertisers, or used to train external models outside the zero-retention agreement with OpenAI.