jevScope
This policy covers the public Jev Fieldnotes website at jev-typesafe.org and the separate Jev Workbench application at app.jev-typesafe.org. Jev Fieldnotes is an independent resource and is not affiliated with or endorsed by TypeSafe AI.
Information the public site processes
The Fieldnotes pages do not require an account. The local Request Builder and Evaluation Bench process their inputs in browser memory. Cloudflare may process ordinary request information, such as IP address, browser information and requested URL, to deliver and protect the site.
Information Workbench stores
When you sign in, Workbench stores the name, verified email address, profile image and stable account identifier returned by Google or GitHub. It also stores hashed sessions, connected sign-in providers, signup country, Decision Run balance and ledger entries, pricing-interest selections, Pack configuration, fixtures, evaluation results and account preferences.
For abuse prevention, Workbench stores keyed hashes derived from an email address, OAuth identity and IP address or IPv6 network. These values are used to prevent duplicate promotional grants, rate-limit sign-in and support manual risk review. Raw IP addresses and canonicalized email variants are not stored in the risk tables.
How Google user data is used
Google account data is used only to sign you in, link your Workbench account and display your account name or avatar. Workbench requests basic identity information only. It does not request access to Gmail, Drive, Calendar or other Google Workspace content. Google user data is not sold, used for advertising, or used to train generalized AI or machine-learning models. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Live Jev requests
Mock runs stay inside Workbench. When you explicitly start a live run, the fixture text required for that run is sent through our Cloudflare Worker to the configured TypeSafe Jev API. Do not submit secrets, regulated data or full customer records. Provider processing is also governed by the provider's own terms and policies.
Service providers and disclosures
Cloudflare hosts the site, Worker and D1 database. Google and GitHub provide optional authentication. TypeSafe processes live Jev requests. We share data with these services only as needed to provide the feature you requested, protect the service, comply with law, or investigate abuse. We do not sell personal information.
Retention and security
OAuth state expires after ten minutes and Workbench sessions expire after seven days. Account and workspace records are retained while the beta operates or until they are no longer needed for the purposes described here. Access controls, server-side secrets, TLS, hashed session tokens and restricted administrative tools are used to protect stored data, but no online service can guarantee absolute security.
Your choices
You can edit your display name and avatar, disconnect by signing out, revoke all active sessions, and avoid live processing by using mock mode. To request access, correction or deletion of account data, contact the support address displayed on the Google OAuth consent screen. Requests may require identity verification, and limited anti-abuse records may be retained where necessary to prevent repeated promotional abuse or meet legal obligations.
Changes
Material changes will be reflected on this page with a new effective date. Review this policy before continuing to use Workbench after a change.