esek.io is operated by Esek, a Meta Tech Provider. We build on the official WhatsApp Business Platform (Cloud API) and the Meta Marketing API on behalf of the businesses that use our service.
whatsapp_business_management, whatsapp_business_messaging. Used to manage merchant WABAs, phone numbers, message templates, and to send/receive messages on the merchant's behalf.ads_management, ads_read, business_management, pages_show_list. Used to create, manage and report on Meta ads (including click-to-WhatsApp) for the merchant's own ad accounts and Pages.What we comply with
Every merchant action we take through Meta APIs is bound by the Meta policies below. Where merchant content (messages, ads, catalogs) is involved, the merchant is the publisher and is responsible for what they send; esek.io enforces platform policy and refuses to transmit content that violates it.
- Meta Platform Terms and Developer Policies
- WhatsApp Business Solution Terms
- WhatsApp Business Messaging Policy
- WhatsApp Commerce Policy
- Meta Advertising Standards and Community Standards
- Applicable data-protection law (GDPR / Israeli Privacy Protection Law). See our Privacy Policy.
WhatsApp messaging compliance
Opt-in
Merchants must obtain explicit opt-in before sending any business-initiated message. We require merchants to declare the opt-in source and retain proof. Templates are submitted to Meta for review; we do not bypass template approval.
Customer service window
Outside the 24-hour customer service window, only approved templates may be sent in the relevant template categories (utility, authentication, marketing). Marketing templates respect per-recipient frequency caps and quiet hours.
Opt-out
All marketing threads honour opt-out keywords (STOP / UNSUBSCRIBE and localized equivalents). Opt-out is recorded and enforced across the merchant's WABA. A recipient who opts out cannot be re-added by import.
Prohibited use cases
We do not enable, and our chat-agent prompts refuse, content that violates the WhatsApp Commerce Policy (firearms, drugs, adult products, real-money gambling, etc.) or that targets WhatsApp users with unsolicited bulk messaging. Suspected abuse leads to suspension pending review.
Ads & Marketing API compliance
- Ads are created against the merchant's own ad account; billing and ownership stay with the merchant.
- Creatives and targeting must conform to Meta Advertising Standards. Special ad categories (credit, employment, housing, social issues) are flagged and require the merchant to confirm category before launch.
- We do not produce ads that imply personal attributes of the viewer, scrape Meta data, or circumvent Meta's review.
- Audiences built from merchant first-party data require a documented lawful basis and respect Meta's Custom Audiences terms.
Data handling
What we collect, how we use it, and the legal bases are described in the Privacy Policy. Highlights relevant to platform compliance:
- Merchant data (account, billing, OAuth tokens): processed to provide the service.
- End-user data (WhatsApp messages, phone numbers, ad engagement): processed on the merchant's behalf as a data processor; the merchant is the controller.
- Encryption: HTTPS in transit, and since October 30, 2026 TLS with verified certificates between our services, database and cache inside our production environment; encrypted at rest by our cloud provider (AES-256). Integration tokens and credentials are encrypted in the application with AES-256-GCM; re-encrypting tokens saved before that encryption was added is planned.
- Retention: operational data is retained only as long as needed for service provision and legal obligations. Account deletion is documented on the Data Deletion page.
- Sub-processors: the full list, with purposes and locations, is on our Sub-processors page.
- Cross-border transfers: data is hosted in the United States. Transfers from the EU and UK rely on the EU-US Data Privacy Framework and Standard Contractual Clauses.
Security & access controls
- Workspace access is role-based (owner, admin, agent). Production access is restricted to the owner's own account. Database query logging and a personal-data access log are planned.
- Secrets stored in Google Secret Manager, with every access recorded in an audit log; no credentials in source control.
- Incoming webhooks from Meta, Paddle, Twilio and Resend are signature-verified and rejected when the signature is invalid.
Incident response
Security incidents are triaged on detection. If an incident affects merchant or end-user personal data, we will notify affected merchants without undue delay and within the timelines required by applicable law (e.g. 72 hours under GDPR), with the information needed for them to meet their own notification duties.
Reporting abuse or a policy concern
If you believe a message or ad sent through esek.io violates Meta or WhatsApp policy, or you want to report suspected misuse of our platform:
- Email compliance@esek.io with the subject Policy concern.
- Include the WhatsApp message (screenshot or sender number) or the ad ID / link, and a short description.
- We acknowledge reports within 2 business days and act on confirmed violations promptly.
GDPR roadmap: what's in place and what's planned
The following is an honest status of our GDPR posture so customers, auditors, and our own AI assistants can answer accurately.
In place today
- Privacy Policy, data-deletion flow, and retention windows.
- Processor model: merchant is controller of end-user data, esek.io is processor.
- Encryption in transit (HTTPS) and at rest (AES-256, by our cloud provider); production access restricted to the owner's account.
- WhatsApp opt-in/opt-out enforcement and template-approval discipline.
- Public sub-processor list with names, locations, and 30 days' email notice to workspace owners before a new sub-processor is added (Art. 28(2)).
- Cookie consent banner: advertising tags on our website load only after consent for visitors in the EU, EEA and UK, and a Global Privacy Control signal counts as a decline.
- Data Processing Agreement (DPA) (Art. 28): published and accepted by the workspace during onboarding, with the version, time and accepting user recorded.
- Incident response procedure and register: a restricted operational register and English and Hebrew notification drafts are in place. The incident coordinator completed a tabletop exercise on 10 October 2026; it did not include live credential rotation. Access-log and access-control follow-ups remain open.
Planned, not yet shipped
- EU data residency: current production is US-hosted under the EU-US Data Privacy Framework and SCCs; migration to an EU region (planned before first EU enterprise customer).
- EU representative appointed and published per Art. 27.
- Records of Processing (RoPA) document (Art. 30) and a DPIA for chat-agent automated decisioning and ad-audience generation (Art. 35).
- Formal data-subject request intake with SLA tracking for access, rectification, portability, and objection requests (Arts. 15, 16, 20, 21).
If you are evaluating esek.io for an EU deployment and need any of the above today, contact compliance@esek.io. We will prioritise items required for your engagement.
Contact
- Compliance & abuse: compliance@esek.io
- Privacy & data requests: privacy@esek.io
- General: hello@esek.io
Legal entity
esek.io is a sole proprietorship (עוסק מורשה) registered in Israel.
- Registered address: Herzl 100, Tel Aviv, Israel
- Email: legal@esek.io
Our Israeli business registration number is available on request from legal@esek.io.