The terminal was still open. The command line blinked like it knew. I typed one last command in zsh and realized—too late—that GDPR is not just about servers in Berlin or encrypted S3 buckets. It’s about what happens every single time your shell spits data back at you.
GDPR in the shell is real. Engineers think of GDPR as something that lives in policies, in legal documents, in cloud regions. But CLI tools leak. Logs leak. Autocomplete caches leak. When you use zsh, with its history files, extended globbing, shell integrations, and plugins, you’re running a system that can quietly store personal data if you’re not paying attention.
Data retention is the heart of GDPR risk in zsh. Every history entry is a record. That record may contain IDs, API keys, usernames, emails, or even personal messages when you test endpoints or scripts. The law doesn’t care if the leakage happened inside a shell session or a SaaS dashboard. If personal data is stored without consent, you are exposed.
To make zsh GDPR-compliant, start here: