Privacy at BlockBriefe

Effective May 29, 2026

BlockBriefe publishes crypto and blockchain reporting. We believe our readers deserve to consume news without being profiled, tracked across the web, or auctioned to advertisers. This page describes exactly what happens when you visit blockbriefe.com — nothing more, nothing less.

What reaches our servers

Every HTTP request leaves standard traces in our Nginx access logs: the requesting IP, timestamp, user-agent string, and the URL path. These records exist for security incident response (rate limits, scraper detection, DDoS mitigation) and are rotated out of live storage after thirty days. They are never exported for marketing.

No accounts, no forms, no profiles

BlockBriefe does not expose reader accounts, newsletter sign-ups, comment threads, or submission forms. There is therefore no email address, name, or payment data that you could hand us even if you wanted to. The only direct channel to reach the editorial team is the public contact page, which routes plain email to the editor.

Analytics — privacy-first by design

We run a self-hosted instance of Umami, an open-source analytics platform that records aggregate visit counts and referrer origins. Umami does not set identifying cookies, does not track you across sessions, and does not collect data that would allow you to be reidentified. The instance is hosted on our own infrastructure; no third-party company receives your behavior.

Cookies we set

• A session cookie managed by PHP exists only while you are actively browsing and is destroyed on close. It carries no identifier tied to you.
• A Cloudflare edge cookie may be set for bot filtering and CDN consistency. Cloudflare's privacy terms govern that cookie.

We do not set advertising, remarketing, or cross-site tracking cookies, because BlockBriefe does not sell advertising inventory.

External embeds and outbound links

Some articles link to exchanges, whitepapers, block explorers, or regulator filings. When you click such a link, you leave our site and enter the destination's jurisdiction. Their privacy policy applies, not ours. We avoid inline embeds (YouTube, Twitter, Substack) that would load third-party scripts on our pages.

How we protect what little we store

The servers hosting blockbriefe.com run behind Cloudflare's proxy with strict TLS, HSTS, and a restrictive Content Security Policy. Database backups are encrypted at rest. Access to editorial tooling is limited to named staff with hardware-based two-factor authentication.

Minors

BlockBriefe writes about a domain regulated as high-risk in many jurisdictions. Readers under 18 should not use this site to make financial decisions, and we do not deliberately collect information from minors.

Your rights

If you are based in the European Economic Area, the United Kingdom, California, or any other jurisdiction with a comprehensive privacy framework, you retain the right to ask what we hold about you, request correction, or demand erasure. Because we do not maintain user accounts, in practice the answer for most readers will be "nothing beyond transient server logs" — but we will confirm that in writing if you ask.

Changes to this notice

Material changes to how BlockBriefe handles visitor data will be reflected on this page with a new effective date. Routine clarifications are made without notice.

Getting in touch

Questions, concerns, or DSAR requests should be sent via our contact form. We reply within five business days.