Beta policy

Privacy Policy

Last updated: May 30, 2026. This policy is intentionally plain-English for the paid beta and should be reviewed before broad public launch.

What we collect

Account information such as your name, email, authentication provider id, and basic profile details needed to operate the product.
Business and content strategy inputs you provide during onboarding, including audience, offer, positioning, proof constraints, stories, your take on the problem, platform preferences, and generated drafts.
Billing status from Stripe, such as customer/subscription identifiers and subscription state. Klarava does not store full card numbers.
Beta feedback you submit, including ratings, comments, and coarse product context like the workflow or content item you were reviewing.
Product analytics and reliability events needed to debug the beta, such as onboarding completion, checkout status, paid-access decisions, generation success/failure, approval/copy/export actions, and feedback submission.

To authenticate accounts, maintain paid beta access, generate strategy-backed content, save your workspace, process support/debugging requests, and improve product quality during the beta.
To enforce Klarava’s credibility constraints: no fabricated testimonials, outcomes, client stories, metrics, transformations, or personal experiences.
To understand whether the beta workflow is useful: paid onboarding → strategy → canonical approval → platform copy/export.

Klarava’s beta analytics are intended to be minimal and privacy-conscious. We prefer coarse events, counts, statuses, ids, and booleans over raw content.
Generated copy, onboarding long-form text, feedback comments, email addresses, and Stripe customer fields should not be sent to third-party analytics by default.
If a third-party analytics or error provider is added, it should be configured behind an explicit environment setting and reviewed for redaction before beta traffic is sent there.

Klarava may use Supabase for authentication and database storage, Stripe for payments, Vercel for hosting, Inngest for background jobs, and AI providers such as OpenAI or Anthropic for generation.
Provider usage may vary by environment. Beta users should not put secrets, private health records, or highly sensitive client information into Klarava.

During beta, we keep account, billing, workspace, feedback, and operational records as long as needed to operate the product, debug issues, satisfy billing/legal obligations, and improve launch quality.
You can request account or workspace deletion by contacting support. Some billing, security, or abuse-prevention records may need to be retained where legally or operationally required.