Collin Craig
Back to Writing

· Flight Day

Privacy first, even after deletion

The rule. Before Flight Day's website went public, I set one rule above the others: privacy first. The site shows the app running in my own home, so any screenshot can give something away. A wallpaper credit, the local weather or a "visible from home" label is harmless on its own. Together, they can show where the home is.

The decisions. The agents checked the screenshots against that rule and masked five. The wallpaper credit came off, along with the weather and sky details that pointed to the home's location.

What broke. Replacing the files wasn't the end of it. After the next release, 40 old files (pictures, clips, stylesheets and scripts) still loaded on flightday.app, even though the site itself answered "not found". Two full purges of Cloudflare's cache didn't help: a cache layer in front of the site put them back within seconds.

The fix, release by release.

  • A temporary rule made the site's files bypass Cloudflare's cache. A second setting made Cloudflare's copies expire within five minutes.
  • The cache rule didn't reach the layer that served the old files, so the site itself now answers "not found" for each retired file, before any cache can.
  • Later, one old stylesheet came back from Cloudflare's copy, so the agents put the same rule back for the retired files.
  • New names: a picture changed for privacy gets a new name, and the site won't publish the old one again.

My part. I didn't write that code; AI agents did, and I directed them. My calls were the rule itself, accepting a slower cache so that deleted files really disappear, and not calling the fix done until the old files were gone from the live site.

What I'd keep. Privacy is about what the site still serves, not what's in the repository.

The details are in Flight Day's release notes.