Privacy

What this site loads and what skep sends

There is no skep account, no skep-operated service and no telemetry. This page lists every network request the website and the tool can make, and where the tool keeps secrets.

Last updated 2026-11-18.

This website

What your browser loads

  • No cookies, no analytics, no trackers. The site is static files.
  • Hosting. The site is served by GitHub Pages, so GitHub’s server logs apply (see GitHub’s privacy statement).
  • Fonts, icons and search come from this site. The two font files are self-hosted, icons are inline SVG, and the search index is loaded from this site the first time you open search. Your search terms stay in your browser.
  • Two requests go to other services. After a page loads, your browser asks api.github.com for the repository’s public numbers and pypi.org for the latest version. Those services see your browser’s request; this site receives nothing. If either request fails, the page keeps the values it was built with.
  • One cache, in your browser. The two responses are kept in sessionStorage for up to an hour so the next page does not ask again. It is cleared when you close the tab and is never sent anywhere.

The skep tool

What stays on your machine

  • No account, no skep service, no telemetry. skep has no usage reporting, no analytics client and no update check. skep onboard prints telemetry: none and that is the whole of it.
  • State is local. Everything lives under $SKEP_HOME, or ~/.skep by default: a SQLite store (runs, events, approvals) and an audit directory of files (patches, evidence, worker logs, the policy decision log).
  • The web UI listens on loopback by default. skep serve binds 127.0.0.1 and requires its token. --host changes the address, and the container image starts with --host 0.0.0.0.

The skep tool

What skep sends, and when

Every outbound call goes to a service you configured or follows an action you approved. This is the complete list.

Outbound calls skep itself can make
Goes toWhen
The model provider’s APIEvery assistant turn and every worker model call; a health probe of each configured provider about every five minutes; skep doctor.
chatgpt.comOnly when the assistant or a Codex project is set to use a ChatGPT plan login.
api.github.com and github.comOnly with the GitHub Copilot provider: the device login and its token exchange.
Telegram, Slack, DiscordOnly for a messenger channel you configured.
Web search and page fetchesWhen the assistant uses its search or read-a-URL tools; each is decided by policy.
Remote MCP serversOnly for an HTTP MCP server you registered.
Your git remote and GitHub (git fetch, git push, gh)Pushing a landing branch and opening or merging a pull request happen only through actions you confirm. A clone skep manages for you (under its own repos directory) is fetched, and its default branch fast-forwarded to origin, before each run; a directory of your own is never fetched for you.
The package index (uv sync)Before re-verifying a uv project, to install its dependencies. The verify command itself then runs offline.
A cloud text-to-speech providerOnly if you choose one. The default is none.
Your mail server and calendar feedOnly if you configure the bundled mail or calendar MCP servers.
Hosts a worker is allowed to reachA run with a network allowlist, through skep’s filtering proxy.
npm, for an ACP adapterWhen you start skep acp govern with an npx command: that is the agent’s own start.

Secrets

Where secrets are stored

  • In files, mode 0600, under the home. Never in the database. That covers model provider keys saved with skep provider set-key or in Settings (llm-secret, llm-secret-<id>), the serve token (serve-token), serve.env, and messenger, webhook and mail secrets (*-secret).
  • Workers get environment variables by name. Only names on the run’s allowlist are passed to a worker.
  • Credential paths are hidden inside the sandbox. A fixed list (~/.ssh, ~/.aws, ~/.config/gh, the agents’ own login files, shell startup and history files, skep’s own secret files) is masked for every sandboxed worker. Other reads outside the workspace are mostly open.
  • An external agent’s credential comes from the environment of the process that starts it. With the opt-in Codex ChatGPT login, a run gets a copy that holds an access token and no refresh token.

Questions

Ask in the open, or privately

Open an issue on GitHub. For anything private, including a security report, use the contact on the security page.