A note on why we built Cruma
Legal

Subprocessors

Every provider Cruma sends customer data to, what it is for, and what data it touches.

Last updated: 2026-07-14

ProviderPurposeData touched
Amazon Web Services (Bedrock, S3)Model inference via Amazon Bedrock; object storage for archivesPrompt/completion content (credential-free by construction), archived run traces
SupabaseDatabase and authenticationAll workspace application data; auth identities
ComposioIntegration broker (Gmail/Drive/Calendar etc. on the customer’s behalf)Content of connected-account reads/writes the customer authorizes
StripeBilling, subscriptions, payments, taxBilling contact, payment method (held by Stripe), subscription state
SentryError monitoringError events and technical metadata (trace/run identifiers; no message bodies by policy)

The work moves
while you sleep.

Point Cruma at the business. It works across the tools you already use and speaks up before you ask. Your mornings can start somewhere else.

  • Works across the tools you already use
  • Advises, unasked, with its sources
  • Nothing consequential without you
Request your invite

Two fields. You'll hear from a real person within two days.

We onboard in small waves, with real help getting set up. Read why we built this.

Already have an invite? Open Cruma