Security & trust
A partner company uploads its records to Mikra. We de-identify them before any customer receives data or a product, and we delete the raw upload within 120 days. This page lists what we promise on paper and nothing else. We hold no security certification today, and we say so below.
01 / Data handlingFrom upload to delivery
Your data stays yours.
- Upload
- The company keeps ownership of its records and sends a copy through Mikra’s secure upload. Mikra receives the raw records.
- Encryption
- Encrypted in transit and at rest.
- Where your records are stored
- Your upload travels by encrypted file transfer to storage Mikra operates itself: a Ceph storage cluster on Mikra’s own hardware in a colocation data center.
- Who can reach them
- Only Mikra staff have access to that storage, and access is logged.
- Where de-identification runs
- De-identification is run from our own storage.
- Rented computing
- When the de-identification models need more computing power, Mikra rents GPU hosts only from providers that hold a SOC 2 report.
- Outside model providers
- When Mikra uses an outside model provider, it uses only providers that hold a SOC 2 report and operate under zero data retention, meaning the provider does not keep what Mikra sends it.
- De-identification
- Before any customer receives data or a product, Mikra removes or replaces information that identifies a person or the company. The same person or company gets the same placeholder across every source.
How de-identification works - Residual risk
- The risk is lower, not zero. It is lower because names, company and client names, contact details, and account numbers are removed or replaced, because the company reviews a sample before anything is delivered, and because customers are contractually barred from re-identifying anyone. No method removes everything.
- Sample review
- Before the first delivery to any customer, the company gets a representative sample of the de-identified data and a short description of the methods. It has 10 business days to point out anything missed. We fix it before delivery.
- Raw upload
- Deleted within 120 days after upload. Mikra keeps the de-identified data and the products built from it.
- Customers
- Customers receive de-identified data and products only. Their contracts bar them from re-identifying anyone.
- Never uploaded
- Patient or health records, biometric identifiers, card and bank account numbers, Social Security and other government ID numbers, passwords and credentials, personal information of anyone under 18, export-controlled or classified information, attorney-client privileged material, and files held for a client under a contract that forbids sharing. Patient records and a law firm’s client files move only through the healthcare and legal track below.
02 / AccessOnly those who need it
Need to know, under contract.
- Raw records
- Seen only by Mikra staff and service providers who need them to review and de-identify. Each is under written confidentiality.
- Expert NDA
- Every expert signs a confidentiality agreement before seeing any task.
- Expert material
- Experts who write and check tasks see only de-identified material.
03 / IncidentsWhat we do when something goes wrong
Told, then fixed.
- Incident notice
- If a material security incident affects a company’s data, we tell that company within 5 business days.
- Missed identifier
- If identifying information is found after delivery, we investigate within 10 business days, correct our copies and future deliveries, and work to have customers replace affected copies.
04 / ComplianceWhat exists today
Posture, stated plainly.
We do not show badges. Each line below states what exists today.
- SOC 2 Type II
- Planned, not started. We hold no SOC 2 report today. The rented GPU hosts and outside model providers we use hold SOC 2 reports; Mikra’s own audit has not started. Planned
- Health and legal records
- Two tracks. On the standard track, Mikra de-identifies. For a healthcare company’s patient or clinical records and a law firm’s client files, an independent provider de-identifies before Mikra receives anything. For healthcare, the provider signs a Business Associate Agreement with the company, and Mikra never receives protected health information. This runs under a Healthcare and Legal Addendum. The provider is not yet contracted. A law firm stays responsible for its duties to its clients and confirms what it may share. Separate track
05 / Responsible AIApplied to every program
What we decline.
- Individuals
- No content designed to target, profile, harass, or deceive specific people.
- Elections
- No work intended to manipulate elections or suppress participation in them.
- Abuse material
- No child sexual abuse material, in any form, under any framing, including synthetic.
- Weapons
- No uplift for biological, chemical, nuclear, or radiological weapons, or for attacks on critical infrastructure.
- Red teaming
- Adversarial work is scoped in writing, run in contained environments, and limited to the model and harms the program names.
06 / DisclosureGood-faith research is welcome
Tell us if something is wrong.
If you find a vulnerability in a Mikra system, email security@mikra.ai. We acknowledge reports, keep you informed while we fix the issue, and do not take legal action against good-faith research that avoids customer data and disruption.
Procurement & security review
Ask before
you sign.
Send us your security team’s questions. We answer with what exists today and say plainly what does not.