This Privacy Policy explains how LeadSlot (“LeadSlot,” “we,” “us,” or “our”) processes personal information when you visit our website, use our application, create or join an account, connect a service, communicate with us, receive outreach sent through LeadSlot, or appear in our business-contact database.
Privacy at a glance
- LeadSlot is a business-to-business prospecting and outreach service. Its features include a database containing more than 450 million business-contact records, data enrichment and verification, campaign tools, and connected-mailbox functionality.
- Some information comes directly from account users. Business-contact information may instead come from public, licensed, contributed, or otherwise permitted indirect sources.
- When customers upload data or run their own campaigns, they generally decide whom to contact and why. LeadSlot processes that information to provide the requested service, subject to the agreement with the customer and applicable law.
- You may ask us to access, correct, or remove information about you, object to certain uses, or opt out of a legally defined “sale” or “sharing.” You do not need a LeadSlot account to make a request.
1. Overview and scope
This policy applies to the LeadSlot website at our website and the LeadSlot service at our application. It also applies to related support, sales, demonstration, billing, integration, data-verification, and outreach activities.
This policy describes our practices; it is not, by itself, a request for consent. Where consent is required, we ask for it separately. You may withdraw consent at any time, without affecting processing that occurred before withdrawal.
A LeadSlot customer may have its own privacy notice that applies when it selects a recipient, uploads a record, writes a message, or otherwise determines how a campaign is run. If you received a message sent by a LeadSlot customer, that customer’s notice should explain its reasons for contacting you. You can still contact us about LeadSlot’s own business-contact database or our processing as a service provider.
2. Information we process
The information we process depends on how you interact with LeadSlot and which features an account administrator enables.
| Category | Examples | When we receive it |
|---|---|---|
| Account and profile information | Name, work email address, authentication identifiers, job title, profile details, preferences, and account status. | When you register, sign in, update a profile, or accept an invitation. |
| Organization and team information | Company name, website, industry, workspace, team membership, roles, permissions, seats, administrator settings, and invitations. | When a customer creates, configures, or administers a workspace. |
| Business-contact and company information | Name, job title or function, employer, business email, business telephone number, general location, professional profile URL, company domain, industry, company size, and related professional attributes. | From indirect sources, customer submissions, verification activity, and individuals who contact or update us. |
| Customer uploads and campaign content | Lead lists, CSV files, contact fields, tags, notes, campaign settings, templates, message text, personalization fields, schedules, and suppression entries. | When a customer imports data, builds a list, or configures an outreach campaign. |
| Connected mailbox and integration data | OAuth access grants or tokens, provider account identifiers, mailbox address and settings, connected CRM fields, and information made available to a feature that you request. | When an authorized user connects Google, Microsoft, a CRM, or another supported service. |
| Message and engagement data | Sender and recipient details, message content and metadata, sending time, delivery status, replies, bounces, unsubscribe or objection signals, opens, and link clicks. | When messages are prepared, sent, delivered, or interacted with through the service. Opens and clicks are collected only where the customer enables those features and their use is permitted. |
| Sales, contact, and scheduling information | Name, work contact details, company, meeting time and time zone, Calendly booking details, form responses, correspondence, call notes, and support history. | When you request a demonstration, submit a form, schedule a meeting, or communicate with us. |
| Subscription and billing metadata | Plan, seats, credits, add-ons, billing contact, invoice and transaction identifiers, payment status, currency, tax-related details, and subscription history. | When a customer starts a trial, purchases, renews, changes, or cancels a subscription. Payment providers process payment-card details; we generally receive metadata rather than full card numbers. |
| Device, log, and usage information | IP address, browser and device type, operating system, pages and features used, referring page, timestamps, session or cookie identifiers, approximate location derived from IP, error logs, and security events. | Automatically when you use the website or application. |
| Feedback | Product suggestions, survey responses, and other feedback you choose to provide. | When you give us feedback about LeadSlot. |
Please do not upload special-category or sensitive personal information unless a LeadSlot feature expressly requests it and you are legally permitted to provide it. LeadSlot does not intentionally build its business-contact database from information such as health data, biometric identifiers, private financial-account credentials, precise geolocation, or information about children.
3. The LeadSlot business-contact database
LeadSlot maintains and provides customers with search, enrichment, verification, and export access to a database containing more than 450 million business-contact records. A record may identify an individual in a professional capacity even when that individual never created a LeadSlot account or dealt with us directly.
What a record may contain
Records may contain the professional and company information described above, together with source or provenance information, validation status, confidence indicators, update timestamps, inferred professional attributes, and preferences or suppression flags. Inferences are based on professional or company information and may be incomplete or incorrect.
How the database is used
Customers may use LeadSlot to identify relevant business contacts, verify or enrich existing records, build prospect lists, and conduct lawful business outreach. Customers must independently determine whether they have a valid reason and legal basis to use a record and must comply with applicable marketing, privacy, employment, and communications laws.
Correcting or removing a record
You may ask us to show you the business-contact information we associate with you, correct an inaccurate record, or remove and suppress it from future LeadSlot customer results. A useful request includes your name, current or former employer, business email address, and a professional-profile URL, if available. We use those details only to locate the correct record and handle the request.
Correct or remove my business-contact record
We may retain the minimum information necessary on a suppression list so that a removed record is not unintentionally added again. A suppression record is not shown to customers or used for prospecting. Removal from LeadSlot does not automatically remove copies that a customer exported before your request or information held by an original source, search engine, or other third party. Those parties are responsible for their own copies.
4. Where information comes from
We receive information from the following sources:
- From you. This includes account registration, profile changes, uploaded files, support messages, feedback, meeting bookings, privacy requests, and settings you choose.
- From your organization and teammates. An administrator or teammate may create your account, invite you, assign permissions, upload a business record, or include you in workspace activity.
- From connected services. At your direction, Google, Microsoft, CRM providers, and other integrations provide information permitted by the access grant and needed for the feature you request.
- From public and publicly accessible professional sources. These may include company websites, professional profiles, public directories, business publications, government or corporate records, and other publicly accessible professional information.
- From licensed and other permitted data providers. We may receive business-contact, company, verification, enrichment, and deliverability information from providers that represent they are authorized to supply it.
- From customers and contributors. Customers may upload, correct, enrich, or validate contact and company information. We may also receive updates directly from the person identified in a record.
- From communications and service activity. Senders, recipients, email systems, security tools, analytics tools, and infrastructure providers may generate delivery, reply, unsubscribe, bounce, usage, and diagnostic information.
Because database information is obtained indirectly and professional details change, a record may be outdated or inaccurate. We use validation and update processes, but we cannot guarantee that every record is complete or current. Please use the correction or removal route above to tell us about an issue.
Where applicable law requires us to notify a person about information received indirectly, we provide notice within the required period using a reasonably available channel. If the law permits an exception—for example, because individual notice would be impossible or involve disproportionate effort—we document the basis, publish the information required by law, and apply any additional safeguards. You may contact us to ask about the source categories associated with your record.
LeadSlot’s matching, verification, and professional-attribute inferences are not intended to make decisions that produce legal or similarly significant effects about an individual. LeadSlot does not itself use Contact Data for automated decisions about credit, insurance, housing, healthcare, education, public benefits, law enforcement, or employment eligibility, and the Terms restrict customers from those uses.
5. How and why we use information
Privacy laws use terms such as “legal basis” to describe a permitted reason for processing. The bases below apply where the relevant law recognizes them. We do not rely on a legitimate interest when your rights and interests override it, and we seek consent where consent is required.
| Purpose | Information commonly involved | Legal basis, where applicable |
|---|---|---|
| Provide and administer the service | Account, workspace, customer uploads, connected services, campaign, subscription, and support information. | Performing our contract with you or the customer; taking requested pre-contract steps; and our legitimate interest in operating the service. |
| Build, verify, maintain, and provide the business-contact database | Professional contact, company, provenance, validation, and suppression information. | Our and our customers’ legitimate interests in accurate B2B research, verification, fraud prevention, and relevant professional communications; consent or another basis where required. |
| Connect mailboxes and run customer-directed campaigns | OAuth grants, mailbox settings, customer lists, campaign content, message metadata, delivery events, replies, and suppression information. | Performing our contract and acting on the customer’s documented instructions. The customer is responsible for establishing any additional basis required for its outreach. |
| Improve functionality and develop features | Usage, error, performance, feedback, and appropriately aggregated or de-identified information. | Our legitimate interest in maintaining and improving the service; consent for non-essential device access or analytics where required. |
| Secure LeadSlot and prevent abuse | Account, device, log, authentication, campaign, and security-event information. | Our legitimate interests in protecting users, recipients, systems, and data; performing our contract; and compliance with law. |
| Manage billing and business operations | Subscription, billing metadata, customer communications, and transaction records. | Performing our contract, complying with tax and accounting duties, and our legitimate interest in managing our business. |
| Respond to sales, support, and privacy requests | Contact, scheduling, correspondence, identity-matching, and request records. | Taking requested steps, performing our contract, complying with law, and our legitimate interest in responding and documenting the outcome. |
| Send service notices and permitted marketing | Account, company, work contact, product-use, and communication-preference information. | Performing our contract for operational notices; legitimate interests or consent for marketing, as applicable. You can opt out of marketing without losing service notices. |
| Comply with law and establish or defend claims | Information relevant to the request, dispute, investigation, or legal obligation. | Compliance with a legal obligation and our legitimate interests in protecting legal rights. |
Mailbox connections and campaign signals
An authorized user may connect a Google or Microsoft mailbox using OAuth. We use the resulting access grant to authenticate the connection and perform the mailbox functions that the user requests, such as sending campaign messages, synchronizing relevant replies, recording bounces, and maintaining suppression status. We do not ask for a mailbox password.
The specific data available depends on the provider permissions shown during connection and the enabled feature. You can disconnect a mailbox in LeadSlot or revoke access in the provider account. Disconnection stops future provider access, but it does not automatically delete campaign records already stored in LeadSlot; those records follow the account controls and retention practices below.
Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We apply comparable purpose and access limitations to Microsoft mailbox data.
Unsubscribes, objections, and suppression
LeadSlot may retain an email address or another limited identifier on a suppression list after a recipient unsubscribes, objects, or asks not to be contacted. This is used to prevent new outreach and to help customers comply with the recipient’s choice. It is not an indication that the recipient agreed to the original message.
6. Our privacy roles
When LeadSlot determines the purpose
LeadSlot generally acts as a controller, business, or similar responsible organization for website data, its own sales and support contacts, account administration, billing, security, service analytics, and the creation, maintenance, and provision of its business-contact database.
When a customer determines the purpose
When a customer uploads its own lead list, configures a campaign, connects a mailbox, or uses LeadSlot to communicate with contacts selected for the customer’s purposes, the customer generally acts as the controller or business and LeadSlot acts as its processor or service provider. The customer decides the purpose of the campaign, the recipients, the content, and the legal basis for outreach. If LeadSlot and the customer have executed a data processing agreement, that agreement governs its subject matter and controls if it conflicts with this general description.
LeadSlot remains responsible for processing it performs for its own purposes. The same data may be subject to different roles in different contexts—for example, LeadSlot may act as a processor for a customer’s campaign copy while acting as a controller for security logs and a suppression record.
7. How we disclose information
We may disclose information to the following recipients for the purposes described in this policy:
- LeadSlot customers and authorized users. Customers can view, verify, enrich, or export business-contact records selected through the service. Workspace administrators and teammates can see information according to their permissions.
- Infrastructure and service providers. Providers may support hosting and delivery, databases, authentication, security, analytics, customer support, scheduling, billing, email delivery, data validation, and other operations. This includes Vercel performance tooling where enabled, CookieYes for consent management, Google Analytics where enabled, Calendly for meeting scheduling, Slack for internal sales or support notifications, and providers supporting features an authorized user selects.
- Connected integrations. At a user’s direction, we exchange information with Google, Microsoft, CRM providers, and other connected services. The third party’s terms and privacy notice govern its own processing.
- Professional advisers and authorities. We may disclose relevant information to auditors, insurers, lawyers, courts, regulators, law enforcement, or other parties when reasonably necessary to comply with law, protect rights and safety, investigate misuse, or establish or defend claims.
- Business transaction parties. Information may be reviewed or transferred as part of a financing, reorganization, merger, acquisition, sale, or similar transaction, subject to appropriate confidentiality and legal requirements.
- At your direction or with your permission. We disclose information when an authorized user directs us to do so or when we clearly explain a new disclosure and obtain any permission required.
“Sale” or “sharing” under privacy laws
LeadSlot charges customers for access to a service that includes business-contact information. Some privacy laws define “sale” broadly enough that providing business-contact records through a paid service may be considered a sale, even if no price is assigned to an individual record. Certain analytics or advertising technologies may also be considered “sharing,” targeted advertising, or a sale under some laws. We do not use a narrower everyday meaning of “sale” to take away a legal opt-out right.
Where applicable, you may opt out of the sale or sharing of your personal information. A database opt-out applies to future availability through LeadSlot but cannot retrieve a copy that a customer lawfully obtained before we processed the request. Cookie choices apply to the browser and device on which they are made.
9. International transfers
LeadSlot operates from India, serves customers in other countries, and works with service providers that may be located internationally. Your information may therefore be processed in a country whose privacy laws differ from those where you live.
When a restricted international transfer requires a safeguard, we use an applicable legal mechanism, such as an adequacy decision, approved contractual clauses, or another mechanism recognized by the relevant authority. We also apply contractual, technical, and organizational protections appropriate to the information and our role. You may contact us to ask about the mechanism relevant to your information.
10. How long we keep information
We keep personal information only as long as reasonably necessary for the purposes described in this policy, including to provide the service, honor opt-outs, meet legal and accounting requirements, resolve disputes, secure our systems, and enforce agreements. The period depends on the type of information, the customer’s instructions and settings, the sensitivity and risk, whether the information remains accurate and relevant, and applicable law.
| Information | Retention approach |
|---|---|
| Accounts and workspaces | Kept while the account is active and for a reasonable period afterward for reactivation, support, security, disputes, and legal obligations, unless earlier deletion is required. |
| Customer uploads and campaign records | Kept according to customer controls, the subscription, any signed data processing agreement, and legal requirements. After the post-termination export period in the Terms, or after a valid earlier deletion instruction where applicable, Customer Data is placed on LeadSlot’s active-system deletion or de-identification schedule, subject to the limited exceptions below. |
| Mailbox access grants | Kept while the integration remains connected. On disconnection or account closure, access is revoked and tokens are removed from active use as soon as reasonably practical, subject to secure backup cycles and legal requirements. |
| Business-contact records | Kept while we reasonably believe the professional information remains relevant, accurate enough for its permitted purpose, and lawful to process. We correct, remove, or restrict records when required or when a valid request is approved. |
| Suppression information | Kept for as long as reasonably necessary to honor an unsubscribe, objection, deletion, or sale/share opt-out and prevent accidental re-addition. We limit it to what is needed for that purpose. |
| Sales, support, and privacy requests | Kept for the time needed to respond, maintain continuity, demonstrate compliance, and handle related disputes or security concerns. |
| Billing and transaction records | Kept for the periods required by applicable tax, accounting, anti-fraud, and financial-record laws and for resolving payment disputes. |
| Cookies, analytics, and logs | Kept according to the relevant consent choice, provider configuration, security need, and legal requirement. Individual cookies may expire sooner; choices can be changed through the cookie controls. |
Secure backups are overwritten on their normal cycle. Before that happens, a deleted item may remain isolated in a backup and is not restored for ordinary use. We may retain de-identified or aggregated information when it cannot reasonably identify an individual, and we take steps not to re-identify it.
11. Security
We use technical and organizational measures designed to protect personal information against unauthorized access, loss, alteration, disclosure, and misuse. Depending on the information and system, measures may include access controls, least-privilege permissions, encryption in transit, secret and token controls, logging, monitoring, backups, vendor review, and incident-response procedures.
No internet service or storage system can guarantee absolute security. Customers are responsible for protecting their credentials, limiting workspace permissions, securing connected accounts, and notifying us promptly about suspected unauthorized use. Please do not send passwords, full payment-card numbers, or other highly sensitive information in an ordinary support or privacy-request email.
12. Your privacy rights
Making a request
Depending on your location and our relationship with you, you may have rights to access, know about, correct, delete, restrict, or receive a portable copy of personal information; object to certain processing; withdraw consent; opt out of direct marketing, targeted advertising, sale, or sharing; and complain to a privacy regulator.
You do not need to create an account or pay a fee to make a request. We may ask for information reasonably necessary to locate the correct record, verify the requester, protect another person’s data, and document the response. We use verification information only for those purposes. If we cannot fulfill all or part of a request, we will explain the applicable reason unless law prevents us from doing so.
Requests involving a customer’s data
If LeadSlot processes information only on behalf of a customer, we may direct your request to that customer or help the customer respond. If you received an outreach message, use the message’s unsubscribe mechanism for the quickest campaign-level opt-out and contact the named sender about its own use of your data. You may separately ask LeadSlot to suppress your record from its own business-contact database.
European Economic Area, Switzerland, and United Kingdom
Where the relevant law applies, you may request access, correction, erasure, restriction, or portability; object to processing based on legitimate interests; and withdraw consent. You have an unconditional right to object to processing for direct marketing. If you object to other processing based on legitimate interests, we will stop unless we demonstrate a compelling lawful reason or need the information for legal claims.
You may complain to the data-protection authority where you live or work or where you believe an infringement occurred. We encourage you to contact us first so we can try to resolve the issue.
California
If the California Consumer Privacy Act applies to LeadSlot and your information, you may have rights to know the categories and specific pieces of personal information collected about you; know the categories of sources, purposes, and recipients; correct inaccurate information; delete information; opt out of sale or sharing; limit certain uses or disclosures of sensitive personal information; and receive equal service and pricing without unlawful discrimination for exercising a right.
The categories collected, sources, purposes, and disclosures during the preceding 12 months are described in Sections 2 through 8 and summarized below. “Sold” and “shared” use the broad meanings assigned by California law; they do not necessarily mean that money was paid for an individual record. LeadSlot does not offer a financial incentive in exchange for personal information through this policy.
| California category | Examples and disclosure | Sold or shared | Retention approach |
|---|---|---|---|
| Identifiers | Business contact details, account identifiers, IP address, and similar identifiers may be disclosed to customers, service providers, and user-selected integrations for the purposes in this policy. | Business-contact identifiers may be sold through paid database access. Online identifiers may be shared if an optional analytics or advertising technology is legally classified as sharing. | Account identifiers follow the account lifecycle; professional identifiers are kept while relevant and lawful or until a valid request; logs and suppression records follow the criteria in Section 10. |
| Professional or employment information | Job title, employer, role, professional profile, industry, and related attributes may be disclosed to customers and providers supporting database features. | May be sold through paid business-contact database access. Not otherwise shared for cross-context behavioral advertising unless an enabled technology is legally classified that way. | Kept while reasonably relevant, accurate enough, and lawful for the stated professional purpose, or until correction, removal, or restriction is required. |
| Internet or network activity | Website, application, device, log, engagement, and campaign activity may be disclosed to infrastructure, security, analytics, and integration providers. | Not sold as Contact Data. It may be shared through optional analytics or advertising technology where that disclosure is legally classified as sharing. | Kept according to consent choices, provider configuration, customer controls, security needs, and legal requirements. |
| Geolocation | Approximate location may be inferred from an IP address and disclosed to infrastructure, security, or analytics providers. | Not sold as Contact Data. It may be shared if an optional analytics or advertising disclosure is legally classified as sharing. | Kept with the associated analytics or security log under the criteria in Section 10; LeadSlot does not intentionally collect precise geolocation for the business-contact database. |
| Commercial, account, and transaction information | Plan, subscription, billing metadata, support history, and service use may be disclosed to operational providers and authorized workspace users. | Not sold or shared for cross-context behavioral advertising. | Kept for the subscription and periods reasonably needed for support, disputes, fraud prevention, and tax, accounting, or other legal duties. |
| Professional inferences | Professional attributes, likely role, verification status, or confidence indicators may be disclosed to customers and providers supporting database features. | May be sold through paid business-contact database access. | Kept while the associated professional record remains relevant and lawful, or until correction, removal, or restriction is required. |
| Sensitive personal information | Account credentials and OAuth grants are used only to authenticate, secure, and provide requested features. LeadSlot does not intentionally include sensitive personal information in its business-contact database. | Not sold or shared, and not used to infer characteristics in a way that requires a right to limit. | Access grants are kept while the integration is connected and removed from active use after revocation or closure, subject to backup cycles and legal requirements. |
You or an authorized agent may submit a request using the links in this section. For access, correction, or deletion requests, we may verify identity and an agent’s authority before completing the request. For a sale or sharing opt-out, we ask only for information reasonably necessary to identify the relevant record or browser choice and do not require account creation or identity verification unless the law permits and the request creates a reasonable fraud concern. We generally respond within 45 days after receiving a verifiable request and may extend that period where the law permits, with notice. Where LeadSlot is required to participate in a state-operated universal deletion mechanism, we process requests received through that mechanism as required by law.
LeadSlot does not knowingly sell or share the personal information of consumers under 16 years of age.
India
To the extent India’s Digital Personal Data Protection Act and rules in force apply, you may have rights to obtain information about processing, request correction, completion, updating, or erasure, withdraw consent, use a grievance process, and nominate another person to exercise rights in circumstances recognized by law. You are also responsible for providing authentic information and not impersonating another person when making a request.
You may raise a privacy grievance using the privacy email below. We will review it under the timelines and procedures that apply at the time. If a grievance is not resolved, you may use the escalation route available under applicable law.
Other locations
Other jurisdictions may provide comparable rights, including rights to appeal a denied request or opt out of profiling or targeted advertising. We honor rights that apply to LeadSlot’s processing and will tell you about an available appeal route in our response.
13. Children
LeadSlot is a business service and is not directed to children under 18. We do not knowingly create accounts for children or intentionally include children in the business-contact database. If you believe we have processed a child’s personal information, please contact us so we can investigate and take appropriate action.
14. Changes to this policy
We may update this policy to reflect changes to LeadSlot, our providers, our legal obligations, or our processing practices. The “Last updated” date shown with this policy identifies the current version. If a change materially affects your rights or how we use personal information, we will provide additional notice through the website, application, email, or another appropriate channel before the change takes effect when required.
An earlier version continues to apply to a dispute or activity to the extent required by law or an applicable agreement. We encourage you to review this page periodically.
15. Contact us
Contact us with a question, privacy request, objection, complaint, or concern about this policy. For a database request, include enough professional information to distinguish your record, but do not send identity documents unless we specifically explain why they are necessary and how to provide them securely.
LeadSlotEmail: arjun@leadslot.io
Website: https://leadslot.io/
Application: https://app.leadslot.io/
Country: India