Privacy & preferences.

Optional visit counts

I use simple counts to understand which public pages get attention, where project inquiries begin, and whether the soundboard gives visitors a reason to return. You can turn these counts off here. Your browser’s Do Not Track or Global Privacy Control signal also turns them off.

The report contains daily totals and public page paths. It does not contain your name, email, account ID, browsing query strings, or a persistent visitor ID. Signed-in visits and private dashboard pages are excluded. Turning measurement off does not affect contacting me, reading stories, or using the soundboard.

To estimate soundboard returns, your browser remembers the date of a visit for up to 90 days of return detection. The site can then count a later-day return without sending a browser identifier. These are estimates; separate devices, cleared storage, concurrent tabs, and blocked requests affect them.

When measurement is enabled, a tab can remember its last public page for 30 minutes and include that path with a project inquiry. Daily cleanup removes measurement totals outside a rolling 90-day window and temporary measurement security records older than 48 hours.

When you contact me

The contact form sends the details you enter—your name, email, project note, and any budget or timing information—to my private inquiry inbox. I use them to respond, understand the work, and keep track of follow-ups. The form does not subscribe you to a newsletter.

Spam checks use temporary security counters and one-way keyed fingerprints to limit repeated requests. The application does not store a raw IP address with an inquiry. Inquiry records are kept separately from the 90-day visit report so I can manage our conversation and any resulting work. Please avoid including passwords or other sensitive account information.

What stays in your browser

Soundboard favorites, recent plays, volume, and keyboard preferences are saved in this browser. They are not synced to an account. Clearing site data removes these preferences.

Sign-in uses session cookies so protected pages can recognize an authenticated account. The owner’s writing editor also keeps local recovery copies to help recover unsaved work. These copies are specific to that browser and account; they are not a public post.

Services that operate the site

Vercel hosts the website. Supabase provides its database, sign-in, file storage, and server functions. Google handles authentication if you choose Google sign-in. Inquiry email alerts use Resend when enabled. These providers receive the information needed to deliver their services and may maintain their own operational and security logs, including network information.

Public stories, project pages, images, and sound files are available to visitors. Links to GitHub, project websites, and other external sites take you to services with their own privacy practices.