This website
Product and learning pages are static. The Beta account service processes sign-in and access metadata. This website does not accept engineering file uploads or run CAN analysis. We do not add advertising trackers or product analytics scripts.
When you visit a hosted website, the hosting provider processes technical request information such as an IP address and requested URL to serve the page. The host’s own handling of that information is separate from the account behavior described here.
Beta accounts
Signing in sends your email address to the account service. Cloudflare Workers and D1 process account records, verified-email state, sessions, free Beta access, safe quota metadata, download response starts and device associations. Resend processes the recipient address and sign-in code to deliver the email. Account emails are not added to a marketing list.
Desktop sign-in associates a random installation ID, first/last app version and timestamps with your account. No hostname or hardware identifier is collected. Only credential hashes reach D1; the computer stores credentials using operating system encryption. Download records mean a response started, including resumes; they do not prove completion or installation.
A necessary HttpOnly session cookie keeps you signed in for up to seven days; it is removed on sign-out. Sign-in codes expire after five minutes and are stored as hashes. Anti-abuse records use keyed hashes of email and request IP, and are stored separately from engineering data. Session records omit IP address and browser agent.
Desktop access tokens last at most 15 minutes, with rotating refresh credentials and a fixed seven-day session. Offline sign-out clears local usable credentials and retains an encrypted server-revocation retry; local engineering files remain. Expired authentication, device-session and limit records are removed by an operator-run cleanup command; expiry blocks use before cleanup. Historical terminal usage records for superseded access grants and access audit records and download-start records are eligible for cleanup after 90 days. Usage records for your current grant are retained to preserve cumulative credit accounting and safe retries, including after an invitation extension. Unknown operation states remain until resolved. Account, current access and its necessary usage records remain until a verified deletion request is processed. Operational cleanup must be enabled before public launch; this phase does not claim automatic cleanup scheduling or account deletion.
For account deletion, email beta@embedvera.com from your account address. We verify the request before removing the account, sessions, devices, download records, entitlements and associated quota/audit records. Email correspondence and provider records follow their own processing and retention. See data handling for the implemented boundaries.
Beta correspondence
Registration and sign-in use the same email-code account flow. No separate email application is required for free Beta access.
If you contact Beta support, your email provider and our receiving mailbox process the correspondence you choose to send. Earlier Beta application emails remain correspondence; registration does not resend or convert them into marketing messages. Do not send customer names, raw logs, DBC files, specifications, source code or other confidential engineering material.
Optional product events, feedback and diagnostics
Desktop product events are off at every app start. If you enable them for the current app session, fixed event names, times, app versions, random event identities and a fixed category for reported failures are associated with your signed-in account and installation. They do not include engineering content, file names or paths, signal names, issue text, findings, prompts or model responses. Failure categories are provider unavailable, input rejected, engine unavailable or unknown; raw error messages are not included. Turning the setting off or restarting discards pending events. Unsent events expire after seven days and the local queue is bounded to 100 entries.
Feedback is sent only when you review and submit the optional text and category. Avoid confidential material; obvious credentials and absolute paths are refused, without storing the rejected message. Diagnostics require a separate preview and explicit consent. Their fixed fields are app/engine versions, Windows platform, packaged-app status, identity state and update state; they contain no raw logs, files, credentials or model text. Being open to a case-sharing conversation does not upload engineering material or authorize future uploads.
Uploaded events are eligible for operator-run cleanup after 30 days; feedback and diagnostic submissions after 90 days. Verified administrators can see bounded product counts, reported failures and your submitted support material. These events measure reported product use, not engineering correctness. At feedback and data controls, you can permanently delete this account’s uploaded events, feedback and diagnostics. Turn Desktop events off first to prevent new uploads. This does not delete the account or necessary access, download, security and usage records.
You can queue an account deletion request while signed in. It remains pending until an operator verifies and processes it; requesting deletion is not confirmation of account removal. Pending requests are retained until resolved; closed requests are eligible for cleanup after 90 days. Cleanup is an explicit operator process and automatic scheduling is not claimed.
Engineering data is local-first
Raw engineering artifacts are local-first in the current EmbedVera engine. Raw large logs are streamed locally and are not sent wholesale to a model. There is no automatic source upload through this website.
Evidence reports use normalized project-relative artifact paths. A traceable source location helps an engineer find the original locally without serializing the absolute project root or local path mappings.
Live AI is an explicit choice
When live AI (Artificial Intelligence) is explicitly enabled in the engine, only selected relevant context may be sent to the configured model provider. This may include relevant specification text and compact structured observations. That context can still be sensitive.
Review the selected context and your provider’s data terms before enabling live AI. Local-first does not mean that an explicitly enabled online model receives no information. This website does not ask for model credentials or initiate those model calls.
Hosted model access is not enabled
A hosted model backend is being prepared locally. It is disabled by default, has not been activated in production, and has no desktop investigation consumer. Signing in does not enable it. Local tests use synthetic selected summaries and a fake provider.
Before any future activation, selected short summaries would require a preview and separate explicit consent, and the provider’s data terms would need review. The preparation stores only operation metadata, a context fingerprint, status and reserved budget amounts; it does not store selected text, model output or provider credentials. A generated summary is not engineering evidence. Reserved cost ceilings are not provider bills, and actual prices, sufficient limits and result quality have not been verified.
User-linked preparation records would be removed with a verified account deletion. Identity-free daily budget totals remain to prevent account deletion from refunding spent or uncertain model reservations. No automatic reconciliation or retention schedule for this disabled preparation is claimed.
Questions about privacy
Contact beta@embedvera.com with a general question. Please do not attach proprietary engineering material.