Security & privacy at Jot
We record our customers’ users, so the defaults are conservative and every promise below is enforced by a named automated test that fails the build when broken. We do not hold SOC 2, ISO 27001 or HIPAA certifications, and we do not claim them.
What the widget never captures
- Passwords: masked regardless of configuration
- Every input is masked by default; opt-in, not opt-out
- .jot-block elements are not recorded at all
- Masking happens in the page, before bytes leave the browser
Where your data goes
- Shadow DOM on your page; no styles leak either way
- TLS to our API; Postgres for Jots and metadata
- Recordings in a private bucket, short-lived signed URLs
- Delete your org: everything purged, verified table by table
Promises with a test attached
Each of these is a named automated test in our suite, run against a real database. If one breaks, the build fails before the code ships.
How long we keep things
Recordings are the most sensitive thing we hold, so they expire first. Deletion is a pipeline, not a promise — these are the numbers it runs on.
- recordings
- 30 days by default, configurable per workspace
- deleted org
- 7-day grace period, then purge begins
- hard purge
- complete within 30 days of deletion
- backups
- point-in-time recovery snapshots are beyond use and purged within 35 days
Found something? Tell us first.
Email security@usejot.co and give us a reasonable window to fix it before publishing. We answer within two business days. We do not run a paid bounty programme yet — we are too small — but we credit reporters who want credit, and we do not pursue good-faith research. Machine-readable details live at /.well-known/security.txt.