Skip to content

Terms of service

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

1 · Parties and purpose

1.1. These terms govern access to the Tarno service ("the Service") provided by its owner, identified in the contract or service order ("the Provider"), to the person or organization that contracts an access key ("the Customer").

1.2. These terms are governed by Chilean law. The competent courts or the arbitration are those set out in the Customer's contract.

1.3. If the Customer's contract says something different from these terms, the contract prevails.

2 · What the Service is

2.1. The Service provides read access to a corpus of the Chilean trademark register built from public sources of the National Institute of Industrial Property (INAPI): the Estado Diario, the open dataset of trademark applications and INAPI's trademark record pages. The corpus is updated every business day.

2.2. Access is provided solely through two interfaces with the same key, the same permissions and the same quota: a REST API (https://api.tarno.cl) and an MCP server (https://mcp.tarno.cl) for artificial intelligence agents. The Customer does not access the database.

2.3. The Service also includes a legal document base (INAPI guidelines and publications, laws with their versions, the Nice list, fees), single-call reports, trademark watching with notices by webhook and, if contracted, the descriptive analysis of logos by a language model (§ 4.4).

2.4. Each response states the date of the data (dataAsOf, coverageThrough). The live freshness status is published at GET /system/freshness.

3 · What the Service is not

3.1. It is not legal advice. The Service delivers data and signals (similarity, historical outcomes, applicable legal texts); it never issues verdicts on whether a trademark is registrable or whether it infringes another. The legal opinion belongs to the Customer's lawyer.

3.2. Deadlines are published with their statute and article, and with a warning (caveat) when there is a subsequent decision that may affect them. A deadline that cannot be grounded in an article is not published. The Service does not replace the Customer's own deadline control.

3.3. It is not an official source. The official register is INAPI's. The Service may contain errors or omissions arising from the source or from the loading process; known defects are documented and corrected.

3.4. The Service does not file proceedings before INAPI, does not send emails to end users (watching notifies by webhook or by query) and does not offer image similarity search (the operation exists and responds "not available").

3.5. Liability. The Customer decides with its own professional judgment; the Provider is not liable for the decisions that the Customer or its clients make based on the data or signals of the Service. The Provider's liability is limited to what is set out in the Customer's contract, except in cases where the law does not allow it to be limited.

4 · Key, permissions and quota

4.1. Key. Access is authenticated with a key in the X-API-Key header. The key has 256 bits of entropy; the Provider only stores its fingerprint (SHA-256) and a prefix to recognize it, never the key in clear text. Revocation and blocking take effect on the next request. A key may have an expiration date and can be rotated without losing the quota.

4.2. The Customer safeguards its key, does not share it outside its organization and notifies the Provider without delay if it suspects the key has been leaked. Requests made with its key are attributed to it.

4.3. Permissions. Each key has a set of permissions (see Authentication and scopes). Write permissions (watch:write), reports (reports:*), the legal base (legal:*) and logo analysis (logo:*) are only granted expressly. Each report has its own permission and can be contracted separately.

4.4. Logo analysis. The logo:analyze permission sends the image provided by the Customer to the provider of the language model (see sub-processors). It is not granted by default: a Customer that does not want it simply does not contract it, and the Provider removes it from its key at the Customer's request. The response states that it was generated by a model and carries a warning that it is not an INAPI decision.

4.5. Limits. Use is subject to a limit per IP address, a burst limit per key, a monthly quota per key, a daily cap on logo analyses and watching caps, as described in the documentation. When a limit is exceeded, the Service responds 429 with Retry-After.

4.6. The quota, the contracted permissions and their price are set out in the Customer's contract or service order.

4.7. Trial key. The Provider may offer a read-only evaluation key, with a reduced quota, without a contract and without any warranty whatsoever; the SLA does not apply to it.

5 · Changes to the API contract

5.1. The API and MCP contract carries no version in the URL. It is versioned through a public change log in which each entry carries a date and a label (see the versioning policy).

5.2. Compatible changes (new operations, optional parameters or fields) take effect without prior notice. The Customer must ignore fields it does not recognize.

5.3. An incompatible change is communicated through its entry in the log and with the instructions for adapting to it, under the terms of the versioning policy. Changes required by law or by security, such as a minimization of personal data, may be applied immediately.

5.4. Changes to these terms. They are published with their date on this page and, if they affect the Customer's rights or obligations, the Customer is notified before they take effect (see legal documents). Continuing to use the Service after that date constitutes acceptance; a Customer that does not accept them may terminate (§ 10).

6 · Availability and support

6.1. The availability, recovery, maintenance and support commitments are those of the service level agreement (SLA).

6.2. An outage or a change in INAPI's sources degrades freshness, not availability: the Service keeps responding with the latest data and indicates this in the date of each response.

7 · Acceptable use

7.1. The Customer uses the Service for its own activity or that of its end clients. It may not:

  • a) resell or redistribute the raw corpus or systematically reconstruct it through mass queries;
  • b) disclose to third parties the personal data it obtains from the Service outside the purpose for which it consults them, or aggregate them into its own databases of persons (see § 7.3);
  • c) circumvent authentication, permissions or limits, or share keys to multiply the quota;
  • d) use the Service for unlawful purposes or against the rights of third parties;
  • e) present the Service's signals as INAPI decisions or as legal opinion.

7.2. License. The Provider grants the Customer a non-exclusive and non-transferable license to use the data it receives, for the purposes of § 7.1 and for the duration of its contract. This license does not extend the rights the Customer may have over INAPI's public data by other means, nor does it exempt the Customer from the conditions of use that INAPI sets for its sources.

7.3. Personal data. The Customer processes the personal data it obtains from the Service only to identify the owner or the representative of a trademark and follow its file, and does not disclose them to third parties, whether in aggregated or disaggregated form, outside that purpose. It complies with Law 19,628 on the Protection of Private Life and Law 21,719 when applicable to it.

8 · Origin of the data

8.1. The corpus is built from INAPI's Estado Diario, the open dataset of trademark applications published on datos.gob.cl and INAPI's trademark record pages.

8.2. The record pages are queried at a minimal volume and only to complete the details of applications with recent activity or without details, not by general crawling.

8.3. The Service does not publish which source originated each field. When the sources disagree, the Service indicates this in a neutral manner.

9 · Personal data and Customer data

9.1. The processing of the personal data in the corpus is governed by the personal data policy.

9.2. What the Customer writes into the Service (data about its organization, watchlists, webhook addresses, its users' email addresses, logo images) is processed on behalf of the Customer under the data processing agreement, with the declared sub-processors.

10 · Suspension and termination

10.1. The Provider may suspend a key immediately in the event of use contrary to § 7, a security risk or non-payment, and informs the Customer of it. The suspension is technical and immediate (blocking of the key, the user or the organization).

10.2. The Customer may terminate with the prior notice set out in its contract. Upon termination, its keys are revoked and its data are deleted in accordance with the data processing agreement § 8.

10.3. The grounds for early termination, the notice periods and their economic effects are those of the Customer's contract.

11 · Security

The security measures of the Service are set out in the data processing agreement § 6.