RedactShot

Review privacy risks before creating a redacted screenshot.

RedactShot proposes sensitive regions based on the sharing destination, shows a numbered preview, and requires a separate reviewed apply action. It never asks an image model to fabricate a “redacted” result. The final PNG is rendered locally by overwriting pixels with solid masks, flattening alpha data, applying safe orientation, and stripping metadata.

Destination-aware checks

Choose public social media, customer support, coworker, bug report, AI assistant, or general external sharing. The preview can identify names, email addresses, phones, addresses, account/payment data, authentication tokens, API keys, customer details, browser tabs, notifications, profile photos, internal URLs, organization names, and other contextual risks.

Mandatory two-run workflow

1. Run action: preview and inspect every numbered region.
2. Copy input_sha256 into expected_input_sha256.
3. Copy the signed preview_token into the apply run.
4. Copy regions into confirmed_regions.
5. If anything is wrong or missing, create a new preview with clearer guidance.
6. Otherwise run action: apply with the exact returned regions and confirmation: APPLY REDACTIONS within one hour.

Apply never runs detection again. It verifies that the normalized image still matches the reviewed SHA-256 digest and that confirmed_regions exactly match the plan bound into the signed preview token, then masks that reviewed plan. Automatic detection can miss context-sensitive data, so do not share the result without a final human inspection.

Billing

A successful preview costs $0.60005: the $0.00005 apify-actor-start event plus $0.60 for redaction-preview-created. A successful apply costs $0.10005: the start event plus $0.10 for redacted-image-created. The complete successful two-run workflow costs $0.70010. Result events are captured only after their artifacts exist. Failed validation or provider steps skip the result event, but the Actor-start charge can still apply. The synthetic preview input is billed like any other run.

Privacy and limits

PNG, JPEG, and WebP; one image per run; up to 12 MB, 8,192 pixels per side, and 20 megapixels. Console uploads are read inside this limited Actor with its scoped storage access. Direct inline data URLs should stay at or below 6 MB of raw image bytes because Apify run-input requests have a smaller limit than uploaded or remote files. Preview content is processed by Dravara, LLC's private service and the OpenAI API using store: false; applicable provider abuse-monitoring retention may still apply. Apply is deterministic and local. Apify retains run input/output under the runner's settings.

Do not use RedactShot as the sole control for regulated or legally mandated redaction. Support: support@dravarahq.com