To translate a research data use agreement correctly, identify what dataset is being shared, who provides it, who receives it, what research uses are permitted, and which uses remain prohibited. The most dangerous mistranslation is a fluent sentence that broadens access: may analyse approved data is not permission to publish identifiable records, contact participants or combine datasets for a new commercial project. A restricted dataset access letter should allow every reader to reconstruct the same permissions and restrictions.
This article explains how to translate data use agreements, restricted research-data licences, limited-data-set requests, institutional access approvals, data security annexes and publication conditions across languages. It serves universities, hospitals, public agencies, researchers, privacy officers, translators and international collaborations. A data use agreement can be contractual, institutional or regulatory in context; obligations must be read against the specific signed instrument, applicable privacy law and any ethics or funder approvals.
Begin with the authorised project, dataset version, participating legal entities and signatories. Then follow the data from receipt and storage to analysis, onward transfer, publication, retention and destruction. Preserve every qualifier, including only, solely, unless, subject to approval and no later than. The following case studies are hypothetical and do not replace institutional privacy advice, research ethics review or binding legal requirements in any jurisdiction.
Quick answer: preserve permission boundaries
A sound translation lets the reader answer who may access which data for what purpose, under whose approval, in which environment, with what security safeguards, until when, and with which permitted outputs. The answers should remain the same in both languages. Data protection terms must not be simplified into broader permissions, and institutional roles must not be merged because their names sound similar.
A practical workflow before translating research data agreements
Step 1
Inventory the signed instrument and every annex. Include data dictionaries, schedules of variables, participant information sheets when relevant, access decisions, ethics approvals, security appendices and later written amendments. A shortened translation without operative appendices should be clearly marked partial.
Step 2
Map roles. Distinguish provider, recipient, data controller, processor, principal investigator, project sponsor, repository and authorised user. Not every legal regime uses the same classifications. Use definitions in the document before importing external language.
Step 3
Classify every clause: permission, prohibition, condition, technical procedure, warranty, disclaimer, audit duty or surviving obligation. An approved analysis purpose is not a blanket statement about data ownership, intellectual property or publication permission.
Step 4
Make a data-flow diagram in words. Identify source, transfer channel, storage environment, personnel access, permitted linkage, outputs, onward sharing, retention and deletion. A single translated verb such as send or disclose can change that path.
Step 5
Protect restricted source material while translating. Review confidentiality rules before using online translation systems, subcontractors, cloud documents or email attachments. The translator is part of the information-handling process and may need separate authorisation.
Step 6
Deliver a version-controlled translation and a terminology log for unresolved concepts. Put the language, date, original agreement version and annex coverage on the translated copy. Have legal or privacy specialists review legally consequential provisions without letting the reviewer rewrite the source meaning.
Thirty-six data-use terms and restrictions that must survive translation
1. Data provider
The provider is the entity releasing data under specified conditions; it may be an agency, university, repository, hospital or consortium. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Do not rename the provider as owner if the agreement deliberately avoids saying who holds title or legal control. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A national repository supplies a hospital dataset on behalf of several contributing institutions. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Translate the named legal entity and its exact stated capacity, including who signs and who can grant access. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
2. Data recipient
The recipient is the legal organisation or approved individual authorised to receive or access the covered data. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: A recipient university is not automatically the same as every student or subcontractor working there. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A faculty member moves to another institution while the access authorisation still names the original university. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Identify whether rights attach to the institution, project team, named investigator or specific account. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
3. Principal investigator
The principal investigator may supervise the project and be responsible for approved use, but is not necessarily the contract signatory. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Translating PI as data owner could invent authority to redistribute the records. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A laboratory’s lead scientist signs a study plan, while institutional legal counsel signs the DUA. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Preserve scientific responsibility separately from contractual signing power. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
4. Project title
The authorised research project may be identified by formal title, ethics number, protocol version or grant reference. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Using an informal shorthand can hide whether a new analysis falls outside the approved purpose. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A project on treatment outcomes later proposes a marketing study using the same records. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Keep the original project identifier and scope even if a short reader-friendly label is added. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
5. Purpose limitation
A purpose clause says what data may be used for and can be more restrictive than general research curiosity. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Replacing solely for approved epidemiological analysis with for research changes the scope. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A dataset may be used to estimate regional risk but not to target individual customers. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Preserve the precise verbs, subject population and exclusions. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
6. Dataset identifier
A file package may be named by accession, project number, release date, version and checksum. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Translating a code or confusing the current dataset with an older extract breaks reproducibility. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A repository updates a dataset while an agreement names the previous version. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Copy identifiers exactly and distinguish data edition from agreement edition. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
7. Covered records
The agreement may define specific tables, variables, study years, locations and participant categories. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: A definition of covered data cannot silently expand to all records held by the provider. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: Only two years of hospital admissions and certain variables are approved for release. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Translate the data schedule and negative scope accurately. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
8. Limited data set
Under United States HIPAA terminology, a limited data set has a defined meaning and can still contain protected health information. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Do not translate limited as completely anonymous or universally free to share. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A health research agreement permits a limited set with dates but excludes direct identifiers. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Retain the jurisdictional category and explain the specific restrictions where necessary. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
9. De-identified data
Data may be described as de-identified using a stated procedure or standard; that claim depends on the actual method and context. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Removing names does not automatically make every record anonymous, especially with rare combinations of characteristics. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A small-area dataset includes age, diagnosis and visit dates that could identify an unusual case. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Preserve the source’s anonymisation claim without strengthening it and query the method if missing. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
10. Pseudonymisation
Pseudonymisation can replace direct identifiers with codes while a separate re-identification key exists. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Calling coded data anonymous may understate the continuing privacy obligations. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A research centre receives codes while a hospital retains the key. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Translate who holds the key, what linkages are possible and what access restrictions apply. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
11. Prohibition on re-identification
A recipient may be expressly prohibited from trying to work out the identity of a person represented in the data. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Do not weaken shall not attempt to identify into should normally avoid identifying. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A researcher considers cross-matching public social media with a rare disease dataset. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Preserve the prohibition and its exact covered activities. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
12. No participant contact
Some DUAs bar contacting individuals whose information appears in the dataset. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: A translation that merely says contact discouraged can create an unauthorised recruitment route. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: An analyst wants to email patients based on records supplied for retrospective research. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Keep the absolute or qualified restriction exactly as drafted. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
13. Ethics approval
Research ethics approval, institutional review board review and legal permission to disclose data are related but separate matters. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Do not claim a study’s approval authorises every possible sharing or publication. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: An ethics committee approves a protocol, while the data provider still requires an access agreement. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Maintain the different approval bodies, versions, dates and authorised scope. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
14. Consent conditions
Participant consent may limit use, reuse, data sharing or future contact according to the underlying documents. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Translating consent obtained as unrestricted permission ignores its boundaries. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: Participants consent to one study but do not approve commercial secondary use. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Retain who consented, to which use and under what conditions. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
15. Legal basis
A contract, statutory permission, research exception or consent basis may be cited depending on the legal regime. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: The fact a DUA was signed does not automatically mean every processing activity is lawful. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A European collaborator asks whether the institution has authority to transfer personal data abroad. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Translate the cited basis and leave legal adequacy to competent counsel. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
16. Permitted users
The agreement may restrict access to named investigators, trained personnel or authorised roles. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Member of project team may not cover all interns, vendors or collaborating clinicians. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A statistician requests access but has not completed the provider’s required training. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Preserve eligibility, named lists, access-request steps and approval status. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
17. Access credentials
Technical access may require unique accounts, multifactor authentication, protected workspaces and audit logs. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: A shared password is not equivalent to named individual account authorisation. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A team proposes using one service account for several analysts. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Translate the technical control and identify any exception only when the agreement explicitly permits it. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
18. Storage location
The data may be required to remain on a secure server, approved cloud environment or specified geographic location. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Confusing remote access with physical transfer can conceal cross-border movement. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: An investigator opens a hosted dataset from another country through a browser. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Preserve residency, hosting and access distinctions, including named prohibited locations. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
19. Encryption requirement
Security clauses may require encryption in transit, at rest or during specific transfer methods. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: A sentence requiring encryption during transport must not be interpreted as the only needed security control. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A recipient encrypts emails but stores the downloaded file in a plain shared folder. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Preserve all phases and the exact conditions stated. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
20. Minimum necessary
Some access rules require limiting shared or used fields to what the task needs, according to the governing regime. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Translating this as data must be small loses the functional principle of relevance and proportionality. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: An analysis requires age bands but the investigator asks for full dates of birth. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Translate the decision criterion and its scope rather than inventing a numeric size limit. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
21. Data linkage
Linking a dataset to another source may be permitted, prohibited or subject to separate approval. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Joining records is not always an internal technical step free of contractual consequences. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A cohort database is to be matched with census microdata for new variables. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Keep source definitions and any prior written approval requirement. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
22. Onward disclosure
An agreement may limit transfer to affiliates, subcontractors, other researchers or external processors. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: The verb share must not be treated as unconditional permission to post a file publicly. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A collaborator wants to forward raw records to a partner university. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Name permitted recipients and preserve transfer restrictions or required amendments. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
23. Subcontractor controls
Third-party hosting or analysis may be allowed only when equivalent confidentiality and security duties apply. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Changing may engage an approved processor to may distribute freely removes a condition. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A research centre outsources statistical work to a specialist firm. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Translate the approval chain, contract requirements and continuing responsibility. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
24. Publication conditions
A data provider may require acknowledgement, disclosure control, review for confidentiality or particular attribution. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Prepublication review is not necessarily a right to alter scientific findings; the exact clause matters. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A draft paper contains a small cell count that might reveal a participant. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Keep review scope, timeline, permitted edits and any approval requirement as stated. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
25. Aggregate outputs
An agreement may allow statistical summaries while restricting record-level exports or small-cell disclosures. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Translate may publish aggregated results without converting it to may release underlying data. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A team produces a table of regional rates from confidential individual records. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Preserve output-level restrictions and applicable suppression rules. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
26. Derived data
New variables, models and analyses may have special reuse or ownership rules independent of raw-data access. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: An algorithm trained on restricted records may not be automatically exempt from all agreement conditions. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A recipient creates prediction scores and wants to sell them as a commercial product. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Check definitions of derivative, output, intellectual property and permitted use. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
27. Commercial use
A DUA may exclude commercial exploitation or limit it to specifically approved contexts. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Translating noncommercial research as educational work can be too broad or too narrow. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A university and startup jointly run an approved study with different institutional roles. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Preserve the actual commercial prohibition and named exceptions without inferring legal status from an organisation type. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
28. Security incident
Security incidents, confirmed breaches and suspected unauthorised access may trigger different reporting obligations. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: A suspicion should not become a confirmed breach in translation, but a mandatory alert cannot become optional. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: An analyst loses a device that may have contained a cached protected file. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Translate the trigger, designated contact and timeline exactly. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
29. Breach notification
The DUA may require reporting to a data provider, ethics office, affected individuals or authority depending on the circumstances. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: A clock starting on discovery is different from one starting on confirmation. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: The team learns of suspicious access on Monday and finishes an investigation on Thursday. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Retain trigger, required recipients, notification method and timeframe. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
30. Retention period
Records may be retained only for a specified project duration, fixed period or until defined events occur. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: No longer needed is not interchangeable with a statutory retention deadline. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A project ends in June while a publication audit remains pending. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Translate both the general retention rule and any legal hold or extension exception. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
31. Secure destruction
At expiry, a recipient may need to delete, return or destroy specified copies and backups, sometimes with evidence. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Saying delete the folder may omit required backup or working-copy controls. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A laboratory deletes working files but retained an untracked export on a portable drive. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Preserve the scope of destruction, verification procedure and authorised exceptions. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
32. Audit rights
The provider may retain rights to inspect compliance records or require periodic certification. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: An ordinary quality check is not necessarily a legal right to audit all recipient operations. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A repository requests an annual declaration of authorised use and security controls. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Keep the precise person entitled to request evidence and the limits of access. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
33. Amendment process
A new purpose, recipient, dataset or duration may require written amendment rather than an informal email. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: A researcher cannot assume that discussing a proposal grants permission to use more records. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A protocol revision adds a new geographic region and an external analysis team. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Preserve approval steps and effective date rather than treating requested amendments as active. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
34. Termination
The agreement may end for time expiry, breach, project completion or another specified trigger. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Ending access may not end every confidentiality, retention or reporting duty. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A team loses portal access but still has obligations for previously exported records. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Identify surviving clauses and distinguish termination notice from final compliance completion. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
35. Data quality
The provider may disclaim completeness or specify known missingness, bias and permissible interpretations. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Translating data as validated when the provider describes known gaps distorts research evidence. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A dataset excludes rural clinics and contains variable missing-value rates. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Keep limitations alongside the analysis permissions. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
36. Governing law
The DUA may identify governing law, forum or conflict-resolution process, which can differ from the recipient’s location. Start by establishing whether the source defines this term or uses it in a special statutory or institutional sense. Definitions elsewhere in the agreement may control the sentence.
The practical failure mode: Do not localise a legal reference into the translator’s home law. The target version must not quietly increase permitted access, remove an approval condition or create a stronger privacy assurance than the original contains.
Illustrative situation: A consortium agreement chooses one jurisdiction for disputes while research occurs in several. The example is fictional; its purpose is to show how a plausible linguistic shortcut can change an actual data-handling decision.
Revision and review: Preserve cited law, forum and jurisdictional references, with counsel consulted for legal meaning. Match roles, exceptions, required notifications and time limits back to the signed source. Record open questions instead of inventing a permission that the original never grants.
Eight worked examples from international research projects
1. Coded does not mean anonymous
A hospital sends patient records with names replaced by study IDs. A draft translation says the data are fully anonymous, although the original calls them pseudonymised and prohibits re-identification. The difference matters because a key remains somewhere and rare combinations may still be sensitive. The correct translation preserves the limitation and directs reviewers to the actual data protection arrangement.
To check the translated clause, write one sentence describing the allowed act and one describing the forbidden act. Then identify any required approval, evidence or timing. A reviewer unfamiliar with the source language should arrive at exactly the same access boundary. If they cannot, rewrite the translation without widening the licence.
2. A collaborator becomes a new recipient
Two universities plan joint analysis. Only one is named as data recipient, and a colleague asks to upload the files to the second institution’s workspace. Translate the onward-transfer prohibition exactly. A friendly research relationship does not automatically amend the signed contract. The appropriate process may require a written request, new data use agreement or approval, depending on the document.
To check the translated clause, write one sentence describing the allowed act and one describing the forbidden act. Then identify any required approval, evidence or timing. A reviewer unfamiliar with the source language should arrive at exactly the same access boundary. If they cannot, rewrite the translation without widening the licence.
3. Publication versus raw-data release
A project is permitted to publish aggregate estimates but not individual records or small cells. A conference presenter wants to post a spreadsheet with row-level data for reproducibility. The English phrase may disseminate results does not grant permission for raw-data redistribution. Translate the defined difference and preserve any disclosure review requirement. Reproducibility and privacy must be addressed through authorised mechanisms.
To check the translated clause, write one sentence describing the allowed act and one describing the forbidden act. Then identify any required approval, evidence or timing. A reviewer unfamiliar with the source language should arrive at exactly the same access boundary. If they cannot, rewrite the translation without widening the licence.
4. The misunderstood deadline
An agreement requires incident notice within a specified period after discovery. The translation changes discovery to confirmation, delaying the apparent reporting duty. Record the trigger word as a high-risk expression and review it with the privacy officer. The translator must not calculate a jurisdiction-specific legal deadline that the agreement itself does not supply.
To check the translated clause, write one sentence describing the allowed act and one describing the forbidden act. Then identify any required approval, evidence or timing. A reviewer unfamiliar with the source language should arrive at exactly the same access boundary. If they cannot, rewrite the translation without widening the licence.
5. A secondary use proposal
Researchers approved to study hospital attendance later want to investigate insurance fraud. The new question may be scientifically interesting but falls outside the stated project. A translation that says authorised research broadly would conceal the distinction. Preserve the permitted purpose, project title and the process for amendment or fresh approval.
To check the translated clause, write one sentence describing the allowed act and one describing the forbidden act. Then identify any required approval, evidence or timing. A reviewer unfamiliar with the source language should arrive at exactly the same access boundary. If they cannot, rewrite the translation without widening the licence.
6. Data hosted overseas
A cloud service is physically hosted in one country, researchers log in from another and backups are held elsewhere. The DUA names approved locations. Translate storage, access, transfer and subcontractor processing separately. A sentence stating data never leave the original country may be materially false even when the primary server remains there.
To check the translated clause, write one sentence describing the allowed act and one describing the forbidden act. Then identify any required approval, evidence or timing. A reviewer unfamiliar with the source language should arrive at exactly the same access boundary. If they cannot, rewrite the translation without widening the licence.
7. An expired agreement
A researcher receives an automated message that portal credentials have expired, but the signed DUA also imposes deletion and certification duties. The translated notice should not say all responsibilities have ended. Explain the current access status and point to surviving clauses in the actual agreement. Permissions and obligations need separate timelines.
To check the translated clause, write one sentence describing the allowed act and one describing the forbidden act. Then identify any required approval, evidence or timing. A reviewer unfamiliar with the source language should arrive at exactly the same access boundary. If they cannot, rewrite the translation without widening the licence.
8. The missing annex
A DUA cites Appendix 2 for approved variables and Appendix 3 for output disclosure rules, but only the main agreement was supplied for translation. The translator should not infer content. Label the missing annexes and request them before issuing a complete version. An apparently polished translation can be dangerously incomplete if the operative restrictions sit in attachments.
To check the translated clause, write one sentence describing the allowed act and one describing the forbidden act. Then identify any required approval, evidence or timing. A reviewer unfamiliar with the source language should arrive at exactly the same access boundary. If they cannot, rewrite the translation without widening the licence.
Frequently asked questions
Is a DUA the same as informed consent?
No. A participant’s consent and an institutional agreement can impose different, simultaneous restrictions. When the actual project is consequential, have the provider, institutional research office and relevant privacy specialists confirm the controlling instrument.
Can data called de-identified be published freely?
Not automatically. Inspect the method, applicable law, agreement and any re-identification risk. When the actual project is consequential, have the provider, institutional research office and relevant privacy specialists confirm the controlling instrument.
Does ethics approval replace the contract?
Usually not. Ethics review and data-sharing permission answer different questions. When the actual project is consequential, have the provider, institutional research office and relevant privacy specialists confirm the controlling instrument.
May a researcher share files with a coauthor?
Only if the agreement and applicable approvals allow that recipient and use. When the actual project is consequential, have the provider, institutional research office and relevant privacy specialists confirm the controlling instrument.
What if the recipient changes jobs?
Review whether authorisation belongs to the person, institution or approved project and what transfer procedure applies. When the actual project is consequential, have the provider, institutional research office and relevant privacy specialists confirm the controlling instrument.
Can a translation change a prohibited use into a recommendation?
No. Shall not and should avoid have different force. When the actual project is consequential, have the provider, institutional research office and relevant privacy specialists confirm the controlling instrument.
What about a machine-translation service?
Restricted records should not be uploaded to an unauthorised external service. Use the organisation’s approved handling process. When the actual project is consequential, have the provider, institutional research office and relevant privacy specialists confirm the controlling instrument.
Is a limited data set anonymous?
Under HIPAA, the category is defined separately from fully de-identified data and may include protected health information. When the actual project is consequential, have the provider, institutional research office and relevant privacy specialists confirm the controlling instrument.
What if the agreement names another country’s law?
Preserve the citation and obtain qualified jurisdictional advice when a legal consequence turns on it. When the actual project is consequential, have the provider, institutional research office and relevant privacy specialists confirm the controlling instrument.
How do I detect an incomplete packet?
Compare clause references and annex lists against the files actually supplied. When the actual project is consequential, have the provider, institutional research office and relevant privacy specialists confirm the controlling instrument.
Final restricted-data translation audit
Before distribution, compare legal entity names, investigator roles, dataset IDs, project scope, definitions, permitted users, security controls, storage location, cross-border access, re-identification and contact prohibitions, onward transfers, publication and disclosure conditions, incident reporting triggers, dates, retention, destruction, amendment, termination and governing-law references. Check that every annex is present and clearly named. Maintain source-language versions and a secure review trail. A good translation should not let a recipient do more, or less, than the original authorised document actually allows.
Official guidance and related language learning
US Health and Human Services guidance illustrates why data use agreements specify permitted purposes, parties, restrictions and security. Its HIPAA materials also distinguish limited data sets from other categories of protected and de-identified information. These sources are jurisdiction-specific examples and not universal rules. This guide provides independent educational translation examples, not a model legal agreement.
Sources: HHS: CMS Data Disclosures and DUAs; HHS: HIPAA and Research; HHS: Common DUA Structure. Continue through Master Art of Translation, the Vocabulary Learning Hub and How English Works: Translation and Meaning Across Languages for their established general learning frameworks.