Controller and scope
The controller identified by VDNX is Victor Diaz García, a self-employed professional, Spanish tax ID 51153851B. Contact: [email protected]. Address: Calle Aires de Lima, n.º 1, 38205 San Cristóbal de La Laguna, Santa Cruz de Tenerife, España Country of establishment: Spain.
This information covers the website, blog and contact form. A professional engagement may require additional privacy information and agreements.
What information is collected
The form asks for your name, email address, project type and message. Company is optional. This information helps us understand and respond to your enquiry; without a valid email address, we cannot reply by email.
The server receives the IP address needed for the connection and uses cryptographic hashes of the IP address, email and content to limit abuse and prevent duplicate submissions. These hashes are pseudonymised data, not a guarantee of anonymity.
We do not request identity documents, keys, recovery phrases, wallet addresses or financial information. Avoid including sensitive information or other people's data that is not needed to explain the project.
Data sources and required fields
Enquiry data comes from what you provide. The IP address and technical request data accompany the connection. Required fields are identified in the form; the company field is optional. If you prefer not to use the form, you can email [email protected] directly. An incorrect email address prevents a reply through that channel.
If you write on behalf of another person or a company, provide only necessary professional information and ensure you can disclose it. If we receive personal data indirectly, the corresponding information duty will be addressed. The form is not intended for medical records, passwords, identity documents or children’s data.
How it is used
- Receive, assess and respond to your enquiry.
- Prepare a proposal when requested and continue discussing the project.
- Detect duplicate submissions, limit form abuse and maintain service availability.
- Serve the website and maintain its technical operation.
This implementation does not add your contact to a marketing list, install analytics or create commercial profiles. It does not make automated contracting decisions; technical limits may temporarily reject a submission. The blog does not provide comments, reader accounts or subscriptions.
AI article generation uses editorial topics and sources; it does not use form messages, visitors' email addresses or technical connection data.
Purposes and legal bases
- Your project request: pre-contract steps you request as a potential party to the contract, under GDPR Article 6(1)(b).
- General enquiries and professional contacts: the legitimate interest in responding and maintaining the relationship with the organisation you represent, limited to necessary data, under Article 6(1)(f).
- Website delivery and abuse prevention: the legitimate interest in keeping the service available and protecting it against automated or duplicate submissions. Temporary controls and data limited to that purpose are used.
- Legal obligations: where necessary to address rights, official requests or legally required records, Article 6(1)(c). Additional contractual processing will be explained if an engagement is agreed.
Legitimate interest is not unlimited permission: it requires assessing necessity and the effect on your rights. You may object on grounds relating to your particular situation. Acknowledging this policy is not treated as consent for other purposes, and your email is not added to advertising lists.
References: GDPR, Articles 6, 13 and 21 and Spanish data protection law, professional contacts.
How long data is kept
The form temporarily holds your text while it is open. The server receives the fields to send them through Resend, without creating a contact database or saving a copy to disk. Application logs include only the technical result, without names, email addresses, IP addresses or messages.
Abuse and duplicate controls use temporary process memory: counters and cryptographic hashes with a key generated at startup and never persisted. These are pseudonymised data, not a guarantee of anonymity.
- IP control: up to 10 minutes.
- Email control and global counter: up to one hour.
- Submission references, hashes and status: up to 24 hours. Cleanup runs with each request and every minute; an expired entry may remain for up to one additional minute. Restarting the process removes these controls.
- Mailbox enquiries without an engagement: 12 months after the last contact, unless legal obligations or claims justify retention.
Resend maintains its own retry protection for 24 hours and publishes 30-day retention for email data and logs on the Free plan used. Mailbox retention is independent. If an engagement is agreed, necessary information will be retained to perform the agreement and address applicable obligations or claims.
According to the infrastructure provider response dated 19 October 2026, application, deploy, build and HTTP logs are stored in the United States for 90 days, including services deployed in Europe, without early or selective deletion. The Pro dashboard provides a 30-day viewing window, which is not the deletion period. These provider logs are separate from the application controls in memory. You can request updated information at [email protected]. Resend retention information.
Providers and international transfers
Cloudflare provides DNS, content delivery and connection protection. Its global network may process IP addresses, HTTP requests and technical data to serve the website and detect abuse. Cloudflare data processing agreement and privacy policy.
Resend receives the form fields to deliver your enquiry by email and uses your address for replies. Its API is used from the server; your browser does not load a Resend widget. Open and link tracking are disabled.
Resend stores data in the United States; selecting a European sending region does not change that storage. Its agreement includes Standard Contractual Clauses for transfers. Resend agreement and subprocessors.
OVHcloud Zimbra provides the [email protected] mailbox, where enquiries are received and managed. OVHcloud data protection.
Cloud infrastructure: we use a provider established in the United States, with the application deployed in Amsterdam, the Netherlands, without its own contact database. This location does not guarantee that logs, support, backups or subprocessors remain exclusively within the EU. Confirmation of the contractual coverage and safeguards actually applicable to the account has been requested.
You may request the infrastructure provider’s identity and a copy of, or reference to, transfer safeguards at [email protected]. Recipients are described by category where indicated; we do not claim that all transfers have already been verified. Recipients required by a legal obligation may also have access. VDNX does not sell enquiries.
Your rights
You can send a request to [email protected], stating the right you wish to exercise and the information needed to locate your enquiry. Additional identity information will only be requested if needed to handle it.
Under the GDPR, where its requirements are met, you may request access, rectification, erasure, restriction or portability, or object to processing. If any processing is based on consent, you may withdraw it without affecting earlier processing.
You may contact the relevant data protection authority. In Spain, this is the Spanish Data Protection Agency.
How we handle a request
Write from the email address associated with the enquiry, state which right you wish to exercise and provide enough information to locate it. Do not send an identity document in advance: proportionate additional identification will only be requested where there are reasonable doubts about identity.
We will generally respond within one month of receipt. If complexity or the number of requests permits a lawful extension of up to two further months, you will be informed within the first month and given the reasons. Requests are free, except in the legally permitted cases of manifestly unfounded or excessive requests.
Erasure may be limited by retention obligations or the defence of claims. You may object to processing based on legitimate interests and complain to the AEPD. We do not use form data to make automated decisions with legal or similarly significant effects on you.
Cookies and local technologies
The application does not install cookies or tracking tools. Scene and form states are temporary. Details of the technical inventory are explained in the cookies and storage policy.
Data protection and technical limits
The connection uses HTTPS. The form limits submission frequency, validates fields and prevents duplicate requests. The application keeps credentials on the server and does not record enquiry contents in its own logs. These measures reduce risk; they do not eliminate every possibility of an incident.
Automatic controls may temporarily reject a submission. They do not decide whether a project is accepted or build a commercial profile. If you cannot submit an enquiry, direct email remains available. A personal data breach will be assessed and the applicable duties to notify the authority and affected people will be addressed.
Changes to this policy
The review date identifies the current text. If a purpose or relevant provider changes, the information will be updated and any required notice or consent addressed before using data for an incompatible purpose. Publishing a new policy does not obtain your consent.
Limited retention for obligations or claims does not permit reuse for marketing. Where statutory blocking applies, data will be restricted to the applicable liabilities during their limitation periods and then deleted.