Privacy
What Plexiform keeps locally, what team features share, and who can read it.
Beta notice. This page summarises the beta's privacy notice, which is a draft and hasn't had its legal review yet. Where they differ, the notice inside the app wins.
In short
The app has a shorter version of this page too: Preferences → Privacy → "What leaves your machine, in plain words".
- The desktop app: no telemetry, analytics or advertising trackers. We do not sell your data. Team sharing and this website have separate disclosures below.
- On for new installs: answering permission prompts from the widget. Existing installs keep the setting they had; Preferences turns it off.
- Off by default: calendar, calendar subscription links and voice questions. Remote device pairing is optional.
- On by default: checking GitHub for pull requests and builds through your own
ghlogin, if signed in, and reading your Focus status on this computer. - Team boards: your cards, handovers and run progress go to your team's hub. The hosted hub is
app.plexiform.dev; a team can run its own. Signing in shares your account name and email with that hub. - Release candidate: supported sessions in a signed-in team workspace are automatically shared with that team to watch (the owner can allow sending for a session). In the chat preview, a chat you share shows teammates only the messages and replies from then on, and the hub stores only that the share exists. The sharing policy below describes prepared release behavior, not confirmation that this candidate is already published.
- Community gallery: only when you press Fetch or Refresh in the app's gallery, it downloads the gallery list from
plexiform.dev. No account or device identifiers are sent; Cloudflare sees your IP address, as for any download. Adding an item happens on your computer and sends nothing. - Update checks and downloads: the app's update feature asks
download.plexiform.devfor newer versions and downloads when requested. This reveals your IP address and app version. - Installing: the installer script (
plexiform.dev/install.sh) and the download page's manual links get releases from GitHub (api.github.comandgithub.com), not fromdownload.plexiform.dev. The download page asksapi.github.comfrom your browser for the latest release. GitHub sees your IP address, as it does for any download. - Cloudflare serves this website and passes hosted hub and update-check traffic through. An injected Web Analytics beacon is described below.
- Crash reports: recorded and scrubbed on your computer only. Sending them is not built yet (there is no receiving endpoint); when it is, it will stay off until you opt in.
What stays on your computer
- The usage reader examines Claude Code conversation logs locally to calculate tokens and cost. Its usage record keeps counts and costs, not a copy of the full conversation.
- Local Tasks keeps the task text you enter, messages you send, AI activity and replies, and checkpoints on this computer. This is different from the usage reader.
- Session state includes folder, state, tool and model labels, task counts and bounded error or reply snippets. If you enable widget answers, temporary requests can contain tool input, plan text or questions while an answer is pending.
- Your settings, rules and cameo photos stay locally unless you explicitly export or share them.
- Voice is turned into text on your device. Audio is not written to disk.
Local storage does not mean all content stays local when you use an AI provider, a team board or a shared session. Those flows are described next.
What leaves, and when
- GitHub: pull-request and build checks through your own login, about every 90 seconds, only if
ghis installed and signed in. - Your AI tools: prompts and task context go to the provider you choose under that provider's terms, using your existing login. Plexiform can hold the messages you select for Tasks or a supported session channel to route them.
- Updates: the app's update checks and update downloads go to
download.plexiform.devand reveal IP address and app version. - Installing: the install script and manual download links use GitHub (
api.github.com,github.com), which can see your IP address. The script sends nothing else and checks the file's SHA-256 before installing. - A calendar subscription link: fetched over HTTPS only if you provide one.
- Your team's hub: board card text, handovers, run progress, member names, linked repository identity and your signed-in account name and email. Credential-like strings and home-folder paths pass a redaction filter, which is not a guarantee that all sensitive text will be removed. The hub operator can read content you send it.
- Phone browser app (release candidate): static app files are served by Cloudflare Pages at plexiform-phone.pages.dev. Account and session requests go to app.plexiform.dev. Connecting uses your existing Google/GitHub hub sign-in and explicit confirmation; the phone keeps a limited credential in encrypted browser storage. Command approvals require separate pairing and passkey confirmation. Physical-device and independent security acceptance remain pending.
- Optional crash reports: off by default, with renewed consent. New reports send only app version, OS family, processor type, time, random report id, and fixed error type or renderer reason/code to app.plexiform.dev. No error text, stack traces, paths, prompts or account identifiers are sent. Reports are capped at 1000 and retained for 30 days plus hourly cleanup. The hub and Cloudflare can see your network address.
- Agent mail (free): a question or handoff your AI drafts for a teammate is held on your team's hub, unseen by them, until you read the exact text in the app and press Send; an unsent draft expires after one hour. Your AI reads back only the replies to its own drafts. Seeing teammates' AI questions is off until you turn it on, and nothing reaches your AI or starts work unless you choose to.
Team sessions in the release candidate
Sessions started in a signed-in team workspace, and Claude terminal channels you deliberately attach there, are automatically shared with that team: sessions Plexiform starts to watch only, and terminal Claude channels you attach on purpose to watch and send. You can allow sending for a session in Overview. Sessions shared before this change keep the access they had. Personal sessions and unrelated provider chats stay separate. Current team-board runs are visible to team members without a separate private-session share. Automatic sharing does not attach an unconfigured terminal or approve provider permissions.
Owners, admins and members can message a supported current session; viewers can watch. Messages the session processes use the session owner's provider quota and existing permissions. Stop a private-session share in Overview or disable automatic team sharing in Preferences. Removing membership or revoking access stops future authorized access; it does not erase messages already stored as team-board history.
Live session relay: selected messages and correlated replies pass through the hub in readable form. The relay holds message text in memory rather than writing that relay text to its database. It does not export a transcript from before sharing. A transport write alone is not proof the agent accepted or answered.
Board task inbox: messages, receipts and replies are stored durably on the team hub as task history and are readable by its operator and authorized team members. The agent must read its inbox and acknowledge or reply. Queued does not mean received, acknowledged or completed, and sending does not automatically resume an agent.
Supported interaction is limited to available Claude or Codex runners and explicitly configured session channels. Activity hooks alone do not provide messaging for every provider. The release candidate still needs provider, packaged-app and team acceptance before release.
This website
Cloudflare hosts this website. A check of the served privacy and download pages found an injected Cloudflare Web Analytics beacon. Its runtime and cookie behavior still need verification in the hosting settings; we do not currently promise an analytics-free or cookie-free website. This is separate from the desktop app's local diagnostics.
If you join the waitlist, we store your email, the agent you said you use, and the time, and use them only to send you a beta invite. Email [email protected] to have it removed.