Cooper Group
Database software terms

Terms and Conditions

Clear terms build strong partnerships. These conditions govern your use of Cooper Group database management software, DBeaver integration services, and consulting engagements.

Last updated: February 21, 2025. By using this website or engaging our services, you accept these terms.

Working terms

What's covered

The applicable order, statement of work, or subscription schedule adds project-specific details. These core rules apply when that document is silent.

Software licensing
Cooper Group grants the client a limited, non-exclusive right to use the licensed software for its internal operations during the paid term. The client may not resell, sublicense, copy, or attempt to derive source code from the software. Configuration work and reports belong to the party named in the applicable project document; pre-existing tools and methods remain with their original owner.
Consulting services
A statement of work sets the database platforms, DBeaver integration tasks, deliverables, milestones, and client contacts. Requests that change the agreed scope require a written change order before work begins. Cooper Group may pause a milestone when required access, credentials, sample data, or decisions are missing.
Payment and taxes
Invoices are due within 30 days unless the order states another schedule. Past-due balances may accrue a service charge of 1.5% per month or the highest lawful rate, whichever is lower. The client is responsible for applicable sales, use, and similar taxes, excluding taxes on Cooper Group's income.
Support and service levels
Standard support is available Monday through Friday, 8:00 AM to 6:00 PM Central Time, excluding U.S. holidays. Critical incidents may receive after-hours handling when that option appears in the service schedule. Response targets, maintenance windows, and escalation contacts are listed below.
Warranties and responsibility
Cooper Group performs services with reasonable care and skill and will correct a material failure to meet the agreed specification when reported promptly. The client remains responsible for backups, lawful data collection, account security, and decisions made from reports or visualizations. No warranty covers interruptions caused by third-party systems, unsupported configurations, or events outside reasonable control.
Liability and indemnification
To the extent permitted by law, neither party is liable for indirect, incidental, special, or consequential losses. Cooper Group's total liability for a claim is limited to the fees paid for the affected service during the 12 months before the event. Each party will address third-party claims caused by its own breach, negligence, or unlawful conduct.
Termination and data retrieval
Either party may end a subscription or statement of work for a material breach that remains uncured for 30 days after written notice. At termination, access ends and outstanding fees become due. Upon request made within 30 days, Cooper Group will return client data in an agreed machine-readable format, subject to the project charges and applicable retention duties.
Governing law
These terms are governed by the laws of the State of Wisconsin, without regard to conflict-of-law rules. The parties consent to the state and federal courts serving Madison, Wisconsin for disputes that cannot be resolved through good-faith discussion.

Service agreement Madison

Our commitment to you

Targets begin when a complete support request reaches the designated support channel. Resolution depends on access, vendor response, and the client actions described in the service schedule.

Central Time
Support response targets by incident severity
Severity Example Initial response Target update Escalation
Critical Production database unavailable 1 business hour Every 2 hours Senior engineer on request
High Major function impaired 4 business hours Daily Service lead after 1 business day
Normal Question or limited defect 1 business day Every 2 business days Account contact after 3 business days

Clients must provide a useful error description, relevant logs, a safe access path, and a contact who can test proposed changes. Planned maintenance is scheduled with reasonable notice.