1. Security model
GhostRate combines application controls with an Identity Firewall designed to prevent response attribution.
- Response payloads are encrypted with AES-256-GCM before insertion.
- Passwords are hashed with bcrypt and are never stored in plaintext.
- HTTPS protects browser and API traffic.
- Authentication endpoints are rate limited and administrative access supports two-factor authentication.
- State-changing operations enforce authorization in the service layer.
2. Identity Firewall
Invite tokens are stored in the ghost_tokens PostgreSQL schema and responses in ghost_responses. There are no cross-schema foreign keys. Tokens are consumed before a response is inserted, response records use a date rather than a timestamp, and fetch order is randomized.
3. Limitations
No online service can promise absolute security. Organizations must avoid questions that ask respondents to identify themselves and must limit access to sensitive results.
4. Reporting
Report suspected vulnerabilities privately to [email protected] with reproduction steps and impact. Do not access data that is not yours or disrupt the service while testing.