Last updated 4 October 2026
spacesheep publishes pages you (or your AI agent) create, and hosts the conversations around them. This page describes exactly what that means for your data. Questions: support@spacesheep.dev.
| Data | Why | Where |
|---|---|---|
| Your email address, a username and profile you choose, and a salted hash of your password if you set one | Identifies your account, your URL namespace, who a space is shared with, and lets you sign in without Google. The hash cannot be reversed — we never see your password | Our database |
| The files of every space you deploy, and their version history | They are the product — a space is served from what you deployed | Our private file storage |
| Space metadata: title, description, visibility tier, org, access list, comments and reactions | Dashboard, access control, and the conversation on a page | Our database |
| Messages you exchange with the agent, on the web or through a connected surface (Telegram, Slack, SMS) | The agent needs the thread to answer in context | Our database |
| Memory: facts your assistants save, conversation turns and their summaries — including the turns of your coding sessions when you install the coding-agent hooks (below) | So every assistant you use can recall context, and so your work across sessions can be summarized | Our database and private file storage; Pinecone when semantic memory search is on |
| Coding-session status and details sent by those hooks: session ID, title, machine, folder, repository, branch and model | Showing your sessions, where each one stands, and how to resume it | Our database |
| Secrets you save (API keys, tokens) and API keys you or a connected app mint | Run worker-mode spaces and authenticate clients. Secret values are never returned by the API, and are redacted from responses that would leak them | Our database |
| Product analytics: page views and feature events, tied to your account | Understanding what people actually use | Mixpanel |
| Request logs (paths, status codes, timings) | Debugging and abuse handling. Retained about 30 days | Our hosting provider |
We do not sell personal data, and we don't use your space content to train models.
spacesheep asks Google for access in three places, each only when you use the feature that needs it:
| Feature | Access | What we do with it |
|---|---|---|
| Sign in with Google | Your email address and basic profile (openid, email, profile) | We keep only your verified email address, which identifies your account. Sign-in asks for no ongoing access. |
| Google Calendar, when you connect it in Settings (one or more Google accounts) | Events on each connected account's primary calendar (calendar.events) | Your agent reads events to answer questions about your schedule, and adds, changes or deletes events when you ask it to. A booking page you publish reads only the start and end times of events on your connected calendars to show which slots are free, and adds the meeting a visitor books. Visitors never see your event titles or details. |
| Google Drive backups, when you turn them on | Only files spacesheep itself creates (drive.file) | A scheduled copy of your spaces and memory, written to a folder in your Drive. We can't see or open any other file in your Drive. |
The tokens Google issues for Calendar and Drive are stored in our database and used only by our servers to make the calls above. When you ask your agent about your calendar, the events it reads are sent to the LLM provider configured for your account, to write the answer; nothing else from your Google account goes to anyone else.
spacesheep's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We don't sell Google user data, use it for advertising, or use it to train AI models, and no person at spacesheep reads it unless you ask us to, it's needed for security or abuse investigation, or the law requires it.
To stop access, disconnect Calendar or Drive in Settings: that deletes the tokens we hold, and for Calendar also revokes them at Google. To withdraw every grant at once, remove spacesheep at myaccount.google.com/permissions.
Who can view is yours to set, per space, in its Share dialog: Only people who were invited (the default), Anyone who signs in (they need the link and a spacesheep account), everyone on a team you share it with, or Anyone with the link (no sign-in; search engines list it only if you also choose to show it on your profile). Anyone with the link means anyone — don't publish anything there you wouldn't put on the open web. Comments are visible to everyone who can see the space.
If you install coding-session hooks on a machine (sessionpipe, which spacesheep sessions install sets up, or the spacesheep CLI's earlier hooks), the new user and assistant turns of supported coding tools — Claude Code, Codex, Antigravity — are uploaded to your account as each turn ends, and each session's status and details (above) are sent as it runs. Installing can also bring in the details of recent sessions already on that machine, and a session's title can come from your first prompt. We use the turns to show and summarize your sessions and to keep your assistants' memory. Credentials are redacted on your machine before anything is sent and again when it arrives, but redaction can miss a detail. Uninstalling the hooks stops future uploads; it doesn't delete what was already stored — ask us to, at the address above.
When you authorize a client — Claude, ChatGPT, Grok, a local agent — through OAuth, it acts as you: it can read, deploy, and share your spaces. Each connection appears in Settings and revoking it there cuts off that client's access.
Spaces, comments, messages, memory, coding-session turns and details, and secrets are kept until you delete them. Deleting a space removes its files and versions. To delete your account and everything attached to it, submit a verified request in Settings → Account → Delete account, or email support@spacesheep.dev from the address on the account; we action it within 30 days. Backups and logs age out on their own schedules (about 30 days).
You can ask for a copy of your data, correction of it, or its deletion, at the address above. If you're in the EEA or UK, the legal basis for processing is performing the contract you signed up for, plus a legitimate interest in keeping the service working and free of abuse.
spacesheep isn't intended for anyone under 13, and we don't knowingly collect their data.
If this policy changes materially, the date at the top changes and we'll say so in the changelog.