Definitions
To help readers understand this policy in practical terms, we define key terms used across project scenarios and case studies. These definitions explain what we mean by personal data, processing activities during model development, the user roles typically involved, and supporting services such as analytics and cloud hosting.
- Personal data refers to any information that can identify an individual directly or indirectly, such as names, business contact details, identifiers, and project-related contact information provided during engagement or support requests.
- Processing means any operation performed on personal data for project delivery: collection, organization, storage, adaptation, analysis, model training (when applicable), testing, and deletion according to defined retention policies and contractual obligations.
- User denotes an individual or business contact who interacts with leaditne services—this includes project owners, technical contacts, end users of deployed solutions, and support personnel involved in case-specific scenarios.
- Service refers to AI software development, integration services, consulting workshops, model deployment, monitoring, and ongoing operational support provided by leaditne for business customers.
- Cookies and similar technologies include small data files set in browsers or device storage to support sessions, analytics, performance monitoring, and feature toggles during product trials and demonstrations.
Data We Collect
We collect data necessary to deliver and improve services. To make this tangible, the following lists map typical data items to common scenarios such as onboarding a pilot, executing data labeling tasks, and operating a production model.
Data You Provide
Data provided directly by clients and users during engagement, project setup, support, or procurement processes.
- Contact details: names, business email addresses, phone numbers used for project coordination and support.
- Project data: sample datasets, annotated examples, business rules, and configuration files required to build and validate models.
- Account and billing information necessary to manage contracts, invoices, and payment processing (excluding raw payment card data which is handled by third-party payment processors).
- Communications: messages, feedback, and support requests submitted via email, forms, or collaboration platforms during project execution.
- Case-specific inputs: user stories, acceptance criteria, test cases, and performance targets provided for scoping and validation.
- Consent and preferences: explicit choices about marketing contacts, analytics opt-in, and demo data sharing permissions.
Automatically Collected Data
When interacting with our website, development portals, or deployed solutions, certain technical and usage data are collected to support operations, security, and product improvement in real use cases.
- Technical data: IP address, device type, browser version, and operating system for troubleshooting and security incident analysis.
- Usage metrics: feature usage, uptime, error reports, and API call logs used in case studies of system behavior and performance tuning.
- Session data: timestamps, session identifiers, and navigation paths used to reproduce issues and improve documentation.
- Performance telemetry: aggregated model latency, throughput, and error rates collected to inform operational adjustments.
- Location data: coarse location inferred from IP for compliance and routing in multi-region deployments.
- Cookie identifiers and similar vouchers used to maintain sessions and preferences during trials and demos.
Third-Party Data Sources
We integrate with third-party services for payments, hosting, analytics, and specialized tooling. Below are examples of common categories of third-party data sharing that occur in typical project scenarios.
- Cloud infrastructure providers that host project environments and store backups (service metadata and encrypted data containers).
- Analytics and monitoring providers that process aggregated telemetry and performance metrics to support operational dashboards.
- Payment service providers that handle invoicing and payments; raw card details are not stored by leaditne.
How We Use Data
We process personal data to fulfill contractual obligations, support project delivery, comply with legal requirements, and improve our services through aggregated operational insights. The items below map practical purposes to real-world project activities and case examples.
- Project delivery and operations: using contact and project data to build, test, deploy, and maintain AI solutions for clients in scenario-based engagements.
- Billing and contract management: processing invoices, payment records, and contract communications required for commercial agreements.
- Security and fraud prevention: using logs and telemetry to detect misuse, secure environments, and respond to incidents during development or production.
- Product improvement: analyzing aggregated, anonymized usage patterns and performance data to refine models and deployment procedures without identifying individuals.
- Support and communications: responding to support requests, scheduling workshops, and documenting lessons learned in practical case studies.
- Legal compliance: retaining records and sharing information where required by law or to establish, exercise, or defend legal claims.
- Research and internal training: using de-identified datasets from completed projects to train internal tooling and improve developer workflows in controlled environments.
- Marketing and events: contacting consenting individuals about relevant workshops, case-study webinars, or product updates related to AI integration projects.
Legal Basis for Processing
Depending on the data and the activity, we rely on one or more legal bases for processing. The following items explain common bases mapped to project activities and client scenarios.
- Performance of a contract: processing required to deliver services agreed in project contracts and statements of work.
- Consent: where individuals have given explicit consent for marketing, demos, or optional analytics during trials.
- Legitimate interests: for operational security, fraud detection, and service improvement when balanced against individual rights and expectations.
- Legal obligation: when retention or disclosure is necessary to comply with applicable laws or regulatory requirements.
Rights Under Applicable Law
Where applicable, we recognize the rights of individuals under data protection laws. Below are typical rights and how they apply in service-delivery contexts and case examples.
- Access: request a copy of personal data processed in relation to a project or account.
- Rectification: correct inaccurate or incomplete data used in project delivery or communications.
- Erasure: request deletion of personal data subject to contractual, legal, or operational constraints described in our retention policy.
- Restriction of processing: request limitations on certain processing activities, such as marketing or profiling for specific use cases.
- Portability: where technically feasible, receive structured data provided to us related to an account or project.
- Objection: object to processing based on legitimate interests in specific scenarios; we will review case-by-case and document the outcome.
Cookies and Similar Technologies
Cookies and similar technologies support core website functionality, analytics, and personalization. We use these technologies in demos, trial portals, and documentation sites to ensure consistent experiences during practical workshops and pilot deployments.
Types include session cookies, persistent cookies, local storage vouchers, and third-party analytics identifiers used to record usage patterns and maintain sessions for demos and admin consoles.
Typical categories: strictly necessary (session management), performance (analytics and uptime), functional (preferences), and targeting (optional advertising or third-party integrations with consent).
Users can manage cookie preferences through browser settings and any opt-in controls presented during trial or demo sign-up. We provide a Cookie Policy link for detailed controls and descriptions.
View Cookie Policy
Data Sharing and Disclosure
We share data only as necessary for project execution, hosting, analytics, legal compliance, or with explicit consent. The following items list common recipients and practical reasons in case-based terms.
- Service providers: cloud hosts, DevOps vendors, and monitoring services engaged to host environments or provide operational tooling.
- Professional advisors: legal, accounting, and compliance advisors engaged for contract or regulatory matters.
- Subcontractors and partners: third-party vendors performing specific development, testing, or labeling tasks under nondisclosure agreements.
- Analytics providers: third-party analytics used to aggregate performance metrics for operational dashboards.
- Legal and regulatory authorities: when disclosure is required by law or to respond to lawful requests.
- Acquirers or affiliates: in the event of a reorganization, merger, or sale, with appropriate safeguards to protect personal data.
International Transfers
leaditne is based in Thailand and may transfer data to service providers and partners in other jurisdictions to deliver services, host environments, and support operations. Transfers are managed in line with applicable law and with contractual or technical safeguards appropriate to the transfer scenario.
Safeguards include data encryption in transit and at rest, standard contractual clauses where applicable, careful vendor selection, and documented access controls to minimize exposure during cross-border processing.
Data Retention
Retention periods depend on the type of data and the purpose for which it was collected. Below are typical retention practices tied to concrete activities and case study timelines.
Account and contract records are retained for the duration of the engagement plus a defined post-engagement period required for compliance and record-keeping. Typical post-engagement retention aligns with contractual terms and legal requirements.
Support and project communications are retained to preserve project history, reproduce incidents, and document lessons learned. Retention periods are set to balance operational needs and data minimization principles.
Operational logs and telemetry are retained for periods needed to contribute incidents and analyze trends; aggregated metrics used for long-term improvement are retained in anonymized form.
When retention periods expire or upon valid deletion requests where no legal or contractual reason to retain data exists, personal data is removed from active systems and archived data is scheduled for secure deletion according to our deletion procedures.
Security Measures
leaditne applies technical and organizational measures tailored to project scenarios to protect data processed during model development and production. Security is applied in layers: access management, infrastructure hardening, encryption, monitoring, and incident response. Practical measures are documented in runbooks used during engagements and demonstrated in post-project reviews.
- Encryption in transit and at rest for project data and backups.
- Role-based access control and least privilege for engineering and operations teams.
- Regular audits, logging, and incident response procedures aligned to case-study lessons and operational playbooks.
User Rights and Requests
To exercise rights or raise privacy-related questions, contact us at [email protected] or by phone at +66927076411. Our office is located at Thanon Ratchadaphisek, Bangkok District, Bangkok 10800, Thailand. Requests will be handled according to applicable law, documented case workflows, and practical review procedures.
- Access: You can request a copy of personal data we hold about you and obtain details about how we process it, illustrated with examples from past AI integration projects such as data sets used for model training and logs of decision-support outputs.
- Correction: If personal information is inaccurate or incomplete, request correction. For instance, in a client dashboard migration case we resolved mismatched user identifiers within 5 business days when notified.
- Deletion: You may request deletion of personal data where retention is no longer necessary. We describe the practical steps and timelines based on previous SaaS decommissioning scenarios and data retention policies.
- Restriction: You can ask us to limit processing while we verify a dispute about accuracy or lawfulness; we document how this affected model retraining schedules in an example management automation deployment.
- Portability: Where feasible, you may request your data in a structured, commonly used format. We provide examples from client transitions where user transaction logs were exported to CSV and JSON for continuity.
- Objection: You can object to processing for direct marketing or profiling in specific contexts. We explain the operational changes, referencing a retail personalization case where profiling was paused upon objection and alternate segmentation used.
- Automated decision review: If an automated decision materially affects you, request human review. We outline a scenario from a claims-triage workflow where appeals triggered manual review and documented outcomes.
- Complaint: You can lodge a complaint with relevant authorities or contact our privacy officer. We describe complaint-handling steps used in prior projects and timelines for acknowledgement and resolution.
How to exercise your privacy rights
To exercise any of the rights above, submit a request specifying the right you wish to exercise, the data or systems concerned, and any supporting context such as project name or account identifier. We use a documented intake workflow to route requests to the appropriate technical and legal teams and provide a confirmation of receipt with a case reference. For practical clarity, we include examples of accepted request formats and the minimum information needed to validate identity for each scenario.
[email protected]
We aim to acknowledge requests within 5 business days and complete standard requests within 30 calendar days. Complex requests that require coordination across partners or deep technical contribute may take longer; in those cases we will notify you of expected timelines and provide interim status updates based on our past handling of multi-vendor AI integrations.
Marketing communications and choices
We may send operational announcements, product updates, and offers related to AI services and case-study events. Communications are based on prior interactions, service subscriptions, and event attendance. Marketing content is separated from service-critical messages to avoid interference with operational alerts; for example, clients in an active model deployment continue to receive system notifications regardless of marketing preferences.
You can opt out of marketing messages anytime via the unsubscribe link in emails or by contacting [email protected]. Opting out of marketing will not impact service messages or contractual communications necessary for ongoing projects.
Children and minors
Our services and offerings are intended for business and adult professional use. We do not knowingly collect personal data from children under 18. If you believe we have inadvertently collected data concerning a minor, contact us with the relevant details and we will take steps to contribute and remediate using procedures similar to those employed in previous client data corrections.
Third-party links and integrations
Our websites and solutions may include links to third-party services, APIs, or marketplaces used in AI pipelines (for example, cloud providers or analytics vendors). These links lead to external privacy practices and are governed by the third parties' policies. In client engagements we document vendor relationships and data flow maps so clients can evaluate third-party processing risks.
Policy updates and change notifications
We update privacy practices as technologies and regulatory requirements evolve. Material changes that affect how we process personal data for clients will be communicated by email and posted on our site with the effective date and a summary of key changes. For example, several updates in 2026 clarified logging retention and model auditability procedures following operational reviews.