Velora Sources Privacy Policy

What the extension reads

The extension reads the active page only when you choose to preview it. It captures the page title, a cleaned URL, and visible text. In the Chrome Web Store edition, you can also choose to include links, image references, and tables. It does not read cookies or form field values, and skips hidden elements and iframe content. URL credentials, query strings, and fragments are removed from captured links.

Visible text can still contain sensitive or personal information. Review the preview and remove anything you do not want to save. You can also download the reviewed capture, as JSON in the Chrome Web Store edition or text in the website download.

Connecting and saving

When you connect the extension, a one-time code pairs it with Velora on your computer. After you review and confirm a capture, the extension sends it to the selected local project over 127.0.0.1. The extension does not send page captures to Velora servers, advertisers, analytics services, or AI providers.

Saving a source is separate from approving it for an agent or for training. If you later use content in a workflow, the desktop app may send it to the model provider you select. See the Velora Privacy Policy for details about desktop workflows and connected providers.

Existing Proofpage connections

The Chrome Web Store edition also supports existing Proofpage users. You can select Proofpage (legacy) to save reviewed content to your local Proofpage library. In that mode, you can also choose an original image or PDF from your computer or request that Proofpage import a public image or PDF URL. Proofpage contacts the source website for a requested public URL without forwarding browser cookies or credentials. Files can contain embedded metadata.

Permissions and storage

Chrome grants access to the active tab when you request a preview. The extension uses scripting to read that page and asks for optional access to 127.0.0.1 to communicate with your desktop app. It does not continuously monitor your browsing.

Velora connection details are stored in Chrome session storage until the browser closes. A pending pairing code may also be held there while Chrome asks for localhost permission. Existing Proofpage connection details can be retained in local extension storage. Pairing codes expire, and the capture preview is held temporarily in the popup.

Your choices

You can disconnect from the desktop app, revoke the optional localhost permission in Chrome, or remove the extension. Removing the extension removes its stored settings. To remove content already saved, delete the source in your desktop app or delete exported files from your computer.

We do not sell extension data or use it for advertising, credit decisions, or purposes unrelated to this feature. For questions, visit Velora Support.