HQ+ · CONTATTI
Contact form privacy notice
Information under Article 13 GDPR about the data entered in HQ+’s Contact form and the resulting email notification. This notice is separate from the chat notice.
1. Controller
The website uses the HQ Plus (HQ+) brand and lists VAT number 14969110965. Full legal name, address, privacy rights contact and any DPO: TO BE CONFIRMED. The Contact form remains available for general enquiries but is not represented here as an approved privacy rights contact.
2. Data
We collect name, email, company, optional role and message, together with any selected product, language, page path without query parameters, date/time, request identifier, anonymised IP and user agent. Acknowledgement is recorded with the notice version, path and server timestamp. Temporary counters, content hashes and a honeypot support abuse prevention and duplicate detection. The backend receives the connection IP before anonymising it; infrastructure logs may contain additional technical information.
3. Purposes and lawful bases
Purposes are handling and answering your enquiry, discussing the project and preventing abuse and duplicates. Proposed bases requiring validation are Article 6(1)(b) for genuine pre-contractual requests and Article 6(1)(f) for other informational requests and security, subject to a legitimate interests assessment. The checkbox acknowledges the notice; it is not consent to marketing or newsletters. The form does not activate promotional campaigns.
4. Optional provision
The current form requires name, email, company and acknowledgement; role and message are optional. Without the required fields or checkbox, submission is blocked. Do not include credentials, passwords, health data or confidential third-party information. Using the form is optional when browsing the website.
5. Processing and recipients
The backend stores the contact in Firestore and emails a notification to the configured HQ+ recipient mailbox. It includes the enquiry and your reply-to address. Authorised staff, Google/Firebase hosting, database and Functions, sender and recipient email providers and technical support providers may process data. Contractual entities and roles need confirmation. Form content is not sent to Claude/Anthropic and no automatic acknowledgement email is sent to the visitor.
6. Security
Firebase App Check with reCAPTCHA Enterprise, validation, request limits, origin checks and deduplication protect the form. The browser may send Google technical data for abuse checks. These checks are not used to make commercial decisions about you. Actual production infrastructure safeguards require verification; absolute security is not promised.
7. Retention
The code proposes expiry 180 days after collection for new contacts, configurable by the organisation; the controller must confirm its adopted period. Firestore deletion requires active TTL policies and is asynchronous. Submission references expire after seven days, duplicate-content hashes after ten minutes and abuse counters after approximately two hours, plus TTL deletion delay. Old records without expiry require separate handling. Email notifications and replies, logs and backups have separate retention TO BE DEFINED; deleting Firestore records does not delete those copies. Any further legal or claims-related retention must be identified and documented.
8. International transfers
Google and email providers may use international infrastructure; exclusively European processing is not guaranteed. The controller must confirm applicable entities, countries, agreements, Chapter V safeguards and how to obtain copies. Provider links alone do not establish HQ+’s account and mailbox terms.
9. Rights
Subject to GDPR conditions, you may request access, rectification, erasure, restriction, portability where applicable, and object to processing based on legitimate interests. Complete the rights contact in section 1. If consent-based processing were introduced, withdrawal would not affect earlier lawful processing. You may complain to the Italian Garante or another competent authority.
10. Changes and acknowledgement
Advertising profiling and automated decisions producing legal or similarly significant effects are not intended. The checkbox starts unchecked and must be selected for each submission; the server verifies acknowledgement and the current notice version before acquiring a new request. The record captures your declaration, not proof that every paragraph was read. Update the notice when processing changes.