Project Requirements
Audience, geography, fields, volume, exclusions, and intended workflow are reviewed before larger delivery.
Responsible Data
Data Privacy & Responsible Sourcing
EnrichPilot prepares audience, enrichment, matching, and activation data around approved project requirements, available source rights, permitted use, exclusions, and practical quality controls.
Data availability does not automatically mean every field or use case is appropriate for every project.
Purpose comes before the data.
Before a project is accepted, EnrichPilot reviews the intended audience or enrichment workflow, requested fields, geography, exclusions, delivery requirements, and permitted use.
Available data and services may vary based on source rights, project requirements, geography, platform requirements, and other applicable restrictions.
Permitted Use
Availability is considered together with source rights, contractual restrictions, platform requirements, and the approved use case.
Review Before Scale
Where practical, counts, samples, match indicators, or feasibility notes help clients review fit before larger delivery.
Data Categories
Data EnrichPilot may work with
Depending on the approved project and available coverage, EnrichPilot may work with several categories of data.
Business & Professional Data
- Names and professional roles
- Titles, seniority, departments
- Business contact information
- Professional profile information
Company Data
- Company identity and domains
- Industry and classification
- Employee size and revenue indicators
- Company profiles and other available firmographics
Location & Address Data
- Business or permitted address information
- Geography and postal attributes
- County, ZIP, and location indicators
- Other available address-quality attributes
Identity, Audience & Signal Data
- Matching indicators
- Available identity attributes
- Mobile advertising IDs (MAIDs) where available
- Intent, job, and company-change signals where available
Customer-Provided Data
- CRM exports
- Account or contact files
- Suppression/exclusion lists
- Other project inputs supplied by the customer
Consumer / Household Data
For approved use cases, certain workflows may include available consumer, household, address-level, property-related, or contact-availability indicators where permitted and appropriate.
Sensitive / Restricted Requests
What EnrichPilot does not treat as an ordinary audience request
EnrichPilot avoids sensitive consumer targeting and may decline requests that are legally inappropriate, inconsistent with data-handling standards, or unsuitable for the available data.
Healthcare audience work is limited to appropriate business, professional, and facility-level information.
Patient records
Protected health information (PHI)
Medical histories
Insurance claims data
Patient-level targeting
Sensitive medical audience segments
Passwords
Payment card information
Other highly sensitive information unless expressly agreed in writing
Suppression
Suppression, exclusions & responsible activation
Project requirements can include suppression and exclusion logic before delivery or activation.
Suppression requirements vary by project and should be confirmed before activation.
Customer-provided suppression lists
Bounced or failed records
Domain exclusions
Account or company exclusions
Geography exclusions
Other agreed project-specific suppression rules
Customer-Provided Files
Customer-provided files
When a customer provides a CRM export, account list, contact file, or other supporting data, EnrichPilot uses the information to review or perform the requested project.
- Customer is responsible for having the right and authority to provide the information
- Access should be limited to the systems and people needed for the project
- Delivery may use approved workflows such as Snowflake, Delta Sharing, Amazon S3, SFTP, encrypted files, or another agreed method
- Information is retained only as reasonably necessary for the project, business/security records, dispute resolution, or legal/contractual obligations
Do not submit patient information, PHI, passwords, payment-card information, or other highly sensitive personal information unless EnrichPilot has expressly agreed in writing to receive it.
Transparency
Transparency over false certainty
No dataset is complete or error-free. People change jobs, companies change, contact information ages, source coverage varies, and matching quality depends on the identifiers available.
EnrichPilot uses available validation indicators, suppression checks, deduplication, matching confidence, review flags, and delivery notes where appropriate so customers can better understand the data before using it.
Privacy Requests
Privacy requests & questions
Individuals may contact EnrichPilot to request access to, correction of, or deletion of information they have submitted directly, or to ask questions about other information associated with them that EnrichPilot may process.
Requests are reviewed subject to applicable legal, contractual, security, identity-verification, and recordkeeping requirements.
Contact: sales@enrichpilot.com
Responsible by design
Have a specific data or permitted-use question?
Share the audience, fields, geography, intended workflow, or data-handling requirement and we will review what is practical before the project moves forward.