Security as a product principle

Principles that guide the work

• Access control — access granted according to what a role actually needs, with clear separation of responsibilities.
• Secure development — security considered while designing and reviewing changes, not only at the end.
• Responsible dependency management — tracking and updating the third-party libraries and services in use.
• Data protection appropriate to context — handling each piece of information according to its sensitivity and purpose.
• Continuous maintenance and evolution — fixes, updates and improvements as part of the product routine.

What this page does not claim

We are deliberately conservative here. This page does not claim certifications (such as ISO or SOC 2), does not assert formal penetration testing, does not specify encryption algorithms, does not establish an SLA, and does not describe a round-the-clock security operations centre.

When any of those become verifiable, they will be described specifically and dated.

About this website

This institutional website keeps no form database: the demo form composes the message in the visitor's browser and hands it to WhatsApp on their action.

No third-party tracking tools are installed.

Security contact

To report a vulnerability or raise a security matter, write to [email protected]. We ask for a reasonable window to review and remediate before any public disclosure.