Legal

Privacy notice

How Ethbus handles personal data and health data when your organization connects devices, systems and people through the platform. Last updated: 13 November 2026.

1. Who is responsible

For tenant data processed inside Ethbus, your organization is the data controller and Ethbus acts as the data processor. We only process tenant data on documented instructions, which are set out in the data processing agreement. For our own website, trial sign-ups and billing contact records, Ethbus is the controller.

2. What we process

  • Account data: name, work email, organization, role, password hash (PBKDF2-SHA256, salted, never reversible), session and login-attempt metadata.
  • Integration data: facility, location, device and system records; message payloads, headers, HL7/JSON bodies and delivery attempts that flow through your connectors.
  • Health data: where a connector carries patient identifiers (for example HL7 ADT/ORU, LIS results or device observations), those payloads may contain special-category health data.
  • Operational data: alerts, metrics, audit-relevant timestamps, IP address and user-agent needed to secure the service.
  • Billing data: invoices, plan, transaction references returned by Chapa. Card data never reaches Ethbus; payment is completed on the provider's hosted checkout.

3. Legal bases

We process tenant data to perform the service contract (GDPR Art. 6(1)(b)) and on your documented instructions as processor. Where health data is involved, the controller is responsible for a lawful basis under GDPR Art. 9(2) (typically Art. 9(2)(h) health care) and under the Ethiopian Personal Data Protection Proclamation No. 1321/2024. Ethbus supports those obligations but does not itself determine your lawful basis.

4. Data residency and location

You choose where the platform runs. Self-hosted and in-country deployments keep the database, message store and backups inside the boundary you select — Ethbus does not copy tenant payloads to our own infrastructure. When you use a managed deployment, the region is stated in your order form. Cross-border transfers require your prior written instruction and an appropriate transfer mechanism.

5. Retention

Message payloads and delivery records are retained according to the Retention configuration of your deployment (default 90 days for payloads, longer for delivery metadata). Deleting a message removes its payload from the store; backups expire on the schedule you set. Account and invoice records are kept for the period required by Ethiopian tax and commercial law.

6. Security

Transport is encrypted with TLS and HSTS; cookies are HttpOnly, SameSite and Secure in production. API keys are stored as salted hashes and shown once at issue time. Access is role-based (Admin, Operator, Viewer) and API keys are bound to a single organization. Outbound connectors enforce an SSRF policy that blocks cloud metadata endpoints and, when configured, private networks and local file targets. All authentication endpoints are rate limited and lock out repeated failures.

7. Sub-processors

By default the platform has no third-party sub-processors for tenant payloads. If you enable Chapa for payments, Chapa receives invoice and transaction metadata only. Any additional sub-processor is listed in your order form and requires notice before it is introduced.

8. Your rights

Data subjects may request access, correction, deletion, restriction, portability and objection. Requests should go to the controller (your organization). Ethbus assists the controller within the response windows required by Proclamation 1321/2024 and, where applicable, the GDPR. Our privacy contact is privacy@ethbus.io.

9. Breach notification

We notify the controller without undue delay, and in any event within 48 hours of confirming a personal-data breach, with the facts known at the time and updates as the investigation develops. The controller is responsible for notifying the Ethiopian Data Protection Authority and affected data subjects within the statutory deadlines.

10. Complaints

You may raise a complaint with Ethbus first, then with the Ethiopian Data Protection Authority. If GDPR applies to your organization, you may also complain to your local supervisory authority.