Cookies and website storage.

01 / OVERVIEW

Transparency before choice.

This page describes storage and measurement technologies related to Caristeo Tecnologia’s institutional website. It separates what is confirmed in code from what depends on configuration or responses from external services. Its categorization and transparency follow the logic of purpose, necessity and control presented by Brazil’s data protection authority (ANPD), without turning guidance into an unvalidated compliance claim.

02 / TECHNICAL DISTINCTIONS

A cookie is not all storage.

Cookies are files that a website or service may place in a browser. A website may also use other forms of storage on a device. In the current implementation, these situations appear differently:

• Cookies: first-party code does not create, read or remove cookies, and the local server response does not show a Set-Cookie header.
• Local storage: the language preference is stored in browser localStorage under the “caristeo-locale” key. It is not a cookie.
• Page memory: institutional forms retain fields only while the page remains open; no sessionStorage or data-submission integration was identified in code.

03 / ACTIVE TECHNOLOGIES

What is technically confirmed.

Rather than publishing an empty cookie table or assumed names, we record only behaviour observable in the repository and local runtime.

• 01

  Local storage

  Language preference · localStorage · first party · preference · active. The “caristeo-locale” key stores the selected language to apply the interface on a future visit. It remains in the browser until another language is selected or it is removed by the person/browser data clearing. The code defines no expiration period.

• 02

  Measurement and tags

  Measurement and tags · third-party resources · Google Analytics and Google Tag Manager · loaded globally. Code loads gtag.js and gtm.js but does not reveal which events, parameters, cookies, identifiers, consent settings or retention periods are active in the external services. This page therefore does not list Google cookie names, duration or category without runtime validation and corresponding approval.

No banner, preference-management button or consent mechanism is implemented on this website. If non-essential technologies require consent in the validated scenario, the solution must be implemented end-to-end before it is presented as an available control.

04 / CATEGORIES AND CONTROL

Categories as reference, not an inventory.

The categories below help explain the purpose of browsing technologies. They do not, by themselves, state that every type is active on this website:

• Strictly necessary: support basic site functions. No first-party cookie in this category was identified in audited code.
• Preferences: remember a person’s choices. An active language preference exists in localStorage; it is not a cookie.
• Measurement: help understand navigation, performance or use. Google Analytics and Google Tag Manager load, but the cookie inventory and configuration require production validation.
• Advertising: may support ads or personalization. No advertising pixel, tag or cookie was identified in audited code.

How to control it in the browser.

A person can inspect, block or remove cookies and site data in browser settings. They can also clear browsing data or remove a domain’s local storage. Options and labels vary between browsers, so the practical path is the privacy, site-data or cookies section in the browser being used.

If localStorage is removed or blocked, the main verifiable outcome is that language returns to the default until another choice is made. Blocking third-party technologies may affect measurement resources or tag loading according to the configuration actually active. No promise is made that blocking has the same effect across all browsers or external services.

05 / THIRD PARTIES AND PRIVACY

Third parties, embeds and pending evidence.

The website loads Google resources for analytics and tag management and links to external destinations. The Google Tag Manager noscript iframe loads only when scripts are disabled. Audited code contains no advertising pixels, video players or social widgets. Storage created by an external resource is also governed by that provider’s practices and must be validated in the published environment before it enters a final inventory.

Relationship with privacy.

Storage technologies can relate to personal data when they identify or make a person identifiable. The Privacy Policy explains the broader website treatment context. Neither text replaces legal validation, audits of external settings or the specific notices needed before new data flows go live.

06 / UPDATES

Updates and contact.

This page should be reviewed whenever tags, cookies, pixels, integrations, preferences, providers or data flows change. Its date and version identify this informational state. The existing public institutional channel is the contact page; its current form states that it sends and stores no data and does not confirm receipt of messages.

INFORMATIONAL VERSION 0.1 · AUGUST 23, 2026