Datacircle

Privacy Policy

Last updated: November 8, 2026

This page says what we collect when you visit datacircle.dev, why, and what you can do about it. "We" means Datacircle, in California, United States.

datacircle.dev is a sheet of GTM APIs. You can read, filter and download the sheet with no sign-up.

Data we collect

  • Request logs. We log each request: your IP address, the names and versions of your browser and operating system (on some phones, the model too), the languages your browser asks for, the page you asked for, the site you came from and the time. If an AI agent connects to our MCP server, we also log the name and version of the app it runs in and the protocol version it asks for, then each tool it calls and what it asks.
  • Visits. Our script keeps a random ID in your browser's local storage until you clear local storage. With this ID, we can tell one person's visits from another's. The script also keeps details of each visit in your browser's local storage until your next visit starts. If your browser refuses local storage, our script keeps the ID and the visit details in session storage. Session storage lasts until you close the tab. Our script uses two cookies when your browser refuses both local and session storage. A cookie named visitor keeps the ID for 400 days after you last open a page. A cookie named visit keeps your visit details for 30 minutes after you last open or leave a page. The script keeps a second random ID that lasts for one visit only. The script keeps the whole address of your first page, with every tag in your link. The script also keeps the campaign tags of your link (utm_source, utm_medium and utm_campaign) as separate items. The script keeps the site and the page that sent you here, as your browser reports them. The script notes how you opened the page: a link, a reload, back or forward, or a tab. The script counts the pages of your visit and how long you spent on them. The script notes whether you scrolled, clicked, tapped, typed or moved the pointer. The script also notes how deep you scrolled into your first page. The script notes whether you typed a number into the price box on a plan page. When you click a link to another site, the script keeps that site's name. The script also keeps the address of our page that held the link, for up to 20 links a visit. The script sends these details to our server, with the times your visit starts and ends. The script uses the time you last opened or left a page to tell when a new visit starts. The script does not send us the time you last opened or left a page. We count visits and visitors from what the script sends us. A bot is a program that runs a browser. A browser that calls itself a bot counts too. The script keeps nothing in a bot's browser. The script sends us one note per page instead. This note holds the page's whole address, campaign tags included. This note also names the site that sent the bot. The script also says how the bot opened the page. We mark the visit as a bot's. We leave the visit out of our visit count. With each visit, we store your IP address. We look up the country and network of your IP address in a list on our server. We store the country and network too. We store the headers of your browser's request with the visit. These headers include your browser's languages and whether you came from another site. We never store your cookies. We store the names and versions of your browser and operating system, and on some phones the model too. We use your IP address so that one address can't add too many visits to our count. The script sets no other cookie. Our server sets a cookie named served on every page. The served cookie holds the time we sent the page and lasts one day. Our script reports your visit. Your browser sends the served cookie back to us with the report from our script. We note whether the served cookie came back. A program can report a visit without loading a page. That program sends no served cookie. A report with no served cookie tells us a program may have sent the report. We give the script's details to no other company.
  • Your account. From your first visit, your browser keeps in its local storage the site you first came from and the first page you opened. When you sign up, your browser sends us the site you first came from and the first page you opened, and we keep both. We keep your work email and the times you signed up and signed in. We keep the ref tag in the link you signed up through. We also keep the ref tag of any later link you sign in through. We keep the time of each click on "Join us on WhatsApp" on your dashboard or a results page. We keep your IP address each time you ask for a sign-in code or type a wrong code. Each time we refuse a sign-up, we log the part of the refused email address after the @. If you talk with us on WhatsApp, we may add your WhatsApp number to your account. Your browser keeps a sign-in token in its local storage, so you stay signed in.
  • An email you send us. We keep the message and the email address you send to wayne@datacircle.dev. We use your message and your email address to answer you and to test the GTM APIs we list. To test these APIs, we look up your LinkedIn page by your name and company. Our test results show how each provider did. They never show your email address, your name or your phone number.

Our use of your data

We use your data to keep the site running and to fix what breaks. We use it to learn which pages you read, to answer you and to test the GTM APIs we list. We don't sell it, and we don't use it for ads.

Who else sees it

  • The services we use. Other companies host our server and our email.
  • The providers we test. We test APIs that find or check an email or a phone number. We also test APIs that find the person behind an email or return a LinkedIn profile. For each test, we send the provider what its API needs: your email address, your name, your company's website, your LinkedIn page or the phone number in your email signature. We find your LinkedIn page through one of the providers we test or through a web search.
  • The law. We give it to a court or a government agency when the law requires it.
  • A new owner. If another company buys or merges with Datacircle, that company gets it, and this policy covers it.

How long we keep your data

  • Request logs. We keep request logs for 400 days, then delete them.
  • The MCP server's logs. An AI app can use our MCP server. We keep the app's name and tool calls for 30 days, then delete them.
  • Our API's limit. You can make 60 calls a minute to our API from each address. To count the calls, we keep a scrambled copy of the address for one minute, then delete the copy. We never keep the address itself.
  • Visits. We keep your visits until you ask us to delete them. Your browser keeps a random ID for your visits until you clear local storage. If your browser refuses local storage, our script keeps the ID until you close the tab. If your browser refuses that too, our script keeps the ID in a cookie for 400 days. We keep the served cookie in your browser for one day.
  • Your account. We keep your account and the data in your account until you ask us to delete them. If you type a wrong sign-in code, we keep your IP address until you sign in. When we refuse a sign-up, we log the refusal and delete the log after 30 days.
  • Your emails to us. We keep your message and your email address until you ask us to delete them.

To have us delete your data, write to wayne@datacircle.dev. We delete your data within 30 days of your email. The law can make us keep some data longer.

Your choices

You can refuse cookies and clear local storage in your browser's settings. The sheet works the same without them. If you clear local storage, you have to sign in again, and our script gives your browser a new ID on its next visit. To ask what data we hold about you, or to have us delete it, write to wayne@datacircle.dev.

Children

We don't offer the site to anyone under 13, and we don't knowingly collect their personal data. If you think we have, write to us and we delete it.

Other sites

The sheet links to each provider's pages. Their privacy policies cover what they collect.

Changes

If we change this policy, we post the new one here and update the date at the top.

Contact us

wayne@datacircle.dev

Best GTM APIs