Eligibility and permitted use
Use of leaditne services requires a lawful purpose and compliance with these Terms. Clients must be capable of entering into binding agreements under applicable law. In practice, our project intake checks verify legal authority to engage, especially for data-sensitive AI initiatives.
Users must be at least 18 years old or otherwise able to contract under local law. Corporate users should ensure authorized representatives sign agreements for project engagement.
Services must not be used for unlawful purposes, to produce disallowed content, or to circumvent applicable regulations. We provide examples of acceptable use cases, such as operational efficiency improvements and customer support automation, and disallowed uses, like automated decisioning in restricted regulated contexts without appropriate oversight.
Services are offered from Thailand and may be restricted in certain jurisdictions. Clients are responsible for ensuring export controls, data transfer rules, and local regulations are respected for each deployment scenario.
Accounts and access
Clients may receive accounts, API keys, or access credentials for service administration and model management. Account privileges are provisioned based on project role and documented in onboarding materials tied to real-world case roles such as data engineer, product owner, and compliance officer.
You must provide accurate information when creating accounts and keep it up to date. In prior migrations we resolved billing or access issues by verifying and updating account metadata to ensure continuity of automated pipelines.
Maintain the confidentiality of credentials and follow recommended security practices (multi-factor authentication, role-based access control). We apply incident response playbooks from earlier client incidents to mitigate unauthorized access swiftly.
Accounts and credentials are non-transferable except by written agreement. Transfers in enterprise acquisitions are handled through an agreed migration plan.
Notify leaditne immediately if you suspect compromise of credentials. We run a documented containment-and-remediation workflow, as applied in a past integration where compromised API keys were rotated and affected models were quarantined.
We may suspend accounts for security reasons, suspected abuse, or nonpayment. Suspension procedures mirror those used in prior customer support cases and include notice and an opportunity to remedy where feasible.
Services provided
leaditne delivers software development, AI model design, data pipeline integration, deployment support, and consulting. Services are scoped per statement of work and may include pilot phases, data readiness assessments, model training, validation, and integration into client workflows.
Service features, APIs, or infrastructure may change. We document changes in release notes and consult with active clients on migrations for critical integrations, based on scenarios from previous platform upgrades.
We strive for high availability but cannot promise uninterrupted service. Service level objectives for mission-critical engagements are specified in contracts and tied to practical mitigation plans such as failover pipelines used in production AI deployments.
User conduct and rules
When using leaditne services you must follow rules designed to protect systems, data, and other users. These are framed in the context of real-world project scenarios to clarify expectations.
- Do not submit data you are not authorized to process; verify data rights before onboarding datasets.
- Do not attempt to exploit or circumvent security controls; report vulnerabilities via our disclosure process.
- Do not use services to produce content that violates law or third-party rights; include compliance checks in automated pipelines.
- Follow rate limits and resource usage policies; architectural guidelines and quota diagrams are provided during onboarding.
- Label and handle personal and sensitive data according to provided classification guidance in integration playbooks.
- Collaborate transparently with leaditne during audits and troubleshooting; provide necessary logs and access for issue resolution.
- Respect contractual restrictions on reverse engineering or redistributing proprietary components unless explicitly permitted in writing.
User content and data
User content includes datasets, prompts, model configurations, and other inputs you supply to leaditne. We treat such content as the primary material for development and deployment workstreams.
You retain ownership of your input data and derived outputs unless otherwise agreed in writing. In practice, client agreements specify ownership of custom models and IP produced during engagements.
By providing content, you grant leaditne a limited license to process, store, and use it to deliver services, perform quality assurance, and maintain operational continuity. This license is scoped to project needs and is documented in statements of work.
You are responsible for ensuring that content you provide does not infringe third-party rights and complies with applicable laws. We use intake checklists and example validations used in prior projects to reduce risk.
You may request removal of non-essential copies of your content from our development environments following project completion; retention for backup or compliance purposes will be communicated at project closeout.
Paid services and fees
Paid engagements are governed by separate proposals and statements of work which specify deliverables, milestones, and payment schedules. Examples of pricing models include fixed-price pilots, time-and-materials development, and subscription-based managed services.
Pricing for services depends on scope, complexity, and resource requirements. We provide sample pricing scenarios for common AI projects such as proof-of-concept, MVP, and full production deployment to help clients plan budgets.
Invoices are issued per the contract schedule. Accepted payment methods and billing details are specified in the statement of work; late payments may result in temporary suspension of non-critical services following standard industry practices.
Subscription offerings for managed services include documented service tiers and renewal terms. Clients receive operational reports and scheduled review sessions included in tier descriptions.
Refunds are handled in accordance with contractual terms and specific project milestones. For example, pilot fees tied to defined deliverables may be refundable pro rata under predefined conditions.
Cancellation terms are set out in each agreement and typically include notice periods, wind-down activities, and responsibilities for data handover and secure deletion.
Clients are responsible for taxes applicable to payments under local law. Fees quoted may exclude taxes unless stated otherwise.
Price adjustments for ongoing subscriptions are communicated in advance with rationale and a transition period, mirroring our approach in prior multi-year engagements.
Failure to pay may lead to service suspension or termination after notices and opportunity to cure, aligned with remediation practices used in enterprise relationships.
Disclaimer
Services are provided to assist clients with AI strategy, development, and integration. Outcomes depend on data quality, client cooperation, and changing technological factors. Statements of work include measurable acceptance criteria and testing scenarios; results in past projects are illustrative and not promises of identical outcomes.
Limitation of liability
Except where prohibited by law, liability for direct damages arising from our services is limited to amounts paid under the relevant contract during the prior 12 months. This limitation reflects the commercial allocation of risk and is consistent with industry practice; it does not affect statutory rights that cannot be limited.
Third-party services and integrations
We may integrate third-party services (cloud providers, analytics platforms, external APIs). Clients must review and accept those third-party terms. In prior integrations we provided vendor risk assessments and data flow diagrams to clarify responsibilities across parties.
Termination
Either party may terminate per the agreement terms. For convenience terminations, notice periods and wind-down obligations apply. In practice, termination checklists include handover of models, export of datasets, and revocation of access credentials to ensure orderly transition.
After termination, we will cease providing active services, secure data according to agreed retention, and assist with transfer of project artifacts. Outstanding fees remain payable. We document post-termination steps used in previous client separations to reduce operational disruption.
Privacy and data protection
We process personal data as described in our Privacy Policy. For client projects involving data transfers or sensitive information, we agree specific safeguards, encryption standards, and audit procedures tailored to the engagement.
Communications and notices
Notices under these Terms should be sent to the contact addresses in the agreement or to [email protected]. Operational communications use project communication channels documented in onboarding materials.
Changes to terms
We may update these Terms for legal, regulatory, or operational reasons. Material changes affecting clients will be communicated in advance and, for active contracts, managed through bilateral amendment processes.
Governing law
These Terms are governed by the laws specified in the client agreement. For services delivered from Thailand, Thai law will typically apply unless otherwise agreed. Dispute resolution procedures are set out in the agreement and informed by practical dispute-handling experience.
Dispute resolution
Parties agree to good-faith negotiation to resolve disputes, escalating to mediation where appropriate before litigation. Our contracts typically include stepwise dispute resolution clauses used in prior cross-border engagements.