This document outlines security practices for the Acadira AI project.
Never commit real API keys or credentials to version control.
All sensitive configuration is stored in .env files which are:
- Listed in
.gitignore - Not tracked by git
- Required to be created from templates (
.env.example)
If you believe any credentials have been exposed:
-
Google Gemini API Key
- Go to: https://aistudio.google.com/app/apikey
- Delete the exposed key
- Generate a new one
-
Firebase Credentials
- Go to: https://console.firebase.google.com/
- Project Settings > Service Accounts
- Regenerate private key if needed
-
xAI (Grok) API Key
- Go to: https://console.x.ai/
- Regenerate your API key
-
Groq API Key
- Go to: https://console.groq.com/
- Regenerate your API key
-
Anthropic API Key
- Go to: https://console.anthropic.com/
- Regenerate your API key
If API keys were accidentally committed:
# Install git-filter-repo
pip install git-filter-repo
# Remove specific file from history
git filter-repo --path-glob '*.env' --invert-paths --force
# Force push to update remote
git push --force origin main- Use
.env.localfor local development - Never commit
.envfiles - Rotate API keys periodically
- Use minimal required permissions for API keys
- Monitor API key usage for anomalies
- Use .gitignore for all credential files