Cookie Policy
This policy explains what cookies Trace uses, what they are for, how long they last, and how users can manage them.
Last updated: 2026-08-05
1. What is a cookie?
A cookie is a small text file stored by a website in the user's browser when visited. Cookies allow the site to remember information about the visit (language, session, preferences) and, in some cases, collect data about usage to improve the service.
2. Cookie types by purpose
- Essential: required for the site to work. Do not require user consent.
- Functional: improve experience (remembering preferences). Require consent, except when set as the direct result of a user action.
- Analytics: collect information about site usage tied to a pseudonymous identifier (not to your name). Require consent.
- Advertising: track the user across sites to show personalized ads. Trace does not use advertising cookies for its own purposes and does not run personalized advertising. Microsoft Clarity, the analytics tool described in section 4, may set an identifier of its own; you can avoid it by rejecting analytics cookies.
3. Cookies we use
As of this policy's date, the Trace website sets only the following cookies and browser storage. In addition, and only if you visit traceerp.com/contacto, the meeting-scheduling provider may set cookies under its own domain; these are described in section 4.2.
| Name | Type | Purpose | Duration |
|---|---|---|---|
NEXT_LOCALE | Essential | Remember the user's selected language. | 1 year |
trace-theme | Essential (preference) | Remember the preferred theme (light or dark). Stored in localStorage. Saved only as the direct result of the user clicking the theme toggle, so it does not require prior consent. | Until cleared by the user |
trace_consent | Essential | Remember whether you accepted or rejected analytics cookies, so we don't ask again. | 6 months |
ph_*_posthog | Analytics | PostHog: anonymous visitor identifier and session data. Only set if you accept. | 1 year |
_clck, _clsk | Analytics | Microsoft Clarity: visitor and session identifiers. Only set if you accept. | 1 year and 1 day respectively |
MUID, CLID | Analytics (third party) | Microsoft identifiers associated with Clarity. Only set if you accept. | 1 year |
Analytics cookies are activated only with your prior consent, requested through a notice on your first visit. If you do not accept them, none are set and the site works normally. You can change your decision at any time from the Cookie preferences link in the footer.
3.1. How the choice is presented
The notice has two layers. The first states the purpose and offers two actions:Accept, which consents to everything, and Preferences, which opens the second layer. In the preferences panel, cookies are grouped as follows:
- Essential — always on and impossible to turn off, because without them the site cannot be provided: session, language, theme and the record of this very choice. These correspond to the
NEXT_LOCALE,trace-themeandtrace_consentrows in the table above. They require no consent because they are strictly necessary or are set as the direct result of a user action. - Experience improvements — the name the panel gives to the analytics cookies described in section 4. They stay off until consented to and can be turned off at any time without losing any site functionality. Analytics cookies are not part of the essential group and never will be: measuring usage is not necessary to provide the service.
Rejecting is done from that panel, by turning Experience improvements off and saving. Closing the notice without pressing either button records no decision at all: nothing is set and the notice will be shown again.
4. Third-party cookies
4.1. Analytics tools
With your consent, the Trace website uses two third-party analytics tools. Both help us understand how the site is used so we can improve it; neither is used by us for personalized advertising.
- PostHog Inc. (United States) — product analytics: page views, button clicks, errors and replay of page interaction. Acts as a data processor, meaning it processes data solely on our instructions. Policy: posthog.com/privacy.
- Microsoft Corporation (United States) — Microsoft Clarity: heatmaps and replay of page interaction (pointer movement, clicks and scrolling). Microsoft acts as an independent controller and may use the data for its own purposes. Policy: privacy.microsoft.com.
These tools do not record what you type: form fields are masked by configuration and their contents never leave your browser. Data is processed in the United States, a country listed by Colombia's Superintendencia de Industria y Comercio as providing an adequate level of data protection.
4.2. Meeting scheduling (only on the /contacto page)
The page traceerp.com/contacto shows a calendar for booking a video call with our team. That calendar is provided by HubSpot, Inc. (United States) and loads inside an embedded frame served from meetings.hubspot.com. When you use it, HubSpot may set its own cookies in your browser, tied to its domain and not to ours, and it receives whatever you enter to book the appointment (name, email and anything you choose to tell us). Policy: legal.hubspot.com/privacy-policy.
Three points that matter, because they set the exact boundary of this:
- That page only. No other page on the site loads anything from HubSpot. In particular, we do not use the HubSpot tracking code, which is what would follow your browsing across the rest of the site.
- No Trace cookie is set because of this. The calendar works with a temporary identifier generated in the page's memory that disappears when you close it, which is why no new row appears in the table in section 3.
- It loads without asking for prior consent, and it is the site's only exception. It is not analytics: it is the tool that does what you asked for by opening that page, in the same way the theme switch stores your preference because you pressed it. If you never open
/contacto, nothing from HubSpot is ever loaded. The analytics cookies in section 4.1 still require your consent, without exception and on that page too.
4.3. Other domains
The Trace application (customer panel, on a separate domain) may additionally include cookies from providers such as payment gateways, governed by their own policies and documented within the application.
5. Online stores built with Trace
Merchants using Trace can publish an online store on their own subdomain. Those stores run Trace software and use the same analytics tools described in section 4, with the same two-layer notice and the same two categories. That is why a store's notice links to this policy: the analytics cookies are Trace's, not the merchant's.
| Name | Type | Purpose | Duration |
|---|---|---|---|
trace_store_consent | Essential | Remember whether you accepted analytics cookies in the store, so we don't ask again. | 6 months |
| Session and cart | Essential | Keep the shopper's session and cart contents across pages. Stored in the browser. | The session, or until the cart is emptied |
ph_*_posthog, _clck, _clsk, MUID, CLID | Analytics | The same as in section 3, for the same purposes. Only set if you accept. | The same durations as in section 3 |
Payment pages are excluded from session recording entirely, and personal data visible on screen — national ID, shipping address, phone number — is masked. Order, payment and shopper account data are the merchant's responsibility and are governed by the privacy policy the merchant publishes; this section covers only the analytics cookies that Trace contributes.
6. How to manage cookies
The user can accept, block or delete cookies from their browser settings. Blocking essential cookies may prevent the site from working properly (e.g., not remembering the chosen language).
Browser instructions (official links):
7. Changes to this Policy
This Cookie Policy may be updated to reflect changes in cookies used or applicable legislation. The current version will always be available on this page, with the last-updated date at the top.
8. Contact
For questions about this policy, write to [email protected].