Privacy

Which personal data the observatory processes, why, and how to exercise your rights.

Controller

aGo lab is the controller of the personal data the observatory processes. Requests about personal data are received at hola@ago.cl.

Which data it processes

Visitors to this site

The portal is a set of static pages. It sets no cookies, does not track visits and loads nothing from third parties: the typefaces are served from the site itself. The only thing it stores is your choice of light or dark theme, in your own browser, and that never leaves it.

The API and its keys

The API needs no key. A consortium institution that needs a higher quota receives one under a written agreement, at its institutional email address, which is used only to write to it about the key. To apply the request limit, the API counts each device’s requests under a digest of its address, computed with a key only the observatory holds, and does not store the address. From those digests, the observatory counts how many queries its API receives each day and from how many distinct network origins, and for each day keeps only the total of queries and the total of origins. The log of operations on an account records only the network prefix they came from.

The institutional dashboard

The dashboard shows consortium companies cross-tabulations of the same figures. Those from sources that count their units carry the same suppression as the portal, and those from sources that do not are shown as the source publishes them. For each person a company appoints, the observatory keeps their username, email address, company, password hash, encrypted authenticator secret and a log of their sign-ins and downloads with the network prefix. It also keeps their acceptance of the terms of use, with the version, the date and the network prefix. It opens no account until the consortium has approved the text of the terms of use. Anyone with an account can ask for it to be closed at any time by writing to hola@ago.cl.

The beekeepers behind the figures

When a capture contains data about beekeepers, such as the microdata of an official register or the reply to a freedom of information request, the observatory stores it encrypted, neither publishes nor releases it, and uses it only to calculate and check the aggregates. The observatory publishes no data that identifies a beekeeper. It publishes aggregates only, and suppresses cells that cover very few producers or where a single producer accounts for the figure, together with the cells that would let someone work them out.

Your rights

You can ask for access to the data about you that the observatory processes, for it to be corrected, erased or blocked, object to its processing, or ask to receive it in a format you can take to another controller. Use the rights form or write to hola@ago.cl, stating who you are, which data or processing your request concerns and the address where you would like to receive the reply.

The reply states whether the right applies in your case and why. The law does not require erasure, or an end to processing, where the data are processed for statistical purposes in the public interest, as with the aggregates the observatory publishes, and allows portability only where the processing is based on consent.

The form gives you a reference number straight away, together with the date the deadline falls, and that is the acknowledgement of receipt; a request that arrives by email is acknowledged at that address. The deadline for a reply is thirty days, counted as calendar days from the day the request arrives. It may be extended once by another thirty days, and you will be told of the extension and its reason.

From 1 December 2026, Chilean Law 21.719 applies, amending Law 19.628. If the request is refused or not answered within the deadline, a complaint may be lodged with the Personal Data Protection Agency (Agencia de Protección de Datos Personales) within thirty working days.

Each processing activity is described in the record of processing, and what the portal stores in your browser on the cookies page.