This project uses sensitive API keys and credentials that must be protected.

• Purpose: Text summarization, AI analytics, voice note processing
• Used in: main.py, ai_analytics.py, summarize_openai.py
• Environment Variable: OPENAI_API_KEY

• Purpose: Speech-to-Text, Firestore database, Cloud Storage
• Used in: transcribe.py, firestore_store.py, gcloud_auth.py
• Files: gcloud-key.json, environment variables

1. Environment Variables: All sensitive keys are stored in .env file
2. Git Ignore: .env and gcloud-key.json are excluded from version control
3. Template File: .env.template provides setup instructions without exposing keys
4. Documentation: This file documents security practices

1. Visit OpenAI API Keys Dashboard
2. Create a new API key
3. Update your .env file with the new key
4. Delete the old key from OpenAI dashboard

1. Visit Google Cloud Console
2. Go to IAM & Admin > Service Accounts
3. Create new key for existing service account
4. Replace gcloud-key.json with new file
5. Delete old key from console

For production environments:

• Use environment variables instead of .env files
• Use secret management services (AWS Secrets Manager, Azure Key Vault, etc.)
• Enable API key restrictions and rate limiting
• Monitor API usage for unusual activity

• .env file is not committed to git
• gcloud-key.json is not committed to git
• All API keys are valid and working
• Team members have their own API keys (don't share)
• API keys have appropriate permissions only

1. Immediately rotate all exposed keys
2. Check API usage logs for unauthorized activity
3. Update all deployment environments
4. Review git history to ensure keys weren't committed