Skip to content

Personal data policy

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

This policy covers the personal data in the corpus, that is, what INAPI publishes about trademark applications. The data that the Customer writes into the Service are governed by the data processing agreement.

1 · Who processes the data

1.1. The owner of the Tarno service, identified in each Customer's contract or service order ("the Provider"), processes the personal data in the corpus as controller.

2 · What personal data the corpus contains and where it comes from

The corpus reproduces INAPI's trademark register. When the owner or the representative of an application is a natural person, this includes personal data:

data source served
Name of the owner or the representative, as published by INAPI open data on trademark applications · INAPI record pages yes: trademark records, party search, reports, watching
RUT INAPI record pages (the open data carry no RUT) yes: in a party's record, in a trademark's parties and in some reports; it is possible to search by exact RUT
Commune and region (not the address) open data yes: alongside the party
Country open data · INAPI record pages yes
Names printed in the Estado Diario (applicant, representative, opponent) Estado Diario yes: in the file annotations and in the daily bulletin
Names and, in a few cases, a RUT within the free text of an annotation (for example, a signatory) Estado Diario · INAPI record pages yes: in the annotation's remarks field
Original files from each source the three sources no: they are kept only so that they can be reprocessed

2.1. The Provider does not collect personal data for the corpus from any source other than INAPI's and does not enrich them with third-party data.

3 · Purpose and basis of the processing

3.1. Purpose. The personal data in the corpus are processed for the same purpose for which the register publishes them: to identify who is the owner or representative of each trademark and to follow the file, so that the Customer can search for prior records, watch trademarks and prepare its filings before INAPI.

3.2. Basis. The data come from an official public register of industrial property and from publicly accessible INAPI sources, and are processed only for the purpose of § 3.1, in accordance with Law 19,628 on the Protection of Private Life and, from its entry into force, Law 21,719.

3.3. Use by Customers. The terms of service § 7.3 require the Customer to use these data only for that purpose and not to disclose them to third parties outside it.

4 · Minimization

4.1. Only what the register publishes and is needed to identify the owner or the representative is served: addresses are not served, nor are the original files from the sources.

4.2. The Provider continuously reviews which data about natural persons are needed for the purpose of § 3.1 and may reduce what it serves (for example, stop returning the RUT of natural persons or redact it in the free text of annotations). Such a reduction is announced in the changelog and may be applied without the window for ordinary changes (terms § 5.3).

5 · Recipients

5.1. The personal data in the corpus are disclosed to Customers with a valid key and read permission, through the API and the MCP. They are not sold or transferred outside the Service.

5.2. The providers that host the Service and its backups have technical access to them as sub-processors. The personal data in the corpus are not sent to any artificial intelligence provider: semantic search is computed on the Service's own infrastructure.

5.3. International transfer. The Service's main infrastructure is in Europe, and some sub-processors process data outside Chile. The Provider only uses providers that offer contractual data protection guarantees (see sub-processors).

6 · Rights of the data subject

6.1. Any person may request access, rectification, erasure or objection with respect to their data in the corpus, by contacting the Provider and stating their name, their RUT and the trademark or data item concerned. Customers may channel these requests through their usual contact with the Provider.

6.2. Rectification. The corpus reproduces INAPI: if the data item is wrong at INAPI, the Provider informs the requester so that they can have it corrected before INAPI, and corrects in the corpus anything that is its own loading error.

6.3. Erasure or objection. Where appropriate, the data item ceases to be served even if INAPI continues to publish it: this is applied at read time, so that the next synchronization with INAPI does not expose it again. If erasure would prevent identifying the owner of a registered trademark in force, the Provider explains this to the requester in its response.

7 · Retention

what how long it is kept
Corpus (trademarks, parties, annotations) while the Service is provided: it is a historical record
Log of detected changes 2 months, except those from the Estado Diario, which form part of the file history
Original open data files the 2 most recent per year
Original INAPI record-page and Estado Diario files archived so that they can be reprocessed
Backups daily, encrypted; 14 days in external storage
Copy in the test environment (without public access) until its next update
Technical logs and metrics 15 days

8 · Security

The measures are set out in the data processing agreement § 6. In addition, the read-only access used by the operations dashboards has no permission over data about persons, annotations or keys.

9 · Changes to this policy

Changes are published with their date on this page and announced as stated in the legal documents.