Refund & Liability Policy

Effective August 12, 2026.

This policy applies to the invite-only Essential Insights controlled beta. Public live checkout is unavailable.

No real charge during the controlled beta

Selected testers may be asked to complete a Stripe test-mode checkout showing $49 to exercise the purchase-to-access workflow. No real payment is processed during this controlled beta, so there is no real customer charge to refund.

Test-mode transactions may still be reviewed, reversed, or reset in the sandbox when needed to test duplicate-charge, failed-access, refund, entitlement, or service-recovery behavior.

Failure and attempt rules

Unsupported formats, prohibited-data screening failures, customer-correctable validation failures, abandoned attempts before confirmed completion, and verified platform failures do not intentionally consume an available assessment allowance.

A successfully delivered low-readiness assessment counts as the final assessment because the customer received the readiness findings and correction plan. A valid delivered result is not considered a platform failure merely because the dataset has quality problems or the tester expected a different conclusion.

Verified system failures may restore the affected attempt. Duplicate test transactions, paid-without-access states, platform delivery failures, and export failures may be submitted through the available owner-review process. Review does not automatically create a refund, credit, or entitlement change.

Future live paid service

This controlled-beta policy does not establish the final refund rules for a future live paid service. Before ProgramMetrics accepts real payments, the applicable customer terms will state the live price, fulfillment boundary, cancellation rules, refund conditions, support scope, and any other material payment terms.

Output and liability boundary

ProgramMetrics outputs are automated analytical and reporting-preparation tools. They do not replace professional review where professional judgment is required. Testers are responsible for reviewing and validating outputs before relying on or distributing them.

The controlled beta may contain defects, incomplete features, or temporary interruptions. ProgramMetrics does not promise uninterrupted or error-free beta operation. Nothing in this policy excludes obligations or liability that cannot lawfully be excluded.

Data-use boundary

The controlled beta is limited to properly de-identified, structured data that the customer is legally authorized to analyze. Prohibited data includes direct identifiers, identifiable regulated data, credentials and security secrets, financial-account information, and open-ended narrative fields that may identify someone.

ProgramMetrics does not perform legal de-identification or certify HIPAA, FERPA, or other regulatory compliance.

Questions

Questions can be sent to hello@programmetrics.io.