Why doesn't SRONIQ publish architecture details?

Publishing implementation detail creates unnecessary exposure without adding value for evaluators — what matters to a buying committee is posture and outcome, which we cover here and in gated documentation available under NDA.

What certifications does SRONIQ hold?

We publish certifications only once formally earned. Check back here or ask your point of contact for current status.

Where is customer data handled?

Data handling commitments, including location and retention, are detailed in our Privacy Policy and in customer agreements.

Trust & Security

Accountability is a design constraint, not a claim.

We describe our posture in plain terms. We do not publish architecture, internal methodology, or implementation detail — enterprise and government reviewers requiring that depth can request it directly under NDA.

Request security documentation

Trust Centre

Everything a security or compliance reviewer needs to start with.

Privacy

Data handling commitments stated plainly and held to, independent of which customer is asking.

Security

Security policy, review cadence, and responsible disclosure processes in place from day one.

Responsible Disclosure

A defined process for reporting suspected vulnerabilities — see our Responsible Disclosure policy.

Compliance

Certifications are published only once formally earned — never as 'in progress' claims.

Architecture Principles

We design for accountability and auditability. We do not publish architecture or implementation detail.

Accessibility

WCAG 2.1 AA is a baseline requirement across the site and product surfaces.

System Availability

Availability commitments and status reporting are detailed in customer agreements.

Security & Trust Documentation

Full security documentation, data handling detail, and compliance references are available to qualified enterprise and government reviewers under NDA.

Request documentation

Frequently Asked