Overview
This policy explains how Ebda AI Studio ("we", "us") handles personal data in Ebda Chat (the "Service"). It applies to merchants who use the Service and, through them, to the merchants' customers who message them on WhatsApp.
1. Who is responsible for what
• The merchant is the controller of its customers' data: phone numbers, names, messages, media and order references that pass through the merchant's workspace. The merchant decides why and how that data is used and is responsible for having a lawful basis, including consent for marketing.
• Ebda AI Studio is the processor of that conversation and contact data. We process it only on the merchant's behalf and instructions, under the Data Processing Agreement (https://ebda.app/en/legal/whatsapp-dpa/).
• Ebda AI Studio is the controller of the merchant's own account, billing and security data, which we use to run and protect the Service.
• Meta Platforms is a separate, independent controller for WhatsApp. When a customer uses WhatsApp, Meta processes data under its own terms and privacy policy. We do not control that processing.
2. What we process
• Merchant account data: name, business name, email, login and role details, team members, settings, plan and billing records (top-ups, wallet entries, statements).
• Customers' data on the merchant's behalf: phone numbers, profile names, message text, media, message status, tags, notes, consent and opt-out records, and order references.
• Technical data: security and audit entries, error reports without message content, and usage records needed for billing.
• AI agent data: if the merchant turns the agent on, the customer's message and the merchant's knowledge base are sent to the AI model to produce a reply.
3. Why we process it, and on what basis
Under Egypt's Personal Data Protection Law No. 151 of 2020 ("PDPL"):
• To deliver the Service to the merchant (receive, store, route and send messages, run campaigns, run the AI agent, bill the wallet): processing needed to perform our contract with the merchant, and carried out for the merchant as controller on the basis the merchant has with its customers (the customer's consent or a legitimate interest recognised by the PDPL).
• To keep opt-out records and honour them: legal obligation and the customer's choice.
• To secure the Service, prevent abuse and keep audit records: our legitimate interest.
• To keep financial records: legal obligation.
• To contact the merchant about the Service: contract and legitimate interest.
We do not sell personal data.
4. No training of AI models
We do not use messages, media or contact data of merchants or their customers to train or improve AI models, ours or anyone else's. If the merchant connects its own model provider, the merchant's model key is stored encrypted and the customer's message goes to that provider under the merchant's own relationship with it.
5. How long we keep data
• While the merchant's account is active, conversation and contact data is kept so the merchant can use the Service.
• After the account ends, the data is deleted within 30 days. Backups expire after 30 days.
• A merchant can erase a single contact, which removes that contact's data from the live workspace, including stored message bodies. Backups taken earlier expire after 30 days.
• Financial records (wallet entries, top-ups, billing records) are kept as the law requires, even after the account is closed or data deletion is requested. They do not contain customers' phone numbers or names.
• Other retention periods are not stated here; where none is stated, the rule above applies.
6. Who receives data, and transfers outside Egypt
• Meta receives the messages and related data needed to send and receive WhatsApp messages, as an independent controller.
• Our service providers (sub-processors) help us host, store, secure and run the Service. They are listed in the Data Processing Agreement. Our hosting provider runs a global network, so data may be processed or stored outside Egypt. The AI model, when used, runs inside our hosting provider.
• Where data leaves Egypt, we do so in line with the transfer requirements of the PDPL and contractual safeguards with the receiving provider.
• We disclose data to authorities only when the law requires it.
7. Security
We use encryption in transit; encrypted storage of business tokens and merchants' model keys; separation of each merchant's workspace from the others; role-based access with owner and staff roles; limits on who in our team can reach production data; and audit logs of sensitive actions. No system is perfectly secure, and we cannot promise absolute security.
8. Breach notification
If we become aware of a personal data breach affecting merchant data, we notify the affected merchants without undue delay and within 72 hours of becoming aware, with what we know and what we are doing. The merchant, as controller, decides on notifying its customers and the authority where required.
9. Rights of data subjects
Customers whose data passes through a merchant's workspace have rights under the PDPL: to know, access, correct, erase, object and restrict, and to withdraw consent. Because the merchant is the controller, a customer should send the request to the merchant. We help the merchant answer. A customer can also opt out of messages at any time by writing STOP. To request deletion of data, see https://ebda.app/en/legal/data-deletion/.
10. Children
The Service is for businesses and is not directed to children.
11. Changes
We may update this policy. For a material change we will notify merchants before it applies.
12. Contact
privacy@ebda.app. Security reports: security@ebda.app. If the Arabic and English versions differ, the Arabic version prevails.