Privacy
Last updated October 27, 2026
Shepherd lets you connect your own accounts (for example Gmail, Google Drive, Slack, Notion, Linear, or the iMessage and coding-session uploaders on your Mac) and read what they contain as a private, read-only filesystem, through this website, the shepherd command-line tool, MCP clients and optional Modal sandboxes. This page explains what the service stores and who can see it.
Your account
- Sign-in is handled by WorkOS (AuthKit). Shepherd receives your account identifier, email address and name.
- Every account has its own private data space. Being a member of the same company or organization as someone else does not give either of you access to the other's data.
What is stored
- Content of the sources you connect: copies of the messages, documents, files and records the provider returns for the access you granted, with their version history (earlier versions and deletions stay visible in your history).
- Provider credentials (OAuth tokens or API keys you enter) are stored encrypted in the collector database and are used only to read from that provider. They are never shown back to you or sent to sandboxes.
- Device keys for the Mac uploaders are shown to you once; the service keeps only a hash.
- Your scratch space: files you or your agents write to
$SCRATCH. - Derived data: a search/SQL index built from your sources.
- Operational logs: request method, path, status and timing. Logs are not meant to contain your source content or credentials.
Where it is processed
- The website, API, collector and its database run on Railway.
- Collected source files are stored on Modal storage volumes. If you enable Modal workspaces, a read-only mirror of your sources and your sandbox scratch are kept on Modal volumes, and sandboxes you start run on Modal; disabling workspaces deletes that mirror and the sandbox scratch volume.
- The providers you connect process your requests under their own terms.
- This deployment is not configured to send your source content to AI model providers. Agents you connect yourself (through MCP or the CLI) read your data under your control.
Who can access it
- You, signed in to your account, and the agents and tools you authorize with your sign-in.
- The operator of this service administers the infrastructure above and therefore has technical access to it. Shepherd does not claim end-to-end encryption or that operators cannot access stored data.
- Shepherd does not sell your data or use it for advertising.
Your controls
- Disconnect any source or revoke any device at any time; collection from it stops.
- Disable Modal workspaces to delete the Modal mirror and sandbox scratch.
- Delete files in your scratch space at any time.
- Deleting already collected source history and closing your account are not self-service yet: ask the operator (contact below) and it is done manually.
Backups
The collector database and the service's working volume are backed up daily (kept 6 days) and weekly (kept 27 days).
Contact
Operator contact for privacy requests: to be confirmed by the operator. (Operator review needed: legal entity name, postal address and contact email for this service.)