Privacy
This page describes how mureo.io — the website you are reading — handles visitor data today. It is not a perpetual promise. If our practices change, this page is updated with a new "Last updated" date. For the data posture of the mureo OSS framework (separate product, runs on your machine), see /security/.
What this site collects today
We use Cloudflare Web Analytics in its cookieless mode. For each page view, it records:
- The URL visited
- The HTTP
Refererheader (if your browser sends one) - Screen and viewport dimensions
- A coarse geography derived from IP; the IP itself is not stored
- A browser / OS user-agent category
Data is aggregated at the edge and retained by Cloudflare for up to 6 months. We do not export it, join it with other sources, or attempt to de-anonymize it.
What this site does not do today
- Set any cookies (no session, no tracking, no preferences)
- Fingerprint your device across sites
- Collect personally identifiable information (name, email, phone, etc.)
- Run a marketing tracking pixel (no Meta Pixel, no Google tag, no LinkedIn Insight Tag today)
- Sell or share data with third parties
Third-party resources loaded by the page
The page loads a small number of externally-hosted resources. Each has its own privacy policy:
- Cloudflare — serves the entire site and provides the cookieless analytics beacon. See Cloudflare's privacy policy.
- Google Fonts — serves the Inter typeface from
fonts.googleapis.comandfonts.gstatic.com. See Google's privacy policy. - Outbound links — links to
github.com,pypi.org, or other services send you to those destinations. Each has its own privacy policy; we do not receive data from those clicks.
Future changes
We may add additional analytics, conversion tracking, or advertising tools in the future. If we do:
- This page will be updated with a new "Last updated" date
- Where required, a cookie-consent banner will be added before any non-cookieless tool loads
- Material changes will be noted in the blog so returning visitors have a chance to notice
Related: the mureo OSS framework
The mureo framework is a separate product. It runs
on the operator's machine, loads credentials from local disk,
and makes API calls directly to the platforms the operator has
authenticated — with no routing through any infrastructure we
operate. Its data posture, including the threat model and the
commitments it makes, is documented at
/security/ (mirrored from
logly/mureo/SECURITY.md).
Contact
Security reports (for the framework or this site): GitHub private vulnerability reporting .
Other privacy questions: open an issue at github.com/logly/mureo.