Lean reads what it needs. It writes only with your permission.

What Lean reads, what it never reads and who decides when an agent acts. Request the SOC 2® report, our policies and our subprocessors in our trust center.

Read-only

Context

Lean connects to your tools and learns what normal looks like for each team. Metadata only.

GitHubJiraSlackDatadogDatabricks
Read-only

Diagnosis

Every leak priced, by team. With the same metadata, without asking for one more permission.

Writes with your permission

Treatment

Agents act only where and how you authorize them, at the level of autonomy you choose.

Lean · Unblock agentComment on PR #482. Permission: comment on PRs.

Read-only for measuring. And what it never reads.

Each integration asks only for the read permissions it needs. In context and diagnosis, Lean works with metadata.

Reads

  • Who did what and when: commits, pull requests, reviews, tasks and deployments.
  • Who messages whom and when, in chat.
  • How many logs there are, and how long queries take and what they cost.

Never reads

  • The text of messages.
  • The content of logs.
  • The text of your queries.
See the detail in Integrations →

Writing is a separate permission. You grant it, at the level you choose.

1ProposesEvery agent starts here

The agent proposes each action and your team approves or rejects it.

2With permissions

What you marked as allowed runs on its own. Everything else is still proposed.

3Automatic

The agent acts on its own, within the permissions you gave it.

  • With the account of whoever turns it onIn Jira, GitLab, Bitbucket and Azure DevOps, writing needs the personal connection of whoever turns the agent on. Its notices go out from their chat account.
  • One permission per actionNotify the owner, comment on tasks or PRs, change a task's assignee, close tasks. Closing a PR is always asked.
  • The tool enforces the scopeThe agent writes only where you authorized it. What can't be executed isn't offered for approval.

Encrypted data, in the United States. Sign in with your SSO.

  • In transit and at restAll traffic to Leanmote uses TLS 1.2 or higher. The database, its backups and the session cache are encrypted with AES-256.
  • Write tokens with their own keyThey're stored encrypted, apart. The application can store them but not read them.
  • Your data doesn't train modelsNot ours, not anyone else's.
  • SSO with SAMLOn the Enterprise plan, your team signs in through your identity provider, with SCIM provisioning, and you can enforce it for the whole organization.

Security questions

Do you store our source code?

No. For measuring, Lean uses metadata: commits, pull requests and reviews, with author and time. If you give an agent access, it can read code while it works on a problem, at the level of autonomy you choose, but we don't store it.

Can an agent write to our tools without permission?

No. Writing is a separate permission, per action, and in Jira, GitLab, Bitbucket and Azure DevOps it uses the personal account of whoever turns the agent on. You choose the level of autonomy: it proposes and your team approves, it acts only on what you already allowed, or it acts on its own within those permissions.

Where is our data stored?

In the United States. The database, its backups and the session cache are encrypted with AES-256, and all traffic to Leanmote uses TLS 1.2 or higher.

Do you use our data to train AI models?

No, neither ours nor anyone else's.

Do you support SSO?

Yes, on the Enterprise plan: SSO with SAML and SCIM provisioning. You can enforce it so your whole organization signs in only through your identity provider.

How do we remove Lean's access?

By disconnecting the integration in Leanmote, or directly in the tool: for example, by uninstalling the GitHub App or deleting the token in Databricks.

How do we request the SOC 2® report?

In our trust center. That's also where you request access to our policies and our list of subprocessors.

How do we report a vulnerability?

Write to us at security@leanmote.com.

The SOC 2® report, in the trust center.

That's where you request access to the report, our policies and our list of subprocessors.

AICPA SOC for Service Organizations

SOC 2® audited by an independent CPA firm.

Another security question? Write to us at security@leanmote.com.