Trust & Security
RowRecon is operated by Shift Warden LLC. This page explains how statements are handled and how to report a vulnerability.
How RowRecon handles statements
Statement contents are processed locally in your browser during normal conversion.
Your PDF is not uploaded to RowRecon for conversion. Scanned pages can use local OCR in the same browser when a file has no usable text layer.
Data RowRecon does not need for conversion
Normal conversion does not send these to RowRecon’s hosted backend:
- PDF bytes
- OCR text
- transaction descriptions
- account numbers
- names
- balances
- page images
Support notes you type yourself are the exception: we store what you write. Do not paste statement tables or account numbers into support.
Data RowRecon may store
- Stripe customer, Checkout session, and subscription identifiers
- Pro entitlement type and status (24-Hour Pass, Monthly, or legacy one-time)
- Pass grant and expiry timestamps (server-authoritative, never client-controlled)
- Normalized email for access recovery (hashed for lookup)
- Terms, Privacy, and Refund Policy versions accepted at checkout
- Privacy-safe analytics (event names and coarse fields; no statement contents)
- Support cases, optional email, and privacy-safe diagnostics
- Refund and billing metadata
See Privacy for cookies and retention.
Payments
Payments are processed by Stripe. RowRecon does not store raw card numbers. The 24-Hour Pass is a one-time payment granting exactly 24 hours of Pro access; Pro Monthly is a recurring subscription. Both are recoverable cross-device via a one-time restore link sent to your checkout email — no account or password required.
Browser and host controls
Production is served over HTTPS. When enabled, HSTS tells browsers to keep using HTTPS. Responses include a Content Security Policy, anti-framing header, nosniff, and restricted browser permissions. Customer cookies are HttpOnly, SameSite=Lax, and Secure in production. These are ordinary web controls, not a guarantee.
Extraction safety
- Uncertain rows are flagged for review.
- Reconciliation may identify mismatches when the statement provides totals.
- Unsupported or ambiguous layouts may fail closed instead of inventing rows.
- Review results against the original statement before financial use.
Vulnerability disclosure
Report suspected vulnerabilities to security@rowreconapp.com.
Do not include bank statements, account numbers, or live secrets in the report if a redacted proof of concept is enough.
We do not offer a bug bounty.
Company
RowRecon is operated by Shift Warden LLC. Support: support@rowreconapp.com. Security: security@rowreconapp.com.