Legal
Privacy policy
How Hawklify processes the personal data of people who visit the site, register and use the service.
This notice, given under Articles 13 and 14 of Regulation (EU) 2016/679 (GDPR), explains which personal data Hawklify processes, why, for how long, and what your rights are.
1. Who the controller is
The controller is Marcello Gallo (sole trader), trading as Hawklify, registered office Via Roma 148, Sant’Antimo (NA), Italia, VAT number IT10786761212. For any privacy question write to [email protected].
We are the controller of the data needed to handle registrations, accounts and the security of the service. For the data the assistant reads or changes in your organisation's Odoo we act instead as a processor on behalf of the organisation, which remains its controller: that processing is governed by the data processing agreement.
2. What data we process
- Registration and account: work e-mail, company, language, role and permissions set by your administrator, creation and last sign-in dates; the address, database and version of your Odoo. If you sign in with Google or GitHub we keep only that account's identifier and the verified e-mail address it reported.
- Free trials: to prevent abuse of free trials we keep a fingerprint of the Odoo of each trial, also after the trial is deleted, used only for this check.
- Credentials: your Odoo login and API key, which you enter yourself on a protected page. We store them encrypted and never send them to the assistant.
- Connected applications: name and addresses of the application you authorise (for example Claude or ChatGPT) and the details of its authorisation.
- Use of the service: the number of requests each user makes, for the plan's limits, and an activity log of sign-ins and of the operations made through the service (who, when, on which records, with what outcome), which your organisation's administrators can consult.
- Your Odoo's structure: when an administrator asks for it, the configuration of your Odoo needed to set permissions. It contains no records.
- Source code (paid plans): if an administrator connects GitHub, the details of the connection (the repositories chosen and the access credentials, which we store encrypted). The code is read when needed and is not stored.
- Payments (paid plans): the billing details your administrator enters on Stripe's payment page (company name, address, VAT number and e-mail), the SDI code or PEC address for the e-invoice if given, the identifiers of the Stripe customer and subscription, its state and renewal date, and the details of each invoice, credit note and refund. The card is entered on Stripe's page only: we never see or keep its number.
- Technical data: the IP address and other technical data of each request, processed by our hosting provider to deliver and protect the service; we keep sign-in attempts for a short time, to protect accounts.
- Contact form: the name, e-mail, company (if given), topic and message you write in the contact form of the website. The website sends them by e-mail to us and does not store them.
- Website visits: the technical data of each request, processed by our hosting provider to deliver and protect the site, and aggregate statistics (pages viewed, country, device, referring site) from Cloudflare Web Analytics, which sets no cookies and does not follow visitors from one site to another. We use no advertising or profiling tools.
3. The data in your Odoo
When you ask the assistant something, the service reads the data it needs from Odoo as your Odoo user and passes it to the assistant. We make no lasting copy of it: some data is kept only as long as needed to complete the request, at most four hours and protected.
4. The AI assistants you connect
You, or your organisation, choose the assistant (Claude, ChatGPT, Cursor or another MCP client). The data read from Odoo reaches the assistant because you asked for it, and from then on the assistant's provider processes it under the contract and privacy policy it has with you or your organisation. We are not part of that relationship and send the assistant nothing else.
5. Why we process it and on what basis
- Handling your registration and free trial: pre-contractual steps (Art. 6(1)(b) GDPR).
- Providing the service, managing the account and sending you sign-in codes, invitations and notices about your trial: performance of the contract with your organisation (Art. 6(1)(b)).
- Collecting the payments of paid plans and handling failed payments, refunds and disputes: performance of the contract (Art. 6(1)(b)); issuing invoices and keeping the accounting records: legal obligation (Art. 6(1)(c)).
- Protecting the service, preventing abuse (including repeated trials) and tracing the changes made to Odoo: our legitimate interest and your organisation's (Art. 6(1)(f)).
- Answering the message you send through the contact form: pre-contractual steps and our legitimate interest in replying (Art. 6(1)(b) and (f)).
- Complying with legal obligations, such as tax rules: Art. 6(1)(c).
- Measuring, in aggregate and without cookies, how the website is used, to improve it: our legitimate interest (Art. 6(1)(f)).
We do not use your data for advertising, we do not sell it and we make no automated decisions about you.
Giving us the data of the registration form is necessary to create your account and, without it, we cannot provide the service; giving us your name, e-mail and message in the contact form is necessary to answer you. Everything else is optional.
6. Cookies
The website uses a single technical cookie, hk-lang, set only when you pick a language with the EN/IT switch and kept for one year so that we remember your choice; your choice of theme stays in your browser's local storage. On the contact page the anti-spam check (Cloudflare Turnstile) reads some technical data of your browser to tell people from automated programs. The site's statistics (Cloudflare Web Analytics) use no cookies. These tools are strictly necessary or anonymous and aggregate, so they need no consent under the Italian Data Protection Authority's guidelines of 10 June 2021; you can clear them in your browser at any time.
Some pages show a YouTube video. Until you press play, the page loads nothing from YouTube, only a still image kept on our site. When you press play, the player loads from youtube-nocookie.com, YouTube's privacy-enhanced mode: from then on Google Ireland Limited receives your IP address and technical data of your browser, and may store information in it, under its own privacy policy. If you prefer, the link under each video opens it on YouTube.
The service's pages use technical cookies only: the session after sign-in (7 days), the progress of a registration (24 hours), a sign-in with Google or GitHub in progress (10 minutes), the connection of GitHub by an administrator (15 minutes) and the chosen language (one year). We use no profiling or advertising cookies.
7. Who we share it with
The providers we need to run the service, appointed as processors: Cloudflare, Inc., which hosts the service and the website and provides security services and the site's statistics, Resend (Plus Five Five, Inc.), which delivers the service's e-mails and the contact form messages, and Zoho (Zoho Corporation B.V.), which hosts the mailbox where we receive and answer the messages sent to [email protected]. Stripe (Stripe Payments Europe, Limited, Ireland) handles card payments, subscriptions, receipts, refunds and disputes; for fraud prevention and its own legal obligations Stripe also acts as an independent controller, under its own privacy policy. To issue invoices we pass the billing details to our e-invoicing provider and, through the Interchange System (SdI), to the Italian Revenue Agency, and to our accountant. If you choose to sign in with Google or GitHub, that provider confirms your identity to us under its own terms. If your organisation connects GitHub to have its code read, the service reads only the repositories chosen there, read-only, under GitHub's terms. Our authorised staff, bound by confidentiality. Authorities, only when the law requires it.
8. Where the data is
The service's database is kept in the European Union. Most of our providers are United States companies or belong to United States groups and may process data outside the European Economic Area, for example while a request passes through the nearest data centre or an e-mail is delivered; they do so under the EU-U.S. Data Privacy Framework and the European Commission's standard contractual clauses.
9. How long we keep it
- Account, credentials and connected applications: as long as the account exists. Your organisation's administrator can delete it at any time, and someone on a trial can delete their own trial; at the end of the contract we delete them as the data processing agreement provides.
- Registrations whose Odoo was never set up: 7 days.
- Expired trials not converted to a paid plan: 14 days after the last day of the trial, with an e-mail notice to their administrators when it ends; then we delete them with their accounts, credentials and settings.
- Organisations started on a paid plan that is never paid: 14 days.
- Organisations whose paid subscription ended (cancelled, or still unpaid after Stripe's retries): 30 days after the end, with an e-mail notice to their administrators 7 days before; then we delete them with their accounts, credentials and settings.
- Payment data: the Stripe identifiers and the subscription's state as long as the organisation exists; the details of each invoice, credit note and refund until we have issued the matching e-invoice, then 30 more days and never less than 62 days from the payment; invoices and accounting records for 10 years, as Italian law requires.
- Fingerprints of deleted trials: 365 days.
- Activity log: 90 days.
- Request counts: 24 hours.
- Your Odoo's structure: until it is read again, the Odoo address changes or the organisation is closed.
- Sign-in codes 15 minutes, activation codes one hour, invitations 7 days; access tokens one hour, refresh tokens 30 days.
- Changes awaiting confirmation: up to four hours.
- GitHub settings for the source code: until an administrator removes them or the organisation is closed.
- Records of sign-in attempts: 24 hours.
- Messages sent through the contact form: as long as needed to answer you and follow up.
- Technical logs and recovery copies: at most 30 days.
10. How we protect it
Connections are always encrypted; credentials and secrets are encrypted; our administrators use a second step to sign in; the assistant works as your Odoo user with the permissions Odoo gives you, plus the limits set by your administrator.
11. Your rights
You can ask us at any time for access to your data, rectification, erasure, restriction of processing and portability, and you can object to processing based on legitimate interest, by writing to [email protected]. For the data we process on behalf of your organisation you can also contact your administrator; requests we receive are forwarded to them. You also have the right to lodge a complaint with a supervisory authority, in Italy the Garante per la protezione dei dati personali (garanteprivacy.it).
12. Changes
If we change this notice significantly, we tell the organisations' administrators by e-mail.