Trust

Subprocessors and Data Flows

Capsule Insights may use third-party providers to operate AI, authentication, database, email, billing, hosting, analytics, and error monitoring features. Actual processing depends on which services are configured in a given deployment.

This is an alpha/beta placeholder. Provider links, retention details, subprocessors, data processing agreements, and international transfer terms should be reviewed before public launch.

OpenAI-specific disclosure

When OpenAI is configured, user inputs may be sent to OpenAI to generate summaries, insights, suggested actions, topic tags, Daily Briefs, Decision Briefs, and personalised interpretation.

AI outputs may be inaccurate, incomplete, misleading, or missing important context. Verify important information before relying on it.

Do not submit content you are not comfortable processing through configured AI providers. Retention and processing depend on provider terms, settings, and Capsule deployment configuration.

OpenAI

AI processing

Optional
When used
Optional: used only when OPENAI_API_KEY is configured.
Data processed
User-submitted text, transcripts, URLs or titles, saved context, preferences, recent topics, and generated prompt context needed to create summaries and insights.
User-facing explanation
OpenAI may process user inputs to generate summaries, insights, suggested actions, briefs, and personalised interpretation.
Provider docs
Provider privacy/security docs link placeholder

Supabase

Authentication and database

Optional
When used
Optional: used when Supabase environment variables are configured.
Data processed
Account identifiers, email, profile data, saved content, summaries, insights, topics, actions, preferences, and related metadata.
User-facing explanation
Supabase can provide account login and persistent saved library data. Without Supabase, Capsule can run in local demo mode.
Provider docs
Provider privacy/security docs link placeholder

Resend

Email delivery

Optional
When used
Optional: used when RESEND_API_KEY and EMAIL_FROM are configured.
Data processed
Recipient email address, email subject, summary or digest content, delivery metadata, and email status information.
User-facing explanation
Resend may send summaries, Daily Briefs, Weekly Digests, and related service emails where email delivery is enabled.
Provider docs
Provider privacy/security docs link placeholder

Stripe

Billing and subscriptions

Optional
When used
Optional: used when Stripe billing keys and price IDs are configured.
Data processed
Checkout session data, customer identifiers, subscription state, plan metadata, invoice/payment events, billing portal metadata, and tax-related metadata where configured.
User-facing explanation
Stripe may process checkout, subscription state, billing portal access, invoices, and payment events. Capsule should not store full card details.
Provider docs
Provider privacy/security docs link placeholder

Vercel

Hosting and deployment

Required
When used
Required or expected for production deployment if Capsule is hosted on Vercel.
Data processed
Application traffic metadata, request logs, deployment logs, serverless function logs, environment configuration metadata, and operational telemetry depending on project settings.
User-facing explanation
Vercel can host the Next.js application and API routes. Actual logs and retention depend on Vercel configuration and plan.
Provider docs
Provider privacy/security docs link placeholder

Analytics provider placeholder

Product analytics

Optional
When used
Optional: disabled or placeholder unless a provider is configured.
Data processed
Privacy-conscious product events such as page views and feature usage. Analytics should not intentionally include transcripts, summaries, secrets, payment card details, or full email content.
User-facing explanation
A future analytics provider may help understand product usage. Provider choice, consent approach, and event payloads should be reviewed before launch.
Provider docs
Provider privacy/security docs link placeholder

Error tracking provider placeholder

Error monitoring

Optional
When used
Optional: placeholder unless a provider such as Sentry is configured.
Data processed
Error messages, stack traces, route or API context, browser/runtime metadata, and redacted diagnostic details. Sensitive content should not be logged.
User-facing explanation
A future error tracking provider may help diagnose crashes and API failures. Transcripts, secrets, and payment details should be excluded.
Provider docs
Provider privacy/security docs link placeholder

Related policies

See the Privacy Policy, Security page, and Data Retention page for more context.