Bring your own storage
Every workspace keeps its diagrams in Zindex’s own storage by default, on every plan. With bring your own storage, an owner of a workspace on Pro or Team can keep them in a private GitHub repository they control instead, so the repository’s access rules, backups and history are yours. Nothing moves unless an owner chooses it in Settings → Storage. Everyone in the workspace still reads the diagrams through Zindex, and agents and tools work as before.
A private GitHub repository is the first location on offer, and more are planned, an S3 bucket among them.
What is kept where
Your repository. It holds every version of every diagram in the workspace, under .zindex/. Each save is one commit by the Zindex GitHub App, signed by GitHub, with the edit’s message as its subject. A version is three files: the exact SVG Zindex drew, a thumbnail, and its record, which holds the scene as written and the version’s details. A manifest lists the diagrams with their IDs, keys, titles and briefs. Each record carries its content and chain hashes, so anyone can check the history from the repository alone, against the chain Zindex reports.
The repository must be private, or internal to your enterprise. Connecting refuses a public one. A connected repository made public goes on hold until it is private again, and a move into it stops, leaving what it copied there.
Zindex’s index. Zindex keeps only what it needs to find, order, check and manage each version and diagram:
- Each version:
- its revision number and time, and when it was deleted
- the saver’s user ID, the app and credential used, and the edit’s
requestIdwhen one was sent, with a hash of the edit - the commit
- the image’s hash, size and engine version, when it was drawn, and whether that was after the save
- counts of what changed
- the chain hash, which covers the content hash
- Each diagram:
- its ID, workspace and owner
- its latest revision number, family, element count and times
- its sharing setting, and who made it public
- who deleted it, and a moderator’s reason if one took it down
- a hash of its key
- Never: a scene, a title, a brief, a key’s text, an edit message or a picture.
Zindex still validates and draws each save, and fetches each read from your repository, holding it in memory only while the request runs. Its database and image store keep no copy, except what someone sends with a problem report or feedback, anonymized by default. Its edge cache keeps published diagrams’ and share links’ pages for up to a minute and their images for up to an hour.
Zindex also records the repository, the branch, the last commit it wrote, and whether the App reaches every repository on the GitHub account. It logs who connected, verified, restored, moved or disconnected, never with content. It keeps account data, MCP call logs, telemetry and the audit log as for any workspace, and share links and stars as metadata.
The App’s access. The Zindex GitHub App can read and write every repository you install it on, so install it on the one repository you connect. If the App reaches every repository on an account or organization, Settings → Storage says so. Zindex reads and writes your repository’s contents only with a token scoped to that repository, which expires within an hour.
Which accounts. The App is installed per GitHub account or organization, and the repository step lists the repositories of every installation your GitHub user can reach, grouped by account. An account or organization the App isn’t on yet gets it from the same step (Connecting).
Your provider. GitHub holds your diagrams under your agreement with GitHub, not as Zindex’s sub-processor, since you choose the repository, install the App and can remove it. GitHub encrypts the repository at rest. The App gets Contents read and write for the whole repository, and Zindex writes only under .zindex/, so use a repository that holds nothing else.
Section 8 of the privacy policy commits Zindex to what it keeps, records and deletes, and its Appendix A.3 states the commitments for the App’s key and tokens.
Checking a repository
Each version’s record holds its scene and its three hashes, under the same names as an export’s line. Check each diagram’s records in revision order as you would the lines of an export, with two differences:
- The hashes are lowercase hex, without the
sha256:prefix. - The image is the SVG file beside the record, not an
image.svgfield.
The latest version’s chain equals the chain a read with view=dsp returns, without its sha256: prefix.
How it works
An owner installs the Zindex GitHub App on one private repository, then chooses it and a branch (Connecting). A workspace that already has diagrams moves first. Zindex copies every version into the repository and checks each copy’s hashes against the index, while saves answer STORAGE_UNAVAILABLE and reads go on. Then it switches and removes its own copies, and its database backups age out within 30 days.
An owner’s Verify now checks every version against the hashes Zindex keeps, and a regular check covers a sample. Zindex detects and reports a rewritten history, though it can’t prevent one.
Limits
- Zindex keeps no copy to answer from. While GitHub doesn’t answer, or past GitHub’s limit of about 80 saves a minute and 500 an hour for the App, a request that needs the repository answers
STORAGE_UNAVAILABLEwith the seconds to wait. - A connection that needs an owner, such as one whose App was uninstalled or whose
.zindex/was changed outside Zindex, goes on hold. Saves answerSTORAGE_HOLD, and reads go on only while GitHub lets the App read the repository (Owner actions and holds).
Leaving
Move back copies every version into Zindex’s own storage, checks each against the index, and leaves the repository as it is. It works on every plan, as long as GitHub lets the App read the repository. Disconnect stops saves and keeps the diagrams readable while GitHub lets the App read the repository. Zindex writes nothing to a disconnected repository.
A diagram deleted for good leaves the branch in one commit, and Git history keeps it. Deleting the workspace, or closing your account for your personal one, removes the connection and the index and leaves the repository untouched.