Security & Compliance
Bluprint holds your company's projects, documents, and conversations — so security isn't a feature we added later, it's part of how the product is built. This section explains how your data is protected and how Bluprint supports your compliance obligations.
Four pillars
| Pillar | What it covers |
|---|---|
| Access & authentication | Who can get in, and what they can do once they're in — secure sign-in and role-based access control. |
| Data protection | Encryption, isolation between companies, Australian data residency, and resilient infrastructure. |
| Compliance | SOC 2-aligned controls, GDPR data rights, and the Australian Privacy Act. |
| Auditability | A tamper-evident record of who did what — people and AI alike. |
Defence in depth
These layers work together rather than relying on any single safeguard: access is controlled by role and membership, data is isolated and encrypted, and every significant action is recorded in a trail that can't be quietly altered. If one layer is bypassed, the others still stand.
The AI is inside the boundary
A common worry with AI features is that your data leaks out to train someone else's model. In Bluprint it doesn't: the Associate runs inside the same security boundary as everything else — same permissions, same data residency, same audit trail.
Reporting a security issue
If you discover a security issue, contact the team at security@alesko.ai. For compliance questions, reach compliance@alesko.ai.
Next
Last updated: 2026-05-31
.png)