> For the complete documentation index, see [llms.txt](https://docs.fraudcheck.co.za/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fraudcheck.co.za/product/overview/how-it-works/consent.md). # Consent and permissible use What you must have before running a check, and what Fraudcheck records. Fraudcheck processes personal information, so consent is a requirement of almost every check, not an afterthought. ## Your responsibilities * **Obtain consent.** Before running a check on a person, obtain their consent, and confirm on each request that you have it. Each product page says whether consent is required. * **Keep the proof.** You are responsible for obtaining and retaining proof of consent in line with the Protection of Personal Information Act (POPIA). Fraudcheck records that you confirmed consent; it does not capture the consent itself. * **Declare a permitted purpose where required.** Some checks, such as credit checks, may only be run for a permitted purpose, which you declare on each request. See [Credit checks and prescribed purposes](https://developer.fraudcheck.co.za/guides/credit-checks-and-prescribed-purposes). * **Act on the result yourself.** Statutory duties, such as refusing a self-excluded gambler or deciding whether a purpose is permissible, stay with you. We explain the rules and our controls; we do not give legal advice or decide permissibility for you. ## What we record Every check has a transaction reference, which is your audit reference. [Cost centres](/product/administration/administration/account/cost-centres.md) let you reconstruct which branch, operator or sub-client ran each check. Keep your consent records together with transaction references so you can show lawful processing when asked. ## Further reading * [Fraudcheck Privacy Policy](https://www.fraudcheck.co.za/privacy/) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.fraudcheck.co.za/product/overview/how-it-works/consent.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.