ReportPatch
USD 99 · ONE REPORT · ONE WINDOW

Report Check.
Terms and limits.

These terms supplement the general service terms, cancellation and refund policy, and privacy notice. Once agreed in writing, these specific terms govern the Report Check phase where they differ from a general description, without reducing existing refund protections or rights that cannot lawfully be excluded.

Scope and deliverable

Report Check is a separate $99 service for one agreed report and one reporting window. We compare up to 50 pairs of supplied, redacted additive source and report totals that fit within one complete UTF-8 JSON-RPC request of at most 65,536 bytes, including its wrapper and metadata, using explicitly selected tolerances. We agree the required structured input format before payment. If it does not fit, we agree a smaller fitting set before payment; batching is not included and would require separate validation and agreement. We provide a two-page summary with counts for all checked pairs by status and up to five prioritized findings. We rank individual pair-linked findings by their own category: discrepancies first, then not-comparable metadata conflicts, then missing evidence. Within each category, we use your agreed pair priority (1 is highest), then pair ID, then finding ID. One pair can produce more than one finding. Counts are by pair; omitted findings are counted individually, including findings on a pair shown in the summary. Report-approval evidence is shown separately from the five slots; unknown approval is unresolved, not a rejection or approval. It includes next checks, scope and limitations; no complete pair-by-pair list is included. You agree this selection before payment. It is not an audit of underlying rows.

For each pair, provide the available source and report totals, matching units and currency where applicable, reporting period, timezone and boundary convention, filters, attribution, refresh cutoff and metric definition/evidence. A missing or unknown value may be supplied as null where the agreed schema permits and will be reported as an evidence gap, not a match. For each pair, you or an authorized reporting owner must explicitly choose a nonnegative absolute tolerance in that pair’s count, currency (with currency code) or decimal unit, and a nonnegative dimensionless relative tolerance as a decimal fraction (for example, 0.01 means 1%). Exact comparison requires both zero. We compare the absolute difference to the larger of the absolute tolerance and relative tolerance multiplied by the absolute source value. At a zero source, the absolute tolerance controls. Missing, incompatible or unsupported evidence remains unresolved rather than silently treated as a match.

We do not independently authenticate underlying events or source values, diagnose joins, certify completeness, approve the full report or guarantee a particular outcome. Rates, percentages, ratios, averages and distinct counts are outside this additive check. The reporting owner retains the acceptance decision. Additional work requires separate written agreement.

Timing and work start

Before payment, we agree the scope, acceptance checks, a feasible delivery date and the permitted data handling in writing, and reserve capacity. The agreed delivery clock begins only after all of the following: written scope and permissions, reserved capacity, reconciled successful payment, and complete usable agreed redacted inputs and explicit tolerances received through the approved transfer method. A missing or changed input may require a revised date agreed in writing.

For cancellation of this paid phase, work begins when ReportPatch starts substantive analysis of the complete agreed inputs after those conditions are met; we record that start time. Administrative fit discussions, reservation and payment alone do not constitute substantive analysis.

Payment, related services and refunds

The fee is $99; applicable tax, if any, will be identified before payment. An enquiry creates no payment obligation or delivery slot. Report Check is distinct from the $500 paid scope review. A fit-confirmed implementation sprint is separately agreed at $2,500 total, with the actual paid $500 review credited once. The $99 fee is not credited toward the $500 review or the $2,500 sprint.

The existing cancellation and refund policy applies to this paid phase: if you cancel before work begins, the phase payment is refunded without a separate cancellation fee. After work begins, we review completed work against the agreed scope and explain any charge for completed work and refund of unused prepaid work in writing. If an agreed acceptance check is not met, we first correct covered defects; if an agreed deliverable cannot be supplied, we agree an appropriate refund for the undelivered portion. Existing policy's 14-day post-acceptance defect support and rights that cannot lawfully be excluded remain intact. Approved refunds return through the original Stripe payment method; processing time depends on the bank. Do not send card numbers in a refund request.

If the agreed $99 delivery date is at risk or missed, we will tell you the status. You may email hello@reportpatchhq.com with your project or payment reference to request cancellation or a refund under the existing policy. Before substantive work starts, we refund the phase payment; after work starts, we explain completed work and the refund of unused prepaid work in writing. If the deliverable cannot be supplied, we agree an appropriate refund for the undelivered portion. You may instead agree a revised date in writing; no revised date is imposed automatically. The separate 72-hour rush remedy applies to the rush offer under its own terms and is not represented as a $99 guarantee.

Authority, processing and privacy

Before sharing material, you confirm that you and the agency/client have the necessary authority to share it and approve the agreed tools, processors, people or accounts with access, transfer and return methods, retention and deletion limits. Send only agreed redacted aggregates and metadata. Do not include client personal records, credentials or payment-card details.

Report Check uses a remote ReportPatch checker: the agreed values and metadata are sent to the service and the result returned through the agreed workflow. This differs from the browser-local working sample on the website. The application is described in existing technical evidence as processing in memory without intentionally storing report bodies in an application database, but hosting providers can process or retain invocation metadata and the assistant platform can retain its own conversation and tool records. Exact host, log, backup and assistant-platform retention and deletion limits are not yet verified; zero retention is not promised. Before receiving data, the parties must agree the actual permitted processors, restricted intake and private return destinations, access, retention and deletion limitations based on verified facts. Do not send files in the initial enquiry. No confidential material will be published as a case study without permission.