Accounts and sessions
- Short-lived access tokens (15 minutes) and refresh tokens (7 days), stored in HTTP-only cookies
- Email one-time codes to confirm sign-up, password resets and password changes
- Sign out one device or all devices from your active sessions
- CSRF tokens on every request that changes data
- Rate limits on sign-in and other sensitive endpoints
Data protection
- All traffic encrypted in transit with TLS
- Passwords stored only as salted bcrypt hashes, never in a readable form
- Access to the database is limited to the application
- Secrets are kept in environment configuration, never in source code
Operations
- Dependencies reviewed and updated on a rolling basis
- Sensitive admin actions are recorded in an audit log
- New listings and edits are reviewed before they go live
Responsible disclosure
Found a vulnerability? Tell us privately first, and we'll work with you on a fix.
We commit to
- Acknowledge your report within 48 hours
- Keep you updated while we investigate
- Fix confirmed issues within a reasonable time
- Credit you, if you'd like
- Not take legal action against good-faith research
In scope
- Authentication bypass or session hijacking
- SQL injection or data exfiltration
- CSRF on protected endpoints
- Privilege escalation (reaching another user's data)
- Cross-site scripting on Ploba pages
- Sensitive data exposed in API responses
Out of scope
- Denial-of-service attacks
- Social engineering of Ploba staff
- Vulnerabilities in third-party tools listed on Ploba
- Issues already reported or being fixed
Report a vulnerability
Email [email protected] with steps to reproduce, the affected URL or endpoint, and the impact you observed.