VeilFrame — Screen Share Privacy Support

VeilFrame support

For activation help, include the VeilFrame version and a masked license suffix. Never send sensitive page content, screenshots containing private data, or a complete license key.

Help users verify mask placement before presenting, explain browser-protected pages and cross-origin frame limitations, and troubleshoot activation without requesting sensitive content.

Blur is visual obfuscation, not destructive redaction. Use Solid or Blackout for high-risk information and verify the shared output before presenting.

A checkout return does not grant Pro. Users paste the delivered license key into VeilFrame settings, where the central API validates the extension, product entitlement, and instance.

Chrome blocks extension injection on browser settings, the Chrome Web Store, and other protected surfaces.

Cross-origin frames need their own approved origin.

Closed shadow roots and canvas-rendered data may require an area mask.

Users must visually verify mask placement before sharing or taking a screenshot.