Cookie policy

This page describes, based on a real review of the source code of economiq.io (HTML, CSS and JavaScript served to the browser) and of the hosting provider’s available contractual documentation, which cookies, local storage and tracking technologies are actually used today, and which are not.

Version of this policy: 2026-09-22.

1. Summary

economiq.io’s code does not intentionally set first-party HTTP cookies. During the checked public navigation, no Set-Cookie response header and no Economiq first-party cookies were observed. The language switcher uses ordinary links to https://economiq.io/ and https://economiq.io/en/. If the browser allows it, the site may store a language preference in localStorage (economiq_language) when you choose ES or EN, or when a default language is applied on a first visit. If you choose ES or EN expressly, the site also stores economiq_language_explicit. That is not an HTTP cookie, it is not sent with every request, and it is not used for analytics or advertising. Economiq does not implement analytics, advertising or visitor-tracking cookies on this website. sessionStorage and IndexedDB are not used. All HTML, CSS and JavaScript that make up the site (js/main.js, js/interest-form.js, js/removal-form.js, js/promotions-form.js, js/config.js, js/i18n.js, js/boot.js) are served directly from this domain; no scripts, pixels, typefaces, maps or embedded content are loaded from third-party domains (for example, there is no Google Fonts, Google Analytics, Google Tag Manager, Meta Pixel, LinkedIn Insight Tag, third-party chat or external CDNs in the site code). Google Search Console is used by the owner through HTML-file verification (google10a40792f88eb6f1.html); that file does not install cookies or scripts on public pages. The only network calls the browser makes on the site’s own initiative are fetch requests on the same domain to api/waitlist.php, api/request-removal.php, api/request-promotions-unsubscribe.php, api/request-promotions-reactivation.php and, when a default language is needed and there is no useful Accept-Language value, api/locale-hint.php, which do not set cookies in the response.

A stored language preference is optional. You can still switch language with the ES | EN links at any time.

2. What cookies and local storage are

Cookies are small files a site can ask the browser to keep in order to remember information between visits (for example, preferences or identifiers). localStorage, sessionStorage and IndexedDB are browser storage mechanisms with a similar purpose, managed from JavaScript rather than HTTP headers. economiq.io does not use first-party HTTP cookies. The only first-party browser storage intended is the language preference (economiq_language and, if you choose a language expressly, economiq_language_explicit) described in the summary.

3. First-party cookies on the site

None are used. The site is static (HTML, CSS and JavaScript) except for the forms that call api/waitlist.php, api/request-removal.php and api/request-promotions-unsubscribe.php / api/request-promotions-reactivation.php; none of these flows set cookies from the economiq.io server. Confirmation links (double opt-in) and unsubscribe links use identifiers in the URL itself (query parameters), not cookies.

4. Third-party cookies or tracking embedded in the site

None have been found. There is no script, iframe, tracking image (pixel) or external font embedded in the HTML of the public pages that could set third-party cookies in the visitor’s browser.

5. Brevo (waitlist and email)

Brevo is involved only on the server: the website calls api/waitlist.php, which in turn calls the Brevo API. The visitor’s browser never connects directly to Brevo domains while browsing economiq.io, so this flow does not set Brevo cookies in the browser during a visit to the site.

Email is a different matter. The messages Brevo sends directly (for example, confirmations) are not website cookies. Economiq uses Brevo as the email service provider for transactional emails. Brevo processes the technical and operational information needed to send and deliver those emails. Transactional email tracking is configured with Brevo’s anonymous email-tracking mechanism. That does not mean that all information associated with the email is anonymous: Brevo’s contact history may show engagement information such as whether the email was opened, whether it was clicked, and how many times it was opened. Brevo transactional logs are retained for 1 month; that period is independent of Economiq’s pending-contact retention and deletion process. Email open/click tracking is a Brevo account setting distinct from the Brevo Tracker (website activity tracking). This website does not implement Brevo Tracker, Google Analytics, Meta Pixel or similar website tracking code. Campaign email tracking is a separate setting. UTM tracking is disabled. That processing happens in the email client and in Brevo’s infrastructure, outside navigation of economiq.io; it is not a website cookie and is not website analytics.

6. OVHcloud (hosting and visit statistics)

OVHcloud hosts economiq.io. According to the owner-stated panel observation, access logs and error logs are retained for approximately 12 months and purged automatically; Economiq does not control that period. That number is not stated in the reviewed public product technical guides. “Daily Logs only” describes daily processing, not a one-day retention period. OVHcloud Web Statistics is the visit-report product; the panel may also show AWStats and it is not established that they are the same store. Whether OVH’s internal logs are included in Web Hosting technical backups of customer storage is not established. Those statistics are explained in more detail in the privacy policy. The economiq.io code does not set cookies for that statistic; it relies on server logs.

7. Technical cookies of the browser or web server

Apart from cookies set explicitly by the site code, OVHcloud documentation may describe infrastructure-level technical mechanisms on Shared Hosting (for example a server-identifier cookie). That is not asserted as an observed fact on economiq.io: during the checked public navigation, no Set-Cookie response and no Economiq first-party cookies were observed. This policy does not invent names, durations or purposes of infrastructure cookies. A provider-documented possible technical mechanism does not by itself require a cookie-consent banner on this website. If a purely technical infrastructure cookie were observed in the future, it would be for the service to work, not for personalisation, analytics or advertising.

8. Language preference

Spanish and English versions of the public pages live at different URLs (for example, https://economiq.io/ and https://economiq.io/en/). Choosing ES or EN follows that link and, if the browser allows it, stores the choice in localStorage (economiq_language and economiq_language_explicit). That is not an HTTP cookie, it is not sent with every request, and it is not used for analytics or advertising. An automatic first-visit default may also store economiq_language without the explicit flag. Approximate country (GeoIP) is used only on that first visit, after the URL and Accept-Language; it does not change the communication language on every later visit. 404 pages follow the URL tree, not GeoIP. An explicit ES or EN choice always wins. English URLs under /en/ stay English unless you have chosen Spanish expressly. Bots are not redirected based on IP.

9. How to manage cookies

Because economiq.io’s code does not set first-party HTTP cookies and does not implement analytics or advertising cookies, there is currently no cookie settings panel on the site. A cookie-consent banner is not introduced merely because a provider may theoretically use a technical infrastructure cookie. In any case, any browser allows you to block or delete cookies from its privacy settings.

10. If this changes in the future

If economiq.io later adds website analytics, on-site marketing, maps, embedded videos or other technologies that involve cookies or local storage in the visitor’s browser, this policy will be updated before those technologies are switched on, to describe exactly what is used, for what purpose, for how long and, where non-essential cookies are involved, prior consent will be requested from the visitor through a cookie-management mechanism equivalent to a consent banner. The waitlist is already active; this section refers only to future website technologies, not to email or to the current registration.

11. Contact

For any question about this cookie policy, write to hello@economiq.io. More information about other processing of data is in the privacy policy.