TwingBot security

TwingBot protects account access, sessions, connected channel credentials, courier settings and sensitive automation workflows.

How access is protected

TwingBot uses authenticated routes, session controls, masked IP display, secret-field handling and background workers for sensitive operations.

What account holders control

Practical controls available to every workspace:

• Users can revoke active sessions from settings
• Connected channel and courier credentials should only be added by authorized users
• Account deletion unsubscribes connected Meta pages and removes or anonymizes workspace data