Cookie Policy — ERa analytics

Version: 1.0
Effective date: 10/26/2026
Last updated: 10/26/2026
Platform: ERa analytics
Platform owner: Artifizio Technology LLC — Wyoming, USA
Contact: soporte@era-analytics.app
Lee esta política en español

IN SHORT. ERa does not use tracking, advertising or analytics cookies, nor any third-party trackers. The only things the Platform stores in the browser or on the device are those strictly necessary for it to work: the session —including a single first-party cookie, the one that keeps it open in the web application—, the User's preferences and a local copy for reading with limited connectivity. That is why it shows no cookie consent banner. This Policy expands on § 11 of the Privacy Policy and is to be read together with it and with the Terms and Conditions.


1. What cookies and local storage are

Cookies are small files that a website places in the browser and that the browser sends back to the site on every visit. Local storage (localStorage, sessionStorage and IndexedDB) is a similar mechanism that keeps information in the browser or device itself but which, unlike a cookie, is not sent to the server on its own with every request.

This Policy covers both techniques alike, as well as any other technique used to store information on the User's device or to read it from there. It applies to the site https://era-analytics.app, to the web application and to the Android and iOS applications.

2. What ERa does not do

ERa does not install or use:

The mobile applications do not read the phone's advertising identifier, contacts or location either (§ 6 bis.1 of the Terms).

3. What ERa stores in the browser or on the device

Everything below is first-party (written and read only by the Platform itself, on its own domain) and serves a technical or functional purpose. None of it is shared with third parties or used to build profiles.

Category What it is for Where it is stored How long it lasts
Session (strictly necessary) The authentication tokens that keep the session open and renew it without asking for the password again. In the web application, the short-lived access token stays in the tab, and the refresh token goes in the era_rt cookie (§ 3 bis). Web application: sessionStorage and the era_rt cookie. Mobile applications: application storage (localStorage). The access token, up to one hour or until the tab is closed; the cookie, up to thirty (30) days. Both are deleted on sign-out or when the account is deleted.
Sign in with Google or Apple (strictly necessary) Temporary markers that allow the sign-in to complete on returning from the identity provider and an error to be shown if it fails. sessionStorage and localStorage Deleted once the sign-in is complete.
Preferences Light or dark theme, preferred judicial district, panel layout, home screen shortcuts and notices the User has already dismissed. localStorage Until the User changes them or clears the site data.
Search: saved and recent items The lists of documents the User has saved and viewed, and a local copy of their text so they can be read when the network fails. localStorage and IndexedDB Tied to the account: deleted on sign-out and when another account signs in on the same browser.
Push notifications (mobile applications only) The opaque identifier provided by the operating system to deliver notifications to the device (§ 12 of the Terms). Application storage Deleted on sign-out or when the account is deleted.

3 bis. The only first-party cookie: era_rt

The web application sets a single cookie, strictly necessary, when the session starts:

This cookie is not used to identify the User outside the Platform or to track their browsing. The mobile applications do not use it.

4. Cloudflare security cookies

The Platform is served through Cloudflare, Inc. To protect the service against bots and attacks, Cloudflare may, in certain circumstances —for example, when traffic appears automated—, set strictly necessary security cookies (such as __cf_bm or cf_clearance). These cookies serve only to tell people apart from bots, are short-lived, are not used to track the User or for advertising, and are governed by Cloudflare's cookie policy.

5. Third-party services outside the Platform

Some actions take the User, at the User's request, to a third party's page. There, that third party's cookies and policies apply, not ERa's:

6. Legal basis and consent

Everything described in §§ 3, 3 bis and 4 is necessary to provide the service the User requests or to remember the preferences the User chooses. Its legal basis is the performance of the contract and ERa's legitimate interest in operating and protecting the Platform, as set out in the Privacy Policy. Since ERa uses no analytics, advertising or tracking cookies, it does not collect separate consent or show a cookie banner. Should it ever use a non-necessary technique, it will add it to this Policy and ask for the User's consent beforehand.

7. How to delete what is stored

The User may, at any time:

Blocking cookies or storage for the site prevents signing in and using the Platform, because the session would have nowhere to be kept.

8. Changes to this Policy

ERa may amend this Policy to reflect technical, legal or operational changes. The new version will be published on this page with its date and, where the change is substantial —in particular, if a technique requiring consent is added—, notice will also be given on the Platform or to the registered email address.

9. Contact

For any question about this Policy, write to soporte@era-analytics.app with the subject "Cookies".

10. Language

This Policy is published in Spanish and in English. The English version is a translation provided for the User's convenience; in the event of any discrepancy, conflict or doubt of interpretation between the two, the Spanish version shall prevail.


This Cookie Policy is supplemented by the Privacy Policy and the Terms and Conditions of ERa analytics, a platform of Artifizio Technology LLC.