Sub-processors
Current version: 2026-10-07. See the legal documents for how changes are announced.
Third parties involved in providing the Service and what data each one sees. "Customer data" are those of the data processing agreement § 2; "corpus" means INAPI's public data, including the personal data of the personal data policy.
1 · Sub-processors
| provider | what it does | Customer data | corpus | location |
|---|---|---|---|---|
| Contabo | hosts the main infrastructure (API, MCP, databases, logs) and the test environment | yes: what is stored in the main infrastructure | yes: in full, also in the test environment | Europe |
| Cloudflare | external storage of the encrypted backups and of the archive; DNS for the domains | yes, within the backups, encrypted before leaving the Service | yes, in the same encrypted backups and in the archive | per the provider |
| Supabase | managed database of the Tarno application: user accounts and application data | only those of whoever uses the application: their account and what they keep in it | only what the application keeps alongside an account | per the provider |
| Bright Data | network intermediary for querying INAPI's record pages | no | yes: it sees the queries to the record pages and INAPI's public responses | per the provider |
| Anthropic | language model for the descriptive analysis of logos (analyze_logo) |
only the image that the Customer sends to that operation, and only if it has the logo:analyze permission |
no | per the provider |
Notes per provider
Contabo. The test environment has no public access and no third-party keys.
Cloudflare. Backups are encrypted with AES-256 and an integrity tag before leaving the Service; Cloudflare does not hold the key. Backups are deleted after 14 days. Customer traffic to the API and the MCP goes directly to the Service's infrastructure and does not pass through Cloudflare.
Supabase. It is only involved in the Tarno application; the API and the MCP keep no Customer data in it. The connection requires TLS.
Bright Data. It is only involved in updating the corpus, never in Customer requests.
Anthropic. The image is validated in the Service (format and size), sent to the model and not stored or logged in the Service; only its SHA-256 fingerprint is returned. There are daily caps on analyses and the permission is not granted by default; it can be disabled per Customer by removing it from its key.
2 · Ancillary services that receive neither Customer data nor corpus data
| provider | for what |
|---|---|
| Vercel | hosts this public documentation (docs.tarno.cl): static pages only |
| GitHub | source code, container images and deployment |
| Slack | operational alerts (metrics and system status) |
| Let's Encrypt | issues the TLS certificates (it only sees the domain names) |
A Customer that builds its own application on Tarno uses its own providers; they are not part of this list.
The sources of the corpus (INAPI, datos.gob.cl, the Library of the National Congress, the Internal Revenue Service (Servicio de Impuestos Internos), WIPO) are public data origins, not sub-processors: the Service queries them and does not send them Customer data.
3 · Changes to this list
A new sub-processor that receives Customer data is announced before it is engaged, in accordance with the data processing agreement § 4.