EvidenceSheet

Art.48 Transfers or disclosures not authorised by Union law

A judgment of a court or tribunal, or a decision of an administrative authority, of a third country requiring a controller or processor to transfer or disclose personal data may be recognised or enforceable only if it is based on an international agreement in force between the requesting third country and the Union or a Member State, such as a mutual legal assistance treaty, without prejudice to the other grounds for transfer in Chapter V. In practice the controller or processor must not treat a foreign order as being by itself a lawful ground to hand over personal data, and must route such demands through the applicable mutual legal assistance route or another Chapter V ground before disclosing.

Source: GDPR, Art.48. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open GDPR in the compliance library.

Many articles apply only where their condition is met (a data protection officer under Article 37, an impact assessment under Article 35, a representative under Article 27); the condition is in each statement.

5
artefacts
0
held by a system
3
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Evidence that each disclosure was traced to an international agreement in force or to another Chapter V ground, and not to the foreign order alone · Vendor register / contract repository
  • Processor contract terms requiring notification to the controller of any third country demand and requiring the processor to challenge or defer it where lawful · Regulator portal / correspondence
  • A transparency report or equivalent record of demands received and responses given, where publication is permitted · Document repository

governing documentDocuments that govern the control

  • A documented procedure for receiving and handling third country law enforcement, regulatory and court demands for personal data, requiring legal review before any disclosure · Policy repository / GRC workspace
  • The register of such demands received, showing the requesting authority, what was sought, the legal basis assessed, and what was disclosed or refused · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

Art.47 Binding corporate rules · Art.49 Derogations for specific situations