StatementForge
Convert a statement
Contact and support

Get help without sharing financial data.

Use the published support channel for product, billing, refund, privacy, or security questions. StatementForge support should never need your complete bank statement.

Last updated August 4, 2026

1. Contact method

Use this form for product support, billing questions, refund requests, privacy requests, or responsible security reports. The request is stored in StatementForge's support queue and is not sent to an unverified email address.

2. Safe details to include

Product issuePage URL, browser and version, operating system, text-based or scanned PDF, export format, approximate page count, and the exact non-sensitive error message.
Billing or refundAccount email, charge date, amount, currency, plan, and Stripe receipt or invoice identifier. Show at most the last four card digits if necessary.
Privacy requestAccount email, the right you want to exercise, and enough information to verify the account. Do not include statement data.
Security reportA reproducible description, affected URL, impact, and safe proof that does not expose another person’s account or financial information.

3. Do not send

  • bank or credit-card statement PDFs;
  • account, routing, card, tax, or government identification numbers;
  • transaction descriptions, balances, exported rows, or OCR text;
  • passwords, OAuth codes, API keys, Stripe secrets, or session cookies; or
  • another person’s private information.

A redacted screenshot is acceptable only when the issue cannot be explained otherwise and every financial or identifying detail has been removed.

4. Subscription management

Where billing management is available, sign in with the account used at checkout, visit Pricing, and choose the billing-management action. Stripe handles subscription and payment-method changes. See the Refund Policy before requesting money back.

5. Response expectations

No response-time or support SLA is currently offered. Requests should be handled in a reasonable order, with billing, privacy, and security matters prioritized when possible. Do not send repeated messages containing new copies of the same sensitive information.