FlickHub is a client-side only application with no backend server. All functionality runs entirely in the browser, significantly reducing the attack surface.
- β No server-side data storage
- β No user authentication or accounts
- β No database or backend services
- β All data stored locally in browser (localStorage)
- β No cookies, trackers, or fingerprinting
- β No third-party analytics or telemetry
- β No user data is collected, stored, or transmitted
- β Favorites stored only in your browser's localStorage
- β HTTPS only communication with TMDB API
- β API keys stored in environment variables (not exposed in client)
- β No sensitive data transmitted
| Version | Supported |
|---|---|
| 2.x.x | β Currently supported |
| 1.x.x | β No longer supported |
We take security seriously. If you discover a security vulnerability, please follow these steps:
- Do NOT create a public GitHub issue for security vulnerabilities
- Send an email to darkdeveloperassistant@gmail.com with:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Any suggested fixes (optional)
| Timeframe | Action |
|---|---|
| 24-48 hours | Initial acknowledgment of your report |
| 7 days | Assessment and initial response |
| 30 days | Resolution timeline provided |
- You will be credited in the changelog (if desired)
- Security advisory will be published if applicable
# Never commit your .env file
# Use .env.example as a template
VITE_TMDB_API_KEY=your_api_key_here- Keep dependencies updated:
npm update - Review dependency vulnerabilities:
npm audit - Use HTTPS in production
We use the following tools to maintain security:
- Dependabot - Automated dependency updates
- npm audit - Vulnerability scanning
- CodeQL - Static code analysis
# Check for vulnerabilities
npm audit
# Fix vulnerabilities automatically
npm audit fix
# Update all dependencies
npm updateSince FlickHub is client-side only:
-
API Key Exposure: The TMDB API key may be visible in browser developer tools. This is acceptable for public APIs with rate limiting.
-
localStorage Security: Data in localStorage is not encrypted. Do not store sensitive information.
-
Third-party Embeds: Video player embeds from third-party sources are beyond our control.
For security concerns:
Thank you for helping keep FlickHub secure!