DB2Google

Licensing policy

This page summarizes the standard DB2Google commercial and licensing model for business and professional customers. A specific order or negotiated agreement may modify individual terms.

1. Licence scope

The licence is non-exclusive, non-transferable and granted to one legal entity or business operator for 12 months. A standard licence covers one production installation, one Microsoft SQL Server source and the number of target Google accounts included in the purchased plan. One internal test instance is permitted.

2. Term and renewal

The licence term is 12 months. It does not renew automatically unless agreed in writing. Renewal can be ordered before expiry at the then-current commercial terms.

3. Updates and support

An active licence includes ordinary bug fixes, compatibility updates for the supported release and email support. New integrations, data-model changes, environment migrations and custom development are outside the licence unless the quotation states otherwise.

4. Use restrictions

The customer may not resell, rent, sublicense or operate DB2Google as a service for third parties without a separate agreement, and may not remove rights notices. Restrictions on analysis, decompilation or other intervention apply only to the extent permitted by mandatory law.

5. Data and third-party accounts

The customer is responsible for having the right to access the source database, for the lawful processing of synchronized personal data, for administration of Google accounts and for its own backups. DB2Google does not acquire ownership of customer data.

6. Google and other third-party services

Functions depending on Google APIs, Microsoft SQL Server or other third-party services may be affected by their changes, limits or outages. During an active licence, reasonable compatibility updates are provided for the supported DB2Google release.

7. Responsibility and acceptance

The specific functional scope, environment and acceptance criteria should be stated in the quotation or order. The customer must perform a verification run before production use. Any liability limitations are defined in the binding contract documents within the limits of applicable law.

8. Contract documents

This public policy is an informational summary. If there is a conflict, an accepted quotation, order or separate licence agreement prevails. Final contract wording should be reviewed for the specific transaction.

Updated: 8 August 2026.