Companies / Redox Engine / Subprocessors
Redox provides a healthcare data integration platform that connects health systems and moves clinical and administrative data into cloud environments. It serves digital health vendors, providers, and payers.
Summarized from its homepage on 4 Nov 2026.
Subprocessors of Redox Engine
Redox Engine declares 5 subprocessors.
| Subprocessor | Purpose |
|---|---|
| Cloud provider | |
| Confluent Cloud - AWS (SAML) | Processing of Customer Data |
| Cloud provider | |
| Mimecast Admin Console | Secure Email Processing |
| Emailing of Confidential Data for Customer Support |
Certifications
| Standard | What the source says | Checked |
|---|---|---|
| HIPAACompany's statement | “Secure, HIPAA-compliant infrastructure”The company's own statement of compliance. There is no official HIPAA certification or registry. | 9 Nov 2026Source |
| SOC 2 Type IICompany's statement | “SOC 2® Type 2 report maintenance”The company's own statement. SOC 2 has no public registry; the report itself is shared by the company, usually under NDA. | 11 Nov 2026Source |
We last read its homepage on 11 Nov 2026 and the FedRAMP Marketplace on 8 Nov 2026. A standard not shown here was not found in these sources. That does not mean Redox Engine lacks it.
Vendor's own statement, retrieved from the source URL on the date shown. StrataDB does not verify the underlying claim. Data sources.
See Redox Engine's full stack
Every vendor with its source and date, and an alert when Redox Engine adds or drops one. The same lookup works for any company.
- Every company and vendor, with its public source
- 100 API calls a month, plus MCP and the Chrome extension
- Work email only. No card, no sales call