# Security

Last updated 10 November 2026

## How your data is protected

- **Keys are stored only as SHA-256 hashes.** A key is shown once, when it's created or rotated.
- **Narrow keys.** Publishable keys (`pk_live_…`) can only read. On Pro, any key can be limited to some bins and environments, and can expire.
- **Private bins stay hidden.** Without a valid key, a private bin answers `404`, the same as one that doesn't exist.
- **Encrypted in transit.** HTTPS everywhere, with HSTS.
- **A strict Content-Security-Policy** on the dashboard: scripts only from hotcfg's own origin.
- **Sessions you control.** See every signed-in device under **Account** and sign any of them out.
- **Rate limits** on sign-in, reads and writes, and on repeated bad credentials.
- **Audit log** on Pro: who created keys, changed roles, promoted or rolled back.
- **Backups.** The database is continuously replicated to encrypted object storage.
- **Deletion.** Deleted data is overwritten in the database straight away and gone from backups within 7 days.

## Reporting a vulnerability

Email [security@hotcfg.run](mailto:security@hotcfg.run) with the details and how to reproduce it. Please give us a reasonable time to fix it before you disclose it, and don't access other people's data or disrupt the Service while testing. We'll acknowledge your report and keep you updated until it's fixed.

Our contact details are also in [/.well-known/security.txt](https://hotcfg.run/.well-known/security.txt).
