Privacy & security · current product

Know what stays local and what gets shared.

Evidence is currently a browser preview and a local-first developer workspace. Here is where search history, feedback, form answers, and agent requests go in those modes.

Current experienceBrowser preview + local workspace API

01 · Privacy

Where your information goes.

Storage depends on whether you are using the static browser preview, a local workspace, or a separately configured API.

SEARCH & WORKSPACE

Search history stays in your browser.

Search requests from the browser preview are sent to Evidence’s hosted endpoint and matched against the deployed public index. The endpoint does not write queries to shared workspace history. Sanitized service events record response status, returned asset IDs, timing, page/image paths, referral hostnames, and unverified bot labels in Netlify storage. These events exclude raw query text, IP addresses, cookies, credentials, and raw user-agent strings. Recent request history and workspace activity are stored in that browser’s local storage. In local development, the API and CLI save request history—including query text—on the host machine in data/state/workspace.json.

FEEDBACK & RESEARCH

Product research is browser-local and consent-based.

Optional research events are recorded only after consent and use an allowlist that excludes raw search queries. Result feedback and follow-up answers stay in the current browser. Optional onboarding and pilot forms are hosted by Tally; submitted answers go to the Evidence team’s Tally workspace and are not linked to an Evidence API account.

For forms and searchPlease do not submit confidential, regulated, or customer information through the preview, research forms, or pilot inquiry.

02 · Security

The boundaries in the current build.

The default setup keeps the search service beside the data it reads. Separate deployments have their own infrastructure and controls.

SEARCH API

Public search is read-only and rate limited.

The hosted POST /v1/search endpoint requires no API key and searches only the public index bundled with this site. It is limited to 60 requests per minute per IP address. Private and locally ingested evidence remains local; the local HTTP API binds to 127.0.0.1, and the MCP server runs as a local stdio process.

KEYS & STORAGE

Development credentials stay in the workspace.

The local API stores API-key hashes in its workspace file. The static browser preview’s development keys are browser-local demo data and are not production credentials. File-based workspace storage is for local development, not a multi-user production database.

03 · Service providers

When another service is involved.

Your browser contacts these providers only for the features that use them.

NetlifyNetlify hosts the public site, API, and sanitized service-event storage.Netlify privacy policy

Google FontsThe site requests its typefaces from Google Fonts.Google privacy policy

MagicMagic handles email-link sign-in on deployments where authentication is configured.Magic privacy policy

TallyTally hosts the optional onboarding questionnaire and pilot inquiry form.Tally privacy notice

Deployment boundary

Check the service before sending sensitive data.

This overview describes the default browser preview and local workspace in this project. If an organization connects a separately hosted Evidence API, that service receives the request and its operator’s storage and retention controls apply. The local development store is not a multi-user production environment.

Ask about a deployment