Bracket is designed from the ground up so that no one — including us — can trace a submission back to the person who made it.
When you submit compensation data, your user identity is encrypted using AES-256-GCM before being stored. The encrypted value is kept in a separate column with no direct foreign key linking submissions to user accounts. The decryption key is stored exclusively in a server-side environment variable and is never exposed to the client or included in database exports.
Individual submission records are only visible to users when at least 3 submissions exist for the same combination of industry, function, and geography. This prevents anyone from deducing who submitted a particular data point based on filtering. Aggregated statistics (medians, percentiles, ranges) are always available regardless of count.
Passwords are hashed using bcrypt before storage. We never store plaintext passwords and have no ability to retrieve them.
All data is transmitted over HTTPS/TLS. Our database is hosted on Neon (PostgreSQL) with encryption at rest. The application is deployed on Vercel with automatic SSL certificates and edge-level security.
Last updated: April 2026