// compliance

Security you can verify.

SOC 2, GDPR, CCPA, and ISO 27001 posture below. Where we are attested, we say so. Where we are aligned but not certified, we say that too. Where the attestation is planned, we name the gap.

last reviewed
next review

Certifications and Standards

SOC 2 Type II

Erebine operates inside colocation facilities that hold their own SOC 2 Type II attestations covering the security, availability, and confidentiality Trust Services Criteria for the physical environment. Erebine itself holds no SOC 2 report of either type today. A SOC 2 Type II examination of the application layer is planned; the audit window has not opened and no report date is committed.

Scope today: physical environment only (attested by the colocation provider). Application layer: planned, not started, no report issued.

Planned

GDPR

Aligned with the General Data Protection Regulation. The platform implements data-subject controls including right-to-erasure, data export for portability, and anonymization. Contact contact@erebine.ai to request a Data Processing Agreement.

Aligned

CCPA

Consumer rights for California residents are honored through the same data-subject controls used to satisfy GDPR (access, deletion, and portability). "Do Not Sell or Share" is a self-service setting under Dashboard → Settings → Data and Privacy: we do not sell or rent personal information in the first place, and turning the setting on records the do-not-sell preference. Marketing email is controlled by the marketing email preference: the account setting and the unsubscribe link. Global Privacy Control signals from the browser are honored as the same request. Anything the in-product controls do not cover can be sent to contact@erebine.ai and is honored within thirty days.

Aligned

ISO 27001

Our information security management system is designed to align with the ISO 27001 control families. Formal ISO 27001 certification is planned and not yet issued.

Planned

Security Practices

  • Encryption in transit: TLS 1.2 minimum on every public endpoint; TLS 1.3 preferred. Internal communication between the router and each Erebine Inference Microservice (EIM) and Erebine Execution Manager (EEM) uses CURVE-encrypted ZeroMQ transport with mutual authentication via Curve25519 keys for every such connection.
  • Encryption at rest: AES-256-GCM authenticated encryption with per-project keys on stored completions, uploaded content, task payloads, and audit payloads. Workspace memory text and embedding vectors are stored in the database without field-level encryption today. Key rotation is operator-controlled per deployment.
  • Access control: Project roles (owner, operator, member) plus per-key scopes, with a separate platform-admin role that holds no content rights. Least-privilege defaults; no implicit cross-project visibility.
  • Monitoring and incident response: Operational monitoring and incident response procedures are maintained by the operator of each deployment.
  • Vulnerability management: Dependency and platform CVEs are tracked against the build graph and patched on the next router release after disclosure.

Trust and Safety

  • Child safety: We prohibit CSAM and report apparent CSAM to NCMEC on actual knowledge, with evidence preservation; reports are filed manually today. The platform has an interface for an automated scanning provider, but no provider is integrated yet, so automated scanning is not performed. The minimum age is 18.
  • Non-consensual intimate imagery: We operate a TAKE IT DOWN Act notice-and-removal process through the removal request form or contact@erebine.ai. A request is valid when it carries a signature, an identification of the image that lets us find it, a good-faith statement that it is not consensual, and contact details the requester confirms by email; we remove the image within 48 hours of that confirmation. An unconfirmed request expires after 30 days.
  • Content reporting: Users can report content in-product or at contact@erebine.ai; an admin review queue triages reports.

Copyright

We respond to DMCA notices and terminate repeat infringers. See /dmca for our designated agent and the notice and counter-notice process.

Sanctions and Export

Use of the service is subject to US sanctions and export-control law. You represent at signup that you are not a sanctioned person and are not in a sanctioned jurisdiction, and we collect registration country to support that representation. The platform has screening interfaces for accounts, payments, and model uploads, but no denied-party list provider is integrated yet, so automated list matching is not performed today; it is enabled per deployment when a list provider is connected.

Data Residency

Erebine allows you to choose where your data is stored by giving you full access to Erebine Inference Microservice (EIM) nodes. Shared services are operated in the United States.

Enterprise customers can request EIM infrastructure with custom data residency requirements.

Data Processing Agreement

We provide a Data Processing Agreement (DPA) for customers who need to comply with GDPR and other data protection regulations. Contact contact@erebine.ai to request a DPA; we respond within five business days.

Reporting Security Issues

If you discover a security vulnerability, report it to contact@erebine.ai. We acknowledge responsible disclosure within three business days and aim to triage within five. A coordinated-disclosure window is negotiated per report.

Automated scanners and security researchers can fetch the machine-readable disclosure metadata at /.well-known/security.txt (RFC 9116).