Metadata
Small records may stay longer.
Minimal metadata such as job status, selected plan, timestamps, row count, confidence, payment status, and refund status may be retained for payment records, abuse prevention, debugging, and compliance.
Data retention
AI Converter keeps source files only long enough to preview, unlock, redo, and download the conversion. The product is built around short retention, not long-term file storage.
Generated files expire after 7 days.
Deleted after failed preview, failed full extraction, completed redo, or the 24-hour private source lifecycle.
Kept for download after conversion, then expired. Download the file after the export completes if you need a copy later.
Support messages, payment records, abuse-prevention events, provider job IDs, and operational logs may last longer when needed for payment, security, debugging, or legal records.
Metadata
Minimal metadata such as job status, selected plan, timestamps, row count, confidence, payment status, and refund status may be retained for payment records, abuse prevention, debugging, and compliance.
Abuse prevention
Hashed connection data, file hashes, and preview-limit events may be retained long enough to limit repeated free previews, payment reuse, and refund abuse. These records are not used by AI Converter to train a model.
Processors
Cloudflare, Dodo, Mistral, CloudConvert, and Convertio may keep service, security, billing, or conversion records under their own terms when they are used for a selected route.
Deletion requests
For deletion questions, use the support form with your job ID and payment email. Do not send source files through support.
Self-serve recovery
If you lose a conversion link, the app can send a short-lived recovery link to the receipt email. It can show matching job IDs, billing status, support status, and available downloads while the generated file still exists. It does not turn AI Converter into a permanent file vault.
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.