Octyl Receipt Terms

Effective date: 3 November 2026 · Version: pilot-2026-11-03

These Receipt Terms are an agreement between Octyl Labs, Inc., a Delaware corporation (“Octyl”) and you, the person or organization that accepts them (“you”). They add to the Terms of Service; where the two conflict about receipts or the Pilot, these Receipt Terms control. Section 9 applies only to members of the Pilot.

The short version

A plain-language summary of how Octyl handles your data. It is not part of the terms you accept and it is not a substitute for them; where they differ, the terms control. octyl login shows it above the full terms.

Your code stays yours. Octyl never receives your code, prompts, or file or repo names. Your AI tools talk to their makers directly.
Receipts say how a run went: model and version, runtime, settings, public extensions, type of work, time, cost, outcome. See the next one before it’s sent: octyl contribute show --next. Everything sent, byte for byte: octyl contribute log.
Contributing receipts is how Octyl works, on every plan. Every run’s receipt goes to the Reef, linked on our side to a random contributor ID, never your name, email, team or company, and used only to delete your contributions, handle concerns and catch attempts to skew results.
The Reef is open evaluations. Weekly public results, only for groups of 20+ people and 20+ runs, never attributed to a person, team or organization. We don’t license Reef data today. If we ever do, it will be deidentified aggregates only, and we’ll tell you first.
You’re in control. Something in a receipt identifies you? octyl contribute report holds it out of the Reef at once, and we reply within 5 business days. Erase: octyl contribute delete removes your receipts from Octyl (raw upload copies expire within 90 days); results already published in the Reef stay, since they’re group totals never tied to you. A copy: octyl contribute export.
Otherwise, just your account: name, username, email and phone number. Telemetry and crash reports are off until octyl telemetry on, and Octyl turns off your AI tools’ own usage reporting where they offer a way. The web app logs usage and errors. Debugging needs your OK: one issue at a time, deleted within 30 days, never used for the Reef or training.
Teams: chatter is references, never code; file, branch and agent names are scrambled, notes sealed. The relay sees commit SHAs and line numbers for about 10 minutes. Messages between teammates, and between your phone and computer, are end-to-end encrypted and the relay can’t read them; teammates’ messages wait sealed up to 7 days for devices that are offline. The team trial and referral seats need an ID check by Stripe; we keep only the result, never your ID or photo.
Your privacy rights: we follow the CCPA for everyone, wherever you live. California: see our Notice of Financial Incentive.

The full text follows.

1. Accepting these terms

1.1 You accept by typing yes when octyl login or octyl contribute terms shows these terms. Octyl records your account, the terms version and the time you accepted.

1.2 Until you accept, you stay signed in, but no agents start and nothing is sent. Agents already running are never stopped.

1.3 If you accept for an organization, you confirm you have authority to bind it.

2. What you get

Octyl itself, on whichever plan you are on:

on Free: up to 12 agents at once, free of charge;
in the Pilot (by invitation, section 9): up to 12 agents at once and teams of up to 3 people, free of charge;
on the paid Pro, Team and Enterprise plans, when they are offered: more agents and team features.

Your plan’s limits are enforced by a signed grant the Software receives when you sign in.

3. Contributing receipts

3.1 Contributing receipts is how Octyl works, on every plan (Free, Pilot, Pro, Team and Enterprise alike). After every agent run that octyl starts, it queues one receipt on your machine and sends it to Octyl. A receipt describes how the run went; it is not your code or your work. There is no setting, plan or environment variable that turns contributing off. Demo and play-mode runs never send a receipt, and simulated runs Octyl uses for its own testing are tagged and never counted in results about real users.

3.2 What a receipt contains. Only the fields listed in the receipt terms that octyl login and octyl contribute terms show. In summary:

