Skip to content

Security and your data

How SpecsGraph Cloud treats your data: what it stores, what we operate for you, how access is limited, and how you export an organisation at any time.

Your specs stay in your repository

Every published task is committed to your own repository, in the project's spec folder. The published spec is YAML files in your Git history, not a record locked inside SpecsGraph, so anyone with access to the repository can read it, diff it and keep it, with or without SpecsGraph running.

SpecsGraph Cloud holds the working side of the spec: workstreams and their changes, proposals under review, tasks, threads, questions and decisions, and the history of every revision. The export described below covers all of that.

What SpecsGraph stores

DataWhy it is stored
The spec of each project, with every revisionIt is the spec you and your agents edit.
Workstreams, tasks, proposals, threads, decisions and notificationsThey carry the work and the reasoning behind each revision.
Members, their roles and sign-in detailsTo know who can do what in the organisation.
Personal access token details: name, access, projects, expiry and last useTo check agent requests and show your token list. The full token is shown only once, when you create it.
The Git connections and each project's repository settingsTo publish tasks.
Work items, deployments reported by CI and the task keys found in merged pull requestsTo track delivery and derive build status. A pull request's title and body are never stored.
Deploy token details and, for the Jira mirror, the Jira site and an encrypted API tokenTo accept deployments from CI and to read the status of mirrored issues. Neither secret is shown again.
Plan and billing detailsTo run your subscription.

The GitHub App has the permissions listed in Connect GitHub or GitLab, on the repositories you select. GitHub has no permission scoped to one folder, so its contents access covers the whole repository; SpecsGraph writes only inside each project's spec folder, and every write is a commit you can inspect.

Access and tokens

Access to an organisation is limited in several layers:

  • Sign-in. People sign in with the providers SpecsGraph offers, and only members of the organisation can open it.
  • Roles. Each member has one role: Owner, Admin, Editor, Viewer. Accepting staged changes and publishing are limited to Editor and above. Only people publish; agents accept only in projects with Agent autonomy on. Members, roles and teams has the full table.
  • Personal access tokens. Agents authenticate with a token that starts with sgp_, so you can add a secret-scanning pattern that catches a leaked one. SpecsGraph shows each token once and cannot show it again.
  • Scoped and revocable. A token carries an expiry, an access level and the projects you select, and never exceeds its owner's role. Revoking it stops the agent at its next request.
  • Token policy. An Admin sets the organisation's token policy. Removing a member from the organisation revokes every token they own.
  • Deploy tokens. CI reports deployments with a project token that starts with sgd_. It does nothing else: it cannot read the spec or reach the MCP server.
  • GitHub least privilege. The GitHub App reaches only the repositories you select, with short-lived credentials GitHub issues per installation.

Traffic to the web app and the MCP server uses HTTPS. Personal access tokens covers creating, rotating and revoking tokens.

What we operate for you

The operational work of running SpecsGraph is ours, on every plan.

AreaWhat we do
Hosting and network securityWe run the servers, TLS and network access controls.
Updates and security patchesSpecsGraph Cloud stays on the current release, so you never schedule upgrades.
BackupsWe take automatic backups and restore them when you ask.
GitHub AppAn App run by SpecsGraph, ready on day one. You install it on your repositories.

Export your organisation

You can export an organisation at any time, not only when you leave: an Owner opens the organisation settings, then Export and chooses Export. SpecsGraph prepares one archive, for example northwind-commerce-export.zip, with every project in the organisation: the specs with their full revision history, workstreams, tasks, proposals with their threads, members with their roles, and project settings.

The archive contains member names and email addresses and your unpublished work, so store it where you keep other sensitive files. Personal access tokens, the GitHub App installation and billing details are not in it. The archive's layout can change between releases, so build scripts on the YAML files in your repository instead; see Spec files in your repository.

Enterprise options

Enterprise is the plan for organizations with stricter requirements. It includes everything in Team, plus:

  • Dedicated single-tenant hosting in your region
  • Custom contracts
  • Security reviews
  • Named account lead

If your security team wants to review SpecsGraph Cloud before you adopt it, tell us what they look for.

Report a vulnerability

If you find a security issue in SpecsGraph, email us through the contact address instead of posting it anywhere public. Include what you found, how to reproduce it and which version is affected. We acknowledge reports and follow up with you while we investigate.

Next steps