We believe in being honest about what we do and do not do. Here are the security practices we have implemented. Nothing more, nothing less.
Every entity in TITANS is protected by row-level security. Users only see and act on records they are authorised to access, based on their role and ownership.
Access is controlled by role — admin, sales, editor, finance. Each role has defined permissions for create, read, update and delete operations.
Business units (TD Publishing, TD & Partners Zimbabwe, TD & Partners UK) keep data separated. Users see only the business units they belong to.
Autopilot actions require human approval before execution. You decide what is automated, what needs approval and what stays manual.
Entity records track created_date, updated_date and created_by_id. Activities and actions are logged with timestamps and user attribution.
External integrations use OAuth-based connections. You authorise each integration explicitly and can revoke access at any time.
We do not claim certifications we do not have. We do not claim SSO, SLAs or dedicated account managers unless they are actually available. As we grow, we will update this page with every new security practice we implement.
For security questions, contact us at hello@salespipeline.cloud
We are happy to walk you through our practices in detail.