Privacy

Payout Recon is designed as a browser-first website. It does not require an account, and it does not maintain a server database containing calculator inputs or reconciliation files.

CSV reconciliation and Monthly Close

When you select CSV files for reconciliation or Monthly Close, the files are read, parsed, grouped, and matched by JavaScript running in your browser. Payout Recon does not upload or store the CSV contents. Marking a month closed is also session-only: the close result itself is not retained after refresh.

Local Monthly Close settings

Monthly Close can store a small settings object in your browser's local storage so the next close can reuse your DoorDash and Uber bank-description filters, bank amount sign mode, amount tolerance, date window, and bank grace days. This local settings object does not contain CSV contents, filenames, payout or order IDs, payout amounts, payout dates, bank transaction rows, close reports, or a record of which months you closed.

These settings stay on the device and browser where they were saved. You can reset them from Monthly Close, and clearing this site's browser storage also removes them. The settings themselves are not included in Payout Recon telemetry.

Operational telemetry

Payout Recon sends small same-origin telemetry events for supported tool page views, CSV loads, schema-detection failures, completed reconciliation results, Monthly Close starts/completions, and clicks expressing interest in the proposed paid plan. These events are deliberately limited to fixed event/tool/source labels, fixed failure reasons, coarse row, column, payout-count, and match-rate buckets, whether exceptions or ambiguous matches exist, whether an Uber Eats description row was detected, and a boolean indicating whether the same browser had previously started Monthly Close.

For that repeat-use signal, the browser stores only a fixed local marker indicating that Monthly Close has been started before. It does not store a user ID, random identifier, start count, start date, closed month, or other activity history. On a later Monthly Close start, telemetry can include only the boolean result of that marker. Clearing this site's browser storage removes the marker.

The telemetry payload cannot include CSV contents, filenames, raw header names, payout or order IDs, exact matched or payout counts, amounts, dates, bank descriptions, calculator inputs, email addresses, locally saved Monthly Close settings, or other arbitrary strings. The proposed paid-plan button does not collect payment or contact information; it records only an anonymous fixed pro_clicked event. The receiving Cloudflare Function applies the same fixed whitelist again before writing or logging an event.

If the optional Cloudflare Analytics Engine binding is enabled, these sanitized event fields can be retained as aggregate operational analytics. Cloudflare also processes ordinary network metadata needed to deliver the website and Function requests under its own service practices.

Calculator sharing

The DoorDash calculator can create a shareable URL containing numeric assumptions in query parameters. Do not use that feature for information you do not want included in a URL.

Third-party links

Payout Recon links to official DoorDash and Uber documentation for reference. Visiting an external site is subject to that site's privacy practices.

Changes

If advertising, accounts, payments, server-side file uploads, or storage of reconciliation data are added later, this page should be updated before those features are enabled.