Custom Dataset Terms

1. What is a Custom Dataset?

A custom dataset is a business contact or company dataset researched and prepared according to requirements agreed for a particular project.

A project may include requirements such as:

• target countries, regions, or cities
• industries or business categories
• company size
• revenue or turnover range
• target companies or accounts
• job titles
• departments
• seniority levels
• decision-maker criteria
• direct mobile numbers
• professional email addresses
• company information
• exclusion or suppression lists
• required record volume
• delivery format
• delivery schedule

The requirements agreed for a project determine what constitutes a valid record for that project.

2. Project Requirements

Before research begins, the customer should provide sufficiently clear targeting requirements.

Depending on the project, we may ask for:

• target geography
• target industries
• target company characteristics
• target job titles
• seniority
• departments
• target account lists
• excluded accounts
• DNC or suppression lists
• required fields
• preferred fields
• required volume
• deadline
• mobile-number requirements
• email requirements
• output format

Where a requirement is marked as strict, we will use it as a required project criterion.

Where a requirement is marked as best effort, we will make reasonable research efforts but its absence does not automatically make the record invalid.

By submitting a custom dataset request and agreeing to these Custom Dataset Terms, you authorize the CookLeads data team to contact you by email or phone to confirm your data requirements and to deliver your custom sample dataset. You may withdraw this authorization at any time by contacting privacy@cookleads.com.

If the customer changes the targeting requirements after research or delivery has begun, the change may require a revised scope, additional work, or a new project.

3. What Counts as a Valid Record?

A record is evaluated against the requirements agreed for the applicable project.

A record may include information such as:

• person's name
• job title
• company
• company website
• location
• professional email
• direct mobile number
• company size
• industry
• revenue or turnover
• other agreed firmographic information

Not every field is necessarily mandatory.

A record is considered valid when it satisfies the required criteria agreed for the project and passes the applicable verification or research process.

An unavailable optional or best-effort field does not automatically make an otherwise valid record invalid.

4. Mobile-Required Projects

Where direct mobile numbers are specified as a mandatory requirement, CookLeads will research and verify the mobile number using the verification methods applicable to the project.

Our verification process may include:

• operator lookup
• ring check
• caller-ID cross-check
• live verification call

A number may also be rechecked when a customer reports that it is incorrect or invalid.

If a required mobile number is confirmed to be invalid after re-verification, the affected record may qualify for an applicable remedy under Section 9 of these Terms.

A mobile number being valid does not guarantee that the person will answer a future call, remain reachable indefinitely, or respond to outreach.

5. Email Data

Professional email addresses are provided on a best-effort basis unless email is expressly defined as a mandatory project requirement.

Mobile-required projects

If a record contains a valid required mobile number but a professional email is unavailable or subsequently bounces, the record may remain valid where email was not a mandatory requirement.

Email-only projects

Where email is a mandatory requirement and a delivered email is subsequently confirmed to be invalid or bounced, the record may qualify for replacement, an additional record, refund, or billing adjustment according to the applicable project terms.

Where a work email cannot reasonably be traced, our research team may make reasonable efforts to identify another professional email where appropriate.

CookLeads does not guarantee future email deliverability after delivery.

6. Verification and Re-verification

CookLeads researches records according to the requirements of the applicable project.

Verification methods can include operator lookup, ring checks, caller-ID cross-checks, and live verification calls.

Verification is performed at or around the time of research and delivery. Contact information can change after delivery.

If a customer believes that a required field is incorrect, the customer should report the affected record through the agreed support or project channel.

CookLeads may re-verify the disputed information before determining whether the record qualifies for a replacement, additional record, refund, or billing adjustment.

7. Firmographic Information

Company information such as:

• employee count
• revenue
• turnover
• company size
• other estimated business attributes

may sometimes be estimated or derived from available business information.

Minor variations between an estimated value and subsequently available information do not automatically make a record invalid or refundable.

Where a firmographic criterion is explicitly defined as a strict requirement for a project, that requirement will be evaluated according to the agreed project specification.

8. Target Account, DNC, and Exclusion Lists

Customers may provide target account lists, existing-customer lists, DNC lists, or other exclusion lists where supported by the project.

Accepted formats may include CSV or Excel files.

