Maxio · Compliance
Maxio compliance
Read from Maxio's own page on 2026-11-10. 5 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.
Trust center
Attestations
framework: SOC1type: SOC 1 Type 2scope: controls relevant to financial reporting for customersperiod: annualreport access: unstated
Maxio undergoes an annual independent SOC 1 Type 2 audit to validate the design and operational effectiveness of controls that are relevant to financial reporting for customers.Read from Maxio's own page on 2026-11-10
framework: SOC2type: SOC 2 Type 2scope: security, availability, and confidentiality of customer dataperiod: annualreport access: unstated
Maxio also completes an annual SOC 2 Type 2 audit, focusing on security, availability, and confidentiality of customer data.Read from Maxio's own page on 2026-11-10
framework: ISO27001type: ISO/IEC 27001:2022 certificationscope: information security management systems across the entire organizationreport access: unstated
Maxio is certified against ISO/IEC 27001:2022, the internationally recognized standard for information security management systems (ISMS).Read from Maxio's own page on 2026-11-10
framework: PCI-DSStype: PCI DSS 4.01 compliancescope: Maxio Payments and Advanced Billingreport access: unstated
Maxio Payments and Advanced Billing are compliant with PCI DSS 4.01, the Payment Card Industry Data Security Standard, for services handling payment card data.Read from Maxio's own page on 2026-11-10
framework: othertype: EU-U.S. Data Privacy Framework certificationscope: personal data transferred from the EUreport access: unstated
Maxio is certified under the EU-U.S. Data Privacy Framework (DPF), a program that allows U.S. organizations to commit publicly to protect personal data transferred from the EU with standards deemed adequate under EU law.Read from Maxio's own page on 2026-11-10
Document
Download YAML · schema: API Commons Compliance 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page