ClearFrame Security — Your code, your models, your machine

The rest of this page documents each of those statements, with its limits. Where a claim can be checked by whoever receives it rather than taken on trust, it is checked that way: a ClearFrame receipt is verified on your own machine at Verify a receipt, and that page names the checks it cannot run.

Where your code lives

Local agents work in isolated copies of your project on your own machine. A suggestion is not written into your working tree until you integrate it, and snapshots of eligible files are captured before a task first uses a tool so a change can be reversed.

Remote execution is a limited owner rollout and is off unless enabled. Where it is enabled, runs use a separate workspace, support new projects or public GitHub repositories, and last up to two hours. Local files are not uploaded automatically, and the additional usage estimate for a remote run is shown before you start it.

Credentials and provider keys

Provider credentials you connect in the desktop app are used by the desktop app to reach that provider under that provider's own terms. The website does not store provider credentials or sign-in tokens in browser storage; web sign-in uses HttpOnly cookies and verified email codes.

On this website, the server-side model credential exists only as an encrypted Cloudflare Worker secret and never reaches the public browser bundle. /api/status reports only whether the model is configured, not what it is.

What the website collects

Three things are collected on this site:

• Signup records. If you join early access, the iOS waitlist or a platform notification list, your email address, the plan or platform you asked about and the time are stored in Cloudflare's database service so the request and the update you asked for can be managed.
• Basic website statistics. A random first-party cookie helps count distinct browsers, accepted email sign-in code requests, email sign-ins that issued a session and downloads without counting retries as new visitors. We record the release, date and first referral domain or campaign source, but do not fingerprint devices or store IP addresses in these statistics. The website does not join this browser ID to your account. Global Privacy Control and Do Not Track requests opt out. There are no advertising cookies on this site.
• Abuse limiting. Signup and anonymous usage limits use a temporary hashed network identifier, so the rate limiter can count requests without the signup database storing your raw IP address.

The web app

The web waitlist stores your email address and the platform you asked about so we can email you once, when access opens.

How this site is hardened

Every response carries a Content Security Policy that restricts scripts, styles, fonts and connections to this origin and the specific services this site uses. Frames are denied, nosniff is set, referrer information is trimmed to the origin, and camera, microphone and geolocation permissions are disabled. The preview frame runs under a stricter policy of its own with connect-src 'none'.

Signup endpoints accept only same-origin form submissions, reject unexpected content types above a small size limit, and rate limit per hour.

What is not claimed

ClearFrame publishes desktop releases for macOS. Windows and Linux builds exist and have platform waitlists for an email when access opens. ClearFrame is not presented as SOC 2 certified, HIPAA compliant or independently audited, and no third-party security certification is claimed anywhere on this site. If your requirements depend on one of those, treat that as unmet until it is documented here.

Reporting a problem

Email support@clearframecode.com with enough detail to reproduce the issue. Please do not test against other people's accounts or data, and give us a reasonable window to respond before disclosing publicly.

Related

See Privacy for the full data-handling notice and Docs for how snapshots, access levels and remote runs behave in practice.