> 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/ios/redaction.md). # Redaction - [PDF Redaction Library for iOS](https://docs.apryse.com/ios/redaction/redaction.md): Learn how to redact content from a PDF document with ease. Get started with simple steps to redact confidential information securely. Try it now! The Apryse iOS SDK streamlines secure document process - [Redact](https://docs.apryse.com/ios/redaction/redact.md): Redact PDFs with Apryse: Learn how to securely remove sensitive content from documents using UI components or APIs. Control redaction style and ensure complete data removal for safe distribution. Expl - [Code samples to redact PDFs on iOS](https://docs.apryse.com/ios/redaction/samples.md): Learn how to redact sensitive content in PDF documents using pdftron.PDF.Redactor. Explore UI samples on iOS showcasing SDK features. Try the redaction demo now! The Apryse iOS SDK streamlines secure - [APIs to redact PDF content on iOS](https://docs.apryse.com/ios/redaction/apis.md): Discover utility classes for redacting PDF documents in iOS (Objective-C/Swift) with PTRedactor. Enhance document security and privacy. The Apryse iOS SDK streamlines secure document processing and se --- # 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/ios/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.