Security and control
Cascand can decide what deserves attention. You decide what it is allowed to do.
That is the whole security model. Here is what it means in practice.
Always available to you: Pause · Revoke · Disconnect · Export
In practice
Consequential software should be controlled. Cascand is.
Your data stays under your control
Your connected systems remain yours. Cascand reads from them and writes back to them according to the access you authorize.
Your account is isolated
Each customer account is isolated from every other customer. Access is enforced at the account boundary, not only in the interface.
You decide what Cascand can do
Permissions are explicit and per capability. Connect only what you want. Pause Cascand for a person, a team or a capability at any time. Disconnect a system and Cascand's access ends with it.
Cascand can reason without you. It cannot act without you.
It can research, prepare and organize work within the limits you set, entirely on its own. Consequential external actions, a send, a booking, a CRM update, always require your approval.
Cascand does not assume an action succeeded
It confirms important actions with the system that performed them, and tells you Uncertain when it cannot. Never a false Done.
Credentials are protected
Connection credentials are encrypted at rest, can be rotated, and are never shown in the product or written to logs. Cascand does not hold your LinkedIn password.
Untrusted text stays text
What arrives from email, the web or a spreadsheet is treated as information, never as instructions. It cannot make Cascand act.
Everything is on the record
Every recommendation, approval and action is kept in a tamper-evident audit trail: even Cascand's own systems cannot quietly edit it. You can see what Cascand decided, what it did, and why.
You can leave
Export everything your account holds at any time. Ask for identifying data to be erased and it is.
For your security review