Legal and security
Security Policy
Information on security and recommendations for safe use. No guarantee of absolute security.
Content last reviewed: 9 October 2026
1. Scope of this information
This review is limited to the code and accessible configuration of the commercial website. It is not a full audit of the service, the client platform or all providers. No certifications, external audits or absence of vulnerabilities are claimed.
Contact and support: rodrigo@zyren.com.co.
2. Validation and access control observed
The demo form validates its fields on the server before saving and includes basic controls against automated submissions. In the configuration reviewed, the commercial records examined cannot be read or written directly from the browser by visitors or ordinary users.
Content administration uses authentication and permission checks. This evidence does not guarantee that all access from other systems or all platform operations are audited.
3. Credentials and confidentiality
The code reviewed accesses private email and payment credentials from the server, not as values published on these pages. Access must be granted on a need basis and credentials must be kept safe and not shared.
This page does not publish keys or instructions for accessing internal systems.
4. Communications and encryption
The website’s public address uses HTTPS. This alone does not evidence the protection of every link between services, the complete cryptographic configuration or encryption at rest for each data set.
End-to-end encryption is not claimed.
5. Logs and dependencies
The code contains logs of errors and certain operational events.
The application relies on external services and libraries. Configuring, updating and assessing those dependencies requires ongoing review; merely using them does not evidence security, certification or compliance.
6. Incidents
To report a possible incident, write to rodrigo@zyren.com.co with the minimum information needed, without attaching secrets or third-party data. Do not access or disclose other people’s information.
Where a personal data breach requires it, the communications and notifications under Articles 33 and 34 GDPR will apply, including notification to the authority within 72 hours of becoming aware of it, where applicable.
7. Safe use by users
Use unique, strong passwords, do not share credentials and sign out on shared devices. Report any unauthorised use and avoid including unnecessary personal data in support messages. None of these recommendations constitutes a guarantee of absolute security.