LeonAI Priority for Make.com
Last updated: 12 September 2026 · Version 1.3
This Data Processing Addendum ("DPA") forms part of the agreement between the customer ("Customer", "Controller") and LeonAI Ltd. ("LeonAI", "Processor") for use of the LeonAI Priority connector for Make.com and its supporting cloud services (the "Service"). It governs LeonAI's processing of Personal Data on the Customer's behalf.
This DPA is drafted primarily under the Israeli Protection of Privacy Law, 5741-1981 (as amended, including Amendment No. 13 in force from 14 August 2025) and the Protection of Privacy Regulations (Data Security), 5777-2017. For Controllers subject to the EU/UK GDPR, Section 13 (GDPR Module) applies in addition.
Where this DPA conflicts with the main agreement on the subject of data protection, this DPA prevails. Capitalised terms not defined here have the meaning given in the main agreement.
The Customer is the Controller/Database Controller of the ERP Data and ERP Credentials. LeonAI acts solely as Processor/Holder and, for the purposes of the Data Security Regulations, as an external service provider (מיקור חוץ) under regulation 15, processing data on behalf of the Controller; the duties the Regulations place on a holder apply to LeonAI directly.
LeonAI operates as a stateless proxy in the data path: every operation the Customer runs in Make.com transits LeonAI's cloud services, which authenticate to the Customer's ERP and relay the request and response. LeonAI Processes Personal Data only to provide the Service and only on the Customer's documented instructions, which include the configured Make.com scenarios and this DPA.
Subject matter: transmission and transformation of ERP Data between Make.com and the Customer's Priority ERP. Duration: for the term of the agreement, plus the short technical retention windows described in Section 8.
Reading, creating, and updating records and running procedures in the Customer's Priority ERP in response to the Customer's Make.com automations; authenticating the Customer to its own ERP; licence metering; and fetching ERP form/field metadata to build the connector's interfaces.
This section describes, transparently, how the Service actually handles ERP Credentials and ERP Data, so that the Customer can assess it against its own obligations.
LeonAI maintains an information security programme certified to ISO/IEC 27001:2022 (certificate no. 1126333). The measures include, at minimum:
The Customer, as Database Controller, classifies its own database under the Data Security Regulations. Because the Service is multi-tenant, LeonAI applies one uniform set of controls (this Annex II) to every Customer, designed with the medium and high security levels in mind, including a database definitions document, access control and authorisation, 24-month access logging and monitoring, periodic risk surveys and independent penetration tests, and incident handling procedures. LeonAI does not vary these controls per Customer; a Customer that requires additional controls should contact LeonAI before onboarding.
The Customer authorises LeonAI to engage the Sub-processors listed at /legal/subprocessors to Process Personal Data in connection with the Service. LeonAI imposes data-protection obligations on each Sub-processor no less protective than those in this DPA and remains responsible for their performance.
LeonAI will give the Customer prior notice of the addition or replacement of a Sub-processor by updating the Sub-processor page and, on request, by email to Customers who have subscribed to notifications. The Customer may object on reasonable data-protection grounds within 30 days; the parties will work in good faith to resolve the objection, failing which the Customer may terminate the affected part of the Service.
Because LeonAI does not maintain a durable copy of the Customer's transactional ERP records, data-subject requests (access, correction, deletion) are ordinarily fulfilled by the Customer directly in its Priority ERP. LeonAI will, taking into account the nature of the Processing, provide reasonable assistance to enable the Customer to respond to such requests, and will action deletion of any transient cache or metadata on the Customer's reasonable instruction. Where a data subject approaches LeonAI directly, LeonAI will, as section 13A of the Law requires of a holder, inform the data subject whether it Processes Personal Data about them on a Controller's behalf, identify that Controller, and forward the request to the Controller.
| Data | Store | Retention |
|---|---|---|
| ERP Credentials (username/password) | Memory only | Duration of the request; never persisted |
| Transactional ERP records (live read/write) | Memory only | Duration of the request; not stored |
| ERP responses / lookup lists (cache) | Memorystore (Redis), private | Auto-expiry, typically 3 min – 1 hour |
| ERP structural metadata + company name | Cloud SQL, private | For the term; refreshed on sync |
| Licence token + usage counters | Cloud SQL, private | For the term |
| Access-audit records (admin actions, data-access audit logs, application access log) | Cloud Logging (me-west1), 24-month bucket | 24 months (regulation 10(ד)) |
| Application logs | Cloud Logging (me-west1) | 30 days active; in-region archive up to 400 days |
| Encrypted backups | Cloud SQL automated backups (me-west1) | 31 retained daily backups (about 31 days) |
LeonAI maintains procedures to detect, investigate, and respond to security incidents. On becoming aware of a security incident that affects the Customer's Personal Data, LeonAI will notify the Customer without undue delay, and in any event within twenty-four (24) hours of becoming aware, and provide the information reasonably available to help the Customer meet its own notification obligations to the Israeli Privacy Protection Authority, supervisory authorities, and affected individuals, as applicable under the Law (including the breach-notification duties introduced by Amendment 13), the Data Security Regulations, and the GDPR where relevant.
Notification will include, to the extent known: the nature of the incident, the categories and approximate volume of data and data subjects affected, likely consequences, and the measures taken or proposed. An initial notification will not be delayed pending complete information.
Where LeonAI is itself required, as a holder under regulation 11 of the Data Security Regulations, to report a serious security incident to the Israeli Privacy Protection Authority, it will do so in coordination with the Customer and will share the report with the Customer.
LeonAI will not identify the Customer in any public statement or regulatory filing about an incident, other than as required by law, without the Customer's prior written consent, and will cooperate reasonably with the Customer's own communications.
LeonAI Processes and stores the Customer's Personal Data for the Service in Israel (GCP me-west1), subject only to the platform-level exceptions disclosed in Annex II, none of which involves storing ERP Data outside Israel. Israel benefits from a European Commission adequacy decision, so transfers of Personal Data from the EEA to LeonAI in Israel do not require additional safeguards. Where a Sub-processor Processes Personal Data outside Israel or the EEA, LeonAI relies on an adequacy decision or Standard Contractual Clauses as appropriate and, as a matter of Israeli law, on regulation 2(8) (recipient in a state party to Council of Europe Convention 108, including the EEA) or regulation 2(4) (the recipient's contractual undertaking to the Israeli standard) of the Protection of Privacy Regulations (Transfer of Data to Databases Abroad), 5761-2001. Transfers to the Customer's own ERP host occur at the Customer's direction and are the Customer's responsibility.
On termination of the Service, LeonAI will, at the Customer's choice, delete or return the Personal Data it holds for the Customer (structural metadata, company identifiers, licence tokens, and usage counters), and will delete existing copies from active systems within 30 days and from encrypted backups within a further 31 days as the retained daily backups rotate (about 60 days in total), save where retention is required by law, and will confirm completion in writing on request. Access-audit records that reference the Customer are kept for the fixed 24-month period the Data Security Regulations require and are then purged. Transient caches expire automatically; ERP Credentials and transactional records are not retained and require no deletion step.
LeonAI will make available to the Customer, on reasonable request and subject to confidentiality, information necessary to demonstrate compliance with this DPA and with LeonAI's obligations under the Data Security Regulations, including its ISO/IEC 27001:2022 certificate, a summary of the measures in Annex II, and — once issued — its SOC 2 Type II report, subject to a non-disclosure agreement. Where the Customer reasonably requires further audit, the parties will agree in advance the scope, timing, and cost, conducted so as not to compromise the security or confidentiality of other customers, no more than once per year absent a specific cause (such as a confirmed incident or a regulator's requirement).
Annual report. Once a year, on request, LeonAI will provide the Customer with a written report on the performance of its obligations under this DPA, as regulation 15 of the Data Security Regulations requires an outsourcing agreement to provide for, covering: the security measures in force, security incidents affecting the Customer during the period, the results of the most recent risk survey and penetration test (in summary), sub-processor changes, and any material findings from LeonAI's internal or external audits.
Regulatory requests. If LeonAI receives a request or order from the Privacy Protection Authority, a court, or another authority concerning the Customer's Personal Data, it will notify the Customer promptly unless legally prohibited, disclose only what is legally required, and support the Customer in seeking protective measures.
Remediation. If an audit or the annual report reveals a material non-conformity with this DPA, LeonAI will prepare a remediation plan within 30 days and implement it within a reasonable period agreed with the Customer, at LeonAI's cost.
Enterprise terms. Customers on the Enterprise plan may execute a signed version of this DPA that adds commitments negotiated for their agreement, including a written confirmation of Annex II against the security level the Customer has assigned to its database, an enhanced liability cap for data-protection and security breaches, and a contractual penetration-testing and risk-assessment cycle with summary reports available under NDA. The signed version prevails between the parties to it; this published DPA applies to all other Customers.
Where the Customer is subject to the EU General Data Protection Regulation (Regulation (EU) 2016/679) or the UK GDPR, this Module supplements the DPA and the parties agree that it satisfies Article 28(3):
LeonAI Ltd. (company no. 516916954), 9 Hannah Rovina St., Mazkeret Batya, Israel. Data protection queries and requests under this DPA: [email protected].
Questions about these terms? Contact [email protected].