Last updated: 2026-06-01

Privacy Policy

Receipt Resolver is in private beta. This policy describes the current local-first product design and the controls intended for public launch.

Short version

Receipt Resolver is built to reconcile bookkeeping evidence without turning your client files into another cloud receipt vault. Your receipts, invoices, statements, extracted text, review decisions, and generated packages are stored in the desktop app's local workspace by default, with app-managed workspace records encrypted locally.

We do not sell bookkeeping data. We do not use receipt, statement, or QuickBooks data for advertising profiles. We do not upload your source documents to Receipt Resolver servers for parsing or matching.

What stays local

The app may process, scan, extract, normalize, and store the following on your computer so it can do its job:

receipt and invoice files, including PDFs, images, HTML, CSV, text, and email-derived files,
card and bank statements,
QuickBooks export files or QuickBooks data synced into the selected workspace,
OCR output and extracted document text,
normalized evidence records such as vendor, date, amount, tax, currency, order ID, and line items,
match chains, likely-match reasons, parser warnings, duplicate flags, and review decisions,
generated receipt packages, missing-receipt memos, and local export history,
local audit events needed to explain what the app did.

Client workspaces

Each workspace is intended to be a separate client or company file. A workspace has its own encrypted local database, encrypted app-managed source copies, import folders, prefilter inbox, generated packages, issue history, and QuickBooks connection state. The global workspace list stores only enough information to show and open workspaces, such as the workspace name, ID, path, status, and timestamps.

QuickBooks Online

If you connect QuickBooks Online, you authorize the app to use the QuickBooks accounting API for that workspace. Receipt Resolver may read company details, accounts, vendors, tax-code references, posted transaction details, existing attachment metadata and files, and attachment targets needed to reconcile evidence.

When you approve a QuickBooks action, the app may upload the generated PDF evidence package to the selected QuickBooks transaction, or create a reviewed QuickBooks Purchase and attach the package so you can accept the suggested bank-feed match in QuickBooks. Files and records written to QuickBooks then live in QuickBooks under Intuit's service terms and privacy practices, not only on your computer.

QuickBooks connection credentials are intended to be stored locally through the operating system's secure credential storage where available. Token metadata on disk should not contain raw access or refresh tokens.

Online sign-in handoff

Production QuickBooks sign-in requires a secure public redirect page. Receipt Resolver's intended hosted component is a minimal OAuth handoff, not a document-processing service.

That handoff may temporarily receive the OAuth authorization code, state value, and Intuit company/realm ID needed to return the connection to the local app. It is not intended to exchange tokens or store receipts, statements, extracted text, QuickBooks transaction payloads, generated PDFs, review decisions, or match chains.

Website data

The public website is a static marketing and documentation site. It does not currently use advertising trackers or analytics scripts. Like most websites, the hosting provider may create ordinary server logs such as IP address, user agent, request path, referrer, and timestamp for security and operations.

When data leaves your computer

Receipt Resolver data may leave your device when you choose to connect QuickBooks, upload an approved attachment to QuickBooks, create a reviewed QuickBooks Purchase, save an exported PDF to a folder, open an original source, open an external original-source link, use a browser-based source capture flow, send files or screenshots for support, store the workspace in a synced folder, or back up your computer to another service.

Those systems are controlled by their own settings and policies. Deleting data inside Receipt Resolver does not automatically delete files already uploaded to QuickBooks, sent to support, stored in device backups, or synced by services such as iCloud, Dropbox, OneDrive, Google Drive, or a managed IT backup system.

Support

Do not send private receipts, statements, QuickBooks exports, or client files to support unless a secure support process has been explicitly provided. Sanitized examples are preferred whenever possible. If you do send support material, we may use it to investigate the issue you reported.

Security controls

The app is designed around local workspaces, encrypted app-managed workspace storage, explicit QuickBooks connection state, operating-system credential storage where available, local API session protection in the desktop shell, redacted audit payloads, and visible review warnings instead of silent corrections.

Deletion

The app includes a local workspace deletion workflow. It is designed to remove the selected workspace's local database, imported evidence, extracted text, generated packages, logs, QuickBooks sign-in state, token metadata, and local QuickBooks credentials where available.

Deletion is local to the device and workspace you choose. You remain responsible for deleting copies outside the workspace, including QuickBooks attachments, exported PDFs, downloads, email attachments, cloud backups, and files manually copied elsewhere.

Children

Receipt Resolver is intended for business bookkeeping work and is not directed to children.

Changes

We may update this policy as the product moves from private beta to public release, especially if support, diagnostics, billing, hosting, or QuickBooks sign-in infrastructure changes. Material changes should be reflected here before they are used in the public product.

Contact

For privacy or support questions during private beta, email contact@receiptresolver.com.