Legal

Data processing agreement

Baseline processor terms for organizations that send personal or health data through Ethbus. This summary is incorporated into the signed DPA in your order form. Last updated: 13 November 2026.

1. Roles

The customer is the controller (or processor acting for a controller) and Ethbus is the processor. Each party complies with the Ethiopian Personal Data Protection Proclamation No. 1321/2024 and, where applicable, the GDPR and sector rules.

2. Scope and instructions

Ethbus processes personal data only to provide the integration service: receiving messages, applying configured rules, delivering to the endpoints the customer configures, producing dashboards, alerts and exports, and maintaining security logs. Processing outside these instructions requires prior written agreement.

3. Confidentiality and personnel

Access to tenant data is limited to personnel who need it to operate or support the service and who are bound by confidentiality obligations. Administrative access is role-based and logged; customer administrators control their own users and API keys.

4. Security measures

  • Encryption in transit (TLS, HSTS) and database encryption at rest in managed deployments.
  • Salted PBKDF2-SHA256 password hashing; API keys stored as salted hashes.
  • Organization-scoped data access enforced on every query, with isolation tests in CI.
  • Rate limiting, login lockout, request-size limits, security headers and a restrictive CSP.
  • Outbound SSRF policy blocking cloud metadata endpoints, with optional private-network and file blocking.
  • Configurable retention windows for payloads and delivery records.

5. Sub-processors

No sub-processor receives tenant payloads by default. Payment processing through Chapa receives invoice and transaction metadata only. New sub-processors require notice and, where required, customer approval.

6. Assistance

Ethbus assists the controller with data-subject requests, impact assessments and prior consultations, taking into account the nature of the processing. Requests are handled through the support channel and within the statutory response windows.

7. Breach notification

Ethbus notifies the controller without undue delay and within 48 hours of confirming a personal-data breach, describing the nature of the breach, the data and subjects affected, likely consequences and measures taken. The controller notifies the Authority and data subjects as required by law.

8. Return and deletion

On termination the customer may export data during the agreed export window. After that window Ethbus deletes production data and lets backups expire on the backup schedule, certifying deletion on request.

9. Audit

Ethbus provides the security documentation and test evidence needed for customer audits. On-site audits require reasonable notice, are limited to the systems processing customer data, and are at the customer's cost.

10. Liability

Liability under this DPA follows the limitation of liability in the terms of service. Nothing in this DPA limits a party's liability to a supervisory authority or data subject where the law does not allow it to be limited.

11. Signing

To execute a DPA or a HIPAA business associate agreement, contact legal@ethbus.io with your legal entity name, registration number and the deployment region.