Your files are handled for the job you start.

AI Converter is built for private upload, short retention, minimal job metadata, and preview-first conversion. We do not ask for bank credentials, and sensitive files should not be sent through support.

Last updated May 17, 2026.

Collected

Only what the workflow needs.

The source file you upload for conversion.
Generated preview rows and converted output files.
Optional email address for payment receipt and job recovery.
Payment status, payment ID, selected plan, timestamps, and job status.
Security metadata such as hashed IP, hashed user agent, file hash, and abuse-limit events.

Not collected

No bank logins. No files through support.

AI Converter does not ask for bank usernames, bank passwords, or one-time banking codes. Support requests should include a job ID and short issue summary, not pasted source-file data.

Processing

Files are used to produce the output you requested.

Digital bank statement PDFs are parsed directly first. If a file is scanned, image-heavy, a receipt, an invoice, a screenshot, or too messy for the native parser, OCR and AI processing may be used when configured. Audio transcript, document Markdown, screenshot-to-HTML, and common file-format conversion run only to produce the conversion you requested.

Low-confidence files fail closed instead of being sent to a human review queue. If the preview cannot be produced safely, there is no charge.

Processors

Processing depends on the route you choose.

Cloudflare runs the app, private storage, database, Turnstile checks, and some AI processing. OCR or AI routes may use Mistral or Cloudflare Workers AI. Provider-backed file-format conversion may use CloudConvert first and Convertio as a backup route. Dodo handles checkout and card processing.

AI Converter does not use uploaded files or generated outputs to train models. External processors receive data only to perform the selected conversion, security check, payment, or support workflow.

Payments

We store unlock status, not card numbers.

Payments are handled by the payment provider. AI Converter stores payment status and payment identifiers needed to unlock a job, prevent payment reuse, and process refunds or credits. We do not store full card numbers.

Retention

Source files have a short lifecycle.

Source files are kept only for preview, paid unlock, and the automatic redo window. Source files are deleted after a failed preview, failed full extraction, completed redo, or the 24-hour private source lifecycle. Generated files expire after 7 days.

Minimal job metadata may be kept longer for payment records, abuse prevention, service debugging, and legal or accounting obligations.

Security

Access is tokened and rate-limited.

Uploaded files are stored privately, job access uses random tokens, and API responses are served with no-store caching. The service limits repeated free previews, repeated same-file uploads, payment reuse, and repeated redo attempts to reduce abuse.

Requests

Use support for privacy and deletion questions.

For deletion, privacy, or payment-related requests, use the support form. AI Converter is operated by the AI Converter team. Do not send source files through support; use the upload flow only.

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.