Website inquiries
The staging contact form stores the information you intentionally submit as a private WordPress inquiry so the workflow can be tested. It does not automatically send email, SMS, voice calls, or marketing campaigns.
Revenue Leak Audit
The current audit workflow is designed for anonymized CSV data. Remove customer names, email addresses, phone numbers, and street addresses before uploading. The audit engine inspects headers for common identity fields and rejects obvious identity-related columns.
Original CSV files are temporary processing inputs and are deleted after successful processing, rejection, cancellation, failure, or staging expiration. Normalized audit results are retained only for the configured retention period.
What the audit stores
The audit can retain normalized business pipeline fields such as estimate identifiers, dates, status, quoted amount, service type, decline reason, aging, classification, and aggregate metrics. It is not intended to retain customer identity fields.
Security and access
Completed audit results use unguessable capability tokens. Administrative WordPress inquiries remain private and are accessible only to authorized administrators. Secrets and production credentials do not belong in public content, browser storage, or committed source files.
Analytics
The staging build records first-party interaction events in the browser for QA and measurement design. It does not load a third-party advertising tracker merely to create an analytics event.
Before production launch
This privacy notice must be reviewed against the final hosting arrangement, vendors, jurisdictions, retention settings, and any communications providers before production activation.