Your code and data

This page is the practical side: where things are and which switch does what. The privacy policy is the full account, and wins where the two differ.

On Graphide’s servers

Opening a project in Graphide while signed in puts it in Graphide’s cloud. That keeps two things on Graphide’s servers:

• A copy of the code. The files git tracks at the commit you are on, plus changed and new files git does not ignore. A file such as .env that is not in your .gitignore is copied too. Your git history is not.
• The graph. Every node, edge and description of the map, and the file paths, symbol names, signatures and short excerpts of code it holds. It keeps uploading while you work.

Members of a cloud project can read its copy. To see what is stored:

gr cloud code

The telemetry levels below do not change either of these: they are how the cloud half of Graphide works. Signing out stops the graph’s uploads.

Telemetry

Graphide sends three kinds of telemetry, at three levels:

Level	Diagnostics and crash reports	The content of your sessions	Screen recordings of the window
full, the default	sent	sent	sent
diagnostic	sent	not sent	not sent
off	not sent, except a usage ping	not sent	not sent

The content of a session is your prompts, the replies, tool calls and their results, and edits. Diagnostics carry file names, symbol names and paths, but no file contents. At off, Graphide still sends a usage ping: your install and account ids and which five-minute windows you were active in, never what you did.

The first time you run Graphide it tells you this and asks before sending anything. To change the level later:

gr telemetry status
gr telemetry diagnostic    # or full, or off

In the app, it is under Settings, Privacy: Usage data and error reports. For one process, set GRAPHIDE_TELEMETRY=diagnostic or GRAPHIDE_TELEMETRY=off. DO_NOT_TRACK=1, which other developer tools read too, turns telemetry off unless GRAPHIDE_TELEMETRY says otherwise. Neither variable can turn anything on.

Your logs stay on your machine at every level. gr logs shows them, and gr report sends them only when you run it.

The policy’s telemetry section has the detail, and how long each thing is kept.

On your machine

A project’s map is in .graphide/ inside the project, and everything else in Graphide’s own folders, listed under Where Graphide keeps things. gr telemetry status prints where your logs are. Your sign-in is kept in the system keychain.

Deleting things

To delete	Do this
A project’s copy on Graphide’s servers	gr cloud delete <project>, or Delete cloud copy… in the project’s menu in the app’s sidebar. It deletes the code, the graph and its run records for everyone it is shared with, and cannot be undone. Opening the project again while signed in uploads it again.
A project’s Graphide data, here and on the servers	Remove Graphide data, in the start page’s project menu or in Settings. Signed out or offline, only the local data goes, and the app says so.
Graphide on this machine	Uninstall
Screen recordings, sooner than their 30 days	Email hello@graphide.com.
Your account	Email from the account’s address, as the policy says.

Deleted code leaves Graphide’s backups within 7 days.