Last updated October 3, 2026.
embd works with or without an account. In the playground, and when you copy a share link for a small chart, that chart's content stays in your browser and inside the link's hash; it is not sent to our servers. Anyone you share that link with can read its content. Saving or publishing an item, working in a shared workspace, or uploading an image sends that content to our hosted service.
You can sign in by email (a magic link or one-time code), Google, or GitHub. Supabase handles authentication. We use your account email and available profile information, such as your name, to identify your account and attribute shared work. We don't use your email for marketing.
Saved charts, Markdown and HTML documents, comments, revision history, and collaboration metadata are stored in our database. Personal drafts are private to your account; published items are public to anyone with the link. Workspace content is shared with the workspace's members, whose roles control what they can do. Managed workspace images are stored separately in private object storage and served after an access check.
You can give external tools access using workspace agent credentials. These credentials have permissions and expiration dates and can be revoked. Content retrieved by an external agent is also handled by that tool and its provider.
Optional CLI and MCP knowledge-base sync downloads selected documents and referenced managed images to a cache on your computer. Local cache reads require a valid access lease. Revoking access does not remotely erase copies that have already been downloaded or exported.
Personal saved items and workspace documents have separate export controls. Export formats contain different data: source and image exports do not include comments or history; those are available through separate document exports. Moving a workspace document to Trash preserves its source, comments, and history for restoration. Trash currently has no automatic purge. Contact hello@embd.sh to request account removal or discuss deletion of stored content.
Your browser stores your sign-in session locally. It also stores editor recovery data and unfinished comments and replies to help preserve work through interruptions. Signing out does not erase every local recovery copy. Clearing browser storage can remove unsynced work.
If you submit feedback, we store your message, any contact details you provide, the page path, browser information, and your account identifier if you are signed in.
Our host may keep standard security and operational logs for site requests, including IP address, user agent, requested path, and timestamps. Those logs help keep the site available and secure.
We use cookieless Vercel Web Analytics to count page views. We exclude workspace, login, and authentication-callback pages, and we do not run analytics inside embedded frames. Operational request logs are separate from analytics. We do not use advertising pixels or ads.
Questions: hello@embd.sh.