Privacy

cells.garden: the web app, the Chrome extension and the Obsidian plugin. Updated 23 September 2026.

Without an account

Your garden stays on your device, in the browser's storage for the site or the extension, or in Obsidian. Garden content is not sent to our sync service unless you choose to sign in.

With an account

Signing in is optional. It syncs your garden between devices and lets you share gardens and plants. For that we store:

• your email address and authentication information needed to keep you signed in (sign-in is handled by Supabase Auth); if you continue with Google, Google also provides your name and profile picture. cells.garden never receives your Google password, and raw passwords are not stored by the app;
• a display name and your generated or drawn avatar;
• your gardens and plants: their names, the text in their cells, and their layout;
• who shares which garden or plant with whom, invite links, plants offered to friends, and cell assignments;
• assignment notifications and whether you have read them.

Synced account and garden data is kept by Supabase in the EU (Ireland). Garden content is readable only by you and the people you explicitly share that garden or plant with. Google is used only when you choose Google sign-in. The website and static OAuth return pages are hosted by Vercel.

Optional push notifications

If you turn on notifications in the web app, we store this device's push subscription address, encryption keys and browser description. We send encrypted assignment notifications through your browser's push provider (such as Apple, Google or Mozilla). A notification includes the sender's display name and the assigned cell's text, which may appear on your lock screen. Turn notifications off in Settings or sign out to unregister this device. Expired subscriptions are removed when the provider rejects them.

What we do not do

No analytics, no ads, no behavioural tracking and no sale of user data. We do not use garden or account data for advertising. We use user data only to provide, secure, sync and share the cells.garden features the user asks for.

Chrome Web Store Limited Use

Use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. We do not allow humans to read private user data except when the user explicitly asks for support involving specific data, when necessary for security, or when required by law.

The Chrome extension

It shows your garden on the New Tab page, in the side panel and in the toolbar popup. It requests sidePanel so it can provide the side-panel view, and storage so the extension service worker can temporarily hold the nonce and return result needed to complete an optional Google sign-in across tabs. Garden data itself uses the app's local storage and, after sign-in, Supabase sync. The extension has no host permissions and does not read the pages you visit, your browsing history, or website content from other sites.

Deleting your data

Without an account, clearing the site's or the extension's storage removes your garden. With an account, ask for deletion through GitHub issues, and the account and everything it owns will be removed.

Questions

Open an issue at github.com/lukketsvane/cells.garden. The code is open source under Apache-2.0.