List Documented Data Handoffs
who_gets_your_data_handoffsList documented data handoffs in Who Gets Your Data, a MORVS pilot register: edges from a source organisation and product, through a data type, to a recipient, each from one primary document (an FTC complaint or order, a Federal Register notice, a court opinion or order). Optional filters: data_type (a substring of the data type in the document's words), legal_status (a status key the register carries, such as allegation_in_complaint, finding, order_terms or request_count; matched against the row's own status and its settlement and remedy statuses, with the match shown), recipient (a substring of the recipient as worded or of a named recipient organisation) and year (the primary document's year, a year the register carries). Up to 25 edges in published order, with the full count and the counts by the rows' own legal status. Each handoff gives the source organisations, product and brands, the data type in the document's words, the recipient exactly as worded (named, or the document's own recipient class), the conduct period as worded, the verbatim quote, the document's type, issuer, date and URL, and a settlement, remedy, current status or opt-out only where a document states one. Each handoff carries its primary document's own legal status with the register's label exactly as published (a court's finding, an allegation in a complaint, a settlement with or without an admission, an order's terms, or a count of requests): an allegation is not a finding, a request is not a disclosure, and old conduct is not current practice. An empty result returns the register's absence note: no documented record in this corpus, which says nothing about what a product or company does now. The three tables (handoffs, broker registry answers, legal duties) hold different kinds of evidence and are never added together, scored or ranked; no answer gives a total across them. A pilot: a small, hand-checked set of documented handoffs, the brokers' own registry answers and one legal-duty exhibit, in three separate tables; it is not a census of data sharing. The answer carries the pilot note, lane note, coverage line, as-of date, file dates, legal-status labels, the register's rules, its licence and the source page on morvs.ai. Organisations, companies, agencies and governments only: no individual is named, and there is no bank or personal-report lookup.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | Optional year of the primary document (YYYY), a year the register carries; all years when omitted. | |
| data_type | No | Optional case-insensitive substring of the data type in the document's words, for example location or viewing history; at most 80 characters. | |
| recipient | No | Optional case-insensitive substring of the recipient as the document words it, or of a named recipient organisation, for example Verisk. | |
| legal_status | No | Optional legal-status key the register carries, for example allegation_in_complaint, finding, order_terms or request_count. |