Commercial Rule
Scope is defined in writing.
Projects, milestones, deliverables, timings and payment terms are governed by the proposal or statement of work tied to the engagement.
Terms of Service
The commercial rules behind our AI, data engineering and analytics work.
These terms summarize the operating rules for Deepthena services across AI strategy, data science, machine learning, analytics, business intelligence and data engineering. Last updated: April 3, 2026.
They are intended to keep delivery assumptions, commercial boundaries, responsibilities and communication channels readable before work scales.
Delivery Rule
Access and approvals must be available.
Client-side access, stakeholder availability and source information are necessary for Deepthena to deliver work to plan.
Ownership Rule
Existing Deepthena methods remain ours.
Unless otherwise agreed, frameworks, accelerators, reusable templates and internal methods stay with Deepthena.
Core Terms
The terms track how AI and data engagements actually run.
The clauses below are framed around the most common delivery realities: scope definition, access, intellectual property, confidentiality, data handling and liability boundaries.
Scope
Deepthena provides advisory and implementation support across AI, analytics and data engineering engagements.
Specific scope, timing, fees, deliverables and responsibilities are defined in project proposals, statements of work or order forms.
Client Responsibilities
Access, stakeholder input and lawful source information must be available.
Clients are responsible for providing access to systems, source data, approvals and internal coordination needed for delivery to move cleanly.
Intellectual Property
Pre-existing Deepthena methods, accelerators, templates and frameworks remain ours unless agreed otherwise.
This protects reusable operating frameworks while allowing project-specific scope to be governed in writing.
Confidentiality
Each party must protect confidential information disclosed during the engagement.
Confidential information should be used only for permitted delivery or business purposes tied to the engagement.
Data Protection
Where personal data is involved, both parties carry obligations.
Each party remains responsible for meeting the privacy and data protection duties that apply to its role in the engagement.
Liability
Services are provided with reasonable skill and care, subject to agreed limits or exclusions.
Commercial liability boundaries should be read together with the governing proposal or statement of work.
Dependencies
Third-party tools and data remain subject to their own terms.
Where delivery relies on client systems, vendors or cloud tools, their availability and contractual position can affect execution.
Change Control
Scope shifts should be documented before work expands.
If business priorities, data access, timelines or deliverables change, both parties should confirm the revised position in writing.
Dependencies
Third-party vendors or source systems can affect execution timing.
External tools, source systems, infrastructure limits and vendor responsiveness can alter the path of an engagement.
Formal Notices
Commercial or legal questions should come through agreed channels.
Operational, commercial or legal questions can be sent to marketing@deepthena.com unless another route is defined in writing.
Updates
These terms may be revised over time.
The published version on this page reflects the current general terms unless a written engagement document states otherwise.
Commercial Summary
The engagement works best when scope, approvals and dependencies are made visible early.
That is what keeps AI, analytics, machine learning and data engineering delivery disciplined rather than reactive.
Contact
Questions about these terms can be sent to marketing@deepthena.com.
If a statement of work or proposal says something different, that written engagement document governs the project in question.