Public inquiry data
definedContact details and buyer context stay within the bounded inquiry workflow.
Trust + governance
ITAD Lens separates the public website from operational customer data and treats purpose, minimization, retention, and disclosure as explicit governance decisions.
The public website privacy boundary and the product principles used to separate public inquiry data, operational asset data, evidence, and customer-specific retention requirements.
Contact details and buyer context stay within the bounded inquiry workflow.
Customer asset records do not belong in the public website architecture.
Public analytics should avoid sensitive asset, project, financial, or operational data.
Production processors and retention periods require deployment-specific documentation and legal review.
Jurisdiction-specific privacy requirements must be reviewed before regional processing or transfer.
A data element should have an explicit purpose before it is collected or retained.
Marketing inquiries must not quietly become an alternate path for customer asset inventories or project records.
Collect only the fields required for the public interaction, then route them to the approved destination.
Retention, access, and deletion expectations should be documented for the deployed services rather than assumed.
Contact details and buyer context stay within the bounded inquiry workflow.
Customer asset records do not belong in the public website architecture.
Public analytics should avoid sensitive asset, project, financial, or operational data.
Production processors and retention periods require deployment-specific documentation and legal review.
Jurisdiction-specific privacy requirements must be reviewed before regional processing or transfer.
These are the kinds of records the operating model must preserve or produce. Availability depends on the product workflow, configured providers, and the event being evidenced.
No. The public website does not serve as an asset-upload, project-intake, or customer portal surface.
Review the website boundaryOnly the fields required to route the enterprise conversation; the form contract prohibits operational asset records.
Request flowNo. Final retention and processor details depend on the deployed services and applicable legal requirements.
Data governanceNo. The production privacy notice requires legal review of the actual deployed processors, regions, and rights obligations.
Review the limitationThe same boundary that protects the public site from operational data also keeps enterprise review simpler and more defensible.