Security by design

We treat security as an engineering requirement from the beginning, not a checklist added at launch.

Core practices

Our approach includes clear data boundaries, least-privilege access, secure transport, input validation, auditability, backups, recovery planning, dependency updates and controlled deployment practices appropriate to each product.

Product isolation

Where practical, licensing, public website systems and customer business data are separated so that one system does not need unnecessary access to another.

Responsible disclosure

If you believe you have found a security issue affecting an Anostayen system, contact us privately through the official contact channel and include enough technical detail for investigation. Do not access, alter or retain data that is not yours.

No absolute guarantee

No software system can be guaranteed completely secure. We continuously improve controls as products and threats evolve.