Privacy Policy
Last updated November 20, 2026
How Zomler collects, uses, shares and protects personal information: the public information the Services organise, the information customers provide, and the information received through accounts and tools customers connect.
This Privacy Policy explains how Zomler, Inc. (“Zomler,” “we,” “us”) handles personal information in connection with the Zomler website, applications, API and related services (the “Services”). It applies whether you are a customer, a visitor, someone whose public information appears in the Services, or a user of an application or AI assistant that connects to the Services.
01Who we are
The Services are operated by Zomler, Inc.. For any privacy question, or to exercise your rights, contact us at support@zomler.com. If you represent a supervisory authority or need our data-protection contact, use the same address and mark it for the attention of the Privacy Team.
02Scope and key definitions
The Services handle three kinds of information, and they carry different rights and obligations, so this policy names them consistently:
- Public Information: information that is already publicly available on the internet, such as public profile pages, public posts and listings, reviews, ratings, business details and similar public records, which the Services collect from public sources and organise.
- Customer Information: information you provide or generate when you use the Services, such as your account details, billing details, the requests you make and the settings you choose.
- Connected-Account Information: information we receive from a third-party platform when you choose to connect an account you hold there. It is received only with your authorisation, used only for you, and never combined with Public Information or made available to other customers.
03Information we collect
- Account and contact details. When you request access, create an account, subscribe or contact us: your name, email address, company, sign-in credentials (held by our identity provider), and billing details (processed by our payment provider; we do not store full card numbers).
- Your requests. The requests you make through the Services: what you asked for, when, through which credential, what it was quoted and charged, and the answer you were given. We keep these so you can see your own activity and spending and so our support can explain any charge.
- Public Information. Information that is already public on the internet, collected from public sources: names, usernames, public profile fields, public posts and their public engagement figures, listings, prices, reviews, ratings, and business details such as a published address or website. Some of this may relate to identifiable people. Where a public source publishes a business contact detail, we may collect it as part of the public record.
- Connected-Account Information. When you connect an account you hold on another platform, we receive what that platform’s interface provides for your account and what you authorise, and nothing else. See “Accounts you connect”.
- Usage and device information. Log data such as IP address, browser and device type, pages viewed and referring URLs, through cookies and similar technologies described in our Cookie Policy.
04How we use information
- To provide the Services: to answer your requests, show your activity and balance, and operate your account.
- To organise Public Information into the answers the Services give, and to keep a record of how a figure changed over time.
- To bill you, prevent fraud and abuse, and enforce our terms.
- To communicate with you about your account, your requests and changes to the Services; marketing messages only with your consent or where the law allows, always with an opt-out.
- To measure and improve the Services, including aggregate analytics that identify no individual.
- To comply with legal obligations and respond to lawful requests.
We do not use Connected-Account Information for advertising, profiling, or any purpose beyond the one you connected the account for.
05Legal bases for processing (GDPR / UK GDPR)
Where the GDPR or UK GDPR applies, we rely on the following legal bases:
- Performance of a contract: to provide the Services you signed up for.
- Legitimate interests: to organise Public Information, secure and improve the Services, and prevent abuse; we balance these interests against your rights, and you may object at any time.
- Consent: for Connected-Account Information (the authorisation you give the platform), non-essential cookies, and marketing.
- Legal obligation: for tax, accounting and lawful requests.
07Accounts you connect (including Meta platforms)
Some features let you connect an account you hold on another platform so that the Services can act for you there. This section applies to every such connection, including connections to Meta platforms, whose terms require us to state the following plainly.
- What we receive: only what the platform’s official interface provides for the account you connected and the permissions you approved. We never ask for your password, and we do not collect information about other people’s private activity.
- What we use it for: to provide the feature you connected the account for, and nothing else. We do not use it for advertising, we do not sell it, and we do not combine it with Public Information or share it with other customers.
- How long we keep it: for as long as the connection is active. When you disconnect, or when the platform tells us you have removed the connection, we delete what we received, including the access token, within 30 days, except where we must keep a record for legal reasons.
- How to delete it: disconnect the account in your dashboard, remove the connection in the platform’s own settings, or use our data-request page. Platform-initiated deletion requests are honoured automatically and confirmed at the address the platform provides.
For a Meta account (Instagram or Facebook), the permissions the connection may request, and the only purpose each is used for:
- instagram_basic / instagram_business_basic: the connected account’s id, username, profile picture, follower and media counts, and its posts.
- instagram_manage_insights: reach, views, interactions, saves and shares for the connected account and its posts, and the aggregate age, gender, city and country breakdown of its own audience. Meta provides audience demographics only for the account that authorised us, never for anyone else.
- pages_show_list and pages_read_engagement: to find the Facebook Page linked to the connected professional account, which Meta requires in order to read the account’s data through this route. We do not post to the Page.
- instagram_manage_comments: to show comments on the connected account’s posts and, only where you ask us to, reply to them.
- instagram_manage_messages / instagram_business_manage_messages: to show and reply to conversations that the other party or you began. We cannot and do not send unsolicited direct messages.
- instagram_content_publish: only if you use publishing, and only to publish content you composed yourself.
- Business Discovery: where available, to read the public profile and public post metrics of professional accounts, which returns only what the platform already displays publicly and never audience demographics, contact details or private data.
08Public sources and platform terms
We collect Public Information from public sources and through licensed providers, in accordance with applicable law and the terms that apply to those sources. We collect only information that is public at the time of collection, we do not attempt to access private accounts or content, and we honour verified removal requests as described under “Removal and opt-out”.
10Connected AI assistants, API keys and the API
The Services can be used from inside a third-party AI assistant or from your own software. This section says exactly what we receive on those paths, because it is less than people expect:
- When you connect an assistant, you sign in to Zomler in your browser and approve the connection. We receive your account identity (the email and name on your Zomler account) and issue the assistant a token for your account. You can revoke it at any time under Connections in your dashboard.
- Each request carries only the inputs of the operation the assistant is calling, for example an identifier, a search query and a row count. We do not receive your conversation, your other messages, files, or the output of any other tool, and we never ask an assistant for its conversation history.
- API keys are stored as a one-way hash; the full key is shown to you once. Every call made with a key is attributed to that key, so you can see its spend and revoke it from your dashboard.
- The answer to a request goes back to the assistant or application that asked, under that provider’s own privacy terms. We do not share your requests or answers with anyone else, and we do not sell them.
11The assistant in your dashboard
The assistant answers questions in your dashboard by making the same requests a connected assistant would, on your account and charged to it. Because it runs inside the Services, we do receive these conversations:
- We store each question you ask, the answer, the requests the assistant made for it and what they cost, together with your account, so you can reopen your chats and so we can run, support, secure and improve the Services. Zomler staff can read them for those purposes.
- To write an answer, your question and the conversation so far are sent to an AI model provider that processes them on our behalf under contract. Do not put information in a chat that you would not want processed this way.
- Deleting a chat removes it from your history. We keep the record of the questions and answers in it for as long as we keep your request records (see “Data retention”), and delete it with your account.
12Browser extensions
Zomler offers browser extensions that bring the Services into the page you are viewing. This section says what an extension can see, what it sends and what it keeps.
- An extension can read the address and the title of the tab you are viewing, and only on the sites it supports, which are named on its store listing and in the browser’s install prompt. It cannot see the address or title of any other site, it does not read or change the content of any page, and it does not collect your browsing history.
- While you are signed in, each profile page you open on a supported site is reported to the Services under your account by its address and the name in the tab title, so the extension can show at once whether your organisation already holds that person’s details, and so your dashboard can show which profiles you looked at. We keep a record of those visits (the page address, the name, and when) against your account. The extension never sends page content, and sends nothing while you are signed out. When you ask it to look someone up, it sends that page’s public identifier to the Services and the lookup is charged to your account.
- You sign in with your Zomler account in your browser. The extension receives an API key for your account, never your password. The key is listed under API keys in your dashboard, where you can see its use and revoke it.
- On your device, in the browser’s own extension storage, it keeps that key, your preferences and the recent answers it has shown you. Signing out of the extension deletes the key and the saved answers; removing the extension deletes everything.
- Information received through an extension is used only to provide the feature the extension exists for. We do not sell it, we do not use or transfer it for purposes unrelated to that feature, and we do not use or transfer it to determine creditworthiness or for lending. It is shared only with the service providers described under “How we share information”, as needed to answer your request.
13Zomler Leads for Chrome
Zomler Leads for Chrome shows the work email and mobile number of the person whose profile you are viewing, using your Zomler Leads account (leads.zomler.com). Everything in “Browser extensions” above applies to it; this section adds what is particular to it.
- Signing in: the extension opens leads.zomler.com in a browser sign-in window, where you sign in with your Zomler account and choose to connect it. The extension receives an API key for that account, never your password. The key spends from your account’s wallet.
- What it can see: only the address and title of tabs on the profile pages it supports, which are named on its store listing and in the browser’s install prompt. It does not read or change page content, and does not collect your browsing history.
- What it sends, and only while you are signed in: each supported profile page you open (its address and the name in the tab title), so it can show whether your account already holds that person’s details; and, when you ask, a lookup for that page’s public identifier, which is charged to your account. We keep the record of those visits and lookups against your account.
- Feedback: when you send feedback from the extension, we receive the text you wrote, the extension’s version and your account, and the address of the page you were on only if you tick the box to include it. We use it to answer you and to improve the product.
- On your device, in the browser’s own extension storage, it keeps the key, your settings and the answers it has shown you. Signing out of the extension deletes the key and those answers from the browser; removing the extension deletes everything it stored. To switch the key off everywhere, write to support@zomler.com and we will revoke it.
- Permissions it asks the browser for: a side panel to show answers beside the page, storage for the items above, the browser’s sign-in window for connecting your account, and a menu item to open it in its own window. It talks only to the Zomler API and the pages it supports.
- Information received through the extension is used only to provide this feature. We do not sell it, we do not use or transfer it for purposes unrelated to this feature, and we do not use or transfer it to determine creditworthiness or for lending. It is shared only with the service providers described under “How we share information”, as needed to answer your request.
14Data retention
We keep personal information only as long as needed for the purposes above: account details and your request records (including your dashboard chats) for the life of your account, and deleted with it; billing records for the period tax and accounting law requires; Connected-Account Information for the life of the connection; and Public Information for as long as it is useful to the Services, subject to removal requests. Historical values may be kept to show how a figure changed over time, and are deleted or anonymised when no longer needed.
15International data transfers
We may process and store information in countries other than your own. Where we transfer personal data internationally, we use appropriate safeguards such as Standard Contractual Clauses or an equivalent lawful transfer mechanism.
16Data security
We protect information with encryption in transit and at rest, access controls, credential hashing, logging and monitoring, and a separation between Connected-Account Information and everything else. No system is perfectly secure; if you believe your account has been compromised, contact security@zomler.com. Our security page describes our practices and how to report a vulnerability.
17Your privacy rights
- GDPR / UK GDPR: subject to conditions, you have the right to access, correct, delete, restrict or object to processing of your personal data, to data portability, to withdraw consent, and to lodge a complaint with your supervisory authority.
- California (CCPA/CPRA): the right to know, delete and correct personal information, to opt out of sale or sharing (we do not sell or share as defined), and not to be discriminated against for exercising your rights.
- India (DPDP Act) and other jurisdictions: the rights the applicable law grants you, including access, correction and erasure.
To exercise any right, contact support@zomler.com. We respond within the time the applicable law allows (within 30 days for GDPR requests) and may need to verify your identity first. Account holders can also delete their account and its data from the dashboard, or through our data-request page.
18Removal and opt-out for people who appear in Public Information
If public information about you appears in the Services and you are not a customer, you can ask us to remove it through our data-request page. We honour verified requests within 30 days, remove the record from the Services, and take steps to prevent it from being collected again. Public sources remain public; removal applies to our copy.
19Children’s privacy
The Services are for businesses and professionals and are not directed to children under 16. We do not knowingly collect personal information from children, and we remove any we learn we hold.
20Changes to this policy
We may update this policy from time to time. We will post the new version here with a new “last updated” date and, where the change is material, tell account holders by email or in the Services before it takes effect.
21Contact us
Privacy questions and requests: support@zomler.com. Security reports: security@zomler.com. Postal enquiries can be sent to Zomler, Inc., for the attention of the Privacy Team, at the address published in the Services.