How accounts are protected

What stands between your connected accounts and anyone else.

Tokens are encrypted
Network tokens are sealed with AES-256-GCM under a key held outside the database. A database dump alone cannot post as you.
Few passwords to lose
Most people sign in with Google, LinkedIn or X, so we hold no credential. Where there is a password it is hashed with bcrypt.
Short sessions
Access lasts fifteen minutes and a refresh thirty days. Signing out ends both.
One workspace per row
Every record is keyed to a workspace and every query is scoped to it on the server.
Roles on the server
Owner, admin, editor and viewer. A viewer cannot publish by finding the right URL.
Approval first
A new workspace holds every draft and first email for a person to read. Turning that off is a choice.
An audit trail
Who connected an account, approved a post or changed a schedule, recorded as it happens.
Permissions checked
Publishing is refused unless the stored token carries the permission the network needs.