Trust
Security stated as it is, including the gaps.
This page describes the product as it stands today. Where something is planned, it says planned. Where something is not done, it says so. A trust page that reads like a brochure is worse than no trust page at all.
Where the data lives
The product is installed inside the customer's environment. Estate data, credentials, evidence files and logs stay there. We do not operate a multi-tenant service, we do not receive a copy of your record, and there is no support tunnel into your installation that bypasses your access controls.
The only outbound traffic the product initiates by default is the licence check. It carries a licence identifier and a version string. If you enable the optional error telemetry, it carries error signatures and counts, never entity names, file contents or credentials. Both can be disabled, and the licence check can be satisfied offline for air-gapped installations.
This marketing website is a separate system. It is a static site hosted on Azure Static Web Apps. It sets no analytics cookies and loads no third-party scripts. See the privacy notice for what the contact form collects.
In the product
- At rest
- Database and evidence store encrypted with keys you hold.
- In transit
- TLS 1.2 or later to every collector endpoint.
- Credentials
- Held in your secret store, brokered per run, never written to logs.
- Audit
- Every run, approval and export attributable to a named user.
- Export
- Documented schema, no proprietary format lock.
Access and permissions
Read-only by default
Discovery credentials are scoped read-only. A discovery-only run will refuse a credential that carries write scope to a covered workload.
No standing vendor access
We hold no persistent access to a customer installation. Support access is granted by you, time-boxed, and revoked by you.
Least privilege inside the app
Roles separate discovery operators, reviewers and administrators. A reviewer can see a record without being able to re-run the collector that produced it.
Compliance position
Checked 17 November 2026
| Item | Status | Detail |
|---|---|---|
| ISO/IEC 27001 | Planned | Not held. A certification body has not been engaged. The target is certification after the entity is incorporated and the information security management system has run for a full audit cycle. |
| SOC 2 Type II | Planned | Not held. No observation period has started. Because the product is installed rather than hosted, the scope will cover the development and support organisation, not a service platform. |
| Cyber Essentials | Planned | Not held. To be assessed after incorporation, since the scheme requires a legal entity. |
| UK GDPR / DPA 2018 | Designed for | The installed model means we are not a processor of target data. Where we handle contact details through this site or a support relationship, the privacy notice sets out the basis and retention. |
| Penetration test | Not yet | No third-party test has been completed. One is scheduled before the first paid production licence. Results will be summarised here without the detail that would help an attacker. |
| Security questionnaire | On request | A current written response is available under NDA. It will include the unanswered items rather than omitting them. |
If a procurement process requires a held certification, we will not pass it today. We would rather you know that before the questionnaire than after it.
Vulnerability handling and disclosure
Dependencies are pinned and reviewed on a weekly cadence. Every release passes an automated dependency audit and a signed build. A severity-one issue in a shipped version triggers a security release, not a scheduled one.
We accept reports from anyone. Send them to security@acqi.tech, ideally with a reproduction. We will acknowledge within two working days, tell you what we intend to do, and credit you if you want credit.
We will not pursue a researcher who acts in good faith, stays within the scope of their own installation or this website, and gives us a reasonable window before publishing. There is no paid bounty programme at this time.
- Contact
- security@acqi.tech
- Machine readable
- /.well-known/security.txt
- Acknowledgement
- Two working days
- In scope
- This website, shipped product builds, the installer and update channel
- Out of scope
- Customer-operated infrastructure, third-party cloud services, social engineering