Built so each customer's data stays its own.

How Astrolabium One protects the data of every operator and every customer, what we build for in Saudi Arabia and the Gulf, and how to report a vulnerability.

Isolation you can test.

Customer data is isolated by query filters in the database layer. Cross-customer tests prove it: they fail when the filter is removed, so a change that would mix two customers' data cannot pass the build.

  • Reason's retrieval is trimmed to one customer before an answer is written
  • A clear refusal at every workspace and tenant boundary
  • Retention policies with purge, and data-subject export and delete in the product
Illustrative screen with sample data.

Platform security

Microsoft Entra ID sign-in only

People sign in with their organization's Microsoft account, so its own MFA and Conditional Access rules apply.

An append-only audit trail

Every action is recorded and cannot be edited, with separation of duties between who asks and who approves.

Four-eyes administration

Dangerous changes need a second person, from a register of dangerous actions, in one admin console.

Customer-managed keys

Encryption keys can be held in your own Azure Key Vault.

Just-in-time provider access

Elevation with customer-approved scope and time, and a break-glass register.

A hardened web surface

Security headers, strict input handling and automated security tests on every build.

Built for Saudi and Gulf buyers.

Astrolabium One is built for the NCA Essential Cybersecurity Controls (ECC-2), the Saudi PDPL and the CST regulations. One evidence item maps to every control it supports, with the responsibility split between Microsoft, the operator and the customer, and assessments sealed at a point in time.

This helps an operator and its customers prepare their own evidence. It does not make anyone compliant or certified, and we claim neither: exports say "pending sign-off".

Illustrative screen with sample data.

Accessible by design.

We aim for WCAG 2.2 AA in the product and on this site, test every route in a real browser, and publish what we find, including the gaps.

Accessibility statement

Privacy, in plain words.

What we collect on this site and why, how long we keep it, and how to use your rights under the PDPL and the GDPR.

Privacy policy

Report a vulnerability

If you find a security issue in this website or in Astrolabium One, email our security team with the steps to reproduce it. Our security.txt file (RFC 9116) has the same contact.

security@astrolabium.solutions

  • We confirm receipt and keep you informed until the issue is fixed.
  • Please do not access or change other people's data, disrupt the service, or publish the issue before we have fixed it.
  • We will not take legal action against research done in good faith under this policy.
  • Machine-readable contact: security.txt.