Trust should be designed into the system.

Our approach

Security and privacy are ongoing engineering and operational responsibilities. HumanoSys works to reduce unnecessary data collection, restrict access, protect information in transit and at rest where appropriate, maintain accountable system behaviour and improve controls as the platform evolves.

Specific controls can differ by product, deployment model, customer configuration and contractual requirements. We avoid presenting a security certification or regulatory-compliance claim unless it is current and supportable for the relevant service.

Privacy by design

We design features with the purpose of processing in mind: what information is needed, who should be able to access it, how long it should be retained and what transparency users need. The public website also provides controls for optional analytics rather than treating analytics consent as automatic.

Read our Privacy Policy and Cookie Policy for the public website.

Access control

HumanoSys products are designed around authenticated access and role-based authorization so that access can be limited according to a user's responsibilities. Customer deployments can require additional organisational and data-scope controls depending on the information being managed.

Customer and tenant data separation

HumanoSys is designed to keep customer data logically separated and access-controlled. Deployment and data-hosting arrangements can vary by customer, so data location, database architecture, administrative access and other isolation requirements should be confirmed as part of each implementation.

Protecting data

We use secure transport for website traffic and apply technical and administrative safeguards intended to protect information against unauthorized access, misuse, alteration or loss. Sensitive customer deployments may require additional controls based on the type of data, operating environment and assessed risk.

Security is not a one-time configuration. Software dependencies, configurations, authorization rules, logs, backups and operational procedures all require continued review.

Auditability and operational accountability

HumanoSys platform capabilities are designed to support accountable operations through permissions, traceable actions and audit-oriented records where those features are enabled. We continue to strengthen logging, monitoring and security validation as products mature.

Responsible AI

AI should support human decisions rather than obscure how a result was produced. Our approach is to minimize unnecessary personal information sent to AI services, keep humans responsible for consequential decisions and make AI use more transparent and configurable as HumanoSys capabilities evolve.

Customer-specific AI controls and data-processing requirements should be assessed according to the deployment, data sensitivity and approved providers.

Security assurance

Our security programme is being developed around recognized application-security and risk-management practices. Customer security reviews can consider the controls, architecture and contractual requirements relevant to the proposed deployment rather than relying on broad marketing claims.

If an organisation has specific requirements for data residency, retention, access, integrations, incident handling or assurance evidence, those requirements should be addressed during solution design and contracting.

Report a security or privacy concern

If you believe you have found a security issue, privacy concern or misuse affecting HumanoSys, contact support@humanosys.com. Please include enough detail for us to understand and investigate the issue, but do not send passwords, API keys or unnecessary personal data.

For general enquiries, use the contact page.

Last updated: 1 September 2026.