Privacy Policy

Data Waypoint handles

When you create an Annotation, Waypoint processes the annotated page URL, including its path, query, and fragment; the Annotation text you write; and any visual changes you select.

Waypoint also records context for the selected element. This may include its text, tag, classes, stable attributes used by its selector, computed styles, dimensions and position, viewport size, parent context, selector, available component or source-file identity, and the click or pin offset used to place the Annotation.

If you choose to include them, Waypoint also handles captured screenshots and image attachments. Preferences, enabled sites, Queue state, synchronization state, and retained lifecycle history are stored so the extension can preserve your workflow.

Where data is stored and sent

The browser extension stores Annotations and preferences in Chrome local extension storage on your device.

When you run the optional Waypoint server, the extension may synchronize Annotation data to 127.0.0.1:3846 on the same device. The server is designed to listen only on the IPv4 loopback interface and stores its Queue and file-backed media locally.

Waypoint does not send Annotation data, browsing activity, screenshots, or attachments to Logbook for Devs or another Logbook-operated external server. A coding agent you separately connect to the local Waypoint server may receive Annotation data when you direct that workflow. That disclosure is governed by the terms and privacy practices of the agent and its provider.

What Waypoint does not collect

Waypoint does not require a Logbook account. It does not include advertising, analytics, or telemetry, and Logbook for Devs does not remotely collect or sell Waypoint user data.

Waypoint does not use its permissions to build a browsing history. Links may open external websites only when you choose them; those sites operate under their own privacy policies.

Browser permissions

Waypoint uses browser permissions to access the active tab when invoked, store local data, install the Annotation interface on development pages, capture the visible tab when screenshots are enabled, and let you explicitly enable additional sites.

Waypoint’s use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Retention and deletion

Resolved and Discarded Annotations remain as lifecycle history until you delete them. Waypoint provides controls to delete individual Annotations, clean retained history, delete a project’s data, or clear all Waypoint data.

You can also remove data by clearing the extension’s stored data or deleting the local server’s data. Deleting synchronized data may require the server to be running so the deletion can be reconciled across both local stores.

Security and contact

Waypoint limits its server to the local loopback interface, validates browser origins and identifiers, and treats page-derived content as untrusted. Read the project’s security policy and private reporting instructions.

For privacy questions, open an issue in the Logbook Waypoint repository. Do not include sensitive Annotation data in a public issue.

Material changes to this policy will be published with a revised date. Chrome Web Store disclosures will also be updated when a release changes how Waypoint handles data.