Acceptance and organizational authority
By installing, assigning, accessing, or using the ContextSign Outlook add-in, the user and the customer organization accept this EULA. If you act for an organization, you represent that you are authorized to do so. If you do not accept it, do not install, assign, or use the add-in.
1. Licensor
The add-in is licensed by Digital David AG, Weserstraße 4, 60329 Frankfurt am Main, Germany, registered with Amtsgericht Frankfurt am Main under HRB 121238 ("Digital David"). Contact: hello@digitaldavid.io.
2. License grant
Subject to this EULA and an active ContextSign entitlement, Digital David grants the customer and its authorized users a limited, non-exclusive, non-transferable, non-sublicensable, revocable license during the applicable service term to install or receive the add-in through approved Microsoft 365 administration channels and use it solely with the customer's authorized Microsoft 365 tenant and the ContextSign service.
The add-in is licensed, not sold. The license is limited to the users, groups, tenants, environments, and other scope authorized by the order or entitlement. Tenant-wide or group deployment does not grant rights beyond that scope.
3. Intended operation and permissions
ContextSign uses the Outlook ReadWriteItem permission
to evaluate limited compose context and write an approved signature
to the current message's Outlook signature slot. It uses Microsoft
identity to request the delegated ContextSign API scope. The
baseline add-in does not request Microsoft Graph mail-read or
mail-send permission and does not install an Exchange transport
rule.
Event-based activation depends on Microsoft 365 administrator deployment, supported Outlook clients and builds, applicable Microsoft policies, and network access. A task-pane workflow may be used where automatic activation is unavailable.
4. License restrictions
Except where applicable law expressly permits it, users may not:
- copy, modify, translate, adapt, distribute, sell, rent, lease, sublicense, or create derivative works of the add-in;
- reverse engineer, decompile, disassemble, discover source code, or circumvent technical protection or entitlement controls;
- remove or alter proprietary notices, signatures, integrity checks, tenant boundaries, or security controls;
- use the add-in with an unauthorized tenant, account, user, environment, service bureau, or competing product; or
- use the add-in unlawfully, to impersonate another person or entity, to distribute malware, or to infringe privacy, confidentiality, intellectual-property, or other rights.
5. Customer and user responsibilities
- Administrators must assign only a validated add-in package to the intended users or groups and manage required Microsoft consent.
- The customer is responsible for signature content, sender and legal data, rule configuration, release approval, and compatibility testing for its supported Outlook population.
- Users must protect their Microsoft accounts and devices, follow organization policy, and report unexpected signature behavior or suspected compromise.
- The customer must not configure another service to write the same Outlook signature slot for the same population unless an approved coexistence design prevents conflicts.
6. Updates and compatibility
Digital David may provide fixes, security changes, and new versions. An update can be required to continue using the service safely or to remain compatible with Microsoft 365. Add-in packages and hosted code must come from Digital David's approved distribution and release process. Modified or unvalidated packages are unsupported.
Microsoft controls Outlook and the Office add-in platform. Digital David does not guarantee operation on every legacy, preview, unsupported, disconnected, or policy-restricted Outlook client.
7. Data and privacy
Use of the add-in is governed by the ContextSign privacy notice and, where applicable, the customer's own privacy notice and data processing agreement. ContextSign does not upload or store message bodies, subjects, attachments, or plaintext recipient addresses. Users must not submit credentials, tokens, or production mail content through support or configuration fields.
8. Ownership
Digital David and its licensors own the add-in, service, software, documentation, trademarks, and all related intellectual-property rights. No rights are granted by implication. The customer retains rights in its approved content and data, subject to the limited processing rights needed to operate the service.
9. Third-party software and Microsoft services
The add-in may include open-source components governed by their own licenses; those licenses control if they conflict with this EULA for the relevant component. Microsoft 365, Outlook, Entra, Graph, and Microsoft Marketplace are Microsoft services governed by Microsoft's agreements. Microsoft is not a party to this EULA, does not license ContextSign, and does not sponsor or endorse the add-in.
10. Support
Support is provided by Digital David as stated in the customer's order or support agreement. Current contact and privacy-safe diagnostic instructions are available at /support. Microsoft is not responsible for ContextSign support or maintenance.
11. Suspension and termination
This license ends when the applicable entitlement or service agreement ends. Digital David may suspend or terminate the license for material breach, unauthorized use, security risk, unpaid fees, suspended entitlement, or as required by law or the Microsoft platform. On termination, the customer must stop use and remove or unassign the add-in where it controls deployment. Provisions on restrictions, ownership, disclaimers, liability, and disputes survive as applicable.
12. Warranty and liability
The warranties, remedies, disclaimers, and liability rules in the customer's applicable order and the ContextSign Terms of Service apply to the add-in. Nothing excludes mandatory liability for intent, gross negligence, injury to life, body, or health, fraudulent concealment, or liability that applicable law does not permit the parties to limit.
13. Export and sanctions compliance
The customer and users must comply with applicable export-control and sanctions laws and may not use or provide the add-in where prohibited. They represent that they are not barred from receiving the software under applicable law.
14. Governing law and general terms
German law applies without its conflict-of-law rules and without the United Nations Convention on Contracts for the International Sale of Goods. If the customer is a merchant, public-law entity, or public-law special fund, exclusive jurisdiction is Frankfurt am Main, Germany. Mandatory law remains unaffected.
The applicable order, this EULA, the Terms of Service, and referenced agreements form the entire agreement for the add-in license. If one provision is unenforceable, the rest remains effective. Failure to enforce a provision is not a waiver. Assignment is governed by the Terms of Service or applicable order.