trilinkai
لوحة التحكماحصل على مفتاح API
Draft pending legal approval. This version is a product and compliance template. Production deployment is blocked until the configured legal entity, contacts, jurisdiction and document version are approved.

Legal · draft-2026-10-21

Privacy Policy

How trilinkai processes account, billing, security, and AI usage data.

The English version controls. Localized navigation is provided for usability; legally approved translations must be attached to the same document version before they are treated as controlling.

Scope

This policy applies to the trilinkai website, console, API gateway, support channels, and related services.

Customer prompts and model responses are not stored by default. Usage metadata, token counts, model identifiers, latency, status, and fraud signals are processed to operate, secure, and bill the service.

Data we process

Account and organization data, authentication identifiers, email addresses, role and invitation records, API key metadata, billing records, support messages, audit events, device and network security data, and aggregated usage statistics.

Payment card data is handled by the configured payment provider. trilinkai stores payment method references and limited display data such as brand and last four digits.

Purposes and legal bases

We process data to provide the service, authenticate users, route model requests, enforce budgets, prevent abuse, maintain security, provide support, comply with law, and improve reliability.

Where required, processing relies on contract performance, legal obligations, legitimate interests in securing and improving the service, or consent. Consent can be withdrawn where consent is the applicable basis.

Disclosures and international transfers

Data may be disclosed to infrastructure, payment, email, observability, support, and upstream model providers strictly as needed to deliver the service, secure it, or comply with law.

International transfers require the safeguards applicable to the relevant service and region, which may include contractual safeguards and transfer mechanisms.

Retention and security

Records are retained according to operational, security, accounting, tax, dispute, and legal-hold requirements. Configured retention periods may delete or anonymize data earlier where no legal obligation requires retention.

Controls include tenant isolation, encrypted secrets, MFA, access logging, least-privilege roles, backup protection, and incident response procedures.

Your rights

Depending on your location, you may request access, correction, deletion, restriction, portability, or objection. Contact privacy@trilinkai.com.

Authorized administrators can use the console DSR and export tools. Identity verification and legal exceptions may apply.

Operator and contact

[Legal entity name must be configured], [Registered address must be configured].

Legal notices: legal@trilinkai.com.

Document version: draft-2026-10-21.