Security

How this site stays safe, and what to do if you find a problem

I work on my own, so this page says plainly what I do, what I haven’t done yet, and how to reach me. Where something doesn’t exist yet, I say so instead of guessing.

Last reviewed 21 November 2026

At a glance

  • Very little to protect. This site is a set of fixed pages. It has no accounts, no sign-in, no forms, and no database, and I don’t set cookies.
  • Encrypted connection. Every page is sent over HTTPS, and plain http:// addresses redirect to it.
  • No formal security test yet. No outside penetration test has been done on this site.
  • Found a problem? Email me. I read every report.

How data is encrypted

While it travels (in transit)

  • Every page and file loads over HTTPS. If you type http://, you are sent to the https:// version automatically.
  • The connection supports TLS 1.3 and TLS 1.2, the current standards for encrypting web traffic. The security certificate comes from Google Trust Services and is managed and renewed by Cloudflare, which hosts the site.
  • Browser protections are switched on: other websites can’t show this site inside their own pages (this blocks a trick called clickjacking), browsers aren’t allowed to guess file types, and only limited information about where you came from is passed on when you click a link.

While it is stored (at rest)

The site itself holds no personal data, so there is nothing of yours to encrypt here. If you book a call or send an email, that information is kept by the services I use for those jobs, and each describes its own encryption and safeguards:

I rely on these providers for encryption of stored data. I don’t run any storage of my own for visitors.

Vulnerability scanning schedule

A vulnerability is a weakness someone could misuse. Because this site has no server code, accounts or database, there is little to scan. I check it by hand on this schedule. I have not set up an automated scanner.

After every change
Check that pages load, that the security protections above are still in place, and that no passwords or keys have been added to the site’s files.
Every month
Check the encryption setup and certificate expiry, the HTTPS redirect, the browser protections, and every link on the site.
Every three months
Review the outside services the site uses (Calendly, Loom, Cloudflare) and the one bundled code library, and update or remove anything out of date.

If a check finds a problem, I fix it and record what happened.

Penetration testing history

A penetration test is a planned attempt by a security professional to break into a system, to find weak points before real attackers do.

Outside penetration tests
None so far.
Why
The site has no login, forms, or stored visitor data, so a formal test would have very little to examine.
What changes this
If I add anything that handles visitor data, I will have it tested before it goes live and list the results here.

The tests described in my case studies are different. They check whether an automation works correctly on test data, and are not a security audit.

Incident response plan, in short

An incident is anything that threatens the safety of the site or of information I hold. If one happens, I follow these five steps.

  1. DetectI watch for alerts from my hosting, code and email accounts, and for reports sent to the address below. Anything suspicious is treated as an incident until I can show it isn’t.
  2. ContainI cut off access first: change affected passwords and keys, pause any automation involved, and roll the site back or take it offline if needed.
  3. NotifyI tell anyone affected promptly and plainly: what happened, what information was involved, what I’ve done, and what they should do. Where the law requires it, I also tell the regulator.
  4. RecoverI restore from a known-good copy (the site is rebuilt from its source code), replace every credential that may have been exposed, check that everything works, and keep watching for a repeat.
  5. ReviewSoon afterwards I write up what happened, why, what worked and what didn’t, and I fix the cause and update the plan.

The full plan contains checklists and private contact details, so I keep it private. Clients who want to see it are welcome to ask.

Where data is stored

This website’s pages
Cloudflare’s worldwide network of data centers, which serves each visitor from a location near them. Run by Cloudflare.
Visit counts
Cloudflare’s privacy-focused analytics, which counts visits without using cookies. Run by Cloudflare.
Booking details
If you book a call, your name, email, and answers to the booking questions are held by Calendly. Run by Calendly.
Emails to hello@
Cloudflare forwards them to my Google (Gmail) inbox. Run by Cloudflare and Google.
Website source code
A public repository on GitHub. It contains no visitor data, passwords, or keys. Run by GitHub.
Light or dark mode choice
Saved only in your own browser. It is never sent to me.
Client project data
Kept in the client’s own accounts and tools wherever possible. I don’t keep copies unless we agree it in writing.

Calendly and Google store data in the regions described in their own policies. I don’t control that choice.

Report a vulnerability

Email me with the subject line “Security report”:

hello@marloiemenchavez.com

I’ll reply within three working days, keep you updated, and fix confirmed problems as quickly as I can. If you’d like credit, I’ll thank you by name once it’s fixed.

What to include

  • What you found and the page or address where you found it.
  • The steps to repeat it, and what you think someone could do with it.

Please

  • Act in good faith and don’t view, change, or delete anyone else’s data.
  • Don’t overload the site, and don’t try to trick me or anyone else into giving up access.
  • Don’t test the services this site relies on (Cloudflare, Calendly, Loom, GitHub, Google). Report problems in them to those companies.
  • Give me reasonable time to fix the problem before sharing details publicly.

I can’t offer payment for reports. If you follow these rules, I’ll treat your report as a favor, not a threat.

A machine-readable version of this contact is at /.well-known/security.txt.