ClipSpacesClipSpaces Docs
Back to app

Privacy Policy

ClipSpaces is local-first. By default your boards never leave your browser, and you only share data with us when you choose to sign in or connect a service. This page explains what is stored, where, and why.

Last updated: June 28, 2026

📄This is a plain-language description of how the app works, not legal advice. If you operate ClipSpaces as a product, have your own counsel review it before you rely on it.

Summary

  • Without an account, your boards live only in this browser.
  • Signing in stores your boards in our database so they sync across devices.
  • We don’t sell your data or use it for advertising.
  • Secrets you provide (AI keys, integration tokens) are encrypted at rest.
  • You can delete your boards, your account data, and connected services at any time.

Data on your device

When you’re not signed in, ClipSpaces saves everything locally using your browser’s localStorage and IndexedDB: your space list, the cards on each board, their positions, and the connections and drawings between them. This data stays on your device and is not transmitted to us. Clearing your browser storage erases it, and it does not transfer between browsers or devices unless you sign in.

Accounts & sync

Signing in is optional and uses a one-time code sent to your email address (passwordless). If you create an account, we store:

  • Your email address, to identify your account.
  • Your spaces and their cards, so they’re durable and sync across your devices in real time.
  • Sharing and membership records when you invite others or join a shared space.

Accounts, storage, authentication, and real-time sync are provided by Supabase (a hosted Postgres platform). Access to your rows is enforced at the database level with row-level security, so other users can’t read your private spaces.

Clip AI assistant

The Ask Clip AI feature is opt-in. When you use it, the contents of the current space (text and metadata of your cards, and how they connect) are sent to the AI provider you’ve configured so it can answer questions about your board.

  • You bring your own provider and model — OpenAI, Anthropic, OpenRouter, or a self-hosted OpenAI-compatible endpoint.
  • If you save an API key, it’s encrypted (AES-256-GCM) before storage and is never returned to the browser.
  • Prompts are processed by your chosen provider under their terms; review their policies for how they handle request data.

Integrations

If you connect Notion, we store an access token for your workspace so the app can import and export pages on your behalf. Tokens are held server-side with restricted access and are removed when you disconnect the integration.

Collaboration

In a shared space, your cursor position, name, and edits are broadcast to other members so you can work together live. For signed-out same-network sharing, two devices connect peer-to-peer over WebRTC; board data travels directly between the participants and is discarded when the session ends. To match devices on the same network we use a salted hash of your public IP address — the raw IP never leaves the server.

Analytics

We use Vercel Analytics to understand aggregate, anonymized usage (such as page views and performance). It is not used to build advertising profiles.

Retention & deletion

  • Local boards: delete them in-app or clear your browser storage.
  • Cloud boards: deleting a space removes its cards from our database.
  • Integrations: disconnecting removes the stored token.
  • Account deletion: contact us to delete your account and associated data.

Contact

Questions about privacy or a data request? Email deitymills@gmail.com.