Your data

Your data is yours

We don't sell your data, and we don't use what you put into Stele to train machine-learning models — beyond features you explicitly turn on inside your own account. No advertising, no cross-context tracking. You keep ownership of your content; Stele stores and serves it back to you.

This page is the plain-language summary. The binding version — what we collect, how we use it, and your rights in legal terms — is the Privacy Policy.

What stays on your machine

The CLI and the plugin run on your own computer. Your credentials and local cache live there, and we don't have access to them. Backfill works the same way: your agent reads your code locally, and only the findings you approve are ever written to the record. Your source code isn't uploaded to us. What reaches the hosted service is the knowledge and tasks you choose to keep.

Where the record lives, and how it's kept separate

The graph itself is stored on managed cloud infrastructure, encrypted in transit. Every project is isolated from every other: you only ever see the projects you're a member of, enforced at the data layer rather than left to the application to remember. A project you're not part of is not something your account can reach.

Take it with you, anytime

From Account → Security in the app, you can export a complete copy of your data as a single file — your profile, your project memberships, and every node you've authored. No request email, no waiting on us. It's a plain, portable format you can read, archive, or move elsewhere.

Delete your account or a project

Same place, no ticket required. You can delete your account — and every project only you belong to — yourself. When you delete a project, its content leaves our active systems within 30 days; backups roll off within another 30 as they rotate. Deletion is yours to trigger and it actually removes the data, rather than just hiding it.

The one exception: public projects

Projects are private by default. You can choose to make one public — and that's the single case where your record is visible beyond you and your team. Public projects appear in the discovery feed for anyone to read; everything else stays yours alone. It's opt-in, per project, and reversible.

Once a project is public, its settings include a README badge builder. Build a row of small badges that show your project's live graph counts — knowledge, tasks, components, documents, and more — each linking back to your public page. Choose a style and color, and whether the badges render light, dark, or follow the reader's theme automatically; then copy the Markdown (or HTML) snippet. The badges re-read your graph on every load, so they stay current with no rebuilds.