In short
HenSistemas sets no cookies of its own on this site. What the site itself stores on the device are entries in the browser’s local storage and session storage — a similar technology, described here with the same care as a cookie — and they exist so the site works, so it remembers choices you made and so visits can be counted in aggregate.
Whatever cookies may exist are set by third parties in specific situations: the anti-robot verification of the forms and, only after an action of yours — accepting advertising or clicking to play a video — the technologies of Meta and YouTube. All of it is described below, item by item.
The site’s own technologies
None of these entries holds a name, an email address, a telephone number or any identifier of a person, and none of them follows the user away from this site.
| Name | Type | Purpose | Duration | Who sets it |
|---|---|---|---|---|
| hen.quote.v1 | Local storage | Holds the quote list — references, titles and quantities — so it survives moving between pages and closing the browser. | Until the user empties it or clears the browser | HenSistemas |
| hen.analytics.session.v1 | Session storage | A random 16-byte identifier, created in the tab, that allows visits to be counted without identifying who makes them. | Ends when the tab is closed | HenSistemas |
| hen.analytics.seen.v1 | Session storage | A short memory of what has already been counted in this tab, so the same view is not counted twice. | Ends when the tab is closed | HenSistemas |
| hen.analytics.measure.v1 | Local storage | Marks, with one fixed word and without identifying anybody, that the browser belongs to the HenSistemas team, so that it is not counted by the measurement. It is only written when somebody opens the administration area; public pages only read it, and it does not exist in a visitor’s browser. | Until the browser data is cleared | HenSistemas |
| hen.attr.v1 | Session storage | Holds where the first page of the tab came from — campaign parameters, the referring domain, the address of that page without parameters and, if the link carried an ad click identifier, the name of that identifier, never its value — so a request sent later is attributed correctly. | Ends when the tab is closed | HenSistemas |
| hen.request.v1 | Session storage | A key that stops a double click or a retry from creating two identical requests. | Ends when the tab is closed | HenSistemas |
| hen.marketing-consent.v1 | Local storage | Holds the choice made about advertising — accept or refuse — so the question is not asked again. | 180 days | HenSistemas |
| hen.recent-products.v1 | Local storage | Holds the references of the last eight products viewed and the date of each visit, only after you turn on product history. | Each visit, 30 days; everything is deleted when the history is turned off | HenSistemas |
| hen.recent-products.consent.v1 | Local storage | Holds the fact that you turned on product history, and when. | 30 days | HenSistemas |
The two measurement entries of the tab (hen.analytics.session.v1 and hen.analytics.seen.v1) only exist on pages that load the measurement script. On pages whose address carries a code — the page of a request, the newsletter confirmation and unsubscribe pages — and in the administration area that script is not loaded at all, so nothing is created. The working preferences of the administration area stay only in the team’s own browsers.
Optional product history
Product history stays off until you turn it on, on a product page or under “History” at the bottom of the public pages. Once on, it stores in this browser the references of the last eight products viewed and the date of each visit, for up to 30 days, and the permission itself expires after 30 days. Turning it off deletes both entries; clearing the history deletes only the list. None of it leaves this browser, except the references sent to the site’s catalog to display the list up to date.
Third-party technologies
| Name | Type | Purpose | Duration | Who sets it |
|---|---|---|---|---|
| Anti-robot verification of the forms (Turnstile) | Technical cookie and browser storage | Tells a person from an automated program when the quote, contact and newsletter forms are sent. On the quote and contact pages the widget is mounted with the page; the newsletter form sits in the footer of every page, but there the widget is only mounted once the visitor touches the email field — until somebody does, nothing is requested from Cloudflare. It builds no profiles. | Session, or a short period set by the provider | Cloudflare |
| Meta advertising pixel (_fbp, _fbc) | Cookie | Measures the outcome of advertisements. It is off by default and is only loaded where it has been configured and after an express acceptance in the notice shown on the page. | Up to 90 days; refusing deletes them from this site’s domain | Meta |
| YouTube video player (www.youtube-nocookie.com) | Cookies and browser storage set by Google | Plays the video of a product page. It is only loaded after the visitor clicks to play; before that, nothing is requested from YouTube. | Set by Google | Google (YouTube) |
No other third-party technology is loaded by default: there are no embedded maps, no fonts fetched from another domain, no social network buttons, and the site does not use Cloudflare network analytics (Web Analytics). On product pages that have a video, the YouTube player is requested from www.youtube-nocookie.com only when the visitor clicks the play button.
How to manage these technologies
- The choice about advertising can be revisited at any time through the preferences button shown on the pages where the integration applies. Refusing deletes the matching cookies from this site’s domain.
- Product history can be cleared or turned off under “History” at the bottom of the public pages.
- The site’s own storage entries can be deleted in the browser settings, under the data of visited sites. Deleting the quote list empties it; nothing else is lost.
- The quote list can also be emptied on the quote page itself, without going through the browser settings.
- Every browser can block or delete cookies and storage per site. Blocking them here prevents neither reading the catalog nor sending a request.
Relationship with the privacy policy
This policy describes what is stored on the device. The processing of the data that results from it — purposes, legal bases, periods, sharing and rights — is described in the privacy policy, which forms part of this one. Both were written on the basis of the LGPD and of the ANPD’s 2022 guidance on cookies and personal data protection.