TEST CHECKOUT ACTIVEReal payment and music uploads stay disabled until these controls pass.
← Back to homepage

PRODUCTION READINESS

Trust is part of the product.

The beta Signal Scan processes selected audio locally and does not transmit or retain it. This page documents what must be completed before the site accepts payment or server-side unreleased-audio submissions. It is a launch checklist, not the final legal policy set.

HighLevel workflow

HighLevel holds contact, order, product, consent, status, deadline, and communication records. Payment events create one opportunity per order and trigger confirmation, reminders, internal tasks, delivery, refund, and deletion workflows.

Private audio storage

Audio lives in a non-public Cloudflare R2 bucket—not in the public site or a routine email. A server issues a randomized, single-purpose upload URL that expires within 24 hours and enforces content-based validation, approved type and size limits, malware scanning, rate limits, and isolated decoding.

Access and deletion

Reviewer access uses short-lived download links and least-privilege permissions. Access is logged. Source audio and working copies are scheduled for deletion 30 days after report delivery unless an approved exception applies.

Rights and consent

Rights-holder confirmation is mandatory. Public previews, audience testing, promotion, testimonials, marketing, and model training each use separate optional, unchecked permissions.

Commercial policies

Checkout records the Terms, Privacy, Refund, and Submission Terms versions accepted by the customer. The final operator, address, support contact, governing law, and attorney approval are required for live sales.

Diagnostic method

The score uses a versioned technical rubric, fixed benchmark tests, source and date disclosure, missing-input handling, confidence labels, drift review, and human quality-control procedures. It is not a chart probability or guarantee.

End-to-end test

The September 9 test confirmed that the processor accepts the $97 test payment, but the configured success URL returned a 502. HighLevel must correct that URL, verify the resulting CRM records and messages, then complete safe-file intake, report delivery, refund, and deletion tests.