Credits and Billing Policy
Draft policy for credits, monthly reset, purchased credits, and refunds.
Credit visibility
Users should see credits left, credits used, purchased credits remaining, cost per action, reset date, and failed generation refunds where real data exists.
Payments via Stripe
Checkout and billing are handled by Stripe (currently in test mode). Obrasken never stores full card details; Stripe processes payments and provides the customer portal for managing or cancelling a plan.
Current status
This is a product placeholder for launch planning. It describes intended controls and user-facing expectations, not final legal advice.
Private by default
Obrasken private workspace data should remain private unless the user intentionally chooses a secure sharing or export workflow.
Security boundary
Provider keys, service-role credentials, payment data, and other secrets must remain server-side and must not be exposed in browser code or logs.