Support

Get help without sending sensitive files.

Use this form for conversion, payment, refund, deletion, or security requests. Include the job ID if you have one. Do not paste bank statements, receipts, invoices, screenshots, or source-file details into the message.

Support can use recorded job status when a job ID is provided.

Request

Send the issue, not the file.

Helpful details

What to include

Job ID and payment email, if available.
The plan you selected.
A short description of what went wrong.
Whether you already tried the stronger redo.

Status

Keep your request ID.

The support form records a ticket ID and status note. A request starts as submitted, moves through review, and is updated when the issue is resolved or needs more information.

Privacy

Do not send source files.

Sensitive files should only be submitted through the upload flow. Email monitoring is planned as a later feature, but the current support form should not receive sensitive files or copied source data.

Paid jobs

Refund and redo help

Paid jobs include one automatic stronger redo. If the redo still cannot produce a usable generated file, the job is marked refund or credit due. Support can use the recorded job status and payment record when reviewing the request.

Deletion

Deletion requests

Source files are deleted automatically after the 24-hour private source lifecycle or earlier after failed extraction or completed redo. For a deletion request, send the job ID and payment email only through the form.

Priority

Expected response

Support requests are recorded for review. Security reports and payment, deletion, or refund issues are treated as priority requests.

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.