Start for free

← Back to Atriqo

Atriqo — Cookie and Similar Technologies Policy

Last updated: 22 September 2026

1. Summary

Atriqo’s analytics tracker does not set cookies or use browser storage to create a persistent visitor identifier on websites that use Atriqo.

That does not mean that cookieless analytics is automatically outside ePrivacy rules. Atriqo’s tracker receives or derives technical information such as User-Agent/browser/device information, language and screen information. Depending on the configuration and applicable law, obtaining information from terminal equipment can require consent unless an applicable exemption applies.

Atriqo also uses authentication/access cookies on its own dashboard (app.atriqo.com) and, where applicable, password-protected shared dashboards. These cookies are not used for advertising, cross-site tracking or visitor profiling.

2. Who operates Atriqo

Atriqo is operated by Iñigo Larrea Arina, trading as Atriqo, NIF 72813588G, with address at Calle Monasterio de la Oliva 31, entreplanta, 31011 Pamplona (Navarra), Spain.

Contact: hello@atriqo.com.

3. Cookies used by the Atriqo dashboard

These cookies are set only when a user interacts directly with Atriqo’s own application or a protected shared dashboard. They are not placed on the device of someone merely visiting a Customer website that has the Atriqo analytics tracker installed.

Cookie Purpose Duration Characteristics
__Host-session Maintains the authenticated Atriqo dashboard session. Browser session by default. If the user expressly selects “Keep me signed in for 30 days”, it persists for 30 days from login and is not automatically extended through use. First-party; HttpOnly; Secure; SameSite=Lax.
__Host-login Temporarily maintains the challenge required to complete one-time-code login. Browser session; the login challenge itself is valid for 15 minutes on the server, or until login is successfully completed. First-party; HttpOnly; Secure; SameSite=Lax.
__share-auth-* Remembers during the session that the correct password has been entered for a protected public dashboard. Browser session, subject to a maximum server-side validity of one hour. First-party; HttpOnly; Secure; SameSite=Strict.

Session authentication cookies and protected-dashboard access cookies are used solely to provide functionality requested by the user.

The 30-day persistent option is not enabled by default. It is only set where the user expressly selects “Keep me signed in for 30 days”, which informs the user that a persistent cookie is used.

Under the current analytics design:

  • Atriqo does not set cookies to identify or track visitors to Customer websites;
  • the tracker does not write any cookies and does not use sessionStorage or IndexedDB. It performs only one read of the atriqo_opt_out key in localStorage. This key is used exclusively to honour a user-requested opt-out: when it is present, no analytics is sent;
  • Atriqo does not perform cross-site tracking;
  • Atriqo does not use device fingerprinting to re-identify visitors; and
  • the raw visitor IP address is processed transiently to derive a daily-changing pseudonymous identifier and country-level location and is then discarded.

However, the tracker receives or derives terminal information such as browser/device information, language and screen information. ePrivacy rules can apply to technologies other than cookies. A Customer must therefore assess whether its use of Atriqo satisfies an audience-measurement or other applicable exemption or whether prior consent is required.

Atriqo does not represent that every plan, retention period, custom-event configuration or Customer use case qualifies for a consent exemption. The Terms of Service, Privacy Policy and DPA allocate the relevant responsibilities.

6. Atriqo’s own website

atriqo.com uses Atriqo’s own tracker to measure use of the website, without cookies, cross-site tracking or fingerprinting. Events are stored pseudonymously for a maximum of 24 months. We are migrating this measurement to a mode that retains only aggregated statistics.

The GDPR aspects of Atriqo’s own analytics are described in the Privacy Policy.

7. Email tracking

Atriqo sends its transactional emails through Scaleway. Atriqo does not enable or use open or click tracking in these emails: they contain no tracking pixel, and their links point directly to Atriqo.

8. Managing cookies

You can delete or block cookies through your browser settings. Blocking cookies needed for authentication may prevent you from staying logged in, completing a login flow or accessing a protected shared dashboard.

Where optional or persistent cookies require consent, Atriqo will provide the relevant choice before setting them. Atriqo will not use a cookie-preferences panel merely for technologies that are genuinely exempt from consent.

9. Changes to this Policy

Atriqo will update this Policy if the cookies or similar technologies it uses change. The current version and “Last updated” date will be published on this page.

10. Contact

Questions about cookies and similar technologies: hello@atriqo.com.