Security

1. Our approach to security

Security is a core consideration in the design and development of AppZano products and services. We aim to minimise the information we collect, reduce unnecessary dependencies, and design products so that sensitive information can remain under the user's control wherever practical.

Security is not a single feature or guarantee. We continuously review our software, infrastructure, dependencies, and operational practices to identify and address potential risks.

2. Data minimisation

AppZano products are designed to collect and process only the information reasonably required for their intended functionality.

Where a feature can operate locally on your device without transmitting information to AppZano, we generally prefer that architecture.

The specific information handled by each product depends on its functionality. Product-specific documentation and our Privacy Policy provide additional information about data handling.

3. Local-first software

Some AppZano applications are designed to operate locally or offline. In these products, information processed by the application may remain entirely on your device unless you explicitly use a feature that transmits it elsewhere.

Local processing can reduce the amount of information exposed to network services, but it does not eliminate the need to secure the device, operating system, application, and any files stored on that device.

4. Application security

We use reasonable security practices throughout the software development lifecycle, including consideration of authentication, authorisation, input validation, dependency security, error handling, data protection, and secure configuration.

We review security issues according to their potential impact and prioritise remediation based on factors such as severity, exploitability, affected users, and exposure.

5. Infrastructure security

AppZano may use established infrastructure and service providers to host, distribute, authenticate, license, or otherwise operate our products and services.

Where third-party infrastructure is used, we consider the provider's security capabilities, operational requirements, and suitability for the information being processed.

Security controls and infrastructure may change as our products and services evolve.

6. Encryption

Where appropriate, AppZano uses encryption and secure transport mechanisms to protect information while it is transmitted between supported services.

The encryption mechanisms used may vary between products and services depending on their architecture and requirements.

Encryption does not protect information from every possible threat. Users should also protect their devices, accounts, passwords, licence credentials, and locally stored files.

7. Authentication and access control

Access to AppZano systems and services is controlled according to the requirements of the relevant system. Access may be restricted based on account credentials, roles, permissions, licence status, or other security controls.

Administrative access is limited to authorised personnel and systems where appropriate.

8. Security updates

We may release security updates when vulnerabilities or other security issues are identified in our software.

Users should install security updates and maintain supported operating systems and dependencies where reasonably possible.

Older versions of software may eventually stop receiving security updates. The applicable support period may vary between products.

9. Vulnerability reporting

If you believe you have discovered a security vulnerability in an AppZano product, website, or service, we encourage you to report it to us responsibly.

Please provide enough information for us to understand and reproduce the issue, including the affected product or service, relevant version information, the steps required to reproduce the issue, and the potential security impact where known.

Do not include unnecessary personal information, credentials, private keys, authentication tokens, or other sensitive information in a vulnerability report.

10. Responsible disclosure

We ask security researchers to give us a reasonable opportunity to investigate and address a reported vulnerability before publicly disclosing technical details that could increase the risk to users.

We will make reasonable efforts to acknowledge valid reports, investigate their impact, and determine an appropriate remediation strategy.

We may communicate with the reporter during the investigation when additional information is required or when clarification would assist remediation.

11. Security testing

Security testing of AppZano systems should be performed only with appropriate authorisation.

You must not intentionally disrupt services, access information belonging to other users, modify or destroy data, perform denial-of-service testing, or otherwise interfere with AppZano infrastructure without explicit permission.

If you discover a vulnerability accidentally while using an AppZano service, stop testing once sufficient information has been obtained to demonstrate the issue and report it to us.

12. Security incidents

If we become aware of a security incident affecting personal information or our services, we will investigate the incident and take appropriate steps to contain, remediate, and assess its impact.

Where notification is required by applicable law, we will notify the appropriate authorities and affected individuals within the applicable legal requirements.

13. Third-party dependencies

AppZano software may depend on third-party libraries, frameworks, operating-system components, and services.

We monitor relevant dependencies and may update or replace them where security issues, compatibility concerns, or other risks warrant doing so.

14. Limitations

While we take security seriously, no software, service, infrastructure, or method of electronic transmission can be guaranteed to be completely secure.

We cannot guarantee that every vulnerability will be discovered or prevented before exploitation, or that third-party systems used by AppZano will remain secure at all times.

15. Changes to this policy

We may update this Security Policy as our products, infrastructure, security practices, or legal requirements change.

The date at the top of this page indicates when this policy was most recently updated.

16. Contact

If you believe you have identified a security vulnerability in an AppZano product or service, please contact us through the security contact details provided on the AppZano website.