For help with imports, data questions, or app behavior, email [email protected].
Support
Help for Cashflow Pilot.
Find contact details, import guidance, privacy notes, and quick fixes for the local-first cash-flow companion.
What to include
Include your device, browser or app version, the import type, and a short description of what happened.
Before sending files
Cashflow Pilot is local-first. Do not send financial exports unless support specifically asks and you are comfortable sharing them.
Quick fixes
Most issues start with import format or local browser state.
Cashflow Pilot does not connect to banks directly. It works from statement exports you choose, then stores records locally on your device.
- Try a CSV export if a PDF import has missing rows or unclear debit/credit signs.
- Review unreviewed transactions after every import before relying on reports or forecasts.
- Export a backup before clearing browser data, reinstalling, or switching devices.
- Use the in-app support/export tools when reporting parser or reconciliation issues.
Statement imports
Supported imports are review-first.
Cashflow Pilot is built around careful local review rather than automatic bank access.
CSV exports
Use statement exports that clearly include dates, descriptions, amounts, and debit or credit direction.
PDF statements
Selectable-text PDFs can work, but CSV is usually easier to review when signs or columns are ambiguous.
Generic formats
Unknown layouts may import through a review-first flow so you can confirm rows before relying on reports.
FAQ
Common support questions.
Does Cashflow Pilot store my data in the cloud?
No. Cashflow Pilot is local-first. Your financial records are stored on your device unless you choose to export or share a file.
Can support recover deleted local data?
No. If local app data is cleared from your device or browser without a backup, support may not be able to recover it.
Why does an import need review?
Bank exports vary. Review steps help confirm dates, debit/credit signs, transfer matches, categories, and reconciliation before reports rely on those rows.
What should I send with a bug report?
Send a short description, device/browser details, screenshots if useful, and any in-app diagnostic export you are comfortable sharing.