Security & Trust
Slabr™ runs on tenant-isolated infrastructure with row-level security, encrypted storage, role and capability-based access, append-only audit logging on critical actions and POPIA/GDPR-aligned data handling.
Six pillars
Each layer covers a different failure mode. Together they keep your quotes, jobs, finance and client data inside your tenant.
Shared responsibility
Security in cloud SaaS is shared. Here's the line — and what each side owns.
Encryption, network isolation, patch management, backups, uptime.
Tenant isolation, RLS policies, role-based access, audit logging.
Sub-processor management, breach notification, DSR tooling.
Who has access, what role, when to revoke.
What you input, who can export, retention preferences.
Which third parties you connect to your workspace.
Incident response
We don't pretend incidents never happen. We tell you what we do when they do.
Automated monitoring on application errors, failed auth, anomalous queries.
Severity assessed and affected tenants identified before any public disclosure.
We maintain internal incident-response procedures and communicate material security incidents to affected customers as quickly and responsibly as possible, with timing aligned to applicable law.
Root cause fix, post-mortem published, controls updated.
We'll send a security and data-handling summary, infrastructure overview and a snapshot of our control practices on request. Sub-processor and data-processing documentation is being formalised and will be shared as it lands.
