Privacy policy

Treft is mission control for coding agents: you compose work, an agent runs it in an isolated cloud sandbox, and nothing merges without your explicit approval. We collect the minimum needed to do that, and nothing for advertising.

What we collect

Account

When you sign in with Apple, Google, or GitHub we receive your name and email address (Apple's private relay addresses are fully supported — we never require your real email) and create an account identifier. If you link GitHub, we store your GitHub username and the identifiers of the GitHub App installations and repositories you explicitly connect.

Your code, transiently; your changes, durably

When you start a run, the connected repository is cloned into an ephemeral, network-isolated cloud sandbox (Firecracker microVM) that is destroyed when the run ends. Portions of your code, and the intent you type or speak, are sent to third-party AI model providers to perform the work you requested — under agreements that prohibit training on your data and limit retention. Which providers power a run can change; every one is bound by the same terms. What we keep is the run record: the agent's tool-call log (arguments redacted at source), test results, the proposed patch (diff), cost accounting, and the append-only audit trail of your decisions (approve, reject, request changes). That record is what the app shows you as evidence.

Model providers receive code through their commercial APIs, which do not use API traffic to train models. We never train on your code bodies either — what we learn from is verification metadata and outcomes, in aggregate, as described in our terms. The Treft GitHub App requests per-repository access you grant explicitly and can revoke at github.com at any time; secrets and credentials are redacted before anything is persisted, not merely before display.

Device push tokens

If you enable notifications we store your APNs device token (with its environment and app bundle) so decisions can reach your lock screen. Tokens are pruned when Apple reports them dead.

Crash and reliability data

Crash reports and release-health signals via Sentry — used only for app functionality, not linked to your identity for tracking, no advertising IDs. This matches the app's Apple privacy manifest (PrivacyInfo.xcprivacy: no tracking, crash data for app functionality only).

Usage/spend telemetry

Per-run cost and quota accounting attributed to your account, so caps and metering work.

First-party product analytics

We record first-party product events on our own servers (for example: signed up, connected a repository, started a run, verification completed, decision made) with sanitized, banded properties — never code, diffs, file contents, or repository names. No third-party analytics service receives them, and aggregate learning honors your account's data opt-out.

What we do NOT do

• No advertising, no trackers, no tracking domains, no sale or sharing of personal data.
• No analytics SDKs beyond Sentry crash/release health.
• Agents never execute on your device — the app executes no code locally.
• If you supply your own model API key, it is stored envelope-encrypted, is write-only (it can be replaced or deleted but never read back through the API), and never appears in logs or run events.
• This website sets no cookies, runs no scripts, and loads nothing from third parties.

Service providers (subprocessors)

Fly.io (API hosting, Frankfurt) · Neon (Postgres) · E2B (ephemeral run sandboxes) · Apple (push notifications, Sign in with Apple, and in-app purchase processing on iPhone) · Google (Sign-In, Android push delivery, and in-app purchase processing on Android) · GitHub (repository access via the Treft GitHub App) · Stripe (payments and subscription billing on the web — Stripe holds your payment details; we never see your card number) · Sentry (crash reporting) · Vercel (hosting for the treft.dev marketing site) · model providers for the runs you start and for voice transcription (third-party AI model providers under no-training, limited-retention agreements; the specific providers can change without changing these terms). Each receives only what its function requires.

Retention & deletion

Run records and audit trails are kept while your account exists (they are your evidence trail). To delete your account: in-app, Account → Delete account, or email support@treft.dev. Uninstalling the Treft GitHub App from your GitHub account revokes repository access immediately.

What deletion does, class by class

This schedule is mirrored, word for word, from the retention table in our code — a test fails if the two ever drift.

• Identity. Your identity — email, name, sign-in identities, sessions, push tokens, and stored model keys — is deleted immediately, in the deletion transaction itself.
• Work product. Your projects, runs, decision cards, and releases are deleted immediately. Treft-workspace repositories and warm sandbox snapshots are removed at their providers by a durable cleanup queue that retries until it completes.
• Run event payloads. Run event history is append-only and survives under an opaque id, but the payloads — which can include code, diffs, logs, and test output from your runs — are redacted within 30 days of account deletion.
• Evidence artifacts. Stored evidence artifacts (screenshots and diffs) referenced only by your decisions are deleted within 30 days of account deletion; an artifact also referenced by another account's evidence survives.
• Audit trail. The append-only, hash-chained audit trail is never modified or deleted. After deletion it references you only by an opaque id; some entries can carry operational references such as repository names or pull-request numbers — never your email or name.
• Billing and usage records. Billing, usage, refusal, and product-event records are retained under the same opaque id as financial and operating truth, including for tax and dispute obligations. They carry amounts, counts, grades, and file paths — never code bodies.
• Provider deliveries. Provider delivery records (GitHub, Stripe, Apple, and Google webhook payloads) are retained for exactly-once processing and dispute resolution, then deleted 90 days after we receive them. Deliveries we could not process are kept until the failure is resolved. They contain the provider's event metadata, such as repository names and pull-request titles — not your code.

What deletion does at our providers

If you have an active subscription, deletion cancels it immediately at Stripe and deletes your payment profile there — a deleted account is never charged again. If you signed in with Apple, we revoke your Sign in with Apple tokens with Apple where Apple-issued tokens exist for your account. Warm sandbox images and Treft-workspace repositories are removed at E2B and GitHub. Each of these runs on a durable queue that retries until it completes; your account itself is gone immediately, and cleanup finishing later never resurrects it.

Why we are allowed to process your data

If you are in the European Economic Area or the United Kingdom, these are our legal bases under the GDPR:

• To perform our contract with you — creating your account, running the work you ask for, storing the run record and its evidence, taking payment, and sending the decision notifications the product exists to send.
• Our legitimate interests — keeping the service secure and available, preventing abuse and fraud, and improving verification quality from aggregate metadata and outcomes (never your code bodies). You can object to the aggregate-learning use at any time; see below.
• Legal obligation — retaining billing and tax records.
• Your consent — push notifications, which you turn on and can turn off in Settings.

Separately from these bases, the iPhone and Android apps ask you in the app before they first send your code or a voice clip to a model provider. Declining sends nothing and leaves the rest of the app usable.

Your rights and how to exercise them

Write to support@treft.dev from your account address and we will answer within one month, unless a self-serve path is named below.

• Access and portability. We will send you a copy of the personal data we hold about you. There is no self-serve export yet — this one is handled by hand, and we would rather say so than imply a button exists.
• Rectification. Your name and email come from the sign-in provider you chose (Apple, Google, or GitHub) — correct them there and they update here on your next sign-in.
• Erasure. Self-serve and immediate: Account → Delete account in the app. What deletion does, class by class, is above.
• Objection. You can object to the aggregate-learning use of your verification metadata; we set the opt-out on your account and every aggregate excludes you from that point.
• Withdrawing consent. Turn notifications off in Settings.
• Complaint. If you are in the EEA or the UK you can complain to your local data-protection supervisory authority.

We do not sell personal data, and we do not use it for automated decision-making that produces legal effects concerning you.

Where your data is processed

Treft's API and database run in Frankfurt, Germany. Sifr Solutions, LLC is a Delaware company, and several of the providers named above process data in the United States, so running Treft involves transfers out of the EEA. Each provider is engaged under its own published data-processing terms; if you need the transfer safeguards that apply to a specific provider, write to support@treft.dev and we will send you what governs that relationship.

Your choices

Notifications are optional (iOS Settings). Repository access is per-repo and revocable at GitHub. You can reject or interrupt any run.

Contact

support@treft.dev · Changes to this policy will be posted at this URL with a new effective date.