[Previous] [Next] [Up] [Title]

5. Compliance test (3) - `Adequate safeguards'


5.1. Authorisation of particular transfers with `adequate safeguards'

In addition to these mandatory exceptions, A26(2) now provides[34] that
'... a Member State may authorize a transfer or a set of transfers of personal data to a third country which does not ensure an adequate level of protection ... where the controller adduces adequate safeguards with respect to the protection of the privacy the fundamental rights and freedoms of individuals and as regards the exercise of the corresponding rights; such safeguards may in particular result from appropriate contractual clauses'.
This last clause seems directed, for example, to a situation where a particular company in a third country provides strong contractual guarantees of privacy to its customers, even where there are no enforceable industry codes and the country does not have overall adequate protection. What might otherwise constitute `adequate safeguards' is not explained.

A26(2) suggests that contractual provisions between a particular company and its clients, as opposed to a sectoral code, cannot amount to an `adequate level of protection' for A25 purposes. It also reinforces the view that an `adequate level of protection' must be found to exist at least at a sectoral level within a jurisdiction, and cannot be found merely at the level of the operations of a particular company, because the alternative view would make A26(2) redundant. This is not, however, free from doubt[35].

The A29 Working Party in `First Orientations' says that the contractual solutions envisaged by A26(2):

have inherent problems, such as the difficulty of a data subject enforcing his rights under a contract to which he is not himself a party ... and are therefore appropriate only in certain specific and probably relatively rare circumstances.

National legislation is required

As with the A26(1) exceptions to A25, A26(2) `adequate safeguards' cannot be relied upon unless and until they are embodied in the national legislation of the fifteen EU member states. Unlike the A26(1) mandatory exceptions, it is completely up to the national legislatures whether they recognise any forms of `adequate safeguards'.

The only implementing law to date, that of Greece, does not recognise any contractual or other forms of adequate safeguards.

5.2. The content of 'adequate safeguards'

The Working Party intends to issue in future some principles as to when `adequate safeguards' might be found, but stresses that `adequate' is used in both A25 and A26(2) and that the substance of its future work on A26(2) is likely to draw significantly on the ideas in `First Orientations', given that both deal with a test of `adequacy'.

If this approach is followed, then contractual `adequate safeguards' will have to provide all of the six `core' principles and equivalents of the three procedural protections that are necessary for `adequate protection' (as discussed above).

5.3. Possible types of 'adequate safeguards'

Data subjects' contracts with suppliers or recipients

The type of contract that is most likely to provide 'adequate safeguards' is that between the individual concerned and either the European data exporter or the third country data importer, or (in some cases) both.

The European exporter is able to give the data subject a wide range of contractual rights and guarantees, including guarantees of observance of the six core principles by both exporter and importer. The contract can give the data subject a right to damages or other remedies for breach. In order to make such contractual remedies meaningful, the law of the contract can be made the law of the country of domicile of the data subject (if different from the domicile of the exporter), and ancillary rights such as payment of all legal costs in the event of a successful action and limitation of awards of costs against (so as to simulate the situation of complaints to a data protection authority). In some cases, it may be possible for the exporter to give the data subject rights to pursue remedies against the exporter under a European data protection law. Whichever way it is done, it should be possible for the exporter to give the data subject meaningful contractual rights covering almost all of the Working Party's requirements for `adequacy', with the possible exception of the institutional mechanism to investigate complaints (which could come from an industry self-regulatory scheme).

Similarly, the data importer could contract with the individual concerned to provide the same rights as discussed above. This may be likely to occur when the individual resides in the same country as the importer.

The crucial point is that any such contracts would have to cover all of the content required for `adequacy'. Neither the Directive, not the Working Party', contemplate contracts being used as a device by which individuals can surrender their rights under the Directive. Their can be no `contracting out' of data protection obligations under the Directive.

Exporter / importer contracts

