Information you provide through forms, inquiries, downloads, subscriptions, or direct communication with AvalenData.
Home / Legal / Privacy Policy
Privacy and data use
Privacy practices for business data.
This policy explains how AvalenData handles website interactions, business contact information, data sourcing, customer requests, and privacy choices. It is written for transparency and does not claim certifications or legal guarantees beyond the practices described here.
Business contact dataWebsite requestsOpt-out handling
What this covers
How we collect, use, and manage data.
AvalenData may collect information submitted through our website, contact forms, email interactions, sales conversations, customer support workflows, and business data operations. The LakeB2B source describes compilation from business directories, public records, registrations, trade events, surveys, transactional data, and other commercial sources; AvalenData applies that same general category framing while rewriting the policy for our own brand and routes.
Business contact data may include professional identity fields such as name, business email, phone number, job title, company, industry, geography, company size, technology context, and related firmographic or campaign fields. We use this information to respond to requests, provide data services, support customers, maintain records, improve data quality, and honor privacy preferences.
Professional contact, company, firmographic, healthcare, industry, and campaign-relevant fields used for B2B data services.
Customer requests, suppression instructions, delivery notes, billing context, and support communications.
Policy commitments
Privacy controls should be operational, not decorative.
Source diligence
We aim to work with business data sources, public or commercial records, customer-provided files, and partner workflows that are relevant to a stated B2B use case.
- Business records and directories
- Publicly available professional information
- Customer or partner-supplied datasets
Data quality
We may normalize, validate, append, deduplicate, and update records so customers can reduce wasted outreach and maintain cleaner campaign or CRM data.
- Field standardization
- Duplicate handling
- Append and verification workflows
Use limitation
We structure services around B2B sales, marketing, analytics, enrichment, audience building, licensing, and related customer operations.
- Campaign planning
- Audience segmentation
- Customer support and delivery
Choice handling
We maintain processes for privacy, suppression, opt-out, do-not-sell/share, and data access or correction requests where applicable.
- Suppression requests
- Correction requests
- Deletion or opt-out workflows
Rights and requests
How to contact us about privacy.
You may contact AvalenData to ask about data associated with you, request correction, request suppression from future marketing use, or submit other privacy questions. We may need enough information to verify and process the request, such as your name, business email, company, jurisdiction, and the specific action requested.
We do not use this page to promise that every request is handled identically in every jurisdiction. The response may depend on applicable law, identity verification, customer contracts, technical feasibility, legal obligations, and whether AvalenData acts as a controller, processor, service provider, or vendor for a particular workflow.
Submit a privacy request
Use the contact form and include “Privacy Request” in the message so it can be routed correctly.
Frequently asked
Privacy questions for B2B data buyers.
Where does AvalenData get business contact data?
Data may come from business directories, public records, professional sources, customer-provided files, partner sources, registration workflows, event contexts, and other B2B-relevant sources. Specific sourcing can vary by dataset and service.
Does AvalenData sell consumer profiles?
AvalenData is focused on B2B, healthcare, firmographic, professional, and campaign-oriented data services. Any customer use should be scoped around a legitimate business purpose and applicable privacy requirements.
How do opt-out and suppression requests work?
When a valid request is received, we can add relevant identifiers to suppression workflows so future use can be limited according to the request, applicable law, and operational feasibility.
How is data protected?
We use administrative and technical practices intended to reduce unauthorized access, misuse, or accidental disclosure. Security practices evolve with the systems, vendors, and delivery models used for each service.