A personal email and full name were found inside a committed .env file in this repository.
🚨 Why this is a problem
.env files must never be committed to GitHub.
Personal data (name + email) inside configuration files violates GDPR data minimisation requirements.
Even if used as “test data,” it can still expose the individual to:
phishing
malware
unwanted contact
scraping
It also poses a risk to the organisation if the inbox becomes a target.
✔️ Recommended actions
Remove the .env file from the repository history.
Replace it with a safe .env.example containing placeholders.
Add .env to .gitignore.
If needed for internal workflow, distribute real .env files privately (Discord, encrypted channel).
Avoid personal data in any test or config file going forward.
🔍 Notes
This issue does not imply wrongdoing from the dev.
It is a routine GDPR and security compliance check.
Please confirm once the file is cleaned or replaced.
A personal email and full name were found inside a committed .env file in this repository.
🚨 Why this is a problem
.env files must never be committed to GitHub.
Personal data (name + email) inside configuration files violates GDPR data minimisation requirements.
Even if used as “test data,” it can still expose the individual to:
phishing
malware
unwanted contact
scraping
It also poses a risk to the organisation if the inbox becomes a target.
✔️ Recommended actions
Remove the .env file from the repository history.
Replace it with a safe .env.example containing placeholders.
Add .env to .gitignore.
If needed for internal workflow, distribute real .env files privately (Discord, encrypted channel).
Avoid personal data in any test or config file going forward.
🔍 Notes
This issue does not imply wrongdoing from the dev.
It is a routine GDPR and security compliance check.
Please confirm once the file is cleaned or replaced.