AI CodeOps

AI CodeOps trust center

Last updated: Oct 11, 2026

Service status — open beta

Live component health is on the status page (refreshed from GET /api/status). Uptime monitors should use GET /api/health — it returns ok, degraded, or down without marketing claims.

  • The service is checked continuously by automated health probes.

Certifications and SLAs

We don't claim SOC 2 or uptime SLAs until they're published here.

  • SOC 2 Type II: not certified.
  • We don't publish an uptime SLA yet; one will be published at general availability.

Subprocessors

When you use the hosted console, these companies process personal data on our behalf. The list is generated from the services this deployment is configured to use, so it changes when they do. Enterprise buyers: see the draft Data Processing Agreement.

SubprocessorPurposePersonal dataRegion
CloudflareNetwork edge for every request: DNS, TLS, CDN and DDoS protectionIP address, request metadata and everything sent to or from the site in transitGlobal
Our data-centre providerHosts the servers, database and nightly database backupsAll data stored in the serviceUnited States
Ollama (Ollama Cloud)AI model that runs AI sessions when a workspace has not connected its own providerTask prompts, repository code and files the session reads, and the generated outputUnited States
Google (Tag Manager, Analytics)Site and console usage analytics, with your consent where requiredPages viewed, events such as sign-up, a pseudonymous browser identifier, IP address and browser detailsUnited States / global
Microsoft (Clarity)Usage heatmaps and session replays, with your consent where requiredClicks, scrolls and page content as displayed (form inputs masked), a pseudonymous browser identifier, IP addressUnited States
Umami (self-hosted by AI CodeOps)Cookieless page-view counts; on the public website, with your consent where required, session replays and heatmapsPages viewed, referrer, browser and device type, country; for replays, clicks, scrolls and page content as displayedOur own servers (analytics.nforge.dev)
SMTP relay (smtp.fastmail.com)Transactional email: sign-in codes, invitations, noticesEmail address and message contentSee provider

Services you choose to connect receive data because you connect them, under their own terms:

  • Google (Sign in with Google)
  • GitHub (Sign in with GitHub)
  • GitLab (Sign in with GitLab)
  • The git provider you connect (GitHub, GitLab, Bitbucket, Gitea or Forgejo)
  • Your organization's SSO identity provider (OIDC or SAML), if your organization sets one up
  • An AI provider your workspace connects with its own key (in place of the platform's)
  • Webhook and MCP server endpoints your workspace configures

We do not use your content (prompts, code, generated output) to train AI models, and we do not sell personal data. With your consent (asked first in the EU, the EEA, the UK and Switzerland), the site uses Google Analytics, Microsoft Clarity and Umami session replays (self-hosted, public website only) to see how it's used; there are no advertising cookies. Every cookie is listed in the cookie policy.

Our public website and documentation may be used by AI search and training crawlers. Your code, prompts and outputs inside AI CodeOps are not: AI CodeOps never uses them to train AI models.

Data handling

You can export your account data, or delete your account, from your account settings in the console, or by emailing [email protected]. An organization owner can delete the organization, which deletes its workspaces and everything in them. What is kept afterwards, and for how long, is set out under "Data Retention" in the Privacy Policy.

Enterprise SSO

OIDC and SAML login are available for verified email domains with active connections. Sign-in starts at /sso/login?domain=, which routes to the appropriate flow; SAML is SP-initiated only (an AuthnRequest via HTTP-Redirect, bound to the browser that started it), so a login started from an identity provider's app dashboard is refused. Details: Enterprise docs.