Subprocessors

Last updated: May 2, 2026

A subprocessor is a third-party company Becki uses to operate the service. We list them publicly here so you know exactly who has access to which categories of your data, and why.

For each subprocessor we name: what they do for Becki, what data of yours they receive, and where it's processed. None of these subprocessors use your content to train their models or for purposes other than providing their service to Becki — that's contractually required.

Reminder: raw meeting audio, verbatim transcripts, AI-generated summaries, your meeting notes, and other meeting participants' names and emails never reach our servers in the first place. See the Privacy Policy for what stays local. The subprocessors below only see the data we actually sync — primarily structured memory like decisions, dead-ends, commitments — plus the in-transit transcript text sent to AI providers at extraction time.

Current subprocessors

Subprocessor	Purpose	Data received	Region
Anthropic, PBC Becki-managed mode only Privacy	Becki-managed Claude calls only. Powers extraction of structured memory — decisions, commitments, dead-ends — from meeting transcripts, summarization, and the prose answers Becki gives you. Calls route through Becki's server-side function using Becki's API key, subject to per-user usage caps. If you opt into BYOK in Settings, calls go direct from your Mac to api.anthropic.com using your key — Anthropic is then your processor under your own agreement, not Becki's subprocessor.	Verbatim meeting transcripts (in transit at extraction time only — not retained server-side after extraction); vault chunks during semantic search; conversation context during prose synthesis. Per Anthropic's API terms, content is not used to train models.	United States (with sub-regions per Anthropic's infrastructure)
Voyage AI Innovations Inc. Always Becki-managed Privacy	Embedding model provider. Generates vector embeddings of vault content (decisions, commitments, etc.) and of user queries for semantic retrieval. Voyage is not available as BYOK — it's called server-side using Becki's API key. The embedding setup is part of Becki's product.	Text content of vault entries when first ingested; user query text on every search. No raw transcripts; no conversation history. Per Voyage's API terms, content is not used to train models.	United States
Supabase Inc. Privacy	Authentication, primary application database (Postgres), file storage for release artifacts, and serverless edge functions. Hosts Becki's account directory and the synced cross-tool vault.	Account email + display name; synced structured memory (decisions, dead-ends, commitments, open-loops) and their vector embeddings; meeting metadata (title + timing only); project list; daily briefings.	United States (AWS us-east). Underlying disk encryption: AES-256.
Fly.io, Inc. Privacy	Hosts the Becki marketing site and tester gating backend (becki.io). Serves the appcast XML, gates download URLs, processes waitlist signups.	Email addresses of users on the waitlist; per-tester access tokens; HTTP request logs (IP, user-agent, request path).	United States
Apple Inc. Privacy	Code signing and notarization of the Becki Mac application. Distribution mechanics — every Mac that runs Becki contacts Apple's notarization service to verify the app's signature on first launch.	Application binary metadata at notarization time. End-user devices contact Apple for ticket validation; Apple receives standard verification metadata about the binary, not user content.	United States
Resend (Resend, Inc.) Privacy	Transactional email delivery for waitlist confirmations, tester approval notifications, and account messages.	Recipient email address; subject line; message body of transactional emails; delivery + bounce metadata.	United States

Optional integrations you control

These services only see your data if you explicitly connect them in the app. They are not subprocessors of Becki by default — they're third-party services where you are the customer:

Service	Activated when	Data received
GitHub / GitLab	You add a project from a GitHub or GitLab repository.	Read-only access to commits, pull requests, and issue metadata you authorize. Becki never writes to your repos.
macOS Calendar (EventKit)	You grant Becki Calendar permission for meeting auto-detection.	Read-only access to calendars on your Mac (events, attendees, conference links). Local-only — never sent to Becki's cloud.
Other AI tools you connect via MCP (Claude Code, Cursor, Zed, etc.)	You install Becki's MCP server into the AI tool of your choice.	Vault chunks the AI tool retrieves through Becki, scoped to your account. The AI tool acts on your behalf with your authentication.

How we choose subprocessors

Only when needed for a specific feature we couldn't reasonably build ourselves (LLM inference, embedding models, hosted Postgres, deliverable email).
Each subprocessor must offer commercially reasonable security (TLS in transit, encryption at rest, access controls).
Each subprocessor must contractually agree not to use your data to train their own models or for purposes outside providing the service to Becki.
We prefer subprocessors with public privacy policies and a track record of honoring them.

Notification of changes

If we add or replace a subprocessor that materially changes who has access to your data, we will update this page and notify users via the app or email at least 14 days before the change takes effect — or sooner if required by your jurisdiction. Removals from this list (subprocessors we no longer use) are reflected in the updated date alone.

To object to a new subprocessor, contact privacy@becki.io within the notice period. If we cannot reasonably accommodate the objection, you may terminate your account and request deletion of your data per the Privacy Policy.

Contact

Questions about subprocessors: privacy@becki.io.