O2.13.1Named third-party recipient disclosuredesignresearch

Users need to know which specific third parties receive data, not a generic category

Aliases: named third-party disclosure · recipient transparency · recipient-level disclosure

What it is

Named third-party recipient disclosure identifies the recognizable organization or service receiving each data class, its role, purpose, and whether it can determine further use. “We may share with trusted partners” supplies only a category and evaluation; it does not let someone identify a flow or apply experience with a particular organization.

Why it happens

Analytics, cloud, support, advertising, and payment can branch behind one interface. Category-only disclosure merges organizations with different powers, reputations, and boundaries and leaves users unable to connect network domains, brands, and legal entities. Naming turns abstract sharing into an inspectable edge and forces internal alignment with actual integration.

Studying it

Trigger features in test accounts and ask who receives which data, whether each party processes on instruction or for an independent purpose, and whom the participant would question. Reconcile answers with domains, server transfers, vendor inventory, and contractual role. Recognizing a logo alone does not establish understanding of data, purpose, or control.

Where it stops holding

When recipients are numerous or dynamically selected, the overview can aggregate by role but should expand to current entities. Security, litigation, or worker privacy may limit contact-level detail without hiding organization and role. Brand, parent, and contracting entity can differ; support both recognition and legal traceability.

Applying it

  • Record recognizable name, legal entity, domain/system, role, data class, purpose, and first/recent date for every transfer.
  • Deep-link from a feature's explanation to its recipients and then to their privacy information and available controls.
  • Distinguish processor, joint determination, independent use, and required disclosure with plain consequences rather than labels alone.
  • Reconcile domains, server destinations, vendor ledger, and disclosure entries; block any unnamed real recipient.

Related

  • Same group: O2.13.2 Data brokers and final-user traceability · O2.13.3 Dynamic disclosure updates · O2.13.4 Sharing clauses in bundled terms
  • Adjacent: O1.08 Contextual integrity · O2.05 Tracking transparency
  • Search terms: named third-party disclosure · recipient transparency · vendor data flow

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/O2.13.1