Refund Policy

Preview first. Redo once. Resolve failures.

You should not pay for a blind export. AI Converter shows a preview first, gives paid jobs one stronger automatic redo, and records refund or credit due when a paid conversion still cannot produce a usable file.

Last updated May 17, 2026.

Before payment

No safe preview, no charge.

If AI Converter cannot safely produce a sample preview, there is no charge. The file fails closed instead of being routed to a human queue.

After payment

One stronger automatic redo.

Paid jobs include one stronger automatic redo. Use it when the full generated file is incomplete, badly formatted, missing rows or fields, or otherwise not usable. The redo uses the stored source file inside the short retention window.

If the redo fails

Refund due or credit due is recorded.

If a paid job still cannot produce a usable generated file after the stronger redo, AI Converter records the job as refund due or credit due. When automatic refunds are enabled and a cash refund is allowed, the refund is requested through the payment provider. If a cash refund is not available automatically, support uses the recorded job status to resolve the credit or refund.

If a usable file has already been delivered and downloaded, support may offer credit instead of a cash refund, depending on the issue and abuse signals.

Limits

Fair use protects everyone.

Repeated free previews from the same file or connection are limited.
Each paid job gets one automatic stronger redo.
Payment IDs are bound to one job and cannot be reused.
Refunds may be denied for altered files, duplicate claims, payment abuse, or attempts to bypass access controls.

Support

Send the job details, not the sensitive file.

Contact support with your job ID, payment email, and a short description of what is wrong through the support form. Do not send bank statement PDFs through support; sensitive files should only go through the upload flow.

Use the preview as your quality gate.

AI Converter is built around a simple rule: inspect the sample before trusting the full export. That matters for bank statements, receipts, invoices, screenshots, and other sensitive files because automated extraction can be wrong when a scan is noisy, a table is unusual, a file is damaged, or a provider cannot safely read the source. The preview gives you an early look at columns, dates, descriptions, totals, signs, and row structure before you pay for the complete result.

For accounting workflows, compare the export with the source statement before importing it into bookkeeping, tax, lending, or compliance systems. Keep the privacy pages close too: source files are handled for the job you start, generated files have a short download window, and support requests should use job IDs rather than pasted bank, receipt, invoice, screenshot, or document contents.

A clean export is only useful when the route matches the file. Choose the most specific output available, keep the original file until you have checked the result, and use the validation notes or row preview to spot missing dates, duplicate transactions, weak OCR, wrong signs, or totals that do not reconcile. If the preview looks off, stop there instead of paying for a full export.