How this website handles your information
This site sets no cookies and runs no analytics or advertising scripts. The contact form sends us the information you enter so we can reply.
Privacy at a glance
The short version
- Just browsing? We collect nothing about you. No cookies, no analytics, no trackers.
- Sent us a message? We keep your name, email, organization, and what you wrote — so we can reply.
- Patient data? It never reaches us. MessageFoundry runs on your servers, and the data stays there.
- Want your message deleted? Ask us, and we'll delete it.
This site sets no cookies and runs no analytics
The pages use HTML, CSS, and a small script for the mobile menu. The site has no tracking scripts.
To be specific, this site has no cookies, no analytics or tracking pixels, no advertising or social media scripts, no fonts or files pulled from someone else's server, and no accounts to create.
GitHub Pages serves the site. GitHub handles those requests under its own privacy statement. We don't run our own server logs, and we don't receive visitor reports from GitHub.
Email us, and we keep what you send
The contact form is the exception. When you fill it in, you send us your name, your email address, your organization if you add one, and your question.
The form posts to Web3Forms, a third-party form service, which emails your message to us. Web3Forms handles it under its own privacy policy.
We keep that email. It sits in our mailbox so we can answer you and so we have a record of the conversation. We use it only to reply to you and to follow up on what you asked. We don't sell it, rent it, or hand it to advertisers, and we won't add you to a mailing list you didn't ask for.
Please don't send patient data through the form. It travels through a third-party service and ordinary email, so keep it to general questions. If you need to discuss something sensitive, say so and we'll arrange a secure channel.
Patient data stays with the organization running MessageFoundry
MessageFoundry is software you install and run yourself. When your organization deploys it, messages move between your systems, on your servers, inside your network.
None of it reaches us. MessageFoundry, LLC does not receive, store, process, or have access to any protected health information (PHI) handled by an installation of MessageFoundry. There is no cloud service in the middle, and nothing phones home.
That means the organization that installs and operates MessageFoundry is responsible for the data flowing through it — including any duties it has under HIPAA or the privacy laws that apply where it works. Our job is to give you software that supports a compliant deployment; it can't make you compliant on its own. The security page explains the controls we build in.
Questions, or want us to delete your message?
Write to us through the contact form and ask. We'll delete the email you sent and confirm that it's gone. You can also ask what we hold about you, and we'll tell you.
If this policy changes
We'll update this page and change the date below. If we ever change something that matters — what we collect, or who handles it — we'll say so here rather than quietly editing the text.
Last updated 10 September 2026. MessageFoundry, LLC.