VeilFrame — Screen Share Privacy Privacy
VeilFrame processes webpage layout locally to position visual masks. It does not capture or transmit the sensitive content being hidden.
Only the extension identifier, license key, locally generated instance name, and server-issued instance ID are sent to CodingFrontend in POST JSON bodies.
CodingFrontend owns checkout and payment-provider integration. The extension never handles card data or calls checkout directly.
No analytics, advertising, tracking pixels, hosted AI, or page-content telemetry is included.
Screenshots or screen-share video
Page HTML or text
Form values or keystrokes
Cookies, browsing history, clipboard, camera, microphone, or location
Analytics or advertising identifiers
UI preferences and approved site origins
Mask selectors, metadata fingerprints, styles, path scopes, and rectangle geometry
Selected local privacy profiles
Anonymous local installation label ID, license key, server-issued instance ID, validation timestamps, and pending deactivation
Licensing
For Pro activation, the license key and a user-readable browser instance name are sent over HTTPS to CodingFrontend and Dodo Payments. The CodingFrontend database stores a keyed hash of the license key, the Dodo instance ID, product association, and validation timestamps—not the raw key.
Payments
Checkout is hosted by Dodo Payments. CodingFrontend never embeds payment credentials in the extension and does not treat the checkout return page as proof of purchase.
Contact
Questions can be sent through the CodingFrontend contact page.