Data & privacy
What Canopy keeps, who can see it, and what changes the moment you publish.
What Canopy stores
Canopy stores the architecture you put on the canvas. It is not a secrets manager - see Best practices for what not to put in a map.
Isolation with Row-Level Security
Every table is protected by Postgres RLS. Policies tie each row to its owner or workspace, so queries can only ever return rows you're entitled to - the database enforces this independently of the application code.
Public reads (public profiles and published maps) go through dedicated, read-only database functions that return only explicitly-public data and never expose private maps, cost, or member details.
Encryption
- In transit - HTTPS/TLS on every request, including the API and MCP server.
- At rest - data is encrypted at rest by our managed Postgres provider.
Public vs private
- Maps are private by default. A map is only ever visible outside your workspace if you publish it (private share links are coming soon).
- Public maps are clearly marked and appear on your public profile at
canopy.8starlabs.com/w/<handle>. Free public maps carry a small "Made with Canopy" badge.
Private share links Pro Coming soon
Private share links (coming soon) will let you share a single map with people outside the workspace without making it public. Until then, sharing is either workspace-only (members) or public.
Publishing is a deliberate action
Before you publish a map or profile, double-check it contains nothing internal
- once a map is public, anyone with the link can view it until you unpublish it.
Data ownership & deletion
Your data is yours. You can edit or delete maps at any time, and removing a workspace removes its maps. Exports (PNG, Markdown, CLAUDE.md, AGENTS.md) are plain files you own and control once downloaded.
Where to go next
- Best practices - habits that keep a map safe to share.
- Two-factor authentication - the strongest control on your own account.