Onward sharing
Onward sharing occurs when a recipient makes data available to another party after receiving it. It can involve distributing files, granting access to a workspace, or allowing a service provider to process records. Whether it is allowed depends on the relevant agreements, rights, and legal obligations.
How it works
Identify the downstream party and what it will receive or access. An agreement may distinguish approved processors from independent users, require prior permission, or impose restrictions that continue downstream. It can also address security, purpose, retention, and further transfers.
Data and computational results may receive different treatment. Do not assume that permission to share one automatically covers the other. A clear map of recipients and access paths helps translate the contract into controls.
Why it matters for licensing
Licensing discussions should cover realistic delivery and processing workflows, including cloud services and affiliates. If a recipient’s process requires downstream access, that need should be assessed before data moves. A provider’s own upstream obligations may restrict what it can authorize.
Example
Fictional example: An evaluation partner wants to give a contractor access to the licensed files for labeling. The parties check whether contractor access is allowed and what purpose, security, and deletion requirements must apply before enabling the account.
Limitations and misconceptions
Calling a transfer “internal” does not resolve whether a separate legal entity is covered. Privacy rules can impose additional requirements, including for international transfers. Contract restrictions also need practical access management; a clause alone does not identify every copy.
Questions to ask
- Which people and legal entities will actually receive or access records?
- Are downstream purposes and further transfers permitted?
- How will access, copies, and end-of-term deletion be tracked?