Legal
Data Processing Addendum
Last updated: 19 November 2026
This Addendum is part of the agreement between the customer organisation ("Customer") and iDigital.Agency ("we") for the Aliaa service (the Terms of Service and the Order). It applies automatically when the Customer accepts the Terms; no separate signature is needed. A signed copy is available on request.
1. Definitions and roles#
1.1 "Data Protection Law" means Israel's Protection of Privacy Law, 5741-1981 (including Amendment 13) and its regulations, including the Protection of Privacy (Data Security) Regulations, 5777-2017; and, where they apply, the EU General Data Protection Regulation 2016/679 ("GDPR") and the UK GDPR. "Personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have their GDPR meanings. In Israeli law terms, the Customer is the database controller and we are the holder.
1.2 "Customer Personal Data" means personal data in Customer Data (as defined in the Terms) that we process for the Customer.
1.3 The Customer is the controller and we are its processor. The Customer is responsible for having a lawful basis for the processing, for giving data subjects any required notice, and for the lawfulness of its instructions.
2. Processing on instructions#
2.1 We process Customer Personal Data only on the Customer's documented instructions, including for transfers abroad. The agreement, and the Customer's use and settings of the Service (including switching features and connections on or off), are the Customer's instructions. Annex 1 describes the processing.
2.2 We will tell the Customer if we believe an instruction breaks Data Protection Law, and may then decline to follow it. If the law requires us to process Customer Personal Data in another way, we will tell the Customer first, unless the law forbids it.
2.3 We do not sell Customer Personal Data, use it for advertising, or use it to train AI models.
3. Confidentiality and staff#
Only staff who need access to provide the Service have it. Each is bound by a written confidentiality undertaking and is instructed in data protection and security. Access is personal and is removed when no longer needed.
4. Security#
4.1 We maintain the technical and organisational measures in Annex 2, appropriate to the risk and in line with GDPR Article 32 and the Israeli Data Security Regulations. We may update them as long as the overall level of protection does not go down.
4.2 If the Customer tells us the security level its database requires under the Israeli Data Security Regulations, we will apply the measures that level requires to the parts of the Service we operate. The Customer is responsible for the measures within its own control, such as choosing Users, roles and sign-in methods and reviewing access.
5. Sub-processors#
5.1 The Customer gives general authorisation for the sub-processors listed in Annex 3. We bind each of them to data protection duties no less protective than this Addendum, and we remain responsible for what they do.
5.2 We will give at least 15 days' notice by email to the account administrator before adding or replacing a sub-processor. The Customer may object on reasonable data protection grounds within that period. If we cannot resolve the objection, the Customer may terminate the affected Service and receive a refund of fees prepaid for the unused period.
5.3 Services the Customer chooses to connect (for example Microsoft 365 or Google Workspace) are not our sub-processors. The Customer uses them under its own agreement with their providers.
6. Helping the Customer#
6.1 Data subject requests. The Service lets the Customer find, correct, export and delete data. If we receive a request directly, we will pass it to the Customer without undue delay and will not answer it ourselves unless the Customer asks us to. We will give reasonable further help where the Customer cannot handle a request through the Service.
6.2 Assessments and authorities. We will give the Customer the information it reasonably needs for data protection impact assessments, prior consultations, security duties and any inquiry by a supervisory authority, including Israel's Privacy Protection Authority.
6.3 Help that goes beyond what the Service provides and beyond reasonable effort may be charged at rates agreed in advance.
7. Personal data breaches#
7.1 We will notify the Customer without undue delay, and no later than 72 hours, after becoming aware of a personal data breach affecting Customer Personal Data. The notice will describe, as far as known, what happened, the kinds and approximate number of people and records affected, the likely consequences, and the steps taken or proposed. Information may follow in stages.
7.2 We will record every security incident, take reasonable steps to contain and remedy it, and cooperate with the Customer's own notifications to authorities and data subjects. Our notice is not an admission of fault.
8. International transfers#
8.1 We are established in Israel, which the European Commission recognises as providing an adequate level of protection. Customer Personal Data is hosted at the location shown in Annex 3.
8.2 AI requests are processed by Anthropic in the United States under Anthropic's Data Processing Addendum, which includes the Standard Contractual Clauses approved by Commission Implementing Decision (EU) 2021/914 ("SCCs").
8.3 If a transfer of Customer Personal Data subject to the GDPR, the UK GDPR or Swiss law is made to a country without an adequacy decision and is not already covered by section 8.2, the SCCs apply to it and are incorporated here by reference: Module 2 between the Customer and us and Module 3 between us and the sub-processor; Clause 7 applies; Clause 9 option 2 with the notice period in section 5.2; Clauses 17 and 18 — the law and courts of Ireland; the SCC annexes are Annexes 1 to 3 of this Addendum; with the UK Addendum or Swiss amendments where those laws apply. If the SCCs conflict with this Addendum, the SCCs prevail.
8.4 Transfers out of Israel are made in line with the Protection of Privacy (Transfer of Data to Databases Abroad) Regulations, 5761-2001. For personal data received from the European Economic Area, we will help the Customer meet the Israeli rules that apply to such data, including deleting data that is no longer needed and keeping it accurate.
9. Return and deletion#
9.1 During the subscription the Customer can download its files from the Service at any time, and we will provide a full export on request. Both remain available for 30 days after the subscription ends.
9.2 We then delete Customer Personal Data from the live Service within a further 30 days. Encrypted backup copies are overwritten on their normal cycle, which takes up to about seven months; until then they are kept protected and are not used for any other purpose. The same cycle applies to data the Customer erases during the subscription. We will confirm deletion in writing on request. We may keep data only where the law requires it, protected under this Addendum.
10. Audits and reports#
10.1 Compliance is shown by documents first. On request, once a year, we will give the Customer a written report on how we meet this Addendum and the Israeli Data Security Regulations, and will answer a reasonable security questionnaire.
10.2 If that is not enough to show compliance, or a supervisory authority requires it, the Customer or an independent auditor bound by confidentiality may audit us once in any 12 months, with 30 days' notice, during business hours, at the Customer's cost, and in a way that does not put other customers' data or our security at risk.
11. Liability and term#
Each party's liability under this Addendum is subject to the limits in the Terms, except where Data Protection Law does not allow it. This Addendum lasts as long as we process Customer Personal Data.
Annex 1 — Details of processing#
| Controller | The Customer named in the Order. Contact: its account administrator. |
| Processor | iDigital.Agency (iDigital Agency, registration number 061253266, Yair Stern 23, Haifa, Israel). Contact: [email protected]. |
| Data subjects | The Customer's staff, volunteers and board members; contacts at funders, partners and suppliers; for organisations that give grants: applicants, grantees, referees, reviewers and their contact persons; beneficiaries and other people whose data the Customer records; people who answer the Customer's forms; people in mail the Customer's Users connect. |
| Categories of data | Names, contact details, roles and account data; organisation records; project, task, budget and financial records; funder records, proposals and reports; applications, reviews and grantee reports (when an application is declined or withdrawn, its answers and files are removed and the record is reduced to name, contact details, a short summary and internal notes); documents the Customer uploads; mail its Users connect; form answers; AI requests and AI Output; system logs. |
| Sensitive data | Not required by the Service. The Customer may record it only where needed and lawful (Terms, section 7(b)). |
| Nature and purpose | Hosting, storage, backup, search, reading text from files, AI drafting, summarising and question answering, reading mail and preparing drafts (when connected), sending notices the Customer switches on, export and deletion — to provide the Aliaa service to the Customer. |
| Duration | The term of the agreement, then section 9. |
Annex 2 — Technical and organisational measures#
- Separation: each Customer has its own instance, with its own database, file store and application. Shared helper components (the web front door, file conversion and search indexing) keep no Customer Data.
- Encryption: all access to the Service is encrypted in transit (TLS). Off-site backups are encrypted with a key that is unique to the Customer and is not kept on the server. Stored mailbox access tokens are encrypted.
- Access control: role-based access inside the Service, enforced in the database; optional two-step sign-in; sign-in through Microsoft 365 or Google Workspace; our own administrative access limited to named staff.
- Outbound control: each instance can reach only a fixed list of outside services (the AI provider and the services the Customer connects).
- AI controls: the AI has no ability to send mail; it sees only what the User asking is allowed to see; restricted material (HR, participants) is kept from it by default; what it proposes takes effect only when a person confirms; a daily and monthly AI spending limit per Customer.
- Local processing: reading text from files and search indexing run on our own servers.
- Backup and recovery: a nightly backup of each instance; an encrypted copy stored off-site with a different provider; restores are tested periodically.
- Updates: timely security updates; services exposed only as needed.
- Logging and incidents: security-relevant events are logged; incidents are recorded.
- People: confidentiality undertakings; security instruction on joining and periodically.
- Suppliers: sub-processors are assessed before use and bound by written data protection terms.
- Deletion: deletion at the end of the service as in section 9.
Annex 3 — Sub-processors#
| Sub-processor | Purpose | Location | Safeguard | Transfer mechanism |
|---|---|---|---|---|
| To be confirmed before the first customer starts | Servers running each Customer instance | To be confirmed before the first customer starts | Data processing agreement | Adequacy if in the EEA or an adequacy country; otherwise SCCs (section 8.3) |
| To be confirmed before the first customer starts | Encrypted off-site backup copy (cannot read the content) | To be confirmed before the first customer starts | Data processing agreement | Adequacy if in the EEA or an adequacy country; otherwise SCCs (section 8.3) |
| Anthropic PBC | AI processing (Claude models through its API) | United States | Anthropic Data Processing Addendum; no training on the data | SCCs (section 8.2) |
| Cloudflare, Inc. | Turnstile: protection of public application and portal pages against automated abuse (browser signals and IP address of visitors; only where the Customer uses public forms) | United States / global network | Cloudflare Data Processing Addendum | SCCs in Cloudflare's Data Processing Addendum |
Transfers from Israel to any of these sub-processors are also made under the Israeli regulations named in section 8.4.