/ Appendix Last updated June 23, 2026

Is it safe?Security policy

How this site keeps your visit and your messages safe — and how to report a problem if you find one.

Security here isn't an afterthought — the same hardware-aware, production-minded approach I bring to industrial systems applies to this site. Here's how it's protected.

1. Can anyone read it on the way?

Every connection to bibinvr.tech is served over HTTPS with modern TLS. Traffic between your browser and the site is encrypted end to end, and plain-HTTP requests are upgraded automatically.

2. What is there to lose?

The site is static. There is no user database, no login, and no personal data sitting on a server waiting to be breached. The only information you can send is a contact message, and that goes straight to my inbox rather than into storage here.

3. How is the contact form kept honest?

The contact form is hardened against spam and automated abuse with layered checks:

4. What does it run on?

The site runs on Cloudflare's global network, which adds DDoS mitigation, a web application firewall, and edge caching in front of the content. Third-party code is loaded only from reputable, well-known sources.

5. Found a flaw?

If you discover a security issue — a vulnerability, an exposure, or anything that doesn't look right — I want to hear about it. Please email contact@bibinvr.tech with:

Please give me a reasonable window to fix things before disclosing publicly, and avoid accessing or altering data that isn't yours, degrading the service, or running automated scans that disrupt other visitors. Act in good faith and I'll do the same — I'll acknowledge your report and keep you posted on the fix.

6. Who do you tell?

For anything security-related, reach me at contact@bibinvr.tech. See also the Privacy Policy.

/ Appendix Last updated {{ updated }}

Is it
safe?Security policy

How this site keeps your visit and your messages safe — and how to report a problem if you find one.

Security here isn't an afterthought — the same hardware-aware, production-minded approach I bring to industrial systems applies to this site. Here's how it's protected.

1. Can anyone read it on the way?

Every connection to bibinvr.tech is served over HTTPS with modern TLS. Traffic between your browser and the site is encrypted end to end, and plain-HTTP requests are upgraded automatically.

2. What is there to lose?

The site is static. There is no user database, no login, and no personal data sitting on a server waiting to be breached. The only information you can send is a contact message, and that goes straight to my inbox rather than into storage here.

3. How is the contact form kept honest?

The contact form is hardened against spam and automated abuse with layered checks:

  • A hidden honeypot field that traps and silently drops bots
  • Strict validation of the name, a real email address, and message length
  • A limit on how many links a single message may contain
  • Client-side rate limiting to stop rapid repeat submissions
  • Server-side spam filtering from the form-delivery provider

4. What does it run on?

The site runs on Cloudflare's global network, which adds DDoS mitigation, a web application firewall, and edge caching in front of the content. Third-party code is loaded only from reputable, well-known sources.

5. Found a flaw?

If you discover a security issue — a vulnerability, an exposure, or anything that doesn't look right — I want to hear about it. Please email {{ profile.email }} with:

  • A clear description of the issue and where you found it
  • Steps to reproduce it, if you can
  • Any proof-of-concept details that help me confirm it

Please give me a reasonable window to fix things before disclosing publicly, and avoid accessing or altering data that isn't yours, degrading the service, or running automated scans that disrupt other visitors. Act in good faith and I'll do the same — I'll acknowledge your report and keep you posted on the fix.

6. Who do you tell?

For anything security-related, reach me at {{ profile.email }}. See also the Privacy Policy.