Data security and privacy for B2B data projects
Understand how client files, project specifications, delivered datasets, and support records are handled. Controls are documented and confirmed before they are shared.
Project data
Target criteria, account lists, CRM exports, suppression files, samples, final datasets, and support communications.
Least privilege
Document which teams can access raw client files and the approval process for that access.
Retention
Written retention periods for source, working, delivered, support, and backup records.
1. Data handled during a project
Depending on scope, a project may involve target criteria, account lists, CRM exports, suppression files, field mappings, samples, final datasets, and support communications. The proposal identifies each data category and why it is needed.
2. Access control
Access controls cover identity, multi-factor authentication, role-based access, privileged access review, onboarding, offboarding, and audit logging. The proposal states which teams can access raw client files and under what approval process.
3. Encryption and file transfer
Encryption standards for data in transit and at rest, key management, secure upload and download methods, link expiration, and backup handling are documented before work starts. Specific standards are published only after the technical owner confirms them.
4. Retention and deletion
Default retention periods apply to source files, work files, delivered files, backups, and support records. The proposal explains how clients request deletion and how deletion is confirmed across production systems and backups.
5. Vendors and subprocessors
Material subprocessors, their purpose, processing locations, and the change-notice process are listed on request. The proposal explains how vendors are assessed and what contract protections apply.
6. Incident response
Detection, containment, investigation, customer notification, recovery, and post-incident review are described in the proposal. Any notification period must match signed contracts and applicable law.
7. Privacy operations
Source categories, opt-out and suppression handling, correction and deletion requests, regional processing roles, data processing agreements, and the privacy contact channel are explained during procurement.
8. Procurement documents
On request, buyers can receive a security questionnaire, data-flow diagram, subprocessor list, retention schedule, incident-response summary, access-control summary, penetration-test summary, insurance evidence, data processing agreement, and available independent audit reports.
9. Security contact
Report suspected security issues to the security team. Do not include live credentials, exploit code, or sensitive records in the initial message. To request security documentation, use the contact form.
Security: security@preciseglobal.com
Phone: +1 (720) 739-9155