Can private contracts between European data exporters and third country data importers (as distinct from their contracts with data subjects) constitute 'adequate safeguards'? The US government pushed for maximum recognition for supplier-recipient contracts[36], and the French data protection authority, CNIL, has allowed a number of transfers from France to countries then without data protection laws (Italy and Belgium) on condition that such contracts were entered into[37]. The International Chamber of Commerce (ICC) was also promoting such an approach and prepared a model contract[38]. A25 makes no mention of contractual clauses at all, and it seems unlikely that contractual clauses could constitute 'adequate protection', even on a sectoral basis where they are adopted by an industry. A26(2) does not clarify whether its mention of 'contractual clauses' includes supplier-recipient contracts. As there would be no privity of contract with the data subject, and therefore no legal rights enforceable by the data subject, it is doubtful that such contracts could constitute 'adequate safeguards' for A26(2) purposes. These are the contracts that the Working Party sees as having `inherent problems'.

Reidenberg, analysing the problems faced by the US private sector in complying with the EU and other privacy standards, identifies weaknesses in a purely contractual solution[39]:

Individuals may be unable to enforce effectively their protections for the treatment of personal information due to a lack of privity, the need to obtain jurisdiction in a foreign country, or the difficulty establishing foreign law in a local forum. In addition, the terms of the contract are negotiated by the companies themselves with the input of data protection authorities. The exporting company acts, in effect, as the agent for the individual, though the individuals have no direct representation during the contract negotiations.
Reidenberg now sees supplier-recipient contracts as only of much value where they are the by-product of an enforceable law in the exporting country, as in the Hong Kong and Québec data export laws discussed below.

Voluntary codes of conduct and industry technical `standards'

Voluntary codes of conduct are much more likely to provide `adequate safeguards' for A26(2) purposes than `adequate protection' under A25, since adequacy can be judged in relation to whether the importing party does actually apply the Code. The downside is that this will involve all the procedural requirements for a `one off' approval in each case, as discussed below.

The same may be said for data protection implementation as a technical standard with accreditation schemes.

In both cases, all of the problems of whether the scheme or standard meets all of the content and procedural requirements of `adequacy' will apply. It seems more likely that both voluntary codes and technical standards could form part, but only part, of `adequate safeguards'.

5.4. Procedures to determine `adequate safeguards'

At the Member State level

In the first place it is up the law of the Member State to determine how it will grant an export authorisation, but it is clear from A 26(2) that authorisations must be on a `one-off' basis (as the controller is required to `adduce adequate safeguards'), not by some blanket legislative provision. The laws of each Member State are likely to differ in these procedures. It seems that the EU-based `controller' would have to be the applicant for authorisation, and there would need to be a separate application in relation to each EU country from which data is to be exported.

The process is therefore not under the control of the company or government department in the importing country, but is one that could be fragmented into applications by every organisation in every EU country from whom the importer wishes to obtain data.

At the EU level
The Member State must inform the Commission and the other Member States of 'authorisations granted' under A26(2) (A26(3))[40]. If another Member State or the Commission objects to the authorisation, the Commission is required to take `appropriate measures', after referring the matter to the Committee in accordance with A31(2) (A26(3)). Such objection would have to be lodged while the data export is still taking place, but this may easily occur in relation to any ongoing export relationships.

All Member States must then comply with the Commission's decision, including decisions that certain contractual clauses or other relationships do or do not offer 'adequate safeguards' (A26(4)).

Conclusion - Is it safe to rely on `adequate safeguards'?

It appears, therefore, that the process for obtaining authorisations on the basis of adequate safeguards' is one likely to be uncertain, complex, time consuming and costly.

Bennett, writing from a Canadian perspective, is sceptical about the extent to which data users can rely on A26[41]:

Clearly, there is sufficient latitude in the directive for North American data users to convince their European counterparts that a combination of contracts and 'professional rules' (ie codes of practice) and security measures affords 'adequate' data protection. But this does anticipate a series of case-by-case battles, and favoured treatment for the larger multinationals

[34] Previous versions of the Directive used the expression `sufficient guarantees' instead of `adequate safeguards'. In some of my earlier papers on this subject I have not reflected this terminological change.

[35] Reidenberg op cit seems to assume that `adequate protection' can be found in `the specific circumstances of each data transfer on a case-by-case basis'.

[36] TDR, Sept/Oct 1991, p37

[37] 65 ALJ 560

[38] Privacy Laws and Business, October 1991, p6

[39] J Reidenberg 'Setting standard for fair information practices in the US private sector', (1995) Iowa Law Review, Vol 80 No 3 497 at 546

[40] In contrast with 'its proposal to grant authorization' as the 1992 Draft required

[41] Colin Bennett `Canada under the gaze of the European Sphinx', Privacy Files, October 1995, Vol 1 No 1, p14 that can afford to fight for their interests.


[Previous] [Next] [Up] [Title]