Privacy Policy
Last updated: November 6, 2026
1. Who we are and what this policy covers
Zero Gaps, Inc. (“0gaps”, “we”, “our”, “us”) is a Delaware corporation at 2810 North Church Street, Wilmington, DE 19802, US. We run 0gaps.com and the 0gaps app, which help managed service providers (MSPs) find local companies with technology gaps, research them and prepare outreach.
This policy explains how we handle personal information about five groups of people:
- Customers and users: people who create an account, buy a plan or use our domain checks.
- Business contacts (prospects): people at companies we research, such as owners and IT decision-makers, whose work details we make available to our customers. Section 3 and our Business contact notice cover them.
- People whose data customers bring to us: for example, contacts synced from an MSP's CRM or PSA. Section 4 covers them.
- Vendor and partner contacts: people at technology vendors and distributors who work with us.
- Live chat guests: people who write to us through live chat, when available, without an account. The Live chat section covers them.
Who decides what happens to the data:
- For customer accounts, business contact data, and our website, 0gaps is the controller.
- For data an MSP collects through our tools or syncs from its own systems, the MSP is the controller, and 0gaps is its processor.
This policy does not cover what our customers do with data after they export it or send outreach. Each customer is responsible for its own use, including compliance with anti-spam and marketing laws.
2. Information we collect about customers
| Category | Examples | Source |
|---|---|---|
| Account | Name, work email, company name, role, password hash, team members | You |
| MSP profile ("DNA") | Your services, prices, service area, positioning, website content | You and your public website, which we analyze at sign-up |
| Plan and billing | Plan, credit balance, top-ups, invoices, billing address, last 4 digits of card | You and our payment provider |
| Usage | Leads browsed, unlocked or disqualified, Profiling and Messages runs, settings, exports | Our app |
| Integration data | Records synced from your CRM or PSA, connection status | Tools you connect (Section 7) |
| Device and log | IP address, browser, device, approximate location, timestamps, error logs | Automatically, via cookies and server logs |
| Communications | Support requests, feedback, calls and emails with our team | You |
| Live chat, when available | Messages, optional email, page addresses, browser and device details, IP address, screenshots you allow | You and your browser (see Live chat) |
| Domain checks | Domains you check and the email you give to receive results | You |
We do not receive or store full card numbers. Payments are handled by Lemon Squeezy, which acts as merchant of record and processes payment data under its own privacy policy.
3. Information about business contacts (prospects)
We research companies and the people who make decisions there, so our MSP customers can offer them relevant services. We only process information about people in their professional role.
What we collect
- Company: name, domain, address, size, industry, news and job posts.
- Company technology: results of checks on public internet records, such as DNS, email authentication (SPF, DKIM, DMARC, BIMI) and publicly visible technology. We do not log in to, test or access any non-public system.
- Business contact: name, job title, work email, work phone number, LinkedIn profile URL and professional background.
- Profiling: an AI-generated summary of a contact's likely responsibilities, priorities and suitable approach, based only on the professional information above.
We do not collect sensitive data (such as health, religion or political views) or personal home addresses for this purpose.
Where it comes from
- Public sources: company websites, public business registries, news, job boards and public professional profiles.
- Public internet records: DNS and similar records anyone can query.
- Business data providers.
Why and on what basis
We make this information available to MSP customers so they can contact businesses that may need their services. Under GDPR and UK GDPR, our legal basis is legitimate interests: helping businesses find relevant IT and security services. We have assessed that this interest is not overridden by the rights of the people concerned, because we use only work-related information, limit access, and offer an easy opt-out.
Who receives it
- When an MSP unlocks a contact, that MSP receives the contact details and can export them or sync them to its CRM.
- A lead assigned to an MSP is not offered to other customers through 0gaps.
- MSPs who receive the data become independent controllers of it and must use it lawfully.
Your choices
If you are a business contact, you can ask what we hold about you, correct it, or ask us to delete it and stop offering it to customers, at any time. Send us a contact notice by sending an email to contact@0gaps.com. We keep a minimal suppression record (such as your email address) so we do not collect you again. Where we have shared your details with an MSP, we will tell you which MSP on request.
4. Data we process on behalf of MSPs
Some tools handle data for an MSP rather than for us. In these cases, we act as the MSP's processor and follow its instructions:
- CRM and PSA sync: records we read from or write to the MSP's own systems.
- Domain checks: checks an MSP runs on domains it chooses, such as its existing clients' domains, using public records only.
We do not use this data for our own lead research or offer it to other customers. People whose data was collected this way should contact the MSP first; we will help the MSP respond.
5. How we use information and our legal bases
| Purpose | Data used | Legal basis (GDPR / UK GDPR) |
|---|---|---|
| Provide the service: findings, unlocks, Profiling, Messages, exports, sync | Account, DNA, usage, integration, prospect data | Contract with you or your account creation; legitimate interests for prospect data |
| Billing, credits and fraud prevention | Account, billing, usage, device | Contract or your account creation; legal obligation; legitimate interests |
| Support and service messages | Account, communications | Contract or your account creation |
| Live chat, when available, including limits on abuse | Live chat data (see Live chat) | Contract or your account creation; legitimate interests |
| Marketing to customers and prospects of 0gaps | Account, usage, business contact data | Legitimate interests, or consent where the law requires it; you can opt out anytime |
| Improve and secure the service, including product analytics | Usage, device, aggregated data | Legitimate interests |
| Vendor and partner program reporting | Limited MSP usage data (Section 8) | Legitimate interests, or consent where stated |
| Legal compliance and disputes | Any relevant data | Legal obligation; legitimate interests |
We do not make decisions with legal or similarly significant effects about anyone solely by automated means. Lead matching and Profiling support our customers' sales decisions; they do not decide anything about the people profiled.
6. How we use AI
Profiling, Messages, findings summaries, and parts of lead research are generated by large language models from third-party AI providers. To produce them, we send the relevant data to those providers: business contact and company data, your MSP DNA, and the instructions you give.
- AI providers process this data only to return results to us.
- We do not use your account data or synced CRM data to train AI models offered to other customers.
- AI output can be wrong. Profiling describes a likely professional picture, not verified facts. Review Messages before you send them.
Live chat, when available, also sends message text to an AI provider, as described under Live chat.
Live chat
When available, you can write to our team through the chat button on our website and in the app, with or without an account.
What we collect
- Your messages and our replies. If you are signed in, they are linked to your account, and replies you have not seen go to your account email.
- Your email, if you are a guest and choose to give it. It is optional. We use it to email you our replies that you have not seen, with a link back to the chat that works for 30 days, and to tell whether a guest chat belongs to an account. We do not add it to marketing lists.
- With each message you send: the address of the page you are on and, when your browser reports it, the address you came from, which can be on another website; your browser and device details (browser identification string, screen size, language and time zone); and your IP address. From both addresses we drop the part after any # and all query values except utm_ values, ref and tab. The rest of each address is kept.
Recognizing a returning guest
If you write as a guest and have allowed analytics cookies, your browser also sends a hash of a few of its details (browser identification string, language, time zone, screen size, platform and number of processor cores). Our staff see it only as a hint that two chats may be the same person. It does not join chats by itself. It is not sent without analytics consent, or with a Global Privacy Control signal. We keep a stored hash until the chat is deleted, unless a later message changes it: each message you send as a guest from the same browser replaces it, or clears it if analytics consent is no longer on. So if you withdraw consent, the stored hash stays until your next such message. Some hashes can no longer change that way and stay until the chat is deleted: those of a browser that has signed in, of a chat that has joined another chat, and of a browser that was removed from the chat because someone opened a link from a reply email. A browser that opens such a link starts with no hash, and its messages send one only with analytics consent.
Joining chats
If you chat as a guest and then sign in on the same browser, the guest chat joins your account when the email typed in it is your account email, or, if no email was typed, when the last guest message was within the previous 24 hours. If you came to the chat through a link in a reply email, it joins only when that address is your verified account email. Our staff can also join two chats in our inbox when they appear to be the same person, and can undo that.
Screenshots
To help with a problem, our team or an automated check may ask for a screenshot of the page you are on. You are asked first, each time, and you can decline. If you allow it:
- Blanking covers form fields only: what is typed or chosen in text boxes, text areas, dropdowns and editable areas. Password fields, embedded frames and the chat window are left out. If your browser cannot show that the blanking works, no screenshot is taken.
- Personal data outside those fields can appear in the image. Anything else on the page may be captured, such as names, email addresses, phone numbers and messages shown as page text, including parts below the visible area, and including other people's contact details shown in the app.
- The image is stored privately and appears in the chat. Only our staff, whoever can read that chat and anyone who has a 15 minute link our team created can open it, and it is deleted after 30 days. A record of the request, with the page address, stays with the chat.
Who receives it
- Slack: our team gets an alert for new messages, with your name or email, your company if you have an account, the page address and up to 500 characters of the message.
- Telegram: our team reads and answers chats in a private Telegram group, when we use it. The group gets your messages, your name or email, your company if you have an account, the page address, the page you came from, and your browser, device, screen size, language and time zone. The team may also see a note that another chat may be from the same person. Screenshots are not posted there as images. Our team gets a note that you allowed or declined one. When a team member asks for it, a link is posted in the group, stored by Telegram like any message. Anyone who has that link can open the screenshot for 15 minutes. Telegram stores what it receives on its own servers.
- Typesafe: an AI provider. To decide whether a screenshot would help, we send it the text of your message and of up to 3 of your earlier messages. We do not add your name, email or the page address, but it receives whatever you typed. Section 6 applies.
- Our hosting and email delivery providers store and send this data as Section 8 describes.
Product and marketing messages
If you have an account, we may use the fact that you wrote to us, when, the page you wrote from and whether you are waiting for a reply to choose which product and marketing messages you get, or to hold them back while you wait. We do not use the text of your messages for this.
How long we keep it and deletion
- We keep chats until they are deleted. Apart from the 30 days for screenshot images, they do not expire. Deleting your account does not delete your chats, so ask us to delete those too.
- To ask us to delete a chat, email contact@0gaps.com. We delete the chat and any chats joined to it, with their messages, email, browser details, IP addresses, screenshots and links. A chat that was never joined to it stays, so tell us if you have had more than one.
- When we use Telegram, deleting a chat also means we delete its topic there. Telegram's own retention of deleted data is outside our control. Deleting a chat does not remove Slack alerts already posted or emails already sent. We keep a record that a chat was deleted, with who deleted it and why, without its messages, email or name.
- If we block a browser, IP address or account for abuse, we keep only a hash of it until the block is removed, even after the chat is deleted. Messages sent while blocked are still stored, without alerting our team.
7. Integrations
You can use 0gaps without connecting any of your systems. Integrations are off until you turn them on, and you choose what each one can do.
- CRM and PSA sync: we write unlocked leads to your CRM and read only the records needed to avoid duplicates and track status.
- We request the narrowest access each provider allows, and store access tokens encrypted.
- You can disconnect an integration at any time in the app or in the connected tool. When you do, we stop syncing and delete stored tokens; synced copies held by us are deleted within 30 days.
We never access your email inbox or your clients' systems unless a feature you turn on clearly says it needs that access.
California and other US state laws
Making business contact data available to customers may count as a “sale” under some US state privacy laws. People can opt out of this at any time. Send us an opt-out notice by sending an email to contact@0gaps.com (“Do Not Sell or Share My Personal Information”). We do not knowingly sell the data of anyone under 16.
9. International transfers
We are based in the US, and our team works from the US and Armenia. Our providers may process data in the US, the EU, and other countries. You can ask us which safeguards apply to a transfer by emailing contact@0gaps.com.
10. How long we keep information
| Data | Kept for |
|---|---|
| Account, DNA, prospects you unlocked and history | While your account exists, including on the Free plan. Deleted within 30 days after you delete your account |
| Billing records | 7 years, for tax and accounting |
| Business contact data in our research database | While it remains accurate and useful, reviewed at least every 3 months; deleted on request |
| Opt-out and suppression records | As long as needed to honor the request |
| Integration tokens and synced copies | Until you disconnect, then deleted within 30 days |
| Logs and security data | 12 months |
| Support communications | 3 years |
| Live chat messages, email, browser details and IP addresses | Until deleted, including on request |
| Live chat screenshot images | 30 days, or until the chat is deleted if sooner |
| Live chat block records (hashes only) | Until the block is removed |
| Data processed for MSPs (Section 4) | As the MSP instructs, and deleted when the MSP's account closes |
11. Security
We protect data with encryption in transit and at rest, role-based access, multi-factor authentication for staff, logging and regular security reviews. No system is perfectly secure. If a breach affects your personal data, we will notify you and the authorities as the law requires.
12. Your rights
Depending on where you live, you may have the right to:
- access the personal data we hold about you and get a copy;
- correct inaccurate data;
- delete your data;
- restrict or object to processing, including processing based on legitimate interests and all direct marketing;
- receive your data in a portable format;
- withdraw consent where we rely on it;
- opt out of the "sale" or "sharing" of personal data and of profiling used for significant decisions (some US states);
- not be treated differently for using these rights.
To use them, email contact@0gaps.com. We will verify your request and respond within one month (GDPR) or 45 days (US state laws). An authorized agent may act for you with written permission.
14. Children
0gaps is a business service and is not meant for anyone under 18. We do not knowingly collect children's data.
15. Changes to this policy
We will post updates here and change the "Last updated" date. For material changes, we will notify customers by email or in the app before they take effect.
16. Contact
Zero Gaps, Inc., 2810 North Church Street, Wilmington, DE 19802, US
Requests: contact@0gaps.com