Skip to content
Menu
Get support

Support

Send context, not financial data.

Settings centralizes Position guides, contact, policies, Position ID and version/build details. Support can use safe context and a reviewed diagnostic preview; no response-time SLA is promised.

Current app path

Settings → SupportCentralized guides, contact, policies, Position ID, version/build details, diagnostic preview and email support are available through the external beta.

Required

  • iPhone and iOS version
  • Affected screen
  • Coarse error wording
  • Safe reproduction steps

Optional

  • A reviewed diagnostic preview with sensitive details removed

What can block completion

  • Any ordinary email containing statements, balances, account numbers, API keys, backups or unredacted screenshots
Local financial data
Preparing a diagnostic does not upload the local database. You review the preview before sharing.
Privacy or AI boundary
Ordinary email is not a financial-document channel. Donation is a separate in-app consent flow.
If it does not work
Remove sensitive details. For an import issue, say whether the Inbox item remains; do not attach the original.

Find help and app details

  1. Open Settings → Support.
  2. Choose a Position guide, contact option or policy from the centralized list.
  3. Use Position ID and version/build details when support asks you to identify the installed app.

Prepare a safe report

  1. For a certified statement failure, open its recovery page and choose Report parser issue.
  2. Review the exact allowlisted fields and opaque case ID; the report excludes document content, filenames, identifiers, exact dates and financial values.
  3. Choose Copy, Share or Support only if you want to send it. Creating or previewing the report sends nothing.
  4. For other support issues, include device/iOS, affected screen, coarse error wording and safe reproduction steps.

Never send through ordinary support

When to contact support

  • A supported statement repeatedly fails after recovery.
  • Reconciliation contradicts the original evidence.
  • A save blocker has no visible Required message.
  • Restore fails with the correct archive and password.
  • A privacy or deletion control does not state its scope.