Back to Developer Portal
Wani for Developers
API & Developer Portal

Privacy Policy

Last updated: October 3, 2026

1

Introduction & Legal Information

Welcome to Wani for Developers (the Developer Portal). Wani for Developers and the Wani platform are owned and operated by the platform team. This policy is specific to the Developer Portal and differs from the privacy policy of the main Wani campaign platform, because the nature of the data processed here is different: here you're using an API to send OTP and WhatsApp messages programmatically from your own application, not through a campaign dashboard.

By using the Developer Portal or its API, you agree to this policy.

2

Roles: you're the controller, we're the processor

This distinction matters, so let's be precise:

●You (the developer / project owner) are the **Data Controller** for the phone numbers of your own end customers that you send OTP or WhatsApp messages to via the API
●We (Wani) act as a **Data Processor** for those numbers — we only relay the message through the WhatsApp Business API on your behalf, and don't use it for any other purpose
●You are responsible for obtaining your end customers' consent, and for having your own privacy policy that informs them of this

This policy covers your data as a developer/project owner, and how we handle the end-customer data that passes through the API.

3

Data We Collect

Your data as a developer/project owner:

●Name, phone number, email, and password (hashed with bcrypt)
●Google account data (name, email, and account identifier) when you sign up or sign in with Google
●Incomplete sign-up data: if you start signing up and don't finish, we keep your email, name, phone number (if entered), and interface language, and may email you a reminder to complete sign-up
●Data for the projects you create (name, members, roles: Owner or Developer)
●Your API keys (we keep a hashed copy to authenticate requests, and a copy encrypted with AES-256-GCM that lets you reveal the full key later from the dashboard after confirming your password)
●WhatsApp connection data per project: Access Token (encrypted with AES-256-GCM), Phone Number ID, WABA ID, display phone number
●The OTP templates you configure
●API usage logs: request counts, send status (success/failure), timestamps
●Billing and balance records: deductions, top-ups, and manual top-up requests (amount, payment method — InstaPay or Etisalat — and coupon code if any)
●Email addresses of members you invite to your project
●CLI sessions: device name, client (User-Agent), IP address, and usage times

Data that passes through the API (belonging to your end customers):

●The recipient phone number, and the content of the message/template used, at the moment of sending only
●We keep a brief log of these requests (for billing, error tracking, and usage limits), not to analyze the identity of those customers
●The OTP code itself is not stored in our database; only a hash of it is kept in Redis for its validity period plus a short margin
4

How We Use the Data

●Operating the API and sending messages on behalf of your project via the WhatsApp Business API
●Validating API keys and applying rate limits
●Displaying usage statistics in your project dashboard
●Receiving template status updates from Meta via the portal's webhook
●Contacting you about your account or project (security alerts, service updates)

We do not use your end customers' data (the phone numbers you send to via the API) for any marketing or analytical purpose of our own.

5

Data Sharing

●**Meta / WhatsApp:** to send messages via the WhatsApp Business API on behalf of your project
●**Supabase / Vercel:** hosting for our database and application
●**Upstash (Redis):** storing the hashed OTP code for verification and rate-limit counters
●**Google:** sign-up and sign-in with a Google account
●**Bred24 SMTP:** sending your account emails (verification, password reset, notifications)
●**Sentry:** technical error tracking
●We do not sell or share your project's data or your end customers' data with any advertising or marketing party
6

Security

●Passwords are hashed with bcrypt, and API keys are stored as a hashed value for authentication plus an encrypted copy (AES-256-GCM) that is revealed only after you confirm your password
●Each project's Access Token is encrypted with AES-256-GCM and is never returned in any API response after being saved
●Every webhook request from Meta is signature-verified (HMAC-SHA256) before being accepted
●Rate limiting is applied to prevent abuse or brute-force attacks
7

Your Obligations to Your End Customers

Since you're the data controller for your end customers, you are responsible for:

●Obtaining their explicit consent before sending them any OTP or WhatsApp message via the API
●Providing your own product/app privacy policy that discloses your use of this service to them
●Fully complying with Meta and WhatsApp Business policies on content and sending limits
●Not using the API to send spam or non-compliant content

We are not responsible for any violation on your part in this regard.

8

Data Retention

We retain your account and project data for as long as the account is active. An archived project has its API keys deactivated but its data remains until it is permanently deleted. OTP usage logs are kept for as long as the project exists (active or archived).

When a project is permanently deleted (available after archiving it, and only if there is no outstanding debt or pending top-up request):

●The Meta connection data (Access Token), API keys, OTP templates, OTP usage logs, the project's balance ledger, and member invites are deleted immediately
●Top-up request records linked to your account are retained for accounting purposes
●We may retain aggregated, non-identifying logs for internal statistical purposes

Account self-deletion is not currently available from the dashboard; to request deletion of your account, email us at the address below.

9

Your Rights

As an account or project owner, you have the right to access, correct, and delete your data (account deletion is done by email request), and to request a copy of it in a readable format. To exercise any of these rights, contact us at the email below.

10

Changes to This Policy

We may update this policy from time to time. We will notify you of any material changes by email or an in-portal notice at least 7 days before they take effect.

11

Contact & Legal Information

Wani and Developer Portal is owned and operated by the platform team.

For questions about the Developer Portal or the API:

Email: support@aiwni.com

Location: Alexandria, Egypt

Have a question about this policy?

Contact us
Terms of Use•Developer Portal Home