Tenant isolation
Every organization-scoped read and write is protected by database row-level security or a server function that checks the authenticated member and role.
Security and data handling
Your procedures are company operating data.
Rampwise treats identity, organization boundaries, draft content, learner access, and payment state as separate authorization decisions.
Draft access
Learner lesson bodies are not exposed through a public table policy. Owners and admins can preview drafts; members need a published course, an assignment, and active organization access.
Server-only generation
SOP generation writes use a server-only Supabase credential. Model and database secrets are never shipped to the browser.
Signed billing events
Stripe webhook bodies are verified using the endpoint signing secret. Event identifiers are stored to make subscription updates replay-safe.
AI providers
Generation uses configured structured-output model providers.
The SOP text and generation prompts are sent server-side to the configured model provider to create the course. Rampwise currently supports OpenRouter with a direct Anthropic fallback. Do not submit information you are not authorized to process through those providers.
Payments
Card details stay with Stripe.
Rampwise creates hosted Stripe Checkout and customer-portal sessions. The application stores customer, subscription, price, status, and renewal identifiers needed to enforce access. It does not collect raw card numbers.
Current launch boundaries
Rampwise is not presented as a certified compliance platform and does not claim SOC 2, HIPAA, ISO 27001, or regulated-data eligibility at launch.
Course deletion, formal data-export tooling, configurable retention controls, and enterprise provider agreements are not yet self-serve product features.
Security questions can be sent to security@rampwise.io.