Acceptable Use Policy
This is my personal website and security blog. It's a small, static site — no accounts, no logins, no comment forms, and nothing here collects data about you. This page says what the site is for, how to report a security issue, and the few things I ask people not to do. Plain language, on purpose.
What you're welcome to do
- Read anything here, as much as you like. No permission needed, no account required.
- Link to and share any page.
- Follow along via the RSS feed.
- Get in touch — questions, corrections, or just to compare notes: Contact@logansmith.us.
- Report a security issue with this site, as described below.
- Read the source — the whole site is public at github.com/Logans415/logansmith-us.
Reporting a security issue
Reports are genuinely welcome. The preferred route is a private security advisory on the repository, or email if you'd rather. The machine-readable version of this is at /.well-known/security.txt, and the full policy — scope, what to expect, response times — lives in SECURITY.md.
When you're looking, please stick to passive testing. Everything here is public and static, so reading the page source is genuinely enough to find real issues. Specifically, please don't:
- Run scans or tooling that generate meaningful load, and never stress or denial-of-service testing.
- Attempt to reach anything that isn't already publicly served — that includes the repository, DNS, and email infrastructure.
- Use social engineering against me or anyone else, or any kind of physical testing.
- Publish a finding before I've had a reasonable chance to respond.
Automated access, crawling, and AI
All of this is allowed. robots.txt permits every crawler, and there's an llms.txt specifically so AI agents can get an accurate picture of the site. If an assistant summarizes or cites something here, that's a good outcome.
What I ask in return is ordinary courtesy: use an honest user-agent, keep your request rate sane, and cache rather than re-fetching in a loop. Automated access stops being acceptable at the point where it degrades the site for anyone else.
What isn't acceptable
- Attempting to gain unauthorized access to the site, its repository, its DNS, or its email.
- Anything that degrades availability for others — denial-of-service, load testing, or aggressive scraping.
- Using my contact address for spam, bulk mail, unsolicited pitches, or phishing.
- Impersonating me, or implying I endorse a person, product, or organization when I haven't.
- Republishing my writing wholesale as though it were your own.
- Using anything from this site to build or distribute something harmful, or to target another person.
Content and reuse
The writing and images here are mine unless noted otherwise. Linking and short quotes with attribution are always fine — no need to ask. For republishing a whole post or reusing an image, please ask first; the answer is usually yes.
The source code is public so people can read it and learn from it. There's no license file on the repository at the moment, which means default copyright applies — so if you want to reuse a meaningful chunk of the code, just ask.
No warranty, and whose views these are
Everything here is provided as-is. The security and technical writing is general information, not professional advice for your specific environment — test things in your own context before relying on them.
The views on this site are my own. They do not represent any employer, past or present.
Changes
I may update this policy as the site changes; the date at the top reflects the most recent revision. If anything here is unclear, or you want to do something it doesn't obviously cover, just ask me — I'd rather have the conversation than have you guess.