Data subject access requests: what a business in Israel must do, and what changes when it has customers in Europe
Any person may ask a business to see the personal data it holds about them and to have it corrected. Israeli law sets fixed deadlines for this in regulations, and a request left unanswered for 21 days is treated as a refusal. A business that sells to people in the European Union is also subject to the EU General Data Protection Regulation (GDPR), under which the rights are broader.
The right of access under Israeli law
Section 13 of the Privacy Protection Law, 5741-1981, provides that every person is entitled to inspect, personally, through a representative authorised in writing, or through a guardian, the personal data about them held in a database. The database controller must allow inspection in Hebrew, Arabic or English, at the requester’s choice. The right applies to every database, including one the business is not required to register. Amendment 13 to the Law, which entered into force on 14 August 2025, did not change its substance.
The deadlines are set in the Privacy Protection Regulations (Conditions for Inspection of Data and Procedure on Appeal), 5741-1981. The business must allow inspection within 30 days of receiving the request. If it refuses, it must give notice in writing, on the form set out in the Regulations, within 21 days, and if it does not reply within 21 days it is treated as having refused. The Privacy Protection Authority may extend these deadlines by 15 days. Under Regulation 6, the requester pays the controller or holder NIS 20 for the inspection. According to the Authority, there is usually no justification for requiring the requester to attend in person, and the data may be provided in a digital file.
The right has exceptions. Data about the requester’s physical or mental health that may cause serious harm to their health or endanger their life is given to a physician or psychologist acting for them, not to the requester directly. There is no duty to disclose data in breach of a privilege established by law, unless the privilege exists for the requester’s benefit. Section 13(e) excludes certain databases from the right, including those of security authorities, the Prison Service and the tax authorities, investigation and enforcement databases of authorities designated by order, the Money Laundering Prohibition Authority database, and information that state security, foreign relations or statutory provisions require not to be disclosed.
Where the database is held by another party (a holder), the controller refers the requester to the holder, giving its address, and instructs the holder in writing to allow the inspection. A requester who first approaches the holder is told whether the holder holds data about them, and the controller’s name and address (Section 13A). Under Regulation 4, a service bureau that processes data for clients may reject the request if it has referred the requester to the owner of the data.
A requester may bring a claim to court against a refusal to allow inspection or a refusal to correct (Section 15 of the Law). Under Regulation 8, the appeal is filed with the Magistrates’ Court in whose district the database is located, within 30 days of the notice of refusal. No reply within the deadline is treated as a refusal (Regulations 5(b) and 7(c)). The respondent is the controller or the holder (Regulation 9). If the appeal is accepted, the court sets the dates for inspection, correction or deletion (Regulation 10(b)).
Amendment 13 added Section 15A, which allows the court to award exemplary damages, without proof of harm, of up to NIS 10,000. The violations that qualify include a controller that did not allow inspection at the time and in the manner set by the Regulations; one that agreed to correct or delete data but did not make the change or did not notify those who received the data from it; and one that did not notify the requester of its refusal to correct or delete.
In addition, the Privacy Protection Authority may impose an administrative fine of NIS 15,000 per breach: failing to allow inspection, failing to make a correction or deletion the controller agreed to, failing to notify the requester of a refusal, and failing to notify prior recipients of a correction.
Correction and deletion
Under Section 14 of the Law, a person who finds that the data about them is not correct, complete, clear or up to date may ask for it to be corrected or deleted. The request is made by registered letter to the controller or, if the controller is resident abroad, to the holder. A controller that agrees makes the change and notifies the requester and anyone who received the data from it in the three years before the request. A controller that refuses must notify the requester within 30 days of receiving the request (the Authority may extend this by 15 days), and no reply within 30 days is treated as a refusal (Regulation 7). A holder must correct the data if the controller agreed to the correction or a court ordered it (Section 14(d)). The Law contains no general right to erasure comparable to the European “right to be forgotten”. There are two limited arrangements. Under Section 17F, a person may demand that their data be deleted from a database used for direct mailing, or that it not be passed on to others. Under the Privacy Protection Regulations (Instructions for Data Transferred to Israel from the European Economic Area), 5783-2023, a person may ask for deletion of data received from the European Economic Area where it is no longer needed or was held unlawfully. These Regulations do not apply to data that a person provided directly to the business in Israel, but they do apply to all other data held in the same database together with data received from Europe.
Under Section 11 of the Law, when a business asks a person for data in order to include it in a database, it must inform them, among other things, of the purpose, to whom the data will be passed, and that they have a right of inspection and a right to request correction. On the notice and the consent requirements, see Privacy notices and consent under Amendment 13.
When EU law also applies
Under Article 3(2) of Regulation (EU) 2016/679 (GDPR), the Regulation applies to a business with no establishment in the Union where it offers goods or services to people in the Union or monitors their behaviour there. An online shop that ships to Germany, an app marketed to users in France, or an Israeli software company selling subscriptions in the Netherlands will usually fall within its scope. The Regulation also applies to data about contact persons at companies (B2B).
Such a business is subject to both laws at the same time and must meet the requirements of each. The most notable difference is scope: alongside access and correction, the GDPR grants rights to erasure (Article 17), to restriction of processing (Article 18), to data portability (Article 20), to object to processing (Article 21), and not to be subject to a decision based solely on automated processing (Article 22). Israeli law has no general equivalent of these rights; see Erasure, objection, portability and automated decisions.
The right of access under the GDPR
Article 15 of the GDPR entitles a person to know whether data about them is being processed, to receive a copy of the data, and to receive accompanying information: the purposes of processing, the categories of data, the recipients, the retention period, the source of the data, and the existence of automated decision-making. The reply is due within one month, which may be extended by two further months where the request is complex or there are many requests, provided the requester is told of the extension and the reasons for it within the first month (Article 12(3)). The first copy is free of charge.
The Court of Justice of the European Union has read the right broadly. On 12 January 2023, in Österreichische Post (C-154/21), it held that the business must disclose the identity of the recipients who received the data, not only their categories, unless this is impossible. On 4 May 2023, in FF (C-487/21), it held that the copy must be a faithful and intelligible reproduction, not a general description of the data; where necessary, it includes extracts from documents or databases in which the data appears.
Where a decision about a person was made by an automated system, they are entitled to “meaningful information about the logic involved”. On 27 February 2025, in Dun & Bradstreet Austria (C-203/22), a case about a mobile phone contract refused because of an automated credit score, the Court held that the business need not disclose the algorithm or a mathematical formula, but must explain concisely and intelligibly how the person’s data led to the result, so that they can contest it. A claim of trade secrecy does not remove this obligation; the sensitive information is provided to the supervisory authority or the court, which balances the interests involved.
Excessive requests
Under Article 12(5) of the GDPR, a business may refuse a request that is “manifestly unfounded” or “excessive”, or charge a reasonable fee for it, and the burden of proving this lies on the business. On 19 March 2026, in Brillen Rottler (C-526/24), the Court held that even a first access request can be excessive. The case concerned a person who subscribed to an optician’s newsletter, submitted an access request 13 days later and claimed compensation. The Court held that a request made in order to create, artificially, the grounds for a compensation claim is an abuse, and that such an intention may be inferred from the circumstances: an unsolicited subscription, a short interval, and a pattern of similar requests and claims against many businesses. It also held that an infringement of the right of access in itself gives rise to compensation, but the requester must prove damage actually suffered.
This limit is narrow. On 26 October 2023, in FT (C-307/22), the Court held that a patient is entitled to a free copy of their medical records even where they want it in order to sue the doctor, and that an access request need not state reasons.
Comparison
| Topic | Israeli Privacy Protection Law | GDPR |
|---|---|---|
| Access | Section 13; 30 days; refusal within 21 days | Article 15; one month, extendable by up to two months |
| Correction | Section 14, including notice to those who received the data | Articles 16 and 19 |
| Erasure | Direct mailing (Section 17F) and data received from the European Economic Area | General right, Article 17 |
| Portability, restriction, objection | No general arrangement; objection to direct mailing only | Articles 18, 20, 21 |
| Automated decisions | No specific arrangement | Article 22 and the right to an explanation under Article 15 |
| Fees | NIS 20 (Regulation 6) | First copy free |
| Refusal | Notice on the prescribed form; appeal to the Magistrates’ Court within 30 days; exemplary damages up to NIS 10,000 | Notice within one month, including the right to complain to the supervisory authority and to seek a judicial remedy |
Handling a request within the organisation
The deadlines are short, and most of the time goes into locating the data. A business that knows in advance which systems hold personal data, and who is responsible for each of them, can meet them. In a body required to appoint a privacy protection officer, handling requests from data subjects is one of the officer’s functions under Section 17B2 of the Law (see Privacy Protection Officer under Amendment 13).
