Trust / Security

Clear data boundaries.

How the current EmbedVera engine handles local artifacts, traceable source references and configured model credentials.

Local-first processing

Log parsing, signal decoding and numeric measurements run locally. The engine filters relevant messages and builds compact observations rather than sending raw large logs to a model.

Live AI requires explicit selection of a configured provider. Relevant context may leave the machine in that mode; it is not an offline-only guarantee. See the privacy notes for that boundary.

Account security

Email codes verify account ownership. Server sessions use HttpOnly, SameSite cookies and Secure cookies on HTTPS. Sign-in mutations require the configured site origin. Codes have a five-minute lifetime, a bounded number of attempts and persistent email/IP request limits. Disabling an account blocks existing sessions from account and entitlement access.

Product access is checked independently of sign-in. First verified email registration enables free Beta access for 30 days. Signing in again does not renew access, restore paused or revoked access, or reset used credits. Quota reservations use atomic database checks and per-account idempotency keys. Payment is off in this phase and the hosted model gateway remains unavailable. Operations pages and access changes require a verified, active administrator role read from the database for every request. The client cannot grant itself that role, and native credentials cannot authorize operations.

Windows installer downloads require active Beta access on every request, including HEAD and resumed ranges. Release identities bind the verified installer hash, object identity and size. Installer objects must stay in a private R2 bucket. Desktop credentials stay in operating system secret storage and the main process; rotating refresh credentials have a fixed seven-day lifetime. Disabled accounts or devices cannot start new investigations; local work remains readable.

Account responses are not cached. Email-provider requests have a timeout and reject redirects. Server secrets are not included in browser bundles, account pages or engineering reports.

Optional support endpoints require authenticated accounts, the configured origin, bounded JSON bodies and fixed fields. Invalid native bearer credentials never fall back to browser cookies. Extra fields are rejected. Retries with the same event/submission identity cannot replace earlier content. Feedback refuses obvious credentials and absolute paths without saving or echoing rejected text. Diagnostics require explicit consent and a fixed whitelist. There is no engineering attachment ingestion endpoint.

Project-relative provenance

Exported evidence identifies artifacts relative to the selected project root. Inputs outside that root are rejected; an engineer must explicitly select a containing root when needed.

Reports do not serialize the absolute project root or runtime path mappings. Source text and user-authored content may still contain sensitive information. Review a report before sharing it.

Model credentials

The current engine reads configured model credentials locally. Application Programming Interface (API) keys are not embedded in reports or the non-secret model-call audit. Credentialed requests do not follow redirects.

This website does not collect API keys. Email verification creates or signs in to an account; no engineering file uploads are accepted.

What the current Beta can promise

  • Evidence boundaries: measured facts, candidate inferences, unknowns and next investigation steps remain distinct.
  • Time boundaries: separate logs, channels and clocks are not assumed to be synchronized.
  • Knowledge boundaries: model output is derived knowledge, not independent engineering evidence; source checks do not replace full semantic review.
  • Access boundaries: the website supports Beta accounts and free access, controlled private installer downloads and desktop sign-in. Hosted analysis is still being prepared.

Enterprise identity controls, compliance certifications, penetration-test attestations and service-level commitments are not offered by this minimum website.

Report a concern

Send an initial, non-confidential description to beta@embedvera.com. Do not include credentials, customer data or proprietary files in an initial message.

Early access Beta

Bring a question.
Leave with a direction.

Register with your email to get free Beta access and download the Windows app. Sign in after installation to start investigating.

Join the Beta