Data Processing Agreement (DPA)
Between a business that uses Mabel and Mabel. Version of October 22, 2026.
This is the wording we offer to businesses. It is still being reviewed by a lawyer, and a business that wants to sign receives a signed copy on request: Mabelai.support@gmail.com
The agreement follows Regulation 15 of the Protection of Privacy (Data Security) Regulations, 2017, the Protection of Privacy Law after Amendment 13, and the Transfer of Data Abroad Regulations, 2001. The business is the controller of the database, and Mabel is the holder (processor).
1. The parties and their roles
1.1 Business ("the controller"): the business that uses Mabel. It decides why the data is collected and what is done with it.
1.2 Mabel ("the processor"): processes the data only on behalf of the business and only on its instructions. Mabel does not use the data for any purpose of her own.
1.3 This agreement is part of theTerms of Use. If there is a conflict on privacy and data security, this agreement prevails.
2. What Mabel does for the business
Answers customers by phone, WhatsApp, SMS, email and on the website. Books, moves and cancels appointments. Sends confirmations, reminders, messages before and after a visit, recall and payment reminders. Keeps a basic customer card, a team chat and an activity log.
3. What data is processed
| Type | Examples | Note |
|---|---|---|
| Customer details | Name, phone, email, address for a home visit | |
| Appointments | Time, staff member, type of service, arrival status | In a clinic, the type of treatment is medical data |
| Conversation content | Text, voice transcript, WhatsApp messages | May include sensitive information the customer shares |
| Payments | Open amount, payment link | Mabel does not store card details |
| Staff details | Name, phone, email, role, messages in the team chat | |
| Activity log | Who did what and when |
3.1 Medical data is "especially sensitive data" under the law. Therefore, in a business in medical mode:
- Reminders and messages to the customer do not include the reason for the visit or the name of the treatment.
- Mabel does not ask for medical details. If the customer shares them, the information is kept only as part of the conversation.
- Mabel does not replace a medical record. Treatment summaries and the medical file stay in the business's own system.
3.2 Mabel does not record phone calls. Voice that passes through Mabel is transcribed and kept as text only.
4. Mabel's commitments
4.1 Only on instructions: Mabel processes data only to provide the service. She does not sell it, does not use it for advertising, and does not train AI models on it.
4.2 Confidentiality: only those who need access get it, and everyone who gets access signs a confidentiality undertaking.
4.3 Security: according to Appendix B, and at least at the level the regulations require of the business's database.
4.4 Security incident: Mabel notifies the business without delay, and no later than 24 hours after discovery. The notice includes what happened, which data was affected, and what was done. Mabel helps the business report to the Privacy Protection Authority when needed.
4.5 Customer rights: if a customer asks to see the data about them, to correct it or to delete it, Mabel helps the business answer within 14 days. A request that reaches Mabel directly is passed to the business.
4.6 Annual report: once a year, and on request, Mabel gives the business a summary of the security measures and of incidents, if there were any (Regulation 15(b)).
5. Sub-processors and transfer abroad
5.1 The business approves the sub-processors in Appendix C. Some of them are outside Israel.
5.2 Transfer abroad is done under the 2001 regulations: to countries that protect data at a similar level (for example the European Union), or to a provider that has committed by contract to protect the data and not pass it on. Mabel keeps these commitments and presents them on request.
5.3 Mabel gives 30 days' notice of a new sub-processor. The business can object, and if there is no solution, end the engagement without penalty.
5.4 Mabel is responsible to the business for everything the sub-processor does.
6. Retention and deletion
6.1 Conversations are kept for 14 days by default. The business can change this in the settings.
6.2 The activity log is kept according to the business's setting, 24 months by default.
6.3 At the end of the engagement the business can export all the data. After 30 days Mabel deletes it, including from backups within a further 60 days, and confirms in writing.
7. Audit
Once a year the business can ask for the security answers, the access log for its data, and a penetration test report when there is one. An on-site audit is arranged in advance and at the business's expense.
8. The business's commitments
8.1 It has a legal basis to collect the data, and it tells customers that Mabel answers on its behalf (privacy notice).
8.2 It collects consent in advance before marketing messages, including recall, under section 30A of the Communications Law.
8.3 It decides for itself who on the team gets access, and removes access from an employee who has left.
9. General
9.1 The governing law is the law of Israel. Jurisdiction, the liability cap and insurance are set in the signed agreement.
9.2 The agreement is in force as long as Mabel processes the business's data.
Appendix A: Processing details
| Subject | Details |
|---|---|
| Customers | The business's customers who contact it or booked an appointment |
| Team | The business's employees who were invited to Mabel |
| Purpose | Answering, appointments, reminders, payments, team communication |
| Duration | The whole engagement period plus 30 days |
Appendix B: Security measures
The full, up-to-date details are on thedata security page. In short:
- Encryption at rest: the whole database is encrypted with AES-256-GCM, and the key is kept only in the server settings.
- Encryption in transit: HTTPS only, security headers and a Content Security Policy.
- Access: role-based permissions, two-step verification on the website and in the app (the owner can require it), a device list and remote disconnect.
- Log: every sensitive action is recorded, including every use of system-administrator access.
- Backup: an encrypted daily backup with a restore check.
- Not yet: an external penetration test, SOC 2 or ISO 27001 certification, a data protection officer.
Appendix C: Sub-processors
| Supplier | What for | Location | What passes |
|---|---|---|---|
| Render | Server | US or Europe, depending on the server region | Everything, while processing |
| Neon | Database | Frankfurt (EU) | Everything, encrypted |
| Anthropic | Mabel's understanding and answers (Claude) | US | Conversation content while answering |
| ElevenLabs | Voice and transcription | US / EU | Voice and transcript during a call |
| Twilio | Phone, SMS, WhatsApp | US | Phone numbers and message content |
| Meta (WhatsApp) | WhatsApp Business, through Twilio | US / EU | WhatsApp message content |
| Google Firebase | Sign in to the account | US | Email and ID of staff members |
| Sentry | Error monitoring | US / EU | The error message only, without content and without user details |
| Postmark | Emails, when turned on | US | Email content |
Data Processing Agreement (English summary)
Between a business using Mabel and Mabel. Version of 22 October 2026.
This is the agreement we offer businesses. It is still being reviewed by a lawyer; a business that wants to sign gets a signed copy on request: Mabelai.support@gmail.com
Roles. The business is the controller (database owner); Mabel is the processor and acts only on its instructions, under Israel's Privacy Protection (Data Security) Regulations 2017, Amendment 13 and the 2001 transfer-abroad regulations.
Data. Customer contact details, appointments, conversation text and voice transcripts, open payment amounts (never card details), staff details and the audit log. In medical mode, reminders never name the treatment, Mabel never asks for medical details and is not a medical record. Calls are not recorded; voice is kept as text only.
Commitments. No selling, no advertising use, no AI training on the data. Confidentiality for everyone with access. Security per Annex B and at least the level the regulations require. Breach notice without delay and within 24 hours of discovery. Help answering data subject requests within 14 days. A yearly security report on request.
Sub-processors. Listed in Annex C (Render, Neon, Anthropic, ElevenLabs, Twilio, Meta, Google Firebase, Sentry, Postmark). New ones are announced 30 days ahead, and the business may object or terminate without penalty. Mabel is liable for its sub-processors.
Retention and deletion. Conversations 14 days by default, the audit log 24 months by default, both adjustable. At the end, full export, then deletion within 30 days and from backups within 60 more, confirmed in writing.
Audit. Once a year: security answers, the access log for the business's data, and a penetration test report once one exists. On-site audits by appointment at the business's cost. Israeli law applies; jurisdiction, liability cap and insurance are set in the signed agreement.