Privacy

Yesfold privacy notice

Last updated: 2026-10-20. Invite-only alpha draft.

Yesfold is a company-brain execution platform for startup teams. AI proposes the work, a person sets how much it may do on its own, and the team executes (optionally connecting your own AI over MCP). This notice covers the personal data we process and your rights.

What we collect

  • Account: your name and email, for sign-in (magic link or password) and to show who did what.
  • Membership: which workspaces you belong to, your role and teams, your timezone, and any chat handles (Slack or Mattermost) linked for notifications.
  • Work: tasks, comments, decisions, notes, attachments, and an append-only audit log of actions. New audit entries record people by id only, and no entry is ever shown with a name or email.
  • Your private work: drafts your own AI captured and your personal tasks. Only you see their content; an Owner or Admin sees counts, never content.
  • Your AI connections: the connections your own AI uses to reach Yesfold (MCP), each acting as you.
  • AI usage: for each AI call, who made it, when, which model, the token counts and the cost. Never the prompt or the reply.
  • Operational: chase and notification history, and your session cookie (httpOnly).

We never put finance values, secrets, or chat tokens in logs, queues, or telemetry.

Why

To run the product for your team: sign you in, keep your data inside your workspace (row-level security), assign and chase work, and keep an audit trail.

AI features (onboarding drafts, Ask Yesfold, backlog triage, thread to tasks) send the relevant task or text to an AI provider: the AI Yesfold provides (the operator's default provider), or your own or your workspace's key if one is added. The providers are listed in the sub-processors list.

Where AI runs. By default, the AI Yesfold provides sends that text to its default provider, which may process it outside the EU, including in the United States. Two workspace settings change this, both in Settings → AI and both changed only by an Owner or Admin:

  • Keep AI on our data in the EU. The AI Yesfold provides sends your workspace's data only to an EU-resident endpoint, or refuses and the feature says so. For an endpoint whose region Yesfold can't check itself, "EU-resident" is the operator's declaration. Your own or your workspace's key is not changed by this setting.
  • Only our AI, for a workspace with its own AI key. The AI Yesfold provides is never used for that workspace; when the workspace's own AI fails, the feature says so instead of falling back.

Your own or your workspace's key is used as you set it up, wherever its provider runs it. Each AI call records whether it went to an EU endpoint, a non-EU one, or one Yesfold can't place.

AI output always enters as a proposal. A proposal is released (assigned to a person) only when a person approves it, or when an autonomy policy your workspace configured releases it. That policy is an Owner or Admin setting: manual by default, bounded, recorded in the audit log with its cause, and never used for finance, governance or destructive actions. The AI never acts on its own, never approves its own work, and cannot read or change that policy. Finance values are never sent to an AI provider. The autonomy policy is your workspace's own configuration and adds no sub-processor.

Sharing

Only with our sub-processors, and only as needed to run the service. Chat, tracker and telemetry processors are engaged only when your workspace connects them.

Your rights (incl. erasure)

You can ask for access to, correction of, or erasure of your personal data. An Owner or Admin can remove a member from the workspace, which erases them there: their assignee details are scrubbed, their chase logs and private work deleted, their AI connections and pending invites revoked, and their membership removed. If it was their last workspace, their sign-in identity (name and email) is anonymized and their sessions revoked. The erasure is recorded in the audit log by user id only. Contact: privacy@yesfold.ai.

Security

Tenant isolation through Postgres row-level security; the app runs as a non-superuser database role. Chat bot tokens, webhook secrets and AI keys are encrypted at rest (AES-256-GCM). Every secret is provided through ESO and OpenBao, never baked into the build.