Velo
Sign inStart a review

Discuss the page while you are on it.

Velo lets you capture website context, pin a note to the place it concerns, and continue the discussion in one review. Feedback stays connected to the page instead of drifting into a separate screenshot or message thread.

The extension is not available to install yet. Chrome, Firefox, and Safari releases are moving through their remaining review steps. Until then, website feedback runs from Velo.

A browser window on fieldnotes.example with the Velo extension active. One pin has landed on the heading, and the extension popup is open under the toolbar.

fieldnotes.exampleVelo extension active

The extension popup, open over the page. Signed in as Ada. Project Field Notes, document Field Notes homepage. Commenting is on for fieldnotes.example, and the primary action opens the document in Velo.

IllustrationThe extension popup open over a captured page, one pin landed on the heading.

Three browsers. One honest status.

  • Chrome

    Pending review

    Pending review: legal and release approval before Chrome Web Store submission.

  • Firefox

    Pending review

    Pending review: legal and release approval before Firefox Add-ons submission.

  • Safari

    Not yet signed

    Built but not yet signed or notarized; public distribution is pending signing, notarization, legal approval and hosted sign-in verification.

The conversation begins with the page in view.

  1. Choose

    Open the site you want to discuss and choose the Velo project and document.

  2. Point

    Select an eligible part of the page and write the note it needs.

  3. Discuss

    Read replies and decisions beside the website context that started the thread.

What the extension asks for—and why.

Browser permissions should describe a boundary, not hide it. These are the current permission paths in the extension.

Active tab and site access
Velo adds its feedback layer only after you choose a site and approve access. On that site, it can use eligible page text and structure to anchor a note, then sends the note, anchor, origin, and route to Velo. Form values, passwords, editable text, cookies, and page storage are outside that read boundary.
Storage and session
Velo keeps sign-in tokens in browser session storage and your project and document choices in local storage. The browser keeps the sites you approve in its own permissions store, so that access can be revoked in browser settings.
Identity and auth callback
Chrome and Firefox use the browser sign-in flow to connect your Velo account. Safari returns through Velo's auth callback after opening a native authentication session; the native app does not receive the access or refresh tokens.

Review the boundary before the release.

The security page sets out the boundaries Velo keeps, and the privacy policy describes how Velo handles extension data. Questions about access, account connection, or the upcoming release can go directly to support.