Security

How MIR protects your data and platform integrity

Last updated: December 2025

MIR is designed as privacy-first, abuse-resistant participation history infrastructure. Security is foundational to the platform -- not an add-on.

Data Protection

Personally Identifiable Information

MIR holds one piece of identifying information about a person: an email address, used to sign in. The participation record itself carries no identity. External IDs are hashed the moment they arrive, and an event has no free-form field, so a partner cannot attach a name, a profile, or any personal detail to what it submits -- the field does not exist. That constraint is architectural, not a policy we could quietly relax. Ordinary operational data -- your IP address and browser, in security logs -- is kept for 30 days and then scrubbed, and the Privacy Policy lists all of it. The record of what you did stays separate from who you are.

Authentication

Infrastructure

Partner API Security

Transparency & Auditability

All partner queries are logged and auditable. Users can view which platforms queried their MIR history and when. We believe security should come with transparency, not opacity.

Incident Preparedness

Procurement & Vendor Assessment

Procurement-readiness materials are available to qualified buyers under NDA. The package includes a NIST CSF 2.0 shared-responsibility matrix, SOC 2 readiness roadmap, vendor-risk questionnaire support narrative, and SBOM policy.

To request the package or to ask security-specific questions, contact security@mirregistry.com.

Questions about security?

We're happy to discuss our security practices in more detail.

security@mirregistry.com FAQ