Refund Policy

1. What refunds can apply to

• Duplicate or incorrect charges.
• Paid subscriptions that cannot be accessed because of a product-side failure.
• Major technical issues that prevent the core upload, review, or export workflow from working for a meaningful period.

2. What refunds usually do not apply to

• Change of mind after successful access to the paid workflow.
• Results you chose not to review before downstream use.
• Credits or subscription capacity already consumed through completed usage.
• Problems caused by unsupported files, low-quality scans, or upstream provider limitations that are disclosed as workflow risks.

3. Subscription expectations

Public billing is subscription-based. If you cancel a subscription, future renewals stop, but access usually continues until the current billing period ends unless local law requires otherwise.

4. Historical one-time credit records

Legacy one-time credit entries may still exist in historical ledgers and old payment records. Those records remain readable for audit and support, but public refunds now mainly concern active subscriptions and billing errors.

5. How to request a refund review

• Use the contact page and include the account email involved.
• Include the payment date, expected issue, and any billing reference if available.
• Describe whether the problem is billing-related, access-related, or workflow-related.

6. How requests are reviewed

We review refund requests against product logs, subscription state, payment records, and whether the core workflow was actually delivered. We may ask for a short description of the issue, but do not send invoice files unless we explicitly request a sample.

7. Processing outcome

If a refund is approved, it is generally returned through the original payment method. Final processing time also depends on the payment provider and the user's bank.

8. Changes

If billing model or refund conditions change materially, this page will be updated.