Legal

Privacy Policy

Stub for v1 — counsel draft pending (GDPR / CCPA where applicable).

Draft for counsel review — not legal advice. This page summarizes the data Front End processes. A full counsel-reviewed policy will replace this stub before launch.

Access keys

Your organization access key (FE-…) authenticates engine use. We store a hash of the key, not the key itself, to validate requests. Keys are issued at signup, shown once on the Hub Connect page and in your welcome email, and can be rotated from Settings. Never commit keys to source control.

Audit logs

We record engine tool-call metadata per organization (which tool, when, entitlement result) to operate the service, enforce tier limits, and detect abuse. We do not use the contents of your code to train models. Logs are retained for a limited operational window.

Hub data

The Hub stores your account profile (name, email), organization and tier, project list, and — on Team tier — manifest snapshots you sync for backup and collaboration (tokens, registry, pages). Your application code stays in your repository; we do not store it. You may delete your account and associated Hub data from Settings.

Billing

Paid subscriptions are processed by LemonSqueezy, which handles payment data and tax. We receive subscription status and tier, not full card details.

Your choices

You can rotate your key, cancel your subscription (engine calls stop at period end; your repo and manifest remain yours), and delete your account. For data requests, contact the operator listed in the Terms of Service.