These are the third parties that process data to run Nibbin. We publish the named list here and update it before anyone new begins processing your data. Your Field Study screen captures never reach any of them — they stay on your device by architecture (see the Data & AI page).
| Subprocessor | What they do | Data they process | Region |
|---|---|---|---|
| Vercel | Web application hosting & delivery | App traffic; aggregate usage analytics | United States / global edge |
| Supabase | Postgres database & the encrypted token vault | Account data; connection tokens (KMS-encrypted in the vault — we never store them in plaintext) | United States |
| Anthropic | Large language model inference (the Grovekeeper, scan summaries, the work you delegate) | Only the content a given task needs; contractually barred from retaining or training on it; never your raw study data | United States |
| Voyage AI | Text embeddings for agent-memory semantic retrieval | Already-redacted derived memory text (facts, preferences, entities) — never raw email or study content | United States |
| Resend | Transactional email (Field Notes, account mail) | Your email address and the message content we send you | United States |
| Stripe | Payments & billing | Billing details — Stripe handles card data directly; we never see full card numbers | United States |
| Google / Gmail + Calendar | Email + calendar connectors — read and write scopes requested at connect (with your explicit OAuth grant); execution gated by owner-set action level (Observe / Draft / Act) | Email metadata and message content you direct a Nibbin to act on; calendar events created by trusted Nibbins; access token held encrypted in the vault | United States |
| Sentry | Error monitoring & performance tracing | Stack traces, request metadata, and application events — no user-generated content | United States |
| Telegram | Inbound and outbound bot messages (reach-me channel) | Chat ID and message content for notifications and inbound commands you initiate | Global (Telegram infrastructure) |
| Twilio | SMS delivery (reach-me channel) | Your phone number and message content for notifications you request | United States |
| Meta / WhatsApp | WhatsApp messaging (reach-me channel) | Your phone number and message content for notifications you request | United States / global edge |
Your Field Study screen captures and recordings (processed and deleted on your device — the capture component has no network capability); your vault tokens in readable form; and your raw connected-service content beyond the specific task at hand. Only redacted, structured text leaves your device, and only on your explicit action.
Changes to this list
We update this page before adding any new subprocessor. New service channels under development (for example, text-message and chat notification providers) will be listed here, with their region and the data they process, before they ever handle your data.
Questions, or something here that doesn't match what you see in the product? That's a bug — tell us: hello@nibbin.com