Skip to content

Data processing agreement (DPA)

Current version: 2026-10-07. See the legal documents for how changes are announced.

1 · Purpose and roles

1.1. This agreement governs the processing of the data that the Customer writes into or sends to the Tarno Service. For those data, the Customer is the controller and the owner of the service, identified in the contract or service order ("the Provider"), is the processor: it processes them only to provide the Service and in accordance with the Customer's instructions, which are these documents, its contract and the use the Customer makes of the API and the MCP.

1.2. It does not cover the personal data in the corpus (what INAPI publishes), which the Provider processes on its own account in accordance with the personal data policy.

1.3. This agreement forms part of the terms of service and of the Customer's contract.

2 · What Customer data are processed

data for what where it is stored
Organization (name that identifies it) and users (email and display name, as contact) onboarding, contact, blocking the Service's database
Access keys: only their SHA-256 fingerprint and a prefix, plus their permissions, quota and expiration authentication the Service's database
Watchlists: list name, watched trademarks or texts and their classes, filters, webhook URL, signing secret watching and notifying the Service's database
Watch notices: the corpus trademark that matched, its similarity and a snapshot of its public data delivering the notices the Service's database
Logo image sent to analyze_logo describing it not stored or logged: it is sent to the model and only its SHA-256 fingerprint is returned
Access line per request: internal identifier of the key and the organization, route or tool (without parameters or arguments), result and latency operations and diagnostics technical logs, 15 days
Usage counters (monthly quota, burst, per-IP limit) enforcing the limits the Service's memory
Operator actions on the organization, its users and its keys audit the Service's database

2.1. The access line does not record the key, the IP address, the query parameters, the arguments of a tool or the body of the request.

2.2. A webhook's signing secret is delivered only once when the list is created; it is never returned in a read or logged.

2.3. The queries the Customer makes (which trademarks it searches for) are not stored beyond the access line described and are not sent to any third party: semantic search is computed on the Service's own infrastructure.

3 · Obligations of the Provider

3.1. To process the Customer's data only to provide the Service; not to use them for its own purposes or disclose them to third parties except to the declared sub-processors or under a legal obligation.

3.2. Isolation by organization. Each operation resolves the organization from the key, never from what the request says; one organization cannot read or modify another's data.

3.3. To require confidentiality from the persons authorized to access the data, who are only those who operate the Service.

3.4. To apply the security measures of § 6 and to assist the Customer, insofar as it depends on the Service, in responding to requests from data subjects.

4 · Sub-processors

4.1. The Customer gives general authorization to the sub-processors in the list of sub-processors.

4.2. Before engaging a new sub-processor that receives Customer data, the Provider updates the list and notifies the Customer's technical contact. A Customer that objects may terminate in accordance with its contract.

4.3. Logo analysis. The only sub-processor that receives content provided by the Customer for processing is the provider of the language model, and only if the Customer has the logo:analyze permission, which is not granted by default. A Customer that does not want that transfer does not contract it, or requests its removal.

5 · International transfers

The Customer's data are hosted outside Chile: the main infrastructure in Europe and some sub-processors in their providers' regions. The Provider only uses sub-processors that offer contractual data protection guarantees.

6 · Security measures

  • Keys of 256 bits; only their fingerprint is stored; immediate revocation and blocking.
  • Permissions by scope, monthly quota, burst limit per key and per-IP limit; each report with its own permission.
  • Isolation by organization in everything that is written.
  • Encryption in transit: TLS on all API and MCP domains.
  • Encrypted backups (AES-256) with an integrity tag, in external storage; 14-day retention; restoration periodically verified and rehearsed end to end.
  • Audit of operator actions (onboarding, keys, access).
  • Deployment: images pinned by their digest; secrets outside the code; each version is deployed only if it passes the full test suite; test environment separate from production.
  • Review: periodic security reviews and scans.

7 · Security incidents

7.1. The Provider will notify the Customer, without undue delay, of any incident affecting its data, with what is known of its scope and of the measures taken, and will give it the information it needs to comply with its own notification obligations.

8 · End of the agreement

8.1. Upon termination of the contract, the Provider revokes the Customer's keys and deletes its watchlists and notices within the period set out in the contract, unless the Customer requests an export beforehand.

8.2. While the contract is in force, the Service already automatically deletes watch notices after 90 days.

8.3. Backups renew themselves within 14 days: what has been deleted disappears from them within that period. At the Customer's request, the Provider confirms the deletion in writing.

9 · Verification

The Customer may verify compliance with this agreement by asking the Provider to answer a security questionnaire, with evidence of the measures of § 6. Other forms of verification are agreed in the contract.