21-03-2026

General terms and practical cases

These Terms govern use of services provided by directva. The section includes practical examples and scenarios illustrating how the terms apply in everyday business software projects: onboarding a small retailer, migrating legacy systems for a mid-size company, and integrating third-party payment APIs. Each scenario clarifies obligations, deliverables, and typical timelines based on past implementations.

21-03-2026

Who may use the services

Services are available to individuals and entities able to form binding contracts under applicable law and able to comply with these Terms. We provide scenario-based eligibility checks during onboarding, such as verifying company registration for corporate accounts.

You must be at least 18 years old to use directva services or have authority as a business representative. For examples, a project lead or authorized procurement contact can represent a company account.

Services must be used lawfully and consistently with the intended business purposes. Case examples of prohibited use include attempts to deploy models that evade legal compliance or deploy tracking beyond disclosed consent mechanisms.

Access to directva services may be restricted by local law or export rules. Practical onboarding includes a country review to identify regulatory constraints relevant to the customer location and the software use case.

Account responsibilities

Account holders are responsible for maintaining accurate account information and for activities occurring under their accounts. We include sample account setup checklists to reduce common onboarding errors.

Provide current, complete, and accurate information during registration and whenever information changes. Case-driven reviews during implementation help detect and correct inconsistencies.

Keep account credentials confidential and follow recommended security practices (strong passwords, multi-factor authentication). We provide implementation scenarios that illustrate secure deployment patterns for small teams.

Accounts are non-transferable except where explicitly agreed in writing. For corporate reorganizations, see our documented procedural scenario for transferring service rights under supervision.

If you suspect unauthorized access, notify us immediately via +66965744983 or the contact form. We will follow incident response procedures and document remediation steps, including case notes on detection and containment.

We may suspend access for suspected breaches, non-payment, or legal reasons. Suspension procedures include notification and a remediation timeline tailored to the incident scenario.

Service scope and practical use cases

directva provides business software development, integration, and support services. Details and deliverables are specified in project contracts; example engagements include prototype development for a logistics SME and a phased rollout for a retail POS integration.

We may modify features or offerings; material changes will be communicated in advance with an explanation and transitional options based on typical deployment scenarios.

We strive for high availability but planned maintenance and outages may occur. For example, scheduled updates for a production client are coordinated during agreed maintenance windows to minimize business impact.

User rules and acceptable use

When using directva services, follow these rules designed around practical enforcement and real-world examples.

  • Do not attempt to reverse-engineer, exploit, or bypass security controls; a case study of audit findings is used to teach compliance.
  • Do not upload or process illegal content; our intake checks flag suspect content for review under documented scenarios.
  • Respect intellectual property rights of third parties; contractual workflows include IP clearance steps for integrations.
  • Do not use services to send unsolicited bulk communications; project templates show lawful communication patterns.
  • Comply with applicable export and import controls; we provide guidance scenarios for cross-border deployments.
  • Operate accounts with valid identification and authorization; onboarding templates give examples of required documents for companies.
  • Cooperate with contribute of suspected misuse; real-world incident response procedures are applied and documented.

User content and business data

User content includes code, configuration, and business data uploaded to directva services. We provide examples showing content types and recommended handling practices.

You retain ownership of your user content. For collaborative projects, contracts detail ownership and rights assignments with concrete examples from prior projects.

By submitting content you grant directva a limited license to operate, display, and process the content to provide the service, troubleshoot, and perform analytics related to service improvement, as described in sample project scopes.

You are responsible for content legality and for maintaining backups. Practical onboarding includes a data retention and backup scenario tailored to small-to-medium deployments.

We may remove content that violates these Terms or applicable law following documented review procedures; removal steps include notification and appeal paths used in past cases.

Intellectual property

directva and its licensors own pre-existing intellectual property used to deliver services. Project-specific deliverables and custom code ownership are addressed in each engagement agreement, with example clauses showing common approaches.

  • Do not copy or redistribute proprietary platform code except as licensed in writing.
  • Do not claim ownership of directva activity or branding in your materials.
  • Respect third-party license terms for integrated components; example component inventories are provided for transparency.

Paid services and billing

Paid offerings include fixed-price projects, subscriptions, and support retainers. Each engagement includes an invoice, scope, milestones, and example payment schedules.

Pricing is set in the applicable order form. Example pricing scenarios and milestone breakdowns are provided during proposals to illustrate cost drivers and delivery phases.

Payments are due as specified in invoices. We accept the methods listed in the project agreement. For recurring payments, clients receive advance notices and example invoice timelines.

Subscription services auto-renew unless canceled per the cancellation procedure. Practical case examples outline renewal timing and migration options for service changes.

Refunds are considered on a case-by-case basis in line with the service contract and documented examples of dispute resolution; standard refunds are limited to fees for undelivered contractual items as demonstrated in comparable case scenarios.

Clients may cancel per contractual terms; cancellation procedures include handover scenarios and data export steps to minimize disruption.

Clients are responsible for taxes applicable in their jurisdiction. Invoices will indicate any taxes collected in Thailand when required by law.

We may update pricing with notice; example migration scenarios are provided to help clients adapt to price changes with minimal operational impact.

Non-payment may result in suspension or termination after notice and a brief remediation period; case examples explain typical recovery workflows used in prior projects.

Disclaimer

Information and services are provided 'as is' to support business decision-making and project execution. We document example outcomes based on past projects, but actual results depend on many variables, including client inputs and environment. Use the provided case studies to assess applicability rather than relying on predictions.

Limitation of liability

To the maximum extent permitted by law, our liability for direct damages arising from services is limited to amounts paid for the relevant services during the prior 12 months. This limitation is illustrated with practical scenarios showing typical risk allocations in client agreements.

Third-party services and integrations

We may integrate third-party components. Integration scenarios include a description of data flows, responsibilities, and testing checklists. Clients are encouraged to review third-party terms before enabling integrations.

Termination

Either party may terminate in accordance with the contract. Termination scenarios include wind-down plans, data export windows, and transitional support where agreed.

On termination, access to services will end and we will follow the documented data retention and export process. Example timelines for data export and archival are provided during offboarding.

Privacy and data protection

Our privacy practices are described in the Privacy Policy available at directva.club/privacy. We include case-driven guidance for data minimization, retention, and secure transfer tailored to business projects in Thailand.

Notifications and communications

We communicate by email, in-product notifications, and phone. Critical notices related to service changes or security incidents may be sent to the account contact and, where appropriate, posted on directva.club. For urgent matters call +66965744983.

Changes to these Terms

We may update these Terms; material changes will be announced with reasonable notice and examples illustrating the impact. The current effective date is 21-03-2026.

Governing law

These Terms are governed by the laws of Thailand. Practical dispute resolution examples reflect local procedures commonly used in Si Sa Ket Province.

Dispute resolution

We aim to resolve disputes amicably by negotiation and mediation. If unresolved, disputes may be referred to courts in Si Sa Ket, Thailand. Case-based escalation procedures are provided to clients during onboarding.

Contact for terms and legal notices

+66965744983
350, Thanon Kasikam, Mueang Nuea Sub District, Amphoe Mueang Si Sa Ket District, Si Sa Ket Province 33000, Thailand