identifiers and versions: a random receipt id, the schema, terms and octyl versions, your operating system and CPU type;
the run: the AI tool and its version, the model, start and end time, duration, exit status, sandbox mode, and whether it ran without a terminal;
the result: whether the run made commits or changes, and how many commits;
usage and cost, when the AI tool reports them: token counts and an estimated cost at public list prices (not what you paid), with the price card used;
what produced the run, each value labelled as reported by the AI tool, detected by octyl, declared in your configuration, or unknown: the model’s public name, version and family (a model whose name is not public is sent as “other”); for open-weight models, the public repository, quantization and context window; the AI tool’s reasoning effort, permission mode and sandbox setting; how the model was reached (hosted, aggregator, self-hosted or local) and the provider, from a fixed public list; public plugins, MCP servers and extensions by their public registry id, and a count of the others; for models on your own or self-hosted hardware, the accelerator family, a memory bucket and the device count; the tuning values (temperature, top_p, top_k, maximum output tokens, reasoning budget, context window, quantization, KV cache type); and a fingerprint (a hash) of these values;
the kind of work, worked out on your machine from fixed, versioned lists: a task category, domain and kind, artifact types touched with size buckets, the top languages and public frameworks, a two-letter system locale, integrations from a fixed public list, a duration bucket, and size buckets for the diff, the files touched and the repository;
Octyl’s own choices, when it made them: whether Octyl context was added (counts of entities and bytes, never the content), a prompt framing pack you opted into (its label and version, never its text), and, in experiments, which AI tool or model Octyl picked, how it chose and the seed;
Oggie decisions: if you act on an Oggie suggestion, a small record of its kind and whether you accepted, overrode or ignored it, never its text.

3.3 Outcome updates. About 7 and 30 days after a run ends, octyl may send an outcome update for the same receipt, worked out on your machine from git: whether the work landed and how (merged, patch or squash), a delay bucket, whether it was reverted or heavily rewritten, how much of it survives after 30 days, how many later commits touched the same files, and the CI result and check counts if known. Setting OCTYL_OUTCOMES=off limits outcome updates to the git-based fields. The local record used to work these out (which holds commit SHAs and paths) is never uploaded.

3.4 Never sent. Your code, diffs, prompts or task text, commit messages, file names or paths, repository or branch names, commit SHAs, terminal output, environment variables, tokens, keys or other secrets, base URLs, host names, IP addresses, the names of private plugins or MCP servers, the names of CI checks or jobs, and the list of AI tools or models installed on your machine. Octyl’s server rejects any receipt that contains a field it does not allow, and octyl runs the same check before queuing one.

3.5 Pseudonym. On Octyl’s side, your receipts are stored under a keyed pseudonym of your account, never your name, email, team or company. A separate table links the pseudonym to your account, and Octyl uses that link only to delete your contributions when you ask, to handle a concern you report, and to match outcome updates to their receipt. While Octyl holds them, receipts are therefore pseudonymous, not anonymous. Published results never carry any ID.

3.6 Exactly what was sent, byte for byte.

octyl contribute show --next shows the exact receipt your next run would send, before it exists; octyl contribute show shows what is waiting and what was sent.
Every byte that leaves your machine is first written to a local, append-only log (~/.octyl/transmissions/log.jsonl); if that log cannot be written, nothing is sent. octyl contribute log prints it (--raw for the exact bytes) and octyl contribute export copies it.
Signed in at app.octyl.ai/reef, you can read your most recent receipts exactly as Octyl stores them. For a copy of everything Octyl holds for you, write to privacy@octyl.ai.

3.7 Something here identifies me. If a receipt looks like it could identify you, your team or your employer, or contains anything it should not, report it with octyl contribute report <receipt-id> (optionally naming the field), or with the button next to the receipt at app.octyl.ai/reef. From the moment the report is stored, that receipt and its outcome updates are held out of the Reef. A person reviews it and answers within 5 business days. If the field identifies you or should not be there, Octyl removes or redacts it from the stored receipt and its outcome updates, the next Reef release is computed without it, and the change is recorded in an audit log. You can follow the status (received, reviewing, scrubbed or no issue found) with octyl contribute concerns or at app.octyl.ai/reef. Please don’t paste the value itself into your note.

3.8 Receipt heartbeat. When your version of octyl supports it, your dock also sends a content-free heartbeat so Octyl can check that receipts arrive intact. It carries only a run number and a fingerprint (a hash) of the receipt, never any receipt field, and in a team it is passed through the chatter relay to Octyl, never to your teammates. Octyl never reads your chatter messages for this.

