Terms of Service

1. A written agreement comes first

These terms outline the basis for discussing a professional-services engagement with AskBacklogAI. Sending an enquiry or browsing this website does not create a paid engagement.

Before work begins, the parties should agree in writing on the contracting entities, scope, deliverables, responsibilities, fees, and schedule. An executed services agreement, statement of work, and any applicable data-processing agreement take precedence over this website overview.

2. Scope and changes

The agreed scope identifies the consulting, configuration, development, integration, migration, or support work to be performed, along with assumptions and dependencies.

Changes to requirements, deliverables, staffing, or timelines should be discussed and documented. Additional work and any resulting fee or schedule changes require agreement before that work proceeds.

3. Client responsibilities

Clients are responsible for providing accurate requirements, timely decisions, authorized access, suitable test environments, and the licenses needed for the project.

Clients must have permission to provide any data, software, or materials shared for the engagement. Access and data should be limited to what the work requires.

4. Fees, invoices, and expenses

Pricing, payment milestones, invoice due dates, taxes, and any approved expenses are set out in the applicable written agreement. The website does not establish a standard fee or payment schedule.

Questions about invoices or changes to a commercial arrangement should be raised with the engagement contact. Cancellation charges and refund eligibility, if any, depend on the written agreement and applicable law.

5. Delivery, testing, and acceptance

The delivery plan should define review points, testing responsibilities, acceptance criteria, and the process for reporting issues. Timelines depend on the agreed scope and the availability of required information, access, and approvals.

Release authorization, backups, and go-live responsibilities should be agreed before production changes. Post-launch support and ongoing maintenance are included only to the extent specified in the engagement.

6. Confidentiality, data, and AI tools

The parties should document confidentiality obligations and any processing of personal data before sharing sensitive project material. Client data must be handled within the agreed purposes, permissions, and security arrangements.

Use of AI or other development tools on client work must follow the engagement’s confidentiality and data-handling requirements. Senior engineers remain responsible for reviewing code and making final architectural and implementation decisions.

7. Ownership and third-party products

Ownership and permitted use of deliverables, pre-existing materials, reusable components, and documentation are defined in the written agreement. No transfer of intellectual-property rights is implied by this website.

Salesforce and other third-party products are subject to their own licenses, terms, availability, and platform limits. Any required subscriptions or vendor fees should be identified in the engagement.

8. Ending an engagement and resolving concerns

Notice periods, termination rights, outstanding fees, and handover or data-return arrangements are governed by the written agreement and applicable law.

Raise delivery or commercial concerns with your engagement contact so they can be discussed promptly. Governing law, dispute procedures, warranties, and liability provisions should be agreed in the client contract; this overview does not create a new liability cap, mandatory arbitration term, or waiver of statutory rights.

9. Changes to this overview

We may revise this page to describe our service arrangements more clearly. A website update does not automatically amend an existing signed agreement.