File handling
Private storage, short windows.
Source files are kept for preview, paid unlock, and the redo window. Generated files expire after 7 days. You can delete a completed job from the converter screen.
AI Converter
Open converter
Trust center
Private file conversion with visible limits.
AI Converter is built around direct upload, free preview, short retention, tokened access, payment-bound unlocks, and no human file review queue.
No SOC 2, GDPR, or bank-feed certification claims are made here.
Access
Job links are tokened.
Uploaded and generated files are not served from public object URLs. Job access requires a job ID and random token, and sensitive API responses are marked no-store.
Processors and subprocessors
External processing depends on the route.
Cloudflare runs the app, private storage, database, security checks, and some AI routes. OCR or AI routes may use Mistral or Cloudflare Workers AI. Provider-backed format conversion may use CloudConvert first and Convertio as backup.
Payments
Card data is handled outside the app.
Dodo handles checkout and card processing. AI Converter stores payment status, payment IDs, plan IDs, and refund status so a job can be unlocked and support can resolve payment issues.
Training
No training use by AI Converter.
AI Converter does not use uploaded files or generated outputs to train models. External processors receive data only to perform the selected conversion or security check.
Support
Send job IDs, not source files.
Use the support form for conversion, payment, refund, deletion, or security questions. Do not paste bank statement, receipt, invoice, or source-file contents into support messages.
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.