Compliance And Privacy

[jonny-pdq]

Problem or use case

Following a discord conversation: https://discord.com/channels/1468014954689855716/1468014955533176977/1473639978553573570

1. What is the data being saved or cached by entire io?
2. Is anything being passed on to AI or ML training?
3. Is there any compliance certificate (Like SOC II)?
4. An example of the lifecycle of a commit with entire + what happens to the data in the CLI and UI would be perfect for max understanding.
   Thanks!

Desired behavior

Proposed solution

No response

Alternatives or workarounds

No response

[Soph]

I think this is a good summary of the current state of things. We are looking right now where is the best place to put this so others can easily find it. If you also have suggestions on the wording or if your feel something isn't clear enough, let me know!

CLI (local)

All session logs, transcripts, and checkpoint metadata are stored in your git repository on the entire/checkpoints/v1 branch. No session data leaves your machine until the branch is pushed to your remote.

When you run entire enable, we ask whether you'd like to opt into anonymous usage analytics. This is opt-in and only sends: which CLI command was run, the configured strategy and agent, CLI version, OS/architecture, and which flag names (not values) were used. Analytics are sent to PostHog (EU) with GeoIP disabled, identified by a hashed machine ID. You can opt out at any time by setting ENTIRE_TELEMETRY_OPTOUT=1 or re-running entire enable --telemetry=false.

Two features call out to AI using your local Claude installation (your own API key/session — we never see the request or response):

• entire explain --generate — explicitly generates a session summary
• The README.md#configuration setting — automatically generates summaries at commit time

No other data is sent to Entire.

entire.io (cloud)

When you log into entire.io with your GitHub account, you will go through the GitHub App flow which allows you to give our backend access to some or all of your repositories. For those repositories that you enable, we will store commit, checkpoint, and repository metadata in our database to power the UI. Session logs are cached server-side when you view them in the browser.

Your data is never used for ML training or analysis. If this ever changes, we will ask for your explicit permission first.