Where an exclusion list is provided before the relevant research is performed, CookLeads can apply the list to the applicable project according to the agreed requirements.

An exclusion list is generally project-specific unless otherwise agreed in writing.

Customers are responsible for providing complete and sufficiently accurate exclusion information.

Where requested and supported by the project, Indian telephone numbers may be tagged or checked against applicable national DND requirements.

Application of a DNC or exclusion process does not constitute a guarantee that a customer's subsequent marketing or outreach will comply with every applicable law or telecommunications rule.

The customer remains responsible for lawful use of the delivered data and for its own outreach practices.

9. Replacements, Additional Records, Refunds, and Billing Adjustments

If a delivered record does not satisfy a mandatory project requirement, CookLeads may, depending on the circumstances and the applicable project arrangement, provide one of the following remedies:

• replacement record
• additional record
• refund
• adjustment against a subsequent bill

The appropriate remedy depends on the project, the nature of the issue, the agreed requirements, and the results of re-verification.

Required mobile number confirmed invalid

If a mandatory mobile number is confirmed to be invalid after re-verification, the record may qualify for an applicable remedy.

Email-only project with bounced email

If email is a mandatory requirement and the delivered email is confirmed to be invalid or bounced, the record may qualify for an applicable remedy.

Valid mobile but missing or bounced optional email

If the required mobile number remains valid and email was not a mandatory requirement, the record does not automatically qualify for a refund or replacement solely because the email is missing or bounces.

Firmographic variation

Minor differences in estimated company size, employee count, revenue, or turnover do not automatically qualify for a refund or replacement.

CookLeads will review disputed records individually against the agreed project requirements.

10. Reporting a Data Issue

If you believe that a delivered record does not satisfy a mandatory project requirement, provide:

1. the project or order reference;
2. the affected record;
3. the field you believe is incorrect;
4. the reason for the dispute; and
5. any supporting information reasonably available.

CookLeads may re-verify the record before determining the applicable remedy.

Customers should report data-quality issues within the project-specific period communicated with the order or delivery. If no project-specific period has been agreed, customers should report issues within a reasonable period after delivery.

11. Delivery

Custom datasets may be delivered in formats agreed for the project, including CSV or Excel where applicable.

Standard projects generally take 1–7 working days.

Niche, highly specific, or very large projects may require 2–3 weeks or another timeline agreed for the project.

Rolling or recurring projects may be delivered in batches according to the agreed schedule.

Delivery timelines are estimates unless a specific delivery commitment has been expressly agreed in writing.

Delays may occur where:

• the project requirements are incomplete;
• customer clarification is required;
• target criteria are unusually narrow;
• the requested volume is unusually large;
• additional verification is required; or
• the customer changes the requirements during the project.

12. Project Changes and Scope

Custom research depends on the requirements agreed for the project.

Changes to:

• geography
• industry
• company criteria
• job titles
• seniority
• required fields
• volume
• verification requirements
• exclusions
• deadline

after research has started may affect pricing, delivery time, or the number of records that can be supplied.

CookLeads may ask the customer to confirm revised requirements before continuing.

13. Customer Responsibilities

The customer is responsible for:

• providing accurate project requirements;
• providing accurate target or exclusion lists;
• identifying mandatory versus best-effort fields;
• ensuring that information supplied to CookLeads may lawfully be used for the requested research;
• using delivered data only for lawful purposes;
• complying with applicable privacy, marketing, telemarketing, electronic communications, and other applicable laws;
• maintaining appropriate suppression or opt-out lists for its own outreach;
• honoring applicable individual opt-outs and objections;
• determining whether its intended outreach is permitted in the relevant jurisdiction.

Receiving a dataset from CookLeads does not by itself establish that any particular marketing communication or outreach activity is lawful.

14. Customer-Supplied Data and Authorization

If a customer provides:

• customer lists
• target account lists
• DNC lists
• exclusion lists
• contact records
• other personal or business data

the customer represents that it has the necessary authority to provide that information to CookLeads for the requested purpose.

The customer should not provide passwords, authentication credentials, or unrelated sensitive information through a custom dataset request.

CookLeads may decline to process a request where the requested activity appears unlawful, unauthorized, or inconsistent with applicable requirements.

15. Data Protection and Privacy

