# Security and privacy

Your credentials stay yours: what leaves your machine, what stays local, where data lives and how EasyCode keeps it apart.

EasyCode drives coding agents on your machine, on your own logins. It is built so that your credentials stay
yours, your working tree stays on your machine, and your org receives only what the team needs to work together.

## Your harness credentials stay yours

Each harness signs in on your machine and keeps its own credentials. EasyCode never reads, copies or uploads them:
not the credential files, not the tokens, not the OS keychain. It may check that a known file exists, never what is
in it. It doesn't write a harness's config either. The harness owns its config and its login.

When you click **Connect** on a harness in **Settings → Harnesses**, EasyCode runs that harness's own sign-in
command in a terminal on your machine. You sign in with the vendor, as you would in your own terminal. No agent or
session can start Connect.

Your git and `gh` logins work the same way. EasyCode runs git with the login you already have and never reads it.

## What stays on your machine

- Your harness logins and their tokens.
- Your working tree: the code in your repos.
- Sessions in your **Personal** space. Nothing about them syncs, not even their metadata.
- The content of an org session you mark **Private**. Its metadata still syncs.
- The local runner's cache. It reads your harness's own logs and leaves them where they are.

## What leaves your machine

**Settings → Privacy & data** lists what this machine sends, first for the machine and then for each space. In
an org space, a team session sends:

- **Metadata**: the harness, model, cost, status, title, the repo remote and branch, and the commits' SHAs. Your
  org can strip titles.
- **Content**: the redacted transcript, capped tool results and the patch. Mark a session **Private**, or have your
  org turn content off, and no content is sent.

**Private** hides a session's content, not the session. It stays in your team's **Sessions** list, marked Private,
with the metadata above. Making a session Private deletes the content already stored for it, and later turns aren't
uploaded. For work your org shouldn't see at all, use your **Personal** space.

Before anything is recorded, the runner redacts secrets it recognises, such as API keys and tokens, from the
session record.

The desktop app also sends:

- **Update checks**: your IP address, app version, OS, CPU and update channel. A policy file from your organization
  can turn them off.
- **Your device**, once you sign in: its name (the hostname by default), OS, CPU and version.
- **Crash reports**, only from a build that includes them, scrubbed of prompts, paths, tokens and emails.
- **Product analytics**, with ids only, and only with your consent. You can decline or withdraw it.

## Keys you give EasyCode

API keys and tokens an admin gives EasyCode, such as a voice provider key, live in an encrypted vault. Each key is
encrypted on its own. A value is used only by the cloud and never reaches your machine, a harness, a log or a
session record. The settings screens show whether a key is set, never the key.

## Where data lives

Your org's data is stored in the EU. Content is kept for 90 days and metadata for 13 months. Every org's data is
kept apart: each query is scoped to your org, and the database checks it again.

## Two domains, on purpose

The app, sign-in and your session live on `easycode.studio`. Anything that runs code nobody reviewed, such as
artifact previews and prototypes, runs on `easycode.run`, a separate domain with no login, no cookie and no access
to your session. Each artifact gets its own address there, so one can't read another.

## Local app and desktop app

The runner and the app listen only on your own machine (`127.0.0.1`) and refuse requests from other sites. The local
app opens only in a browser you paired with it. The desktop app keeps your sign-in in the OS's secure storage; the
runner never sees it.

## What agents can and can't do

- An agent never approves a gate. Only a person, in the web or desktop app, decides one.
- An agent can't merge or push to your default branch. EasyCode refuses the known commands for it; how strictly
  depends on the harness, so treat it as a guard, not a sandbox.
- Text from a document, a ticket or a web page reaches an agent as data, never as instructions.
- An agent never publishes a library change, even in an admin's session.

## Controls for owners and admins

Admins set what team sessions share in **Settings → Sessions**: content on or off, and titles kept or stripped.
Every sign-in, role change and key action is in the audit log. See [Roles and access](/overview/roles-and-access)
for who can change what, and [Network and firewall](/setup/network-and-firewall) for the hosts to allow.

## Report a problem

Write to `hello@easycode.studio`. A person reads every report.
