DATA BOUNDARIES

What the app sends
and stores.

This public website

This website is static content hosted on Cloudflare. It links to the hosted signup and dashboard. It has no application analytics scripts, advertising trackers or forms that collect provider credentials. Cloudflare processes requests to deliver and protect the site.

Your engine instance

The engine sends the evidence you submit to its configured model provider when inference is needed. The published local runtime and hosted service currently use Vercel AI Gateway. Newer source and self-hosted engines can select TypeSafe AI direct or Cloudflare Workers AI. Review your selected provider's data handling terms before submitting sensitive information.

Local engine credentials and usage are stored on your computer. A hosted engine keeps its durable state in its owner's deployment. The public website does not receive that engine's API requests.

Engine activity and receipts retain metadata such as connection identity, service, outcome, token counts and latency. The engine does not intentionally retain raw request bodies in the usage ledger. Exact input caching exists in process memory with a configurable lifetime.

The free early access

The hosted workspace sends verification codes to your email through Cloudflare Email Service. It stores a hash of your normalized email to recognize your account, an editable display name initially taken from the part before @, hashed short-lived verification codes, hashed sessions, scoped connection credentials, daily and monthly usage and recent request metadata. Cloudflare processes delivery addresses and email delivery logs. Short-lived hashes of network addresses limit sign-in abuse. It sends decision input to Jev through Vercel AI Gateway when a model evaluation is needed. Do not submit information you are not permitted to share with that provider.

Invites expire after 48 hours and work once. Customer browser sessions expire after seven days. A recovery invite restores the same account and signs out its previous browser sessions when redeemed. The preview administrator can suspend an account; you can revoke your own connections from the workspace.

Recent receipts are limited to the latest 2,000 across the engine, with up to 100 displayed in your workspace. This is not a promise of complete or long-term history. Email codes expire in ten minutes and allow six verification attempts. Verification reopens the same account without resetting usage. Private invitations also remain available for existing preview accounts. There is no password database or payment collection.

Credentials and controls

Consumer keys are stored as hashes. Provider secrets remain server-side; local secret files are permission-restricted, not encrypted at rest. Use scoped credentials, expiration and revocation, and keep the administrator link private.

Client-reported names help display activity but do not establish identity. The credential determines the connection and its limits.