09

Your data

What Umtri receives, what it never sees, and how you take it back out.

A map, not a copy

Umtri keeps a map of your project — what it is made of and how the parts connect. It is not a copy of your code, and it does not look at your repository.

What Umtri receives is only what you or your AI agent write into it, through the app or through MCP:

  • the names, descriptions and types of the parts of your system (trunk, limb, twig, leaf, vein)
  • for each part, the file paths it lives in (implements) — paths only, never the contents
  • the connections between parts, and their labels
  • bug titles, descriptions and solutions
  • wiki pages you write
  • season labels and the ground’s name

What Umtri never sees:

  • your source code or any file contents
  • your git history — Umtri has no git integration and runs nothing on your machine. A commit shows up on a ground only because your agent sent its SHA and the list of changed paths
  • environment values, keys, passwords, credentials
  • your customers’ data

Your agent is told the same thing: the MCP server’s rules say to keep secrets, credentials, personal data and verbatim code out of every node and page. If you ask your agent whether something is safe to send, it can read umtri://about/data and answer from it.

Where it lives and who can see it

  • Stored on servers in Seoul (AWS) in PostgreSQL. Every connection uses TLS.
  • No ground is public. Only members of the organisation that owns the ground can see it — and in a team, only the people assigned to that ground. The demo is separate, fictional data.
  • API tokens are stored as SHA-256 hashes. The plain token is shown once, when you generate it. A Read token cannot write. You can revoke any token at any time from Settings → API Tokens.
  • Operators access data only to run the service, as described in the privacy policy.

Taking it out, or deleting it

  • Export. Every ground can be exported as one JSON file — nodes, connections, bugs, seasons and wiki — with GET https://api.umtri.io/api/projects/<slug>/export and your token, or by asking your agent to call export_ground.
  • Delete a ground. Deleting a ground removes it immediately. It cannot be undone.
  • Delete your account. Settings → Delete account removes your account and your personal grounds immediately. Content you wrote in a team’s ground stays with the team, without anything that identifies you.
  • Server backups are taken daily and expire after about two weeks. Nothing is kept indefinitely.

Umtri is built for teams that want their agent to keep a shared map. If your organisation’s rules do not allow a map of your system to live outside your own infrastructure, tell us at support@umtri.io — that is exactly the case we are planning a self-hosted edition for.