Custom dataset projects may involve personal data, including professional contact information.

Processing of personal data is also subject to the CookLeads Privacy Policy and, where applicable, separate contractual data-processing terms.

The applicable legal role of CookLeads and the customer may depend on the nature and purpose of the particular processing activity. Where a customer provides personal data to CookLeads for processing on the customer's documented instructions, the parties may need appropriate contractual data-processing arrangements.

Nothing in these Custom Dataset Terms is intended to replace a legally required Data Processing Agreement, data-transfer mechanism, or other mandatory privacy documentation.

Customers operating in jurisdictions with specific data-protection requirements remain responsible for determining and complying with the requirements applicable to their own processing and outreach activities.

16. International Data and Cross-Border Processing

Custom projects may involve research, storage, processing, or delivery across different countries.

Where applicable, CookLeads will use appropriate contractual, organizational, and technical measures for relevant personal-data processing.

Where a separate data-processing or international-transfer agreement is required, the parties may enter into that agreement separately.

For EU/EEA-related controller-processor relationships, appropriate contractual arrangements should be used where required by applicable GDPR rules.

17. Data Security

CookLeads uses organizational and technical measures appropriate to the nature of the information and services provided.

Access to customer project information should be limited to personnel and service providers who require access for authorized project activities.

Customers should not submit credentials, passwords, payment credentials, or unrelated confidential information through a custom dataset request.

18. No Guarantee of Future Accuracy

Business information changes over time.

People change:

• employers
• job titles
• telephone numbers
• email addresses
• responsibilities

Companies change:

• ownership
• employee counts
• revenue
• locations
• business activities

Accordingly, verification reflects the information available and verification performed at the relevant time.

CookLeads does not guarantee that a contact record will remain accurate or reachable indefinitely after delivery.

19. Prohibited or Restricted Requests

CookLeads may refuse or modify a custom dataset request where the requested data, target group, use case, or research activity presents legal, privacy, safety, ethical, or operational concerns.

CookLeads does not undertake custom research for purposes that are unlawful or that would require unauthorized access to restricted systems or information.

20. Relationship With Other CookLeads Terms

These Custom Dataset Terms supplement the other applicable CookLeads policies and agreements.

They do not replace:

• CookLeads Terms of Service
• CookLeads Privacy Policy
• applicable Data Processing Agreement
• applicable project/order specification
• other written contractual terms expressly agreed for a particular customer or project

If a signed or otherwise expressly agreed project-specific contract contains terms that conflict with these public Custom Dataset Terms, the project-specific contractual terms may govern to the extent expressly agreed.

For custom dataset projects, the replacement, additional-record, refund and billing-adjustment remedies in Section 9 of these Custom Dataset Terms apply in place of the statement in Section 8.4 of the Terms of Service that fees are non-refundable.

21. Changes to These Terms

CookLeads may update these Custom Dataset Terms from time to time.

The “Last updated” date at the top of this page indicates the current version.

For an existing project, the version applicable to the project will generally be the version incorporated into or accepted for that project, subject to any separate written agreement between the parties.

Material changes to an ongoing contractual arrangement may be communicated through the applicable customer or project channel where appropriate.

22. Contact

If you have questions about these Custom Dataset Terms or a custom data project, contact CookLeads through the support or sales channel associated with your project.

For a data-quality dispute, include your project or order reference and the affected record(s) so that the research team can review the issue efficiently.

Email: privacy@cookleads.com

Humanzo Technologies Private Limited
Gurugram, Haryana, India

Plain-English Summary

For convenience, the main principles are:

• Your project requirements determine what counts as a valid record.
• Mandatory mobile numbers are checked and can be re-verified if disputed.
• Email is best effort unless email is a mandatory project requirement.
• A valid mobile does not become invalid solely because an optional email is missing or bounces.
• Email-only projects receive separate treatment for bounced emails.
• Estimated firmographic information can vary.
• DNC and exclusion lists can be applied when provided and supported by the project.
• Confirmed problems with mandatory data may qualify for a replacement, additional record, refund, or billing adjustment.
• The customer remains responsible for lawful use of the delivered data and its own outreach compliance.
• These terms govern custom dataset projects and work alongside CookLeads' other legal and privacy documents.