Current and optional service providers

Purpose: Authentication, database, and private file storage.

Data involved: Account, user, organization, workforce, document metadata, and uploaded file data.

Purpose: Application hosting, deployment, runtime logs, and public-site analytics when enabled.

Data involved: Application traffic, runtime metadata, logs, and aggregate analytics events.

Purpose: Billing, subscription lifecycle, invoices, and payment method handling.

Data involved: Billing contacts, Stripe customer/subscription metadata, invoice/payment lifecycle data.

Purpose: Application error monitoring and diagnostics.

Data involved: Error traces, environment metadata, route context, and diagnostic logs when configured.

Purpose: Outbound transactional email.

Data involved: Email addresses, message content, and delivery metadata when configured.

Purpose: Google sign-in diagnostics and optional Google Calendar or Drive reviewed sync when a customer authorizes the provider connection.

Data involved: Verified identity profile, selected calendar/file metadata, staged event or source content, sync cursors, and provider delivery metadata. OAuth tokens remain server-only.

Purpose: Microsoft sign-in diagnostics and optional Microsoft Calendar or SharePoint/OneDrive reviewed sync when a customer authorizes the provider connection.

Data involved: Verified identity profile, selected calendar/site/file metadata, staged event or source content, delta cursors, and provider delivery metadata. OAuth tokens remain server-only.

Purpose: Optional reviewed source sync for selected Notion pages when a customer authorizes the provider connection.

Data involved: Selected page metadata/content staged for Resources review, page version evidence, sync cursors, and provider account display metadata. OAuth tokens remain server-only.

Purpose: Optional Slack webhook notification delivery and Slack app OAuth outbound notification delivery when a customer authorizes the app and configures a channel. Interactive approvals, slash commands, and two-way workflows remain out of launch scope.

Data involved: Redacted notification summary text, deep links, destination metadata, and delivery status when configured.

Purpose: Optional SMS notification delivery when server-side SMS settings are configured.

Data involved: Recipient phone number, redacted notification summary text, deep links, and delivery status when configured.

Purpose: Web Push transport for users who enable supported browser or installable PWA notifications.

Data involved: Encrypted notification payloads, push endpoints, and delivery metadata handled by the user browser/device push service.

Purpose: Optional public marketing-site analytics after first-party visitor consent.

Data involved: Public marketing page events, device/browser metadata, and approximate traffic measurement data.

Purpose: AI-assisted resource lookup, summaries, and admin/employee assistant features.

Data involved: Prompt content and selected context when AI features are enabled.