Transparency

Running a store means trusting somebody else with your customers, your orders and your revenue. This section is where we set out what that trust rests on — and where it does not rest on anything yet.

We have tried to write it the way we would want to read it: every claim on these pages either names how it was measured, or says that it has not been measured. A security page is the worst possible place to round an unknown up to a yes.

What is on this page

Where your data livesRegion, database engine and what stays inside it.

Availability & recoveryZone redundancy, point-in-time restore, and the drill result.

How stores are kept apartRow-level security in the database, with the measured coverage.

Monitoring & alertingWhat is watched, who is paged, and the drill that proved it fires.

Sign-in protection & auditLockout, two-step verification, and which sign-ins are recorded.

Business continuityWhat happens during an outage, and who does what.

Archiving policyWhat we keep, for how long, and what leaving looks like.

Restore test scheduleHow often recovery is rehearsed, and where results are recorded.

What we do not have

We would rather you read this from us than discover it later.

• No ISO 27001, ISO 27701 or ISO 22301 certification. CIQRA holds none of these. Certifications that a cloud provider holds for its own data centres are the provider’s, not ours, and presenting them as CIQRA’s would be misleading.
• No third-party penetration test report. One has not been commissioned.

Both are queued for after our 1.0 release. When either changes, it will appear here with a date and a scope — not as a badge.

The short version, including the uncomfortable parts

If you read nothing else:

• Encryption at rest — on, for both the database and file storage.
• Recovery — data-loss window under five minutes; the restore horizon is set to 35 days but is still filling — 6.7 days were actually restorable on 9 August 2026, reaching the full 35 on 6 September 2026. The restore itself has been rehearsed, with a PASS.
• Failover — configured and healthy, never rehearsed. We do not call it tested.
• Web application firewall — traffic passes through Cloudflare, but we have not verified that a WAF rule set is enforcing anything, so we do not claim WAF protection.
• Two-step verification — available per user; a store cannot yet require it of its whole team.
• Sign-in audit trail — complete on CIQRA’s operator console, absent on the merchant admin, by design.
• Certifications and penetration testing — neither exists.

Every one of those is expanded, with its measurement, on the pages above.

If something you need is not answered here, ask us — we would rather tell you “not measured” in a reply than have you infer a yes from silence.