This English translation is provided for convenience. In the event of any conflict or ambiguity, the Spanish version governs.
Privacy policy
Last updated: 28 October 2026
1. Data controller
Adrian Butnaru, Tax ID 46191779M, residing at Calle Cristofor Colom 36, 17300 Blanes (Girona), Spain. Contact: info@buangh.com.
2. Personal data processed
The content fields of the form are:
- name: required, between 2 and 100 characters.
- email address: required, up to 254 characters.
- company: optional, up to 120 characters.
- message: required, between 10 and 5000 characters.
- service: required, chosen from "Custom web application or PWA", "Lead generation website", "PHP maintenance and evolution", or "Other inquiry".
- origin: optional, technical identifier up to 50 characters indicating the page or button leading to the form.
If you arrive from a service or campaign link, the origin identifier (origen) and URL campaign parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term) are submitted with the form to identify the referral source and are not linked to cookies.
The mandatory checkbox accepting this policy is also verified. To prevent abuse, a honeypot field, form initiation timestamp, and arithmetic captcha ID and answer are processed.
A cryptographic hash (HMAC-SHA256 with a secret salt of at least 32 characters) is generated from your IP address; for IPv6, the first 64-bit prefix is used. The form code saves this hash, not the plain IP, in the rate-limiting file and, where applicable, diagnostic logs. The hash is also included in the internal email notification. It is not considered anonymous data. Upon submitting a contact inquiry, a SHA-256 hash of the normalised email and its timestamp are also saved in the private database, solely to halt automatically any active follow-up email sequence to that address.
In the checklist form, I process email address (required, up to 254 characters), service of interest (optional: web app/PWA, lead gen web, or PHP maintenance), language, explicit subscription acceptance, and technical captcha, honeypot, and timestamp fields. I retain proof of consent (timestamp, text version, and HMAC-SHA256 IP hash), status, dates of confirmation, activity, and sequence dispatches, origin, valid campaign parameters, and cryptographic hashes of confirmation and unsubscribe links (including the dedicated unsubscribe token for each sequence email). Secret tokens are never stored in plain text.
The self-assessment runs entirely in your browser's memory. Answers, scores, and summaries are never sent to or stored on a server, nor appended to the form. You alone decide whether to copy the summary and share it.
3. Purposes of processing
- To address and reply to your inquiry or request and send an automated receipt acknowledgement.
- To protect the form against spam and abuse via a honeypot field, 3-second minimum completion time, session-based captcha, rate limiting, and technical diagnostics.
The checklist subscription serves to manage double opt-in verification, deliver the PDF and self-assessment links (E00 and E01), and dispatch an educational follow-up sequence of four editorial emails (E02 to E05) at +2, +5, +9, and +14 days after confirmation, designed to explore scope, budgeting, architecture, and technical reviews of web applications. The sequence enforces a minimum interval of 2 days between dispatches, retries up to 3 times upon technical delivery failure, and stops permanently upon unsubscribing, presence on the suppression list, or submitting an inquiry via the contact form. The contact form does not subscribe anyone.
4. Legal basis
To answer your inquiry and deliver the receipt: your consent upon ticking the mandatory acceptance checkbox (Article 6(1)(a) GDPR) and, where applicable, pre-contractual measures taken at your request (Article 6(1)(b) GDPR). Without mandatory fields and acceptance, the form cannot be processed.
To prevent abuse and perform technical diagnostics: the controller's legitimate interest in ensuring the security and availability of the website and email systems (Article 6(1)(f) GDPR).
For the subscription, delivery of the checklist, and the educational follow-up sequence, the legal basis is your explicit consent granted by ticking the dedicated checkbox and confirming your email via double opt-in (Article 6(1)(a) GDPR and Article 21(1) LSSI-CE). It is independent of contact inquiries and analytics consent. You may withdraw it at any time via the unsubscribe link included in every email or by writing to info@buangh.com.
5. Receipt acknowledgement and absence of an inquiry database
The website does not store inquiry contents in an internal database. Validated submissions are transmitted directly to the controller's inbox via authenticated SMTP with TLS/SSL. The internal alert contains the completed form fields, timestamp, and IP hash.
Following successful delivery to the controller, an automated receipt is attempted to the provided email, without including a copy of your inquiry message. If this receipt fails to send, it does not invalidate delivery to the controller.
Subscriptions, unlike the content of contact inquiries, are stored in a private SQLite database on the server (along with the SHA-256 hash of contacting emails, used to stop the sequence). All emails (confirmation, initial delivery, and follow-up sequence) are dispatched via the same authenticated SMTP transport with TLS/SSL and include one-click unsubscribe headers and links. Each delivery retains its own unsubscribe token hash to ensure the link remains functional.
6. Alternative WhatsApp channel
If the form cannot be submitted due to a configuration or email failure, your browser automatically opens WhatsApp (wa.me) with your name and the start of your message (up to 500 characters) pre-filled in the URL. No message is sent until you press send in WhatsApp. Once the link opens, WhatsApp/Meta processes those details as an independent controller under their own terms and privacy policy.
The automatic opening of the link transmits those details to WhatsApp/Meta even if you do not proceed to send the message. If you do not wish to use that service, please contact me directly via email.
7. Recipients and processors
No personal data is transferred to third parties, except where required by law and the described WhatsApp fallback, which triggers automatically if form submission fails. The website uses a web hosting and email provider acting as data processor in accordance with Article 28 GDPR.
8. International transfers
No international data transfers outside the European Economic Area are planned for form processing or the controller's email. Opening WhatsApp, including the described automatic redirection, is subject to the terms and transfer mechanisms of that platform.
9. Retention periods
- Inquiries received by email: for the duration of addressing the inquiry and, at most, one year following the last interaction.
- Captcha: each challenge expires after 10 minutes (600 seconds); up to five simultaneous challenges are kept. A verified challenge is deleted immediately, and expired ones are discarded upon generating a new one. The session identifier cookie is deleted when closing the browser; this does not imply immediate deletion of session data on the server.
- Rate limiting: up to 5 submissions per IP hash within 1 hour (3,600 seconds) and 50 global submissions within 24 hours (86,400 seconds). Hashes and timestamps cease to count once their window expires; entries older than 24 hours are purged from the private file upon admitting a new submission. In the absence of new submissions, the file may retain older entries until that next update.
- Diagnostic log: 30-day retention window. Each new log entry deletes lines dated on or prior to the 30-day limit and malformed lines, protected under the same exclusive lock that guards file writing. There is no independent cron purge: without new entries, physical deletion remains pending until the next write. The log contains solely timestamp, event code, and IP hash (or 64 zeroes in the event of configuration failure).
Checklist subscriptions: pending confirmation links expire after 48 hours; unconfirmed requests are removed via a CLI cleanup script. Confirmed subscriptions are purged after 1 year from the last recorded voluntary interaction. Dispatching an email or visiting the thank-you page does not reset this period. The cleanup runs daily as a scheduled task on the server.
Upon unsubscribing, subscription details are immediately deleted, retaining only the SHA-256 hash of the normalised email (lowercase, trimmed) in a private suppression list, indefinitely and solely to block future dispatches even if the resource is requested again with the same address. That list does not retain the plain email, IP, timestamp, or unsubscribe reason. Independent anti-abuse logs maintain the retention windows specified above.
10. Rights of data subjects
You may exercise your rights of access, rectification, erasure, objection, restriction, and data portability, as well as withdraw your consent at any time, by writing to info@buangh.com. Withdrawal does not affect the lawfulness of prior processing.