Privacy Policy

Effective 20 August 2026. Governed by the laws of Ethiopia.

Push.et operates push.et. This policy describes how we process personal data for the messaging console and API. It is written for operators sending telecom traffic in Ethiopia.

Data we process

We process account data (name, email), organization KYC records, device and SIM identifiers, recipient phone numbers, message content and delivery receipts, wallet and payment metadata, API logs, and opt-out entries. Message bodies may include one-time codes or other personal data you choose to send.

Why we process it

We use this data to authenticate users, route and bill Ethiopian SMS/MMS, enforce KYC and quiet hours, honor STOP opt-outs, detect abuse, and meet telecom and financial-record obligations. Payment providers (such as Chapa or Stripe) receive only what is required to complete a top-up. Session cookies are described in the Cookie Policy.

Roles and subprocessors

For account administration we act as a controller. For message content, recipient numbers, and KYC documents you upload, we act as a processor under the Data Processing Addendum. Subprocessors include hosting, email, and payment providers in Ethiopia and the United States.

Retention and sharing

Delivery logs and ledger entries are kept for billing and dispute windows, then partitioned and purged on a rolling schedule. We do not sell recipient lists. We share data with subprocessors (hosting, email, payments, error monitoring) under contract, and with authorities when required by Ethiopian law.

Your choices

Recipients can opt out with STOP. Organization admins can update KYC details from the console. Contact privacy@push-et.com for access, correction, or deletion requests, which we handle subject to legal retention. KYC and sender-ID questions go to compliance@push-et.com. Other routes are on the contact page. Use of push.et is also subject to the Acceptable Use Policy.