Skip to Content

Licences & Licence Verification

Transparency about our licence models and the data processed by MailDesk licence validation

1. Our licence models

Depending on the product, our modules are shipped under the following licences (the licence stated in the respective module or product description prevails): MOPL-1.0 (Metzler Odoo Proprietary License), OPL-1 (Odoo Proprietary License), LGPL-3, AGPL-3 and the proprietary MailDesk v4 licence. Usage rights are governed by our Terms (Sec. 6).

As of the MailDesk v4 generation, part of the product code is shipped in protected form and unlocked via licence activation. The protection safeguards our intellectual property and licence model - it does not hide any additional functionality, and no program code is downloaded from the internet: the runtime loader only executes code contained in the locally installed package.

2. Which data does the licence check transmit?

Licence validation communicates with our licence server via TLS in three operations: one-time activation, periodic token renewal and a licence heartbeat. Only the following data is transmitted:

DataExplanation
Licence key / licence IDyour purchased licence
Anonymous instance identifierrandom UUID of the Odoo database - no inference about your company or data possible
Odoo and module versione.g. “19.0” - for compatible updates
Number of internal Odoo usersthe number only (heartbeat) - no names, no e-mail addresses
Technical security fieldstimestamp, random value (nonce), HMAC signature - protection against tampering and replay attacks
IP addresstechnically visible to the server, as with any HTTPS connection

Not transmitted: e-mails, e-mail content, attachments, contacts, mailbox content or any other business or personal data from your system.

Legal bases: Art. 6(1)(b) GDPR (performance of the licence agreement) and Art. 6(1)(f) GDPR (protection against licence abuse). More information: Privacy Policy.

3. Verifiability for customers

On request, we offer existing customers a technical description of the licence verification process, a joint review session of the relevant logic (under NDA if desired) and a written data protection confirmation. Contact: [email protected].