Browser Extension Privacy Policy

How the free imisofts browser extensions handle your data.

Last Updated: October 22, 2026

1. Scope

This policy covers the free browser extensions that imisofts publishes in the Chrome Web Store. Our website is covered by our main Privacy Policy.

2. SPF, DKIM & DMARC Checker by imisofts

The extension looks up the public DNS records of a domain you enter (SPF, DKIM, DMARC, MX, BIMI and MTA-STS) and shows the results with suggested fixes. From version 1.1.0, its Propagation tab also checks whether a DNS record you name (A, CNAME, TXT, MX, NS or AAAA) has reached six public DNS providers. See the SPF, DKIM & DMARC Checker page for what it checks.

What it handles

  • The domain you enter. If you enter an email address, the extension keeps only the part after the @ on your device. The rest is discarded straight away and is never sent or stored.
  • DNS lookups for the email checks. To run a check, the extension sends DNS queries for that domain and related names (such as _dmarc.yourdomain.com, selector._domainkey.yourdomain.com and the names in your SPF record) over HTTPS to Google Public DNS. If Google Public DNS cannot answer, the same queries go to Cloudflare DNS. These services answer the queries under their own privacy policies.
  • DNS lookups for propagation checks. When you check a record on the Propagation tab, on the Keep checking page or in the New domain checklist, the extension sends a DNS query for that record name and type over HTTPS to six public DNS providers: Google Public DNS, Cloudflare DNS, AliDNS (Alibaba Cloud), DNS.SB, Control D and DNS4EU. To say where the domain's DNS is hosted, it also asks Google Public DNS for the domain's SOA and NS records. When a CNAME does not show up on a domain hosted at Cloudflare, it asks Google Public DNS for that name's A record, to tell whether Cloudflare's proxy is on. The expected value you type is compared on your device and is never sent. Keep checking repeats the query every 30 seconds while its tab is open, and stops by itself. These services answer the queries under their own privacy policies.
  • Saved on your device. The last five domains you checked on the Email records tab, the last five records you checked for propagation, the tab you used last, and the domain and records you paste into the New domain checklist are saved in the extension's local storage on your device, so you can use them again. They are never sent to us, and removing the extension deletes them.
  • Copy report. When you click Copy report, a text summary of the results is placed on your clipboard. Nothing is sent anywhere.

What it does not do

  • imisofts does not receive, collect, store, sell or share any data from the extension.
  • The extension has no analytics, no cookies, no accounts and no remotely hosted code.
  • The extension requests no browser permissions, so it cannot read the pages you visit or your browsing history.

Links to imisofts.com

The guide links and the "Get it set up by imisofts" button open pages on imisofts.com in a new tab, only when you click them. These links carry UTM tags that tell us a visit came from the extension. They do not identify you. Once you are on imisofts.com, our main Privacy Policy applies.

The Flush Google, Purge Cloudflare and whatsmydns.net links on the Propagation tab open those sites in a new tab, only when you click them. The whatsmydns.net link includes the record name and type you checked, and the expected value if it is a single word (never for TXT), so that site can run the same check under its own privacy policy.

3. Send to Webhook for n8n, Make & Zapier by imisofts

The extension sends the page you are viewing, or text you select on it, to a webhook URL that you add yourself, such as an n8n, Make, Zapier or Clay webhook, and shows that webhook's reply. See the Send to Webhook page for how it works.

What it handles

  • The webhooks you add. Each webhook's name, URL and optional secret header are saved in the extension's local storage on your device. They are never sent to us, and removing the extension deletes them.
  • The page you send. The extension reads the current page only when you click its toolbar icon, choose one of its right-click menu items or press its keyboard shortcut. Clicking the icon opens a small window that shows what will be sent, and nothing is sent until you click Send. It reads the page's address, title, description and social sharing tags, author and date tags, language, main heading, and any text you selected. If you right-clicked a link or an image, it also reads that link's address and text, or the image's address. If you turn on "Include the page text", it also reads the page's visible text, up to 20,000 characters. It never reads password boxes or boxes for passwords, one-time codes or card numbers, and it does not read what you typed into form fields unless you selected that text in a text box.
  • Where it goes. That data, with any note you type, is sent once, as JSON, to the webhook you chose and to no one else. The extension does not follow redirects, so it never sends the data to any address other than the one you saved. Webhooks on the internet must use HTTPS; plain HTTP is allowed only for local and private network addresses, such as a self-hosted n8n on your own computer. No cookies or referrer are sent. What happens to the data next is decided by you and the service behind your webhook, under that service's own privacy policy.
  • The webhook's reply. The reply is shown in the extension so you can see the result. It is not stored. For a send from the right-click menu or the keyboard shortcut, and for a send that failed after you closed the extension's window, a one-line result (for example "Sent to Research queue" or the reason it failed) is kept in the browser's memory, never on disk, so the extension can explain a failed send the next time you open it. It is deleted once it has been shown, and in any case when you close the browser.
  • Browser permissions. The extension can read a page only when you act on it (Chrome's activeTab permission). When you save a webhook, Chrome asks whether the extension may send data to that webhook's website, and only that website. When you delete a webhook, that permission is removed if no other webhook needs it.

What it does not do

  • imisofts does not receive, collect, store, sell or share any data from the extension. There is no imisofts server involved.
  • The extension has no analytics, no cookies, no accounts and no remotely hosted code.
  • It does not read pages in the background or read your browsing history, and it sends nothing unless you ask it to.

Links to imisofts.com

The "Get it built by imisofts" button and the other imisofts.com links open in a new tab, only when you click them. These links carry UTM tags that tell us a visit came from the extension. They do not identify you. Once you are on imisofts.com, our main Privacy Policy applies.

4. Chrome Web Store User Data Policy

The use of information received by imisofts browser extensions adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

5. Changes to This Policy

If an extension starts handling data in a different way, we will update this page before that version is released and change the date at the top.

6. Contact Us

Questions about this policy or our extensions: