> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/product-guides/luciq-pii-masking/additional-privacy-control.md).
# Additional Privacy Control
Explore additional privacy controls in Luciq to protect user data. Learn about advanced masking options beyond standard PII masking features.
#### Grayscale screenshot mode
Capturing screenshots in grayscale adds a layer of privacy by reducing visual detail and shrinks file size by roughly 40–60%. Treat as defense-in-depth, not a substitute for masking.
**Android**
```
SessionReplay.setScreenshotQuality(ScreenshotQuality.GREYSCALE)
```
**iOS**
```
SessionReplay.screenshotQualityMode = .greyScale
```
**ReactNative**
```
SessionReplay.setScreenshotQuality(ScreenshotQuality.greyscale);
```
**Flutter**
```
SessionReplay.setScreenshotQualityMode(ScreenshotQualityMode.greyScale);
```
***
#### Secure window handling (Android)
By default the SDK respects FLAG\_SECURE only with a clear understanding of the security implications.
```
// Kotlin
Luciq.Builder(application, token)
.ignoreFlagSecure(true) // Default: false
.build()
```
***
#### Selective user-data transmission
When the users-page feature is disabled (`usersPageEnabled`` ``= false`), only attribute keys are transmitted — not their values — further limiting the PII that leaves the device.
Note: This flags controls collecting of users device info, OS, name and email. but not related to user attributes added by the API
***
#### User consent gating
Session Replay (and related capture) can be gated behind an explicit user-consent check so that nothing is recorded until the user has agreed.
```
if userHasConsented {
SessionReplay.enabled = true
} else {
SessionReplay.enabled = false
}
```
***
---
# 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.luciq.ai/product-guides-and-integrations/product-guides/luciq-pii-masking/additional-privacy-control.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.