Privacy Policy

ccccharter ("the service") is a small tool for writing team and role charters. This policy explains what we collect, what we do with it, and how to remove it. It's written in plain language because that's the point.

What we collect

• Account email. When you sign in, we send a magic link to your email and store the address. We never store passwords.
• Charter content. Whatever you type into a charter — purpose, focus areas, measures, decision rights, roles, guidelines.
• Membership. Which orgs you're a member of and your role (owner/member).
• Slack credentials, if you connect Slack: workspace ID, workspace name, and an encrypted bot token. Encryption is AES-256 with an organization-only key.
• Slack-derived signals, if you connect a charter to a channel: counts and short summaries derived from recent messages. We do not persist raw message text beyond the in-flight processing window.

Slack scopes and how we use them

When you connect Slack, we request the following bot scopes:

• channels:history, groups:history — read messages in channels you authorize, only for the channels a charter is connected to.
• channels:read, groups:read — list channels so you can pick which ones to connect.
• users:read, users:read.email — resolve user IDs to display names and emails when summarizing channel signals.
• commands — handle the /charter slash command.
• chat:write — post replies to slash commands and direct messages back to the user.
• team:read — read your workspace name (for display).

We do not read DMs, threads in unconnected channels, files, or any other Slack content. We do not train AI models on your data.

Retention

• Charter content persists as long as the charter exists. You can delete a charter, an org, or your account at any time.
• Slack draft jobs (the in-flight data when you generate a charter from a channel) are kept for up to 24 hours, then permanently deleted by a daily job.
• Slack message text processed during a draft is held only in memory while the job runs; it is not written to disk.
• Charter review signals (computed observations from connected channels) persist with the charter so you can see what was flagged and when. Underlying message text is not stored.
• Logs rotate within 30 days.

Where data lives

Charters and org metadata: Postgres on Supabase (US region by default). Application: Vercel (static frontend + serverless functions). Email magic links: Resend. AI drafts: Anthropic Claude. We send only the messages we read for a draft; we don't send other org data, and we don't enroll your data in model training.

Sharing

We don't sell or trade your data. We don't share it with third parties except the sub-processors listed above (Supabase, Vercel, Resend, Anthropic) where strictly necessary to operate the service.

Revoking and deleting

• Disconnect Slack: org settings → Connectors → Reinstall (with new scopes) or remove. You can also uninstall the ccccharter app from Slack's workspace settings — that revokes the token immediately and our endpoints stop working until you re-install.
• Delete a charter: from the charter's Settings tab. Removes the charter and its version history.
• Delete an org: from org Settings. Removes all charters, member relationships, and the Slack connection.
• Delete your account: email clay@cpj.fyi. We'll remove you from every org and delete unclaimed data tied to your address.

Contact

Privacy questions, deletion requests, or anything that requires a human: clay@cpj.fyi.