Legal
Data processing agreement
The Art. 28 GDPR agreement between Hawklify and customer organisations for the data processed in their Odoo.
This agreement supplements the terms of service and governs, under Art. 28 GDPR, the personal data that Marcello Gallo (sole trader), trading as Hawklify (the provider, processor) processes on behalf of the customer organisation (the customer, controller) in providing Hawklify. Where it conflicts with the terms of service, this agreement prevails on data protection.
1. Subject matter and duration
The provider processes the customer's personal data only to provide the service described in the terms, for the whole relationship and until the deletion set out in section 10.
2. Nature and purpose
The service reads and, within the permissions set by the customer, changes data in the customer's Odoo at the request of users authorised by the customer, through the AI assistant the customer chose; if the customer connects GitHub, it reads the source code of the repositories the customer chose; it keeps the accounts, the credentials and an activity log that the customer's administrators can consult.
3. Data and data subjects
- Types of data: whatever the customer's users have the assistant read or write in Odoo (for example records of customers, suppliers and employees, contacts, sales and accounting documents, messages, the text of attachments), the customer's users' account data and their API keys, and the source code the customer has read from GitHub, which may contain the names and e-mail addresses of its authors.
- Data subjects: the customer's users and the people whose data is in the customer's Odoo (customers, suppliers, employees, contacts).
- The service is not designed for special categories of data (Art. 9 GDPR): if Odoo holds any, the customer restricts access with the service's roles and hidden fields or with Odoo's permissions.
4. The customer's instructions
The provider processes the data only on the customer's documented instructions. Instructions are the terms of service, the customer's settings in the service (users, roles and permissions) and the requests the customer's users make through the assistant. The provider tells the customer if it believes an instruction infringes data protection law.
5. Confidentiality
The people the provider authorises to process the data are bound by confidentiality and access the data only when needed to provide or protect the service.
6. Security measures
- Encrypted connections between users, assistants, the service and Odoo.
- API keys and secrets encrypted with keys kept separately from the data, each API key usable only for its user and its Odoo.
- Passwords and tokens kept only in a form that cannot be reversed; short-lived access tokens.
- Every user acts as their own Odoo user, under Odoo's access rules, plus the roles, permissions and hidden fields set by the customer.
- Changes checked against Odoo before they run and approved by a person for the users for whom the customer chose the approval card; changes awaiting confirmation kept encrypted for at most four hours; activity log.
- Read-only access to GitHub, limited to the repositories the customer chose; the code read is kept only in memory.
- Separation between organisations; second step for the provider's administrators; database recovery history.
7. Sub-processors
The customer authorises the provider to engage the following sub-processors, bound by obligations equivalent to those of this agreement: Cloudflare, Inc. (United States) (hosting and infrastructure of the service, with its database in the European Union, and security services), Resend (Plus Five Five, Inc., United States) (delivery of service e-mails) and Stripe (Stripe Payments Europe, Limited, Ireland) (payments of the paid plans: the billing details of the customer and of the administrators who pay). The provider notifies the customer's administrator by e-mail at least 30 days before adding or replacing one; if the customer objects on reasonable grounds it may terminate without penalty.
The providers of AI assistants are not the provider's sub-processors: the customer chooses and connects them and governs that relationship. Neither are Google and GitHub, which a user may choose to sign in with, nor GitHub when the customer connects its repositories: the customer chooses it and governs that relationship.
8. Assistance to the customer
The provider helps the customer, as far as reasonable, to answer data subjects' requests and to carry out impact assessments and prior consultations, and informs it of a personal data breach without undue delay and in any case within 48 hours of becoming aware of it, with the information available.
9. Transfers
The service's database is kept in the European Union. The sub-processors may process data outside the European Economic Area, for example while a request transits their network or an e-mail is delivered; any such transfer takes place only with the safeguards of Chapter V GDPR, namely the EU-U.S. Data Privacy Framework and the standard contractual clauses.
10. Deletion at the end of the relationship
When the organisation is closed, the provider deletes within 30 days the customer's accounts, API keys, connected applications and other settings, unless the law requires otherwise. When a paid subscription ends and is not renewed, the organisation is closed 30 days after the end, after an e-mail notice to its administrators 7 days before. Recovery copies run out within 30 days and the activity log within 90 days. Odoo data is not copied by the service and stays in the customer's Odoo.
11. Audits
The provider makes available the information needed to demonstrate compliance with this agreement. The customer may carry out an audit, at its own expense, with 30 days' notice, at most once a year unless there has been a breach, also through an auditor bound by confidentiality.