Privacy
A small, first-party data footprint.
This portfolio records a small set of aggregate site metrics and keeps contact information limited to public professional channels.
- Aggregate metrics
- The site records total and daily visit counts.
- Limited storage
- Request metadata is not retained as readable identity data.
- Short retention
- Temporary deduplication and daily records expire automatically.
- First-party infrastructure
- Persistent counters are stored in the site's private Redis database.
What is measured
The site maintains a total visit count and a daily count. Repeated reloads from the same request context within a short window are consolidated to keep the numbers useful.
How request data is handled
Basic request metadata is used briefly on the server to prevent duplicate counts. Redis stores only opaque, short-lived keys and aggregate numbers; readable request values are not written to the database.
What is not collected
- Accounts, form submissions, or private profile data
- Advertising identifiers or session replay recordings
- Precise location, demographic inference, or behavioral scoring
- Cross-site browsing history
Availability
If the private counter storage is unavailable, the public counter shows an unavailable state instead of a generated placeholder value.
Contact data
The public contact page exposes only the brand email alias and GitHub profile. It does not publish a phone number, exact address, private mailbox, or original CV file.