Security & Trust

How Kaura protects workflow and lead data.

Kaura connects to tools that small businesses rely on, so the product is built around clear account boundaries, limited integration access, and practical monitoring.

Account and data boundaries

Every dashboard request is tied to the signed-in user. Workflow, lead, run, and profile records are protected with Supabase row-level security so accounts can only read and update their own data.

Connected app access

OAuth tokens are used only to run workflows the account owner configures. Kaura asks for integration access through each provider, and users can disconnect integrations from the dashboard.

Transport and storage

Application traffic uses HTTPS. Production data is stored with managed infrastructure providers that support encryption at rest, access controls, backups, and operational monitoring.

Operational monitoring

Kaura monitors application errors and workflow failures so issues can be investigated quickly. Workflow run history also helps users see what happened when an automation needs attention.

Core providers

Kaura uses established service providers for infrastructure that would be risky to build from scratch.

  • Supabase for database, authentication, and row-level security
  • Vercel for application hosting
  • Stripe for billing and payment portal flows
  • Resend for transactional email delivery
  • Sentry for production error monitoring
  • Upstash for workflow queues and rate limits