3.9 Your AI tools’ own telemetry. Separate from receipts: Octyl’s own usage telemetry (octyl telemetry) is off unless you turn it on, and is not a condition of any plan. For every crew member it runs, Octyl turns off that AI tool’s own telemetry and usage reporting where the tool offers a way, and sets DO_NOT_TRACK=1 for it. Octyl itself does not read DO_NOT_TRACK.

4. Limiting what is sent

4.1 Contributing receipts can’t be turned off on any plan. octyl contribute off changes nothing and says so.

4.2 You can limit what is sent at any time: nothing is sent while you start no agents (agents already running are never stopped); you can delete what was sent (section 6); and you can close your account. None of these is a breach.

4.3 If receipts can’t upload for more than 24 hours (for example you are offline), team features pause and you can run up to 12 agents at once until they send again. Being offline is never treated as a choice to stop contributing.

5. How Octyl uses receipts

5.1 License. You grant Octyl a worldwide, non-exclusive, royalty-free, perpetual license (subject to section 6) to store, copy, analyze, combine and create aggregated results from your receipts and outcome updates, for the purposes in 5.2.

5.2 Purposes.

(a) Run Octyl: enforce your plan’s grant, notice failed uploads and support you.

(b) The Reef: publish aggregated results comparing AI tools, models and configurations. Results are published on a fixed weekly schedule and anyone may use them.

(d) No licensing. We don’t license Reef data today. If we ever do, it will be deidentified aggregates only, and we’ll tell you first. Any such use needs a new version of these terms that you accept.

5.3 Protections on everything Octyl publishes.

Only aggregated results, combined across many people and runs.
A minimum group size: every published result is computed from at least 20 different people and 20 runs; smaller groups are suppressed or generalized (for example an exact version becomes the model family).
Never attributed to a person, team or organization, and never individual-level: no receipts, receipt ids, contributor IDs, account ids, email addresses or per-person time series.
Octyl does not try to re-identify anyone from aggregated results.

5.4 No training on your content. Octyl does not receive your code or prompts, and never gives individual receipts to anyone.

5.5 Consideration. Access to Octyl under section 2 is the full consideration for the license in 5.1.

6. Deleting your receipts

6.1 octyl contribute delete (or deleting your account) removes every receipt and outcome update Octyl holds for you, and the link to your account, from Octyl’s database at once. Backup copies expire within 14 days and raw upload copies within 90 days. You can also ask at privacy@octyl.ai.

6.2 Published results don’t change. Results already published in the Reef are frozen group totals that never identified you; deleting your receipts leaves them as they are and leaves your receipts out of every result computed afterwards.

6.3 Deleting receipts doesn’t change your plan or your allowance.

7. Your obligations

You will not tamper with, forge, replay or inflate receipts or outcome updates, run agents to generate fake receipts, try to skew or control what the Reef publishes, or try to use Octyl without contributing. Octyl may then suspend or end the accounts involved (Terms of Service section 11). You remain responsible for following your Providers’ terms when you run many agents at once (Terms of Service section 2).

8. Publicity

Octyl will not name you or your organization as a user or Pilot member publicly without your written permission.

9. The Pilot

9.1 The Pilot is closed and by invitation. Octyl adds a member by account or verified email address; an invitation alone grants nothing until you sign in and accept these terms.

9.2 The Pilot runs until Octyl ends it. Octyl may end the Pilot, or your membership, on at least 14 days’ notice, or at once for breach. When it ends, your account moves to Free or to a plan you choose.

9.3 The Pilot is pre-release software and services, provided “as is”. Octyl may ask for your feedback.

10. Disclaimers and liability

The disclaimers and limitation of liability in the Terms of Service apply.

11. Changes

If Octyl changes these terms in substance, it changes the terms version, and octyl asks you to accept the new version before new agents start; until you accept, no new agents start and nothing new is sent. Receipts sent under an earlier version stay governed by the version in force when they were sent.

12. Contact

Octyl Labs, Inc. · privacy@octyl.ai