Mask PII & Sensitive Content

Why This Matters

Under GDPR / CCPA you are the data-controller.
UXCam records screens so you can debug and improve UX—but it should never receive raw Personally Identifiable Information (PII) such as:

• passwords • access tokens
• credit-card or IBAN numbers
• government IDs • phone numbers • e-mail addresses
• faces or documents shown in an OCR/KYC flow

The SDK lets you mask or blur that content on the device, before the video is encoded, so nothing sensitive ever leaves the user’s phone.

Out of The Box Occlusions:

• Android EditText with android:inputType="textPassword" or
  InputType.TYPE_TEXT_VARIATION_PASSWORD is auto-occluded.
• Jetpack Compose does not auto-occlude—use the KTX helper below.

Identify What Needs To Be Hidden

Run the app once with full UXCam recording enabled, and go through all user flows in your app. Then answer:

ℹ️

Gesture capture: Overlays and blurs can keep or hide touch dots. If the user might type a password, disable gesture capture too.

Pick an SDK helper

All helpers share two powerful parameters:

screens(List<String> screenNames)     // limit to certain screens
excludeMentionedScreens(boolean)      // treat list as allow-list (false) or deny-list (true)

Step-by-step examples

Each snippet is self-contained—copy it into onCreate()of yourApplication or the target Activity.

Hide one payment screen completely

// 1) Build an overlay that hides touches too
UXCamOverlay payOverlay = new UXCamOverlay.Builder()
        .screens(Collections.singletonList("PaymentActivity"))
        .withoutGesture(true)
        .build();

// 2) Apply it
UXCam.applyOcclusion(payOverlay);

Effect: Every frame captured inside PaymentActivity is replaced by a red plate.
Touches are suppressed, guarding against key-logging.

Blur everything except Settings

UXCamBlur globalBlur = new UXCamBlur.Builder()
        .excludeMentionedScreens(true)           // treat list below as “allow video”
        .screens(Collections.singletonList("SettingsActivity"))
        .blurRadius(12)                          // medium blur
        .build();

UXCam.applyOcclusion(globalBlur);

Effect: All screens are blurred, but SettingsActivity remains crystal-clear—ideal when only one screen is non-sensitive.

Occlude all text fields on Checkout + Login

UXCamOccludeAllTextFields hideText = new UXCamOccludeAllTextFields.Builder()
        .screens(Arrays.asList("CheckoutActivity", "LoginActivity"))
        .build();

UXCam.applyOcclusion(hideText);

Effect: Every EditText (even future ones) on the listed screens is boxed—no extra code per field.

Mask a single EditText

EditText cardInput = findViewById(R.id.cardNumberInput);
UXCam.occludeSensitiveView(cardInput);

Effect: Only the card box is hidden; the rest of the screen is visible, so you can still diagnose flow problems.

Apply occlusions automatically at startup

Put multiple rules in one list and pass them to the initial configuration:

UXConfig config = new UXConfig.Builder(BuildConfig.UXCAM_KEY)
        .occlusions(Arrays.asList(globalBlur, hideText))  // from examples above
        .build();

UXCam.startWithConfiguration(config);

Jetpack Compose Quick-Start

For a more in depth breakdown of occlusion in Jetpack Compose, see here.

1. Add the Kotlin extensions:

   Kotlin

   implementation("com.uxcam:uxcam-ktx:1.+")

2. Hide a Composable:

   Kotlin

   @Composable
   fun SecureField(password: String) {
       val view = LocalView.current
   
       TextField(
           value = password,
           onValueChange = { /*…*/ },
           modifier = Modifier.onGloballyPositioned { pos ->
               UXCamKt.occludeSensitiveComposable(
                   identifier = "pwdBox",
                   view = view,
                   coordinates = pos          // position on screen
               )
           }
       )
   }

The identifier must be unique per screen;isInDialog=true if that composable sits inside a Dialog.

Dashboard-only Rules (No Code)

Prefer a zero-code workflow?
Open App Settings → Video Recording Privacy on the UXCam Dashboard:

• Blur / occlude all screens in one click.
• Add screen-specific rules (e.g., blur Checkout, hide Login).
• Toggle “Record gestures on blurred screens” if needed.

Dashboard rules override SDK calls in this order:

1. Screen-specific overlay (dashboard)
2. Screen-specific blur (dashboard)
3. Global overlay / blur (dashboard)
4. Screen-specific overlay / blur (SDK)
5. Global overlay / blur (SDK)

Verify: replay a test session to confirm every PII element is masked or blurred before pushing to production.