What we can see during scoping
Initial scoping asks which systems you run, their date ranges and approximate volumes. Do not upload raw records at intake. Any later technical access should use a written scope, limited permissions and an approved access log. A preliminary estimate is not a buyer commitment.
What happens before anything moves
Before a sample is disclosed, review employee notices, customer and vendor contracts, confidentiality terms and applicable privacy law with your counsel. Record who can authorize disclosure and which categories must be excluded. Access to an export tool does not establish a right to license its contents.
De-identification
An owner-approved provider can remove direct identifiers and transform contextual identifiers under an agreed plan. Free text, attachments and combinations of facts can still identify people or reveal confidential material. Review a sample of the processed result and residual disclosure risk. The following categories stay out by default:
- HR files, performance reviews and compensation records
- Health and medical information
- Data you hold on behalf of clients or under a confidentiality obligation
- Payment card data, bank details, credentials and secrets
What buyers see before they bid
Prospective buyers can evaluate an approved data sheet describing systems, date ranges, volumes, exclusions and proposed uses. A sample is optional and requires separate written authorization, rights review and safeguards before disclosure. A confidentiality agreement alone does not cure missing permission.
What happens after you sign
Bulk delivery follows a signed license identifying the recipient, permitted dataset and conditions. The following are safeguards to request and negotiate; the signed agreement determines the actual obligations:
- No re-identification. Request a prohibition on re-identification, incident notification and remedies; residual risk remains.
- Bounded term and field of use. Define duration, field of use, termination and any rights retained by the seller.
- Limits on onward transfer. Specify approved recipients, sublicensing permissions and notice or approval conditions.
- Raw copies deleted. Negotiate a deletion deadline, backups, verification and handling of trained models or derivatives.
What Bright Info keeps
The engagement and processing plan should state what Bright Info and each provider may retain, for how long, and how deletion is evidenced. Distinguish source records, approved samples, metadata, bid records and signed agreements. Do not assume deleting raw files removes trained model artifacts.
Reporting a concern
Write to hello@brightinfo.com. The stated acknowledgment target is two business days. Include the affected page or process and a description; do not send raw confidential records or credentials.