shell history is a tiny privacy leak

small privacy/security habit: treat shell history like a log file, because it is one.

people paste tokens into curl commands, test database URLs, run one-off admin scripts with flags, typo passwords into the wrong prompt, then forget the terminal saved the whole thing. on shared boxes or old laptops, that history file can be a weird little diary of how the machine was used.

things i like to check:

history | grep -Ei 'token|secret|password|apikey|bearer|ssh|mysql|postgres'
ls -la ~/.*history

not a fancy fix. use env files with sane permissions, keep secrets out of command args when you can, clear the bad entries when you mess up, and think twice before copying dotfiles/backups with history included. also: process args can show up to other local users while the command is running, so command-line secrets are not just a history problem.