Pre-launch policy outline
Privacy
Revenue Found analyzes anonymized operational estimate data while minimizing the information it collects and retains.
This page is a product-design outline, not a final privacy policy or legal advice.
Data the audit is designed to use
The audit workflow is intended to accept fields such as an internal estimate ID, dates, estimate status, amount, service type, source, salesperson, and decline reason. Customer names, email addresses, phone numbers, and street addresses are outside the allowed dataset.
Data handling
Original CSV uploads are intended to remain outside the public web root, be processed for the requested audit, and be deleted after processing. Only normalized anonymized records and aggregate audit information are intended to remain for a short retention period.
Security approach
The application foundation uses secure sessions, request-forgery protection, output escaping, restrictive response headers, prepared database connections, and protected private storage conventions. No system can promise absolute security.
Before public launch
A qualified reviewer must complete this policy with the business identity, lawful basis, retention schedule, user rights, contact channel, service providers, and jurisdiction-specific disclosures that apply at launch.