I'm Scott Hoaglund. This policy explains privacy on scotthoaglund.com, my professional portfolio and blog. It applies to visitors throughout the United States.
What the site collects
You can read the site without creating an account. The public pages don't use advertising trackers, social-media embeds, or visitor analytics scripts. I don't sell personal information or use it for targeted advertising.
Vercel hosts the site. Delivering and protecting it involves processing technical information, such as your IP address, browser information, requested pages, and request times. Vercel may retain technical logs under its service settings and policies. Its privacy notice explains its own practices. Hosting infrastructure may process information outside your state or country.
Cookies and tracking
The public reading pages don't set application cookies. The private owner editor uses necessary cookies to complete sign-in and keep the owner signed in; readers don't need them. The sign-in check cookie lasts up to ten minutes, and the production editor session lasts up to eight hours or until sign-out.
Owner sign-in
The production editor uses Google sign-in, only for the authorized site owner. Google provides an account identifier, email address, and email-verification status so the site can verify access. This sign-in does not request access to Gmail messages or other Google files. Google processes sign-in activity under its privacy policy. Local development uses browser pairing instead of Google sign-in.
Unpublished content, revision history, and publication records are stored in Neon, and private uploaded images are stored in Vercel Blob. They require owner authorization; publishing makes selected content and referenced images public. These services may retain backups and technical logs separately.
The site doesn't track your activity across websites. It doesn't change its behavior in response to browser Do Not Track signals because that tracking isn't implemented.
Other websites and messages
The contact form sends the message you enter, including any contact details you choose to share, through Google's Gmail service to my email inbox. I use it to respond and manage our conversation, not for marketing. Please don't send sensitive personal information. Messages aren't stored in the site's database, but Gmail retains email copies under its settings and policies. See Google's privacy policy.
To reduce spam, the form uses a hidden spam-check field and temporary request counters. The database stores a keyed hash of your IP address, not the address itself, and an overall counter. Counters expire within a day and are removed on subsequent requests. These protections don't use visitor cookies.
I keep correspondence while needed for our conversation and reasonable follow-up, then delete it when no longer needed, subject to legal obligations. Provider logs and backups may have separate retention schedules.
Links to LinkedIn and other websites take you to services with their own privacy practices. This policy doesn't cover those services.
If you message me through LinkedIn, I use the information you share to respond and manage our conversation. LinkedIn stores messages under its own policies. Please don't send sensitive personal information.
Your choices
For privacy questions, or to request access, correction, or deletion of information you've shared with me, use the contact form or contact Scott on LinkedIn. These requests are welcome regardless of your state. I'll respond as required by applicable law; identity verification and legal retention requirements may affect what I can provide or delete. LinkedIn handles requests about its own records separately.
Changes
I'll update this page and its date when these practices change. If a change materially affects information you've already provided, I'll give additional notice where required.