Skip to main content
Graphify stores the graphs it builds from the repositories you connect, plus the memory your workspace saves. It does not train models on your code. Data is encrypted in transit and at rest, and access is limited to the workspace and repositories you choose.
This page covers Graphify, the hosted product. Graphify Local runs on your machine and sends nothing to Graphify; see Graphify Local below. The Privacy Policy is the binding text.

​
What Graphify stores

To export or delete your data, contact the Graphify team.

​
Model providers and training

Graphify does not train models on your code. To produce results, the hosted service sends code and content to its LLM subprocessors, OpenAI and Anthropic. Under their API terms, neither Graphify nor they train models on it. The full list is on the Subprocessors page. An assistant you connect, such as Claude Code or Cursor, sends what it retrieves from Graphify to its own provider. That traffic follows the assistant’s terms, not Graphify’s.

​
GitHub App permissions

Graphify reads repositories through a GitHub App. You choose All repositories or Only select repositories when you install it, and you can change the selection in GitHub at any time. Read access lets Graphify index a repository, not change it. Applying a suggested fix needs contents write access. For each webhook, Graphify queues only a sanitized copy of the event, not the raw payload.

​
Google Drive

Google Drive uses the read-only Drive permission. Graphify reads file names, contents, links, and modification times in the folders you choose. It never modifies or deletes Drive files. OAuth tokens are encrypted at rest, and the graph is stored on AWS in the United States. When you stop syncing a folder or disconnect Drive, Graphify stops reading it and revokes its token. See Google Drive.

​
Assistant access

Assistants reach Graphify through the hosted MCP server at https://api.graphify.com/mcp.
  • Each assistant signs in with OAuth in the browser. No API key sits in a config file.
  • An agent that cannot open a browser, such as one in CI, uses an API token from the MCP tab of Connectors. Store it as a CI secret, never in the repository.
  • An assistant reaches only the workspace it signed in to, and only repositories indexed in that workspace.
  • Some tools save notes or switch workspaces. Approve a tool call only when that is what you meant.

​
Graphify Local

The open-source graphifyy package runs on your machine, with no account.
  • Code is parsed locally with tree-sitter. Source files are never executed.
  • The MCP server uses stdio by default. The HTTP transport is opt-in and binds to 127.0.0.1 unless you pass --host 0.0.0.0.
  • Semantic extraction sends content only to the model backend you configure.
  • Credential-shaped strings are redacted from labels before they are written to graph.json.
The full threat model is in SECURITY.md.

​
Compliance

Graphify maintains a SOC 2 Type II program. A Data Processing Addendum is available on request. Check the Trust Center for current evidence. For self-hosting, see Enterprise.

​
Report a vulnerability

Do not open a public issue for a security problem. For the open-source engine, use GitHub’s private vulnerability reporting. For the hosted service, contact the Graphify team. The only official channels are graphify.com, the Graphify-Labs GitHub organization, and the graphifyy package on PyPI.