> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/android/redaction.md). # Redaction - [PDF Redaction Library for Android](https://docs.apryse.com/android/redaction/redaction.md): Learn how to redact content from a PDF document with ease. Get started with Redact, a powerful tool for secure information removal. The Apryse Android SDK streamlines secure document processing and se - [Redact](https://docs.apryse.com/android/redaction/redact.md): Learn how to redact PDFs in Android using UI components or APIs with Apryse. Safely remove sensitive content for secure distribution. Explore the redaction process and control options. The Apryse Andr - [Code samples to redact PDFs in Android](https://docs.apryse.com/android/redaction/samples.md): Learn how to redact sensitive content in PDF documents using pdftron.PDF.Redactor. Explore UI samples and features of the SDK in this Android showcase app. Click to view the redaction demo! The Apryse - [APIs to redact PDF content in Android](https://docs.apryse.com/android/redaction/apis.md): Enhance PDF documents with utility classes for redaction in Android using com.pdftron.pdf.Redactor. Learn how to efficiently manage sensitive information. The Apryse Android SDK streamlines secure doc --- # 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.apryse.com/android/redaction.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.