Plain refund policy for SaaS subscriptions, usage credits and digital add-ons.
Refunds are handled through product records, provider-confirmed transactions and Paddle payment workflows. This page does not promise automatic refunds for delivered digital services.
No automatic refund boundary: Refund requests are reviewed from billing evidence and applicable law; delivered digital access, consumed credits and completed service periods are generally not refundable.
1. What this policy covers
This policy covers WebRiskOps software subscriptions, usage credits, digital add-ons, billing records, cancellation state, refund requests and service-credit requests.
- SaaS subscriptions
- Usage credits and digital add-ons
- Billing and refund records
2. Subscriptions and cancellations
Customers may cancel subscription renewals through the billing workflow. Cancellation stops future renewals, but it does not automatically refund a period that has already started or completed.
- Cancel future renewals
- Keep access through the paid period when applicable
- No automatic refund for completed periods
3. Usage credits and digital deliverables
Usage credits, reports, scan evidence, remediation tasks, monitoring results and other digital deliverables are generally non-refundable once access, delivery or consumption has started.
- Consumed credits are preserved in billing records
- Delivered reports and evidence remain traceable
- Service-credit handling may apply when payment refund is not appropriate
4. Cases we can review
Refund or service-credit requests can be reviewed for duplicate charges, billing errors, provider confirmation issues, unsupported-before-delivery cases, platform-side access failures and cases required by applicable consumer protection law.
- Duplicate charge or billing error
- Unsupported before delivery
- Technical access issue caused by WebRiskOps
5. How to request help
Use the authenticated support form or the transaction actions in Billing. Include the account, transaction or invoice context, plan or credit type, visible blocker and expected outcome without sending payment method details.
- Start from Billing when a transaction is visible
- Use the refund request support category when no transaction action is available
- Do not send card numbers or payment credentials
6. Paddle payment handling
Payments are processed by Paddle as merchant of record where Paddle is enabled. Provider records, webhooks, receipts and applicable law can affect the final refund or adjustment outcome.
- Paddle provider boundary
- Webhook and receipt evidence
- Applicable-law exceptions