Privacy policy

Account information used to authenticate you, such as your name, email address, and provider account identifier.

Project content you choose to send to ShareView, including prototype artifacts, HTML version history, comments, replies, and project membership information.

Recordings, screenshots, and page activity you save with the ShareView Capture extension, as described under ShareView Capture.

Connection and security metadata needed to operate the plugin, CLI, MCP server, and extension, such as authorization grants, token identifiers, scopes, timestamps, request status, and diagnostic information.

Feedback you intentionally submit through the ShareView CLI.

ShareView Capture is a Chrome extension. It records a browser tab or takes a screenshot, then saves that capture to a workspace and project you choose. It does not collect from a page until you start a recording or screenshot, and it does not read your other tabs.

A saved recording includes the video of that tab and, if you selected a microphone, your voice. It also includes the page address and title, pages opened during that take, the browser and window size, console messages, network requests the page made, clicks, and text typed into fields other than passwords. Authorization, cookie, and similar headers are removed before upload. Shorter request and response bodies that contain a password, token, or similar secret are redacted.

A saved screenshot is the image of the visible tab, including any crop or notes you add, plus the title and description you enter. The recording and the screenshot include whatever was visible on the tab you chose.

On this device the extension stores your sign-in (server address, access token, name, and email), your last workspace and project, the microphone you picked, and temporary state for a capture in progress. Signing out removes the session. Discarding a capture removes it on this device and does not upload it.

Anyone who can open the artifact can see the saved capture, including the page activity stored with a recording. We use this information only to save the capture you started and to show it in that project. We do not sell it, and we do not use it for advertising, credit, lending, or purposes unrelated to ShareView.

We use this information to authenticate users, enforce project access, store and deliver prototypes and captures, synchronize artifacts, support review comments, maintain version history, prevent abuse, diagnose failures, and improve ShareView.

We do not sell personal information, use private project content to advertise to you, or use it to determine creditworthiness or for lending.

The CLI uses browser-approved device authorization and stores its credential in the operating system credential store when available, or in a protected local configuration artifact when explicitly configured. ShareView does not print access tokens in normal CLI output.

ShareView Capture uses the same device sign-in. Its access token stays in the extension on this device and is sent only to ShareView.

The MCP server uses OAuth authorization with scoped permissions. Read and write access are requested separately, and authorization can be revoked through the connected account authorization controls.

We may use infrastructure, identity, storage, and monitoring providers to operate ShareView. They process information only as needed to provide those services.

We may disclose information when required by law, to protect users and the service, or as part of a business transaction subject to appropriate safeguards.

We retain account, project, and authorization information for as long as needed to provide the service, meet security and legal requirements, and resolve disputes. Retention periods may vary by data type.

Project owners can remove project artifacts through ShareView. You may contact us to request access, correction, or deletion of personal information, subject to legal and operational requirements.

We use reasonable technical and organizational safeguards, including authenticated access, scoped authorization, encrypted transport, and access checks for project operations. No system can guarantee absolute security.

Information may be processed in countries where ShareView or its providers operate. Depending on your location, you may have rights to access, correct, delete, restrict, or object to processing of your personal information.

We may update this policy as ShareView changes. The effective date on this page will be updated when revisions are published.