Skip to content
Chorafios.com
← chorafios.com

Privacy

Last updated: 6 April 2026

Summary

This site sets no cookies, runs no analytics, and doesn't track you. The data controller is Savvas Chorafios ([email protected]).

Some sections of the site cause your browser to contact third-party servers — this is described below. The Visitor Intel fingerprinting demo only runs after you explicitly click "Reveal my profile".

Hosting & server logs

The site is hosted on Netlify. Netlify may record your IP address, user agent, and request metadata in standard access logs for delivery and abuse prevention. We don't receive or keep copies of those logs. Retention and security are governed by Netlify's privacy policy.

Third-party services your browser contacts automatically

When you visit certain sections of the site, your browser makes direct requests to the following third-party APIs. Each request reveals your IP address and HTTP headers to that service — no additional data is sent by us.

Security feeds

CISA (cisa.gov)— Known Exploited Vulnerabilities catalogue
SANS ISC (isc.sans.edu)— Global threat level (Infocon)
NIST NVD (services.nvd.nist.gov)— Recent CVE feed

Service status board

Cloudflare, Fastly, Akamai— CDN & edge status
GitHub, GitLab, Vercel, Netlify, npm— Dev platform status
DigitalOcean, Fly.io, Render— Cloud hosting status
Datadog, Sentry, New Relic, CircleCI— Observability & CI status
OpenAI, Supabase, Notion— SaaS product status
Auth0, Okta, Stripe, Twilio, SendGrid, Mailgun, Algolia, Mux— Platform & API status
These requests are made from your browser, not our server. We don't log, intercept, or store any of the responses. Each third party's own privacy policy governs how they handle your IP.

Visitor Intel — browser fingerprinting demo

The Visitor Intel panel is an educational demo that shows what a website can learn about your browser without setting cookies. It only activates when you click Reveal my profile.

What runs locally, in your browser only

  • Device type, OS, browser, screen & viewport size
  • GPU vendor & renderer (via WebGL)
  • Canvas fingerprint — a hash derived from how your GPU renders text
  • WebRTC LAN IP detection — local network IPs only, no STUN servers contacted
  • Network quality — effective type, estimated downlink & RTT
  • Browser permission states — notifications, geolocation, camera, microphone
  • Ad-blocker presence detection
  • Speech synthesis voice count
  • Battery level & charging state (where available)
None of this data is transmitted to any server. It is computed in your browser, displayed back to you, and discarded when you leave or refresh.

Optional IP lookup (ipapi.co)

After revealing your profile, a second button — Enable IP Profile — appears (hidden if Do-Not-Track is enabled). Clicking it makes a one-time request from your browser to ipapi.co to return approximate geo/network metadata for your current IP. We send no additional identifiers, store no response, and it disappears on refresh.

ipapi.co may process your IP outside your country. See their privacy notice for details.

Legal bases (GDPR Art. 6)

Site delivery & Netlify access logs

Legitimate interests Art. 6(1)(f)

Automatic third-party API fetches (status board, security feeds)

Legitimate interests Art. 6(1)(f)

Browser fingerprinting demo (Visitor Intel)

Consent Art. 6(1)(a) — via 'Reveal my profile' click

Optional IP lookup (ipapi.co)

Consent Art. 6(1)(a) — via 'Enable IP Profile' click

Your rights (GDPR)

Under GDPR you have the right to access, correct, erase, restrict, or port personal data we hold about you, and to object to processing based on legitimate interests.

Because we store no personal data ourselves (server logs are held by Netlify, not us), most of these rights are best exercised directly with Netlify. For anything else, contact us and we'll help.

Your choices

  • Don't click Reveal my profile to skip all browser fingerprinting.
  • Don't click Enable IP Profile to avoid the ipapi.co request.
  • Enable Do-Not-Track in your browser to hide the IP Profile button by default.
  • Use a content blocker to restrict the automatic third-party API fetches.

Contact

Questions or requests: [email protected]