Security
Built to be trusted with your name
Cadence holds an access token for your LinkedIn profile and a key for your AI provider. Here is how both are handled.
Controls in place today
Encrypted credentials
LinkedIn tokens and your AI provider key are encrypted before they are written to the database and are only decrypted server-side at the moment they are used.
Workspace isolation
Every row belongs to one owner and is filtered by the database itself, not by application code. A new account opens empty and cannot read another account's data.
Keys never reach the browser
Provider keys and tokens are used only on the server. Nothing sensitive is sent to the page you are looking at.
Hard publishing limits
Daily and weekly caps plus a minimum gap between posts prevent bursts, even if something upstream misbehaves.
Kill switch
One control halts every outbound write. It is checked before any publishing work begins, not after.
Full decision record
Every draft, block and publish is logged with the reasoning behind it, so an action can always be explained after the fact.
Where we are honest about the stage
Cadence is in private beta. We do not hold SOC 2 or ISO 27001 certification, and we will not claim otherwise. What we can show you is the architecture above, the decision log inside the product, and a direct line to the person who built it.
Reporting a problem
If you find a vulnerability, email support@bdotindustries.com with the details and steps to reproduce. We will acknowledge within two working days and will not pursue anyone acting in good faith.