Privacy Policy

Rodrigo Junquera Peláez, an individual trading under the business name ZYREN, is the owner of this website. ZYREN is not a separate company and no company has currently been incorporated for this activity.

Country: Spain. Location provided: Collado Villalba, 28400, Madrid, España.

Data protection contact: rodrigo@zyren.com.co.

This policy is reviewed under Regulation (EU) 2016/679 (GDPR), Spanish Organic Law 3/2018 and, for communications and browsing technologies, Spanish Law 34/2002.

The form asks for name, company and email address. These details are stored together with a request identifier and the date and time of registration. A notification with the request details is sent to the owner’s email so it can be handled.

The purpose is to manage the requested demonstration and directly related communications. The legal basis is Article 6(1)(b) GDPR where these are pre-contractual steps requested by the data subject. If you act as a company contact, the application of Article 6(1)(f) GDPR and Article 19 of Organic Law 3/2018 must be assessed, limited to maintaining relations with the entity represented and subject to weighing the interests and rights involved.

The form requires ticking a box confirming you have read this policy. That record is for information only: it is not general consent, does not constitute acceptance of a contract and does not authorise marketing campaigns. This form has not been identified as subscribing anyone to advertising lists. Sending other promotional communications requires a separate analysis of the legal basis and the requirements of Law 34/2002.

The requested fields are necessary to process a request through this form. No health data or other special categories are requested; please do not enter them.

The form uses a hidden control field and the time elapsed before submission to reject certain automated requests. These values are validated but not stored as fields in the request records.

The purpose is to protect the form against abuse. The legitimate security interest under Article 6(1)(f) GDPR must be documented, assessing necessity, proportionality and rights.

This website’s code includes contracting through a payment provider and subsequent collection of first name, surname, company and work email. Order data, amounts, status, dates and payment provider references are kept; the demo form does not collect card numbers. Once contracting details are completed, the code provides for identification and order information to be passed to the ZYREN platform for setup.

Managing a contract requested by the data subject may rely on Article 6(1)(b) GDPR; company contacts require the analysis described above. Article 6(1)(c) applies only to specific legal obligations that are actually enforceable, for example tax or accounting, and not as a generic justification for any data.

Authenticated access exists to manage website content. Account, permission and activity data must be limited to the purpose of access and administration.

Where the client determines the purposes and means, it will normally be the controller of that processing. If the owner of ZYREN processes data on behalf of the client, roles must be defined and the processing agreement under Article 28 GDPR put in place where required, covering instructions, confidentiality, sub-processors, security, assistance, incidents and return or deletion. This page does not replace that agreement.

The client must have a legal basis, provide data subjects with the necessary information and not add unnecessary data or special categories without an assessment and appropriate safeguards.

The code includes session management, error logs and operational statuses for requests and payments. Security and diagnostics may rely on legitimate interests under Article 6(1)(f), subject to balancing and minimisation; legal obligations will only justify what is specifically required.

It is not claimed that sales profiles are collected, that behavioural advertising takes place or that these logs are anonymous.

The following have been identified: Lovable Cloud for application infrastructure, database and authentication; Lovable’s managed email service for notifications; Stripe for payments; and Google Fonts for typefaces loaded from external servers. Loading a typeface involves a connection to that third party and may disclose technical data such as your IP address.

A payment provider may act as an independent controller for certain operations; the same role is not attributed to all providers.

Data will only be disclosed to authorities or other recipients where there is a legal basis.

The retention criterion is to keep data only for as long as needed for each purpose and, where applicable, to apply the legal periods, access restrictions and blocking required. No immediate deletion or unimplemented period is promised.

You may request access, rectification, erasure, objection, restriction and portability, in the cases provided by law, by writing to rodrigo@zyren.com.co. State the right and the information needed to locate your request; additional proof of identity will only be requested if there are reasonable doubts, and proportionately. Do not send unnecessary identity documents.

Where processing is based on consent, you may withdraw it without affecting the lawfulness of prior processing. You may object to processing based on legitimate interest in the cases set out in the GDPR. Requests will be handled within the legal deadlines and exceptions; the general deadline is one month, which may be extended with reasons in the cases under Article 12 GDPR.

You may lodge a complaint with the Spanish Data Protection Agency (AEPD) at https://www.aepd.es, or with another competent supervisory authority. If data is processed on behalf of a client, the request may need to be passed to that controller, with the appropriate assistance.

Local storage has been confirmed for remembering the language, and session storage mechanisms for authenticated access. No unverified cookie inventory is presented, nor is it stated that all technologies are strictly technical.

Google Fonts is loaded when the page opens.

If non-essential technologies subject to consent are identified, they must be blocked until consent is obtained, with options to accept and reject shown with equal prominence, plus easy access to change preferences.