Recovery software should avoid taking custody of customer files.

High Caliber products should process selected files locally on the customer's own device by default. The normal product flow should not require customers to upload their original libraries, backups, databases, photos, messages, documents, or mind-map files to High Caliber.

• No private file uploads from ordinary sales pages.
• No passwords, payment-card details, or unrelated personal details requested by High Caliber forms.
• No analytics, tracking pixels, customer-data capture, or external form endpoints until explicitly approved.
• Any future diagnostics, crash reports, or telemetry must be opt-in, explained plainly, and covered by reviewed privacy wording.

Support should start with minimum necessary information: product name and version, operating system, error text, order or licence reference, and non-sensitive generated report text where available.

• Do not ask customers to send original recovery files by default.
• Use synthetic examples for screenshots, demos, training, and public marketing unless explicit permission exists.
• If a real customer file is ever required, use an approved secure transfer route and clear customer consent before receiving it.
• Keep phone-support, recording, transcription, helpdesk, and CRM wording aligned before any live support provider is connected.

Each product page and in-app privacy/about screen should explain what is processed locally, what support information may be requested, what is not collected, and which future provider will handle payment, receipt, licence, and download records if commerce is approved.

Next: check the support route, the delivery draft, or return to the recovery app catalogue.