Privacy Policy
Effective 5 October 2026. This describes what this website actually does today — not a template. If we change it, we change this page and move the date.
Who we are
Mindpod Technologies, 8735 Dunwoody Place #5088, Atlanta, GA 30350, United States. Questions or requests: Info@mindpodtech.com.
The short version
- Two optional services can run, and only after you press “Accept”: business-visitor identification (Instantly / RB2B) and the Meta Pixel. Declining or ignoring the banner means neither script loads. If this browser cannot store the choice, nothing loads until you press Accept, and the next visit asks again.
- Instantly / RB2B sets
_reb2bloadedand_reb2bsessionID. The Meta Pixel sets_fbp. Details and how to change your choice are in sections 6 and 7. - Apart from those services, this site sets no cookies of its own. Your consent choice
is kept in your browser’s local storage (key
mp-visitor-consent), which is not a cookie and is never sent to us. - We collect an email address only if you hand us one.
- We do not sell, rent, or trade personal information. We never have.
What we collect, and why
1. Newsletter signup — The Mindpod Spot
If you subscribe, we collect the email address you enter and, if you provide it, your name. It is sent to our email provider and used to send you the newsletter. Nothing else. Every issue carries an unsubscribe link, and it works immediately.
2. The chat assistant on this site
If you use the chat widget, the message you type is sent to our hosting provider’s AI service to generate a reply. We do not store your conversation and we do not use it to train any model. Please don’t paste passwords, account numbers, health information, or anything confidential into it — it is a website assistant, not a secure channel.
3. The M365 Pulse Check request form
If you request a Pulse Check, we collect the name, work email, company, role,
seat-count range and reason you enter, plus any message you add.
Each request is sent as one email to info@mindpodtech.com through our
transactional email provider (Resend), with your work email as the reply address so we
can answer you. We use it only to reply about the Pulse Check. It does not add you to a
mailing list, and we do not keep a separate database of requests.
4. Abuse prevention
Our signup, chat and request-form endpoints briefly hold your IP address in memory to enforce rate limits, so the forms can’t be flooded. It is not written to a database, not linked to your identity, and disappears when the process recycles. Our host also keeps standard server logs.
5. Fonts
Pages load typefaces from Google Fonts. That request necessarily reveals your IP address to Google. We are working toward self-hosting these files to remove that hop.
6. Visitor identification — consent required
We use a third-party service (Instantly, which is powered by
RB2B) that attempts to identify business visitors to this
site — potentially including a name, employer, job title, LinkedIn profile,
and work email — from your network address and browsing signals. Loading it also
hands your IP address, the pages you view on this site, and your user agent to
r2.leadsy.ai, an Amazon CloudFront distribution that serves the second-stage
script, and api.instantly.ai. We use what it returns only to understand which
businesses are interested in our services. We do not use it to build profiles of private
individuals, and we do not sell what it returns.
It is off by default. The script is not in our pages. A small
first-party file (/consent.js) shows a banner and injects the vendor script
only after you press “Accept”. If you decline, close the page, ignore
the banner, or block browser storage, the script is never fetched and no request is made to
any of the hosts above.
Cookies it sets, once you accept:
| Cookie | Set by | What it does |
|---|---|---|
_reb2bloaded | RB2B script | Flags that the tracking script has already loaded in this browser, so it is not initialised twice. |
_reb2bsessionID | RB2B script | Identifies your current browsing session so page views on this site can be grouped into one visit. |
Both are first-party cookies written in your browser by the vendor’s script. RB2B documents them in its own cookie and consent guidance. This page and the 404 page never load the visitor-identification service. The 404 page does not load the consent gate, so it never loads the Meta Pixel either.
No location-based restriction. RB2B states that it identifies visitors in the United States only. We do not detect or filter by country: the same consent banner is shown to every visitor, wherever you are, and nothing loads until you accept. We make no claim here about compliance with any particular privacy law — this section describes only what the site does.
To change your choice or opt out:
Your choice is stored per browser. Use the buttons below to set it.
Turning it off stops any further loading of either script on this browser. It does not by itself delete cookies already set — clear cookies for this site to remove them, and any standard tracker-blocking extension also prevents the scripts from loading. To have details a service already returned about you suppressed or deleted, email Info@mindpodtech.com and we will action it.
7. Meta Pixel — consent required
After you press “Accept”, the same first-party file loads the
Meta Pixel (Meta Platforms) from connect.facebook.net.
It sends Meta a page view for the page you are on, including the page address, your
IP address, and your browser’s user agent. We use that to measure visits to this
marketing site. The script is not in the page markup, and there is no fallback image
for browsers with JavaScript disabled, because that request would fire with no choice
recorded.
If you submit the M365 Pulse Check request form and our server confirms the request was sent, the pixel records one Lead event. The only detail we attach is the content name “M365 Pulse Check”. The page does not send your name, email address, company, role, seat count, or message to Meta. The Lead request is still a pixel request, so Meta receives the page address, your IP address, and your user agent with it, the same as a page view. A validation error, a refused request, a server error, or a network failure does not record the event.
Cookie it sets, once you accept: _fbp, written by
Meta’s script so it can recognise this browser on a later visit. If you arrived
from a Meta ad, Meta may also set _fbc from the click id in the address.
This page can load the pixel after you accept. The 404 page never does.
Who processes data on our behalf
| Provider | What it handles |
|---|---|
| Microsoft Azure | Website hosting, server logs, and the AI service behind the chat assistant |
| Mailchimp (Intuit) | Newsletter list and delivery |
| Resend | Delivery of the Pulse Check request email to our inbox (see section 3) |
| Cloudflare | DNS, and the redirect from the bare domain to www |
| Font delivery only | |
| Instantly / RB2B | Business-visitor identification — only after you consent (see section 6) |
| Meta Platforms | Advertising measurement (Meta Pixel) — only after you consent (see section 7) |
Each holds data under its own terms. We share personal information with no one else, except where the law requires it.
How long we keep things
Newsletter subscriptions are kept until you unsubscribe or ask us to delete them. Pulse Check requests are kept in our inbox as ordinary email; ask us and we will delete them. Rate-limit data lives for minutes to a day. Server logs follow our host’s retention. Chat messages are not retained by us at all.
Your rights
Wherever you live, you can ask us to show you what we hold, correct it, or delete it. Email Info@mindpodtech.com and we will respond within 30 days. You do not need to explain why, and we will not treat you differently for asking.
If you are in the EU/UK or California, you may also have rights to restrict or object to processing, to data portability, and to complain to your data protection authority. We do not sell personal information as those laws define it.
Children
This site is for business audiences and is not directed at children under 13. We do not knowingly collect their information.
Changes
If we add anything that collects more than what is described above, this page changes first, with a new effective date at the top.