Confidentiality & Data Handling

Last updated: October 26, 2026

Start with an inventory, not raw data

You can begin with asset descriptions: code language, repository count, commit date ranges, documentation categories, record quantities and applicable ownership restrictions. Do not upload private source code, credentials, customer files or candidate records through a public website form.

Separate access and permissions

A conversation or inquiry does not grant us access to your systems and does not authorise buyer distribution. If diligence is appropriate, the parties should agree the purpose, access scope, confidentiality terms and authorised recipients first. Provide only the minimum information needed at each stage.

Sensitive data safeguards

Before any dataset is assessed for external licensing, consider personal information, client confidentiality, trade secrets, contractual permissions, open-source obligations, malware or embedded secrets. Where a file cannot be lawfully disclosed or appropriately minimised, it should be excluded from the proposed scope.

Communication channels

Use support@datadealpilot.com to discuss an appropriate controlled transfer route if deeper technical diligence is approved. Ordinary email or a public website form should not be treated as a secure raw-data submission facility.

Retention and follow-up

The agreed diligence process should define what is accessed, who can see it, how long it is kept, and what happens if a licensing conversation ends without a deal. Refer to our Privacy Policy for website inquiry information and applicable requests.

Report a concern

If you believe information was sent in error or have a confidentiality concern, contact support@datadealpilot.com and describe the issue without including additional sensitive content.