Privacy
Updated September 29, 2026
ClearFrame is operated by Blue Marble Money Inc.
Your account
We store your verified email, username, subscription status and included AI usage to provide sign-in, billing and a shared allowance across devices. Cloudflare processes sign-in emails and stores account data. Apple and Stripe process purchases through their respective services. We do not use this information for advertising or sell it. If you send an Enterprise inquiry, we store the organization, expected seat range and needs you submit so we can respond. We do not treat an inquiry as a purchase.
Team work
If you accept a Team invitation, we record your verified email membership, role and assigned seat. Team owners and admins can see member and seat details plus aggregate usage, including the remaining percentage and reset date. They cannot see your local projects or agent history through Team management. You choose Personal or Team billing context for hosted work; joining a Team does not automatically cancel a personal subscription.
Browser tasks
Browser tasks, drafts and files are saved in local storage on this device under your signed-in account. They are not synced to other devices. Clearing this site’s browser data removes these local copies. Submitted prompts and files are sent to the model service to generate responses.
Your work
Your computer runs your coding tasks and stores task history. The iOS app connects to your Mac directly. When you choose included ClearFrame AI, your prompts and supplied project content pass through ClearFrame’s service to the model provider. With your own API key, requests use your configured provider directly. Each provider’s processing terms apply.
Observatory scan results
When you upload a scan receipt or run a hosted MCP scan, Observatory stores the target identifiers, checks, scores, and results with your account on Cloudflare. Hosted scans contact the public endpoint you submit. Your private results are separate from the public Safety Index. Retention and usage limits depend on your account and are shown in Observatory. Existing Observatory GitHub accounts keep their own results; signing in to ClearFrame does not automatically combine accounts.
Deleting your account
Request account deletion using the support email below. Account deletion removes your login and owned account data. We retain a keyed, non-readable email digest recording that the starter allowance was redeemed, to prevent repeated claims. Billing records required for accounting may be retained. Deleting your account does not cancel an Apple or Stripe subscription; manage subscriptions separately.
Basic website and app statistics
We use a random first-party browser cookie to count website visits, accepted email sign-in code requests, email sign-ins that issued a session and downloads without counting retries as new browsers. We record the release, byte ranges served, date and first referral domain or campaign source. We do not fingerprint devices or store IP addresses in these statistics. Global Privacy Control and Do Not Track requests opt out of browser statistics. With those controls off, a validated first-touch source may also be saved on a newly verified ClearFrame account to understand which introductions lead to signups. The account does not store the browser cookie or its identifier. With either control on, we do not save a source with the account.
ClearFrame 0.15.0 and later can report a random app profile identifier, app version, platform, daily activity and turn outcome counts to our Cloudflare account service. These authenticated statistics never include prompts, code, file paths or conversation content. You can disable them in Settings → Share basic usage statistics. Account authentication, billing and metered managed usage records are separate and necessary to provide the service.
Separately, the desktop app can report setup milestones with a different random installation identifier, its version and platform: first run, launch, engine readiness, AI access and the first finished agent turn. This identifier is separate from your account, the authenticated app activity identifier and the website visitor cookie. These milestone reports contain no prompts, code, file paths or conversation content. The same Settings toggle controls both types of app statistics. Turning it off stops these reports and requests deletion of the milestone events; if the request fails, the app retries on a later reporting attempt while the setting remains off. After the service confirms deletion, it keeps an excluded installation record with the old identifier, version, platform, and first and last seen dates so later messages using that identifier stay excluded. After a confirmed opt-out, turning the setting back on creates a new random installation identifier.