Skip to main content

Security & Privacy

This page is the full privacy model behind STAK: what lives only on your machine, what is Cloud-backed, what a public STAK contains, and the isolation guarantees you get when trying one.

Local state

Your desired Environment (main), Skill directories for each agent, and local Project mappings all live on this machine. Local Project mappings in particular are a machine-specific binding only — see Memory & Projects — and are never uploaded or published as part of a Project's identity.

Cloud state

Memory and logical Project identity are private, Cloud-backed state. Cloud storage is what lets Memory and Projects follow you across machines — sign in on a new machine, run stak pull, which also restores your latest staged private Memory generation; stak memory recover remains available for explicit/history recovery — see Workflows for the current sequence.

Public STAK contents

A published STAK contains only portable Skill snapshots — instructions, context, and tool definitions, stripped of anything machine- or account-specific. That is the entire payload. See Sharing for the complete list of what is and is never included.

Credentials

Tokens, API keys, and other auth state are never read, stored in, or published with a STAK. Each agent's CLI handles its own sign-in independently of STAK; STAK only reconciles Skills and launches the agent.

Memory privacy

Memory is private, Cloud-backed state — separate from Skills, and never implied to be part of a public STAK. Backing up Memory is read-only with respect to your agent's native files: it copies allowlisted Memory into STAK's own private store and never modifies the originals.

Isolation guarantees

stak try runs a STAK in an isolated, temporary runtime. It does not mutate main, your normal agent bindings, or any permanent agent state, and the trial runtime is cleaned up afterward. That is the full isolation guarantee — nothing a STAK does inside a trial persists once it ends.

stak try @owner/name -- codex