omniralph

Privacy policy

Last updated: October 9, 2026

This policy explains what this Omniralph deployment ("the service") collects, why, who it is shared with and how long it is kept. Omniralph is self-hosted software; this deployment is run by its operator ("we"). Using the service is also subject to the terms of service.

What we collect

  • Your account. When you sign in with GitHub or GitLab: your name, email address, profile picture and account ID, and your session. We also store your organizations, roles and invitations, your active organization and your theme.
  • Code-host data. For repositories an admin connects: repository details, pull and merge requests, their diffs and comments, CI results, and webhook events. Agents clone and fetch these repositories to review or change them.
  • Reviews and runs. Review findings, dismissals and the rules learned from them, coding tasks, their stories and messages, jobs and their logs.
  • Linear data. For a connected Linear workspace: the issues, epics, comments and agent sessions delegated or mentioned to Omniralph.
  • Chat data. For a connected Slack workspace or Discord server: the workspace or server name; the messages that mention Om and the replies in its threads, with their authors' user IDs and display names; and, in Slack, the email address on the author's profile, used to recognize members of the organization. Other messages and direct messages are ignored and not stored. Chat accounts linked to an Omniralph account are stored with that link.
  • Agents. Agent hosts' names, versions, enrollment and token records, and an audit log of their requests.
  • Credentials. Integration tokens (such as Slack bot tokens and Linear tokens) are stored encrypted.

Cookies

The service uses only cookies it needs to work: the sign-in session and short-lived cookies that protect integration installs against forgery. There are no advertising or analytics cookies.

How we use it

Only to provide the service: to sign you in and enforce access, to review code, to build Linear issues, to answer questions in chat, to show the organization its data in the control panel, and to keep the service secure and running. We don't sell your data or use it for advertising.

Who we share it with

  • Members of your organization see the organization's data. Nobody outside the organization sees it, and its jobs only run on its own agents.
  • AI model providers. Agents send code, diffs, issues and instructions to Anthropic's Claude to review and write code. Chat questions and the organization's data needed to answer them are sent to a model through the Vercel AI Gateway.
  • Infrastructure providers. The control panel runs on Vercel and stores data in a Postgres database (Neon). Agents run on hosts chosen by the operator.
  • Connected services. Reviews, comments, commits, pull and merge requests, issue updates and chat replies are posted back to GitHub, GitLab, Linear, Slack and Discord, where their own privacy policies apply.
  • When the law requires it.

How long we keep it

Data is kept while the organization uses the service. Disconnecting a code host, Linear workspace, Slack workspace or Discord server revokes its credentials and stops new data from it; removing a code-host connection deletes its repositories. Short-lived records, such as webhook deliveries, rate limits and one-time link states, are deleted automatically. To have an organization or account and its data deleted, ask the operator.

Security

Traffic is encrypted in transit, integration credentials are encrypted at rest, agents only get short-lived, scoped credentials, and each organization's data is kept apart from the others.

Your choices and rights

  • Unlink a chat account under Settings › Linked chat accounts; an unlinked Slack account isn't linked again by email.
  • Leave an organization, or ask its admins to remove you.
  • Ask the operator for a copy of your data, or to correct or delete it. Depending on where you live, you may have further rights under data protection laws.

Changes

We may update this policy. The date above shows the latest version.

Contact

Privacy questions and requests go to the operator of this deployment, or to your organization's admins.

Terms of servicePrivacy policy