Security and Compliance
Payment Security
No Card Data on Burdenoff Servers
Burdenoff does not store raw card numbers, CVVs, or full card details. All card data is entered directly into secure, PCI-DSS-compliant forms hosted by Stripe or Razorpay. Burdenoff receives only a secure token reference.
Server-Side Price Calculation
All prices are calculated on the server at the time of purchase. The price displayed in the browser is for information only and is never used as the actual charge amount. This prevents price manipulation attacks.
HTTPS Everywhere
All billing API calls are made over HTTPS with TLS 1.2+. Payment provider communications use mutual TLS where supported.
Access Control
Role-Based Access
Billing data is protected by role-based access control (RBAC). To view or modify billing information, users must have an appropriate billing role assigned by an organisation admin.
| Role | Can do |
|---|---|
| Billing viewer | View invoices, transactions, and usage |
| Billing manager | All of the above + manage payment methods, purchase plans |
| Org admin | Full billing access including account management |
Organisation members without a billing role cannot see any billing data.
Organisation Isolation
Billing data is strictly scoped to an organisation. There is no way for one organisation to see another's invoices, payment methods, credit balance, or subscription details — even for users who belong to multiple organisations.
Webhook Security
Payment provider webhooks (Stripe, Razorpay) are verified using HMAC signature validation on every request. Events with invalid or missing signatures are rejected immediately.
Audit Trail
Every billing action — account creation, payment, refund, credit grant, subscription change — is logged with the actor ID, timestamp, and a description. This audit log is immutable and retained for compliance purposes.
Data Handling
What We Store
- Billing account details (name, email, billing address)
- Payment method tokens (from Stripe/Razorpay — not raw card data)
- Invoice and transaction history
- Credit balance and transaction ledger
- Subscription status and history
What We Do Not Store
- Raw card numbers or CVVs
- Bank account numbers in full (last 4 digits only for display)
- Passwords or authentication credentials
Data Retention
Billing records (invoices, transactions, subscriptions) are retained for the period required by applicable accounting and tax regulations (typically 7 years in most jurisdictions). Credit transaction history is retained for the lifetime of the account.
Right to Erasure
Where legally required, you can request deletion of your personal data. Note that billing records required for tax and audit compliance cannot be deleted until the applicable retention period expires — they can be anonymised.
Compliance
- PCI DSS: Card processing is delegated entirely to Stripe and Razorpay, both of which are PCI DSS Level 1 certified.
- GST (India): GST-compliant invoices are issued for INR payments.
- VAT (EU/UK): VAT is calculated and shown on invoices for EU and UK customers based on the billing address.