CLEAR BOUNDARIES. BETTER EXPECTATIONS.
Keep the source.
Share the experience.
Source-private delivery-not a promise that visible work cannot be copied.
What the visitor receives
The Framevault viewer interface, rendered images from a remote Chromium browser, and limited interaction messages. The uploaded HTML, JavaScript, CSS and asset files are not served as a downloadable website through that viewer.
A public URL does not become a private website
A URL frame runs a public website in the remote browser. The original website and its publicly available source remain reachable at their original addresses. Frame access controls apply to the Framevault link, not the upstream host. Use an uploaded build if your aim is to avoid publishing that build on a public website.
What remains possible
Screenshots, recordings, transcription and reproducing visible behavior remain possible. This is not DRM or a guarantee against reverse engineering. Anything displayed on screen can be captured.
Who may access an upload
The service operator controls the infrastructure and can manage uploads. Use a viewer password or temporary one-time password for restricted frames and share it separately. Availability windows and session limits give each review a defined scope. Source-private delivery is not end-to-end encryption against the operator.
Runtime boundaries
The renderer uses sandboxed Chromium with a deny-by-default network proxy and a limited input protocol. Production must pass the browser sandbox deployment checks. These controls do not substitute for audited multi-tenant isolation, patching, resource controls and operational security.
Who can see viewing activity
Frame owners can review their frame’s viewing activity. Administrators have broader operational oversight. Access times, duration and available IP or country information are activity records, not proof of a visitor’s identity. Understand preview analytics.
Private previews stay out of search
Framevault’s public product pages are indexable. Dashboards and remote-viewer pages use noindex. Uploaded projects and URL frames are excluded from the public sitemap; public preview metadata is generic and does not expose the uploaded build.