LEGAL / PRIVACY
Website privacy policy.
How the institutional website handles — and still needs to validate — information related to people.
This is an informational institutional text. It requires legal and operational validation before it can be treated as a final policy or published as a final commitment.
INFORMATIONAL VERSION 0.1 · AUGUST 23, 2026
01 / IDENTIDADE
Identity and role.
Caristeo Tecnologia Inteligente Ltda. is the entity identified on this institutional website. For personal data handled directly through this website, Caristeo acts as controller when it determines the purpose and means of processing. In client projects, products and services, controller, processor and other applicable roles depend on the context and contractual instruments of each operation.
This document covers only Caristeo’s institutional website and flows observable in this implementation. It does not replace notices, contracts or policies specific to products, clients, partners or third-party platforms.
02 / DADOS E FINALIDADES
Data by source, without inferring beyond the code.
Below is what the current implementation makes possible to identify. Where behavior depends on external configuration or infrastructure, that limitation is stated clearly.
- 01
Navigation and measurement
The code loads Google Analytics and Google Tag Manager. Depending on their active configuration, navigation information and online identifiers may be processed. The repository does not reveal which parameters, cookies, events or retention periods are configured in production; these points need confirmation before a final version.
- 02
Language preference
The language choice is stored in the browser under the “caristeo-locale” key. This preference does not, by itself, identify a person, and the code sets no expiration period for it.
- 03
Contact and project brief forms
The interfaces display fields such as name, email, company, subject, message and project context. The application sends and stores no data. The form prepares a local message that can be copied or opened in an email app for the person to review and send. Input remains in the page session until it is changed, closed or reloaded.
- 04
Applications
The published job page has no application form or technical résumé-receipt mechanism. It links to the contact page; any future application flow must present a specific notice before activation.
- 05
Infrastructure and technical records
The website code alone does not support a statement about records maintained by hosting, networks, browsers or other infrastructure services. Such processing should be detailed only after operational and legal confirmation.
03 / FINALIDADES
Purposes and legal bases.
In its current state, processing verifiable in the website itself is limited to the local language preference and loading analytics and tag-management technologies. Their intended purposes are to present the site in the chosen language and measure/manage its navigation, according to the configuration actually active.
This version does not assign a specific legal basis to each purpose: tag, cookie, infrastructure and any data-receipt channel configurations still need validation. No new collection flow should go live without a defined purpose, legal basis and corresponding notice.
04 / COMPARTILHAMENTOS
Sharing and processors.
The current implementation references Google services for analytics and tag management. Code alone does not establish which data is sent, which sub-processors participate or which settings have been approved. The current institutional forms have no data-submission integration. Other processors or sharing must be disclosed only when technically confirmed, necessary to the flow and approved for publication.
05 / TRANSFERÊNCIAS
International transfers.
External services loaded in the browser may involve processing outside Brazil depending on each service’s architecture and configuration. The project does not document countries, transfer mechanisms or applicable safeguards. Before a final version, these elements must be verified and described according to actual processing.
06 / RETENÇÃO
Retention by criteria, not assumption.
The language preference remains in browser local storage until it is replaced or removed by the person, browser settings or data clearing. The code defines no retention for analytics, infrastructure logs, forms or applications. When those activities are activated or confirmed, retention criteria should consider purpose, necessity, applicable obligations and secure disposal — without promising unapproved timeframes.
07 / SEGURANÇA
Security proportionate to context.
Security and privacy inform product, engineering and operations decisions, but this policy does not claim controls, certifications or guarantees that have not been validated for the flow in question. The depth of controls and responsibilities may vary with the system, data, integrations and contracted scope.
Read the security approach08 / DIREITOS LGPD
Data subject rights and available channel.
Under Brazil’s LGPD and where applicable, a data subject may request confirmation of processing, access, correction, anonymization, blocking or deletion, portability, information on sharing, withdrawal of consent and review of automated decisions, subject to legal limits and the context of the request.
- Do not send passwords, tokens, identity documents or sensitive data in an initial contact.
- Explain your relationship with the website, the right you wish to exercise and the data involved.
- The existing public institutional channel is the contact page; its current form states that it sends and stores no data. It therefore does not confirm receipt of a rights request.
- An operational privacy or data-protection-officer channel will be published only after validation. Until then, this page must not be read as confirmation of service through an email address, form or specific timeframe.
The project contains no approved DPO contact, response timeframe or identity-verification process for public disclosure.
Open institutional contact09 / CRIANÇAS E ADOLESCENTES
Children and adolescents.
The current frontend presents no age collection, parent/guardian-consent mechanism or flow directed to children and adolescents. If a product, project or future interaction involves their data, the processing must be assessed separately with applicable safeguards and legal grounds before operation.
10 / TERCEIROS E COOKIES
Third-party links and cookies.
Links to sites, app stores and other external destinations follow their own privacy practices. When leaving this website, people should consult the destination’s notice. Storage and measurement technologies related to this site are also addressed on the Cookies page; it must evolve with the same legal and technical validation as this policy.
Read the Cookies page11 / ATUALIZAÇÕES
Updates, version and validation.
This text will be reviewed whenever actual data flows, integrations, cookies, contact channels or applicable obligations change. The published version and date help identify the content in force. While it remains marked informational, it does not replace legal review or the operational definitions needed for a final policy.
INFORMATIONAL VERSION 0.1 · AUGUST 23, 2026