evidence
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

Your usage belongs to your account.

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. Account search stores request IDs, channel, result count/status, latency, and credit usage in PostgreSQL, without storing query text in account usage. Your account name, email and onboarding preferences are also stored there. 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. Account onboarding saves your name, workspace, use case, and chosen integration to your account. Optional research questionnaires and contact forms use Tally and remain separate from account onboarding.

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. The anonymous preview is limited to 10 searches per day per IP when account storage is configured, with a 60-per-minute edge ceiling. Signed-in browser, API, and MCP searches use prepaid credits. Private and locally ingested evidence remains local. Account sessions, onboarding, hashed API credentials, credit entries, and usage metadata are held in the account database. Usage records exclude query text.

KEYS & STORAGE

Access is verified on the server.

Account API keys are generated with cryptographic randomness and stored hashed. A new key is displayed only once, and revocation takes effect on subsequent requests. Sessions use HttpOnly cookies; OAuth tokens and codes are hashed, resource-bound, and scoped to retrieval. The separate local CLI still has development-only file storage.

03 · Service providers

When another service is involved.

These providers process data only for the features that use them. Email delivery, identity verification, database access, and payment verification can occur on the server.

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
ResendResend delivers one-time email sign-in codes when configured.Resend privacy policy
StripeStripe processes card checkout. Evidence retains purchase status and credit entries, never card numbers.Stripe 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 public search preview, account workspace, and local development tools. Magic verifies Magic-link sign-ins; Resend delivers email codes when enabled; Stripe handles card checkout. Evidence stores payment status and credit grants, never card details. 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