---
title: Privacy
description: Glade has no account, no telemetry and no crash uploads. Your projects, chats and credentials stay on your machine.
sidebar:
  icon: lock-key
---

Glade runs on your machine and talks to the services you choose. There is no Glade account and no
Glade cloud.

## What stays on your machine

- **Projects and chats.** Transcripts, checkpoints and settings live in `~/.glade` on the machine that
  runs them.
- **Agent sign-ins.** Each agent's CLI keeps its own credentials. Glade never stores them.
- **MCP sign-ins.** Connector tokens are kept in a private file readable only by you, and agents never
  see them. See [MCP servers](/features/mcp-servers).

## What leaves your machine

- **Your agents' requests**, sent by each agent's CLI to its own provider, under that provider's
  terms.
- **Update checks** against Glade's GitHub Releases.
- **The MCP server catalog**, a signed list fetched once a day from useglade.dev.
- **Skill searches** sent to skills.sh and GitHub when you add a skill.
- **Services you connect**, such as GitHub, MCP servers and Tailscale, when you use them.

## No telemetry

Glade sends no usage analytics and uploads no crash reports. Logs are written locally, in
`~/.glade/userdata/logs`, for you to read. Review and redact them before you share them.

`/feedback` opens a GitHub issue draft in your browser. Nothing is sent until you submit it yourself.

## Remote access

[Remote access](/machines/remote-access) connects your devices straight to your machine. There is no
relay or hosted service in between, and connections from public internet addresses are refused.