Founder-stage fairness
PixelClear is currently moving from founder-led rollout into a more market-ready product state. The refund posture should feel fair, readable, and confidence-building rather than defensive.
The intended public policy is a simple founder-friendly promise: if a paid customer requests a refund within 30 days of the initial charge, the request should be reviewed promptly and handled reasonably.
Recurring subscriptions
Refund handling for recurring renewals should be stated clearly on the live site. The public site should avoid vague language that leaves customers uncertain about what happens after renewal or cancellation.
Cancel-at-period-end posture, failed-payment recovery, and billing notices should stay consistent between the public refund policy and the app's billing workflow.
What the public site should avoid
Do not publish a refund page that sounds punitive, confusing, or obviously copied from a mismatched SaaS template. The tone should remain calm, practical, and honest.
Do not overpromise instant refunds, guaranteed outcomes, or product guarantees that the app itself does not make elsewhere.
Operational follow-through
Once production billing is live, refund requests should have a clear support path and an internal handling cadence so the policy is operationally true, not only present for Paddle review.
The final production page should also reference where customers can ask questions about billing, cancellation, or plan changes.