> For the complete documentation index, see [llms.txt](https://docs.onefootballclub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onefootballclub.com/7-the-network/7.2-privacy-data-governance-and-compliance.md). # 7.2 Privacy, data governance and compliance The network is built on privacy as a condition, not an afterthought. Consent is explicit, permissions are scoped, and fans can manage or revoke access from their own account. Sensitive personal data remains off-chain. What can be written on-chain are proofs that an action happened, consent was given, or a credential is valid, rather than the underlying personal data itself. Partners do not receive unrestricted copies of a fan’s record. They receive permissioned Data Views: scoped slices of context the fan has agreed to share. This allows clubs, brands, and platforms to understand relevant fan behaviour without exposing the full underlying identity or activity history. The cohort structure extends this principle across the network. Fan reputation can travel between experiences, while the activity beneath it remains protected and aggregated. Platforms can contribute to and benefit from the shared fan graph without giving up their own first-party data. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.onefootballclub.com/7-the-network/7.2-privacy-data-governance-and-compliance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.