1. Data controller
The data controller is Veraxis. For any privacy or data-protection matter, you can reach us at contact@veraxis.pt.
Veraxis respects your privacy and is committed to protecting the personal data you entrust to us. This policy explains what data we collect through this website, for what purpose, on what legal basis, and what your rights are under the General Data Protection Regulation (GDPR).
The data controller is Veraxis. For any privacy or data-protection matter, you can reach us at contact@veraxis.pt.
We only collect the data you voluntarily provide through the contact form, plus the minimal technical data needed to operate and secure the service:
We process your data to respond to your contact request and to follow up on the communication you initiate.
The legal bases are your consent and the taking of steps prior to entering into a contract at your request (Art. 6(1)(a) and (b) GDPR). Processing of technical data for security relies on our legitimate interest (Art. 6(1)(f)).
Form data is sent by email to an official Veraxis mailbox (contact@veraxis.pt) so that we can reply. We do not use this data for unsolicited marketing, nor do we sell it to third parties.
We rely on service providers that act on behalf of Veraxis and only under our instructions:
We keep contact data only for as long as necessary to handle your request and manage any resulting relationship, and, where applicable, to comply with legal obligations. After that period, the data is deleted.
Under the GDPR, you have the right to:
To exercise these rights, contact us at contact@veraxis.pt. You also have the right to lodge a complaint with the supervisory authority — in Portugal, the Comissão Nacional de Proteção de Dados (CNPD), at www.cnpd.pt.
This website does not use tracking cookies, advertising cookies or third-party analytics tools. Only the resources strictly necessary for the pages to function are used.
We apply appropriate technical and organisational measures to protect your data, including encrypted connections (HTTPS) and secure storage of credentials, outside the public code.
We may update this policy whenever necessary. The version in force is always the one published on this page, with its update date.