Skip to main content
<enginora>
  • How it works
  • Example territory
  • Use cases
  • Pricing
Sign inBook a demoBuild your first territory
  • English✓
  • Français
  • Español
Main navigation
  • How it works
  • Example territory
  • Use cases
  • Pricing
Sign inBook a demoBuild your first territory
  1. Home
  2. Cookies

COOKIES AND OTHER TRACKING TECHNOLOGIES POLICY — ENGINORA

Version 1.0
Effective date: September 1, 2026

This Policy describes the use of cookies and other storage or terminal-access technologies in connection with Enginora websites and services.

Enginora is published by:

I AND YOO
105 avenue des Grésillons
92230 Gennevilliers
France

General contact: contact form
Data protection contact: privacy@iandyoo.com

This Policy supplements the Enginora Privacy Policy.


1. WHAT IS A COOKIE OR TRACKER?

A cookie is information that may be stored on a user’s device when visiting a website or using an online service.

The term “tracker” also covers other mechanisms used to store or read information on the device, including certain identifiers, browser local storage or session storage.


2. PRINCIPLES APPLIED BY ENGINORA

Enginora limits the use of trackers to the needs of operation, security and the features actually provided.

As of the effective date of this Policy, the Enginora corporate website uses Google Analytics 4 to measure its audience and compile usage statistics, only after the user’s Analytics consent has been obtained.

The Enginora corporate website does not use:

  • advertising cookies;
  • retargeting pixels;
  • social-network trackers;
  • Google Ads integration;
  • advertising personalization.

These uses must be distinguished from technologies necessary for the operation or security of the services, which are described below.

2.1 Google Analytics 4

The Enginora corporate website uses Google Analytics 4, provided by Google, with measurement ID G-7B8RLE8P5B, to measure the website’s audience and produce statistics about its use.

Google Analytics 4 is registered in the tarteaucitron consent manager through its built-in gtag service. Its activation is based on the user’s prior consent and is not presented as exempt from consent.

The configuration applies strict Analytics consent:

  • Google Analytics 4 does not load before Analytics consent;
  • it remains unloaded after a refusal;
  • no cookieless Analytics signal is intentionally sent before consent or after refusal;
  • Google Consent Mode keeps the relevant permissions denied by default until the corresponding consent is granted;
  • the user may later withdraw consent through the Enginora cookie-management control.

After consent, Google Analytics 4 may process in particular:

  • session and website-usage information;
  • page-view and navigation events;
  • approximate geolocation;
  • browser and device information;
  • interaction events that the enabled Enhanced Measurement configuration is technically able to detect, including page views, scrolls, outbound clicks, file downloads, video interactions and form interactions.

The actual detection of these interactions depends on the applicable technical conditions. Internal site-search measurement is disabled.

Enginora does not intend to transmit names, email addresses, telephone numbers or form contents to Google Analytics 4. User-provided data collection is disabled. Google Signals is disabled, advertising personalization is disabled, and no Google Ads integration is currently used.

After consent, first-party Google Analytics cookies such as _ga and related GA identifiers may be created. Event-level and user-level data retention is configured for 14 months.


3. STRICTLY NECESSARY TRACKERS

Certain storage or device-access mechanisms may be necessary for the operation or security of a service requested by the user.

They may relate in particular to:

  • authentication;
  • Account security;
  • prevention of abuse and automated submissions;
  • maintaining a session;
  • technical choices necessary for the operation of the interface.

Where a tracker is strictly necessary to provide the requested service, it may be used without prior consent in accordance with the applicable regulations.


4. CLOUDFLARE TURNSTILE

The Enginora contact form currently uses Cloudflare Turnstile to limit automated submissions and abuse.

Turnstile performs technical checks in the browser and generates a token used to verify the legitimacy of the submission.

This processing is used for security and abuse-prevention purposes.

Depending on its configuration and technical operation, Turnstile may use storage mechanisms necessary to perform this verification.

Enginora does not use Turnstile for advertising or marketing profiling purposes.


5. BREVO

The Enginora contact form uses Brevo to receive and process requests submitted through the website.

Loading and submitting the form may result in technical communications with Brevo services.

Personal data submitted through the form is processed in accordance with the Enginora Privacy Policy.

Brevo is not used on the corporate website as an advertising tracking or audience-measurement tool.


6. ENGINORA APPLICATION AUTHENTICATION

The Enginora application available at https://app.enginora.co uses Firebase Authentication for authentication and management of access to Accounts.

Technical storage mechanisms may be used in particular to:

  • maintain authentication status;
  • secure access to the Account;
  • avoid requiring a new authentication on each navigation where this is not necessary.

These mechanisms are used to provide the service requested by the user and ensure its security.


7. TAWK.TO SUPPORT

Enginora currently uses Tawk.to for certain support functions in the application.

The Tawk.to widget may use:

  • cookies;
  • local storage;
  • session storage;

in particular to manage a conversation, maintain the connection across several pages or tabs and remember certain settings necessary for the support function to operate.

Where the use of such trackers requires prior consent under the applicable regulations, they must only be activated after that consent has been obtained.


8. STRIPE

Payments, subscriptions and certain billing functions are managed using Stripe.

When a user accesses a Stripe interface such as Checkout or the Stripe Customer Portal, the user accesses a service operated by Stripe.

Stripe may then use its own cookies and technologies in accordance with its policies and the applicable requirements.


9. GOOGLE CALENDAR

Booking an Enginora demo is offered through a link to an external Google Calendar service.

Google Calendar is not directly embedded in the Enginora page as an iframe.

The technologies used by Google apply when the user chooses to follow that link and accesses the relevant Google service.


10. CONSENT

Where a tracker requires the user’s prior consent, Enginora applies the following principles:

  • no activation before the user’s choice;
  • the ability to accept or refuse;
  • refusal as accessible as acceptance;
  • the ability to change or withdraw the choice later.

Trackers strictly necessary for the operation or security of a requested service are not subject to the same consent mechanism where they benefit from the exemption provided by the regulations.


11. CHANGES TO TOOLS

Enginora may change the technical tools it uses.

This Policy is updated where the addition, removal or modification of a tool materially affects the use of cookies or other trackers.

Any addition or modification of an analytics, advertising or marketing solution using trackers will require a new assessment before activation.


12. MANAGING TRACKERS

Where trackers subject to consent are used, users are provided with the corresponding management mechanism to express or change their choice.

The browser may also allow certain cookies or storage to be deleted or blocked.

Blocking strictly necessary trackers may, however, prevent certain features from operating, including authentication, security or support.


13. PERSONAL DATA

For more information about the personal data associated with these services, their purposes, recipients, possible transfers and the exercise of rights, please consult the Enginora Privacy Policy.


14. CONTACT

For any question concerning cookies, trackers or data protection:

privacy@iandyoo.com

For general questions relating to Enginora:

contact form


End of the Enginora Cookies and Other Tracking Technologies Policy — Version 1.0

<enginora>

The SEO Territory Engine

Product

  • How it works
  • Example territory
  • Pricing

Use cases

  • SEO consultants
  • SEO agencies
  • B2B marketing teams

Resources

  • Blog

Company

  • Contact
  • Book a demo

Legal

  • Privacy policy
  • Terms
  • Data Processing Agreement
  • Acceptable use policy
  • Subprocessors
  • Data export and switching
  • Cookies