Legal•March 5, 2026
Privacy Policy
We respect your privacy. Here's exactly what we collect, why, and how — in plain language.
Overview
This Privacy Policy explains how we collect and use information when you visit this blog. We are committed to being transparent: we collect as little data as possible, and none of it can personally identify you.
What We Collect
When you visit a post, we record an anonymous view event. Each event stores only the following fields:
| Field | Type | Description |
|---|---|---|
| id | varchar(36) | A random unique ID for the view event |
| created_at | datetime | Timestamp of the visit |
| updated_at | datetime | Last update timestamp |
| post_id | varchar(36) | Which post was viewed |
| ip_hash | varchar(191) | A one-way hash of your IP — the original IP is never stored |
| user_agent | text | Your browser and OS identifier (e.g. "Chrome on Windows") |
| fingerprint | text | An anonymous fingerprint derived from non-personal browser signals |
How the Fingerprint Works
To count unique visitors without using cookies or accounts, we generate an anonymous fingerprint in your browser from the following signals:
- Browser User-Agent string
- Browser language setting
- Screen resolution (e.g. 1920×1080)
- Timezone (e.g. Europe/Budapest)
- Platform (e.g. Win32, MacIntel)
These signals are combined and hashed into a single anonymous string. This process happens locally in your browser. We never see the raw values — only the resulting hash. The fingerprint cannot be reversed to identify you.
What We Do NOT Collect
- Your name or email address
- Any account or login information
- Cookies or persistent tracking identifiers
- Your precise or approximate location
- Any form of payment information
- Any data from third-party advertisers
How We Use This Data
The analytics data described above is used solely by the blog owner to understand how many people are reading each post and which content is most popular. This is purely operational — no data is sold, shared with third parties, or used for advertising.
Data Retention
Analytics records are kept for as long as the blog is operational. Because no personally identifiable information is stored, there is nothing to delete on a per-user basis. If you have concerns, you can contact us using the details below.
Third Parties
We do not use Google Analytics, Facebook Pixel, or any other third-party analytics or advertising services. All analytics are self-hosted and remain under the blog owner's sole control.
Your Rights
Because we do not store any information that can be linked back to you as an individual, we are unable to provide, correct, or delete records about a specific person — there simply are none. If you have questions or concerns about this policy, feel free to reach out.
Last updated: March 5, 2026