Last drafted: 18 October 2026
1. What cookies this website uses
This website's first-party cookies are set by Pol Munné Martínez, a natural person trading as a self-employed individual (autónomo), with tax ID 48244334V and registered address at Vilafranca del Penedès (Barcelona), 08720, owner of rechnia.com (hereinafter, «the provider»), responsible for their use; for any question about cookies or data protection: rechnia@rechnia.com. Any third-party cookies that may be set when a map loads, when the payment box is opened or when passing through the website's delivery network are managed by their provider, identified in section 3, which decides their purpose and duration; the provider reports them here and asks for consent where required.
This website sets seven cookies, all first-party, all created by the application's own server, and none for analytics, advertising or tracking purposes. None of them stores the name, e-mail or password in the browser; the session cookie carries only the account's internal numeric identifier and two timestamps (expiry and last activity), signed by the server, which do not allow the person to be identified without access to the database.
rn_session — The session cookie. Keeps the logged-in person identified while they use the application; without it the password would have to be typed on every screen. It contains a token signed by the server with the account's internal identifier and two timestamps (expiry and last activity). It is set at login and renewed with use. It has no expiry date of its own: it is a browser session cookie, which normally disappears when the browser is closed; in any case the server stops accepting it after thirty minutes of inactivity and, at most, thirty days after login.
rn_sesion — The open session identifier. Each account may have only one session open at a time, and this cookie is what distinguishes that session from an attempt to open another in parallel. It contains a random identifier specific to that session, with no personal data or anything derived from it. It is set at login and deleted at logout; it is also a browser session cookie.
rn_relevo — The session hand-over. It only appears when someone types their password correctly and the account is already open on another device: for two minutes it holds a signed proof that the password has been checked, so the person can press «Close the other session and sign in here» without typing it again. It contains the internal account identifier, an expiry and the server's signature; it does not open a session by itself. It expires after two minutes and is deleted when used.
rn-idioma — The chosen language. It is set only when the person changes the website's language (Spanish, Catalan or English) or opens a link that specifies it («?idioma=» in the address), and stores only that value, so that the website keeps appearing in that language. It lasts one year if remembering the language was allowed in the panel; otherwise, only until the browser is closed (section 2). While logged in, the language preference is stored in the account and this cookie no longer decides.
rn-fondo-acceso — The chosen sign-in screen background. It is set only when the person chooses, in Settings › Appearance, a background for the sign-in screen other than the usual one (one of the website's or a photo of their own) and each time they sign in with their account in that browser, and stores only that choice —the name of the background or the random internal name of the photo—, so that the sign-in screen can show it before knowing who is looking. It lasts one year if remembering preferences was allowed in the panel; otherwise, only until the browser is closed. It is not deleted when logging out: it is that browser's background.
rn-aviso — The save notice. When something is saved and the application moves to another screen, this cookie carries the notice text («saved», or an error with its code) to display it on the next screen. It lasts sixty seconds and the application itself deletes it as soon as the notice is shown.
rn-cookies — The cookie choice. Stores what was chosen in the cookie panel (whether the language is remembered and whether third-party maps load automatically), the date of the choice and the version of this breakdown, so as not to ask again on every visit. It lasts one year, and the question is asked again if the breakdown changes.
All seven are marked SameSite «lax» and, when the service is published, «secure» (they travel only over HTTPS). All except the notice cookie are httpOnly, that is, not accessible from the page's JavaScript code; the notice cookie is deliberately not, so that the application can delete it when it shows the notice.
Previous names. Until 20 September 2026 these cookies and keys were called ig_session, ig_sesion, ig_relevo, ig-idioma, ig-aviso, ig-cookies, ig-rechnia-chats, ig-fichajes-auto-popup and ig-fichajes-shown-for, and they are no longer set under those names. Until 30 November 2026 the application still reads cookies with the previous name: when it uses them it replaces them with the new one and deletes the old one, and it also deletes them when a choice is saved in the cookie panel or the language is changed. Browser storage keys are copied to their new name the first time they are read. Anything left under the previous name stops being read on that date, expires on its own and can be deleted at any time from the browser settings.
2. The cookie panel: what can and cannot be chosen
The first time this website is visited, a panel appears with a summary and three options: accept all, only the necessary ones, or configure category by category. Rejecting is as easy as accepting, neither of the two options that can be chosen (preferences and third-party content) is pre-ticked —the necessary ones appear ticked and without a switch because there is nothing to choose—, and the panel does not prevent use of the website while deciding. Until a choice is made, only the necessary cookies act: the language is not remembered beyond the visit and maps load only when «Show map» is pressed; continuing to browse, scrolling the page or closing the tab is not interpreted as acceptance, and the panel is shown again until a choice is made. The choice can be changed at any time from «Cookie settings», in the footer of the public website, in the application's Settings screen and on this very page. The panel also shows, under «Configure», a table with each cookie and each browser storage entry: name, who sets it, what for, how long it lasts and what type it is.
Necessary, with no option to turn them off: the session cookies (rn_session and rn_sesion), without which it is impossible to log in or use the application, and the session hand-over cookie (rn_relevo), which only serves to close a session open on another device and sign in; the save notice cookie (rn-aviso), which only shows the result of a save on the next screen; and the choice cookie itself (rn-cookies), which is what avoids asking again. They are technical cookies, exempt from the duty of prior consent under article 22.2 of Law 34/2002 (LSSI).
Preferences, optional: remembering for one year the chosen language (rn-idioma) and the background chosen for the sign-in screen (rn-fondo-acceso). If not allowed, each is still set when chosen —so that the website appears in that language or with that background during the visit— but without an expiry date, so that the browser discards it when closed.
Third-party content, optional: whether screens with a map load the Google Maps frame when opened. If not allowed, each map loads only when the person presses «Show map» in that frame. What the map provider receives and may leave is explained in section 3.
This website sets no analytics, advertising, social media or tracking cookies. The seven above are the only cookies the provider creates. No third-party cookies are set on the public pages, except the security cookies that the website's delivery network may set; within the application, the only other third parties that may set their own are the map provider —only with permission or when «Show map» is pressed— and Stripe, solely when an administrator opens the payment box, as explained in section 3. The provider does not track browsing inside or outside this website and carries out no profiling; what third parties do with their own cookies is explained in section 3. This website and the application are aimed at companies and professionals; they are not intended for children under fourteen and cookies are not used to identify or profile them.
3. Third-party cookies and content
No third-party content is loaded on the public pages of this website. Within the application, while logged in, screens with a map load the frame from Google Maps: when opened, if third-party content was allowed in the panel, or when «Show map» is pressed if not. That load is made by the browser of the person opening the screen, and in it Google receives the coordinates of the point, that browser's IP address and the rechnia.com origin, and may set its own cookies or read those it already has in that browser (for example, if the person is signed in to their Google account). Among them, according to Google's policy, is NID, which remembers preferences and expires six months after last use; that policy also explains which ones it uses for advertising and how to turn them off. The provider does not control those cookies.
The provider is Google LLC —for those in the European Economic Area, Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland)—; cookie policy: https://policies.google.com/technologies/cookieshttps://policies.google.com/technologies/cookies; privacy policy: https://policies.google.com/privacyhttps://policies.google.com/privacy.
That map is part of the service contracted by the customer company, which authorises it in the data processing agreement. Blocking third-party cookies in the browser settings prevents Google from leaving cookies even if the map loads; a content blocker may also prevent the load, in which case the frame remains empty and the rest of the application works the same.
Google LLC is a United States company adhering to the EU-US Data Privacy Framework, which is the safeguard covering that communication. International transfers are detailed in section 7 of the privacy policy, and further information may be requested at rechnia@rechnia.com.
Stripe, only when the payment box is opened. When an administrator presses «Pay» in «Your plan», the application loads Stripe.js in their browser, the script of Stripe Payments Europe, Ltd. (Ireland), which renders the payment box inside a frame served from Stripe's domain; what is typed in it goes from that frame to Stripe and never passes through the provider. On loading, Stripe sets two cookies to prevent fraud: __stripe_mid (one year) and __stripe_sid (thirty minutes), holding a random identifier of the browser and of the payment session. For the same purpose, Stripe.js sends Stripe the IP address, the rechnia.com origin and signals from the device and from activity on the page (for example, how the form is filled in), and within its own frames Stripe may use other cookies described in its policy. They are necessary for the payment to be made and verified and are exempt from prior consent under the same article 22.2 of the LSSI. Stripe.js is not loaded for anyone who does not open that box, nor on the public pages; once opened, it stays loaded in that tab, also when moving to other screens of the application, until the tab is reloaded or closed. Stripe's cookie policy: https://stripe.com/es/legal/cookies-policyhttps://stripe.com/es/legal/cookies-policy; privacy policy: https://stripe.com/es/privacyhttps://stripe.com/es/privacy.
Stripe Payments Europe, Ltd. is based in Ireland (European Union); its parent, Stripe, Inc., is a United States company adhering to the EU-US Data Privacy Framework. What Stripe receives when paying, and under which safeguards, is explained in the privacy policy (payment provider).
The delivery network. The hosting provider serves this website through the network of Cloudflare, Inc. (United States), which protects it against attacks. To tell people from bots, Cloudflare may set the __cf_bm cookie (it expires after thirty minutes) and, if it shows a security check, cf_clearance (the proof of having passed it). They are security cookies, exempt from prior consent under article 22.2 of the LSSI, and are not used to track browsing. What Cloudflare receives, and under which safeguards, is explained in the privacy policy (network and security provider).
4. Browser local storage (similar technologies)
Cookie legislation (article 22.2 of the LSSI and the AEPD guide) also covers «similar technologies»: the browser's own storage (localStorage and sessionStorage), which keeps data in the browser without sending it with each request. This website and the application use it for six entries, all first-party, none for analytics or tracking. None is sent to the server by itself, and the server cannot read them; only the turns of the ongoing conversation with the help travel with each question, as the privacy policy explains. They are technical or chosen by the person themselves, so they do not require prior consent; they are explained in the same way as cookies.
rn-idioma (session storage, for as long as the tab lasts) — A copy of the language in use for the error screen that appears if the whole application fails to load, which from there has no other way of knowing which language to speak. It has the same name as the language cookie, but it is a different thing: it is written on every page load, also on the public pages, disappears when the tab is closed and is not affected by the «Preferences» choice in the panel, because it remembers nothing between visits.
rn-chats (local storage, until deleted; each conversation is discarded after ninety days) — Your conversations with RechnIA, the application's help, so you can return to them from the chat's own history: the last twenty, kept per account. They are stored only in your browser: the server does not keep them —the turns of the ongoing conversation travel with each question to the artificial intelligence provider, which may only keep them temporarily, as the privacy policy explains—, and they are deleted one by one or all at once from that history.
rechnia:margen-por-coche (local storage, until deleted) — Whether the margin per car on Home and on Accounting › Balance is shown in euros or as a percentage, as the person leaves it with the € · % switch. It stores only that choice; if deleted, it goes back to euros.
rn-formulario:solicitud and rn-formulario:contacto (session storage, for as long as the tab lasts) — What was typed in the access request or in the public website's contact form (company, contact person, e-mail, phone, plan of interest and message), saved when pressing send so it can be put back if the form returns with an error and does not have to be typed again. It does not store the acceptance tick boxes. It is deleted the next time that form is opened and, in any case, when the tab is closed; what the provider receives is the submitted form itself, not this entry.
rn-recarga-por-version (session storage, for as long as the tab lasts) — The time at which the application reloaded itself because the open page belonged to a version earlier than the published one, so that it is not reloaded again within thirty seconds. It carries no data about the person.
All six can be deleted from the browser settings with no effect on the account.
5. How to disable them
All cookies can be blocked or deleted from the browser settings. Be aware that, since they are the ones that maintain the session, blocking rn_session or rn_sesion prevents logging in to the application: the service can no longer be used. Blocking rn-idioma only means the website appears in Spanish again on every visit; blocking rn-fondo-acceso, that the sign-in screen shows the usual background; blocking rn-aviso, that the green or red confirmation after saving is not shown; blocking rn-cookies, that the cookie panel appears again on every visit; and blocking Stripe's (__stripe_mid and __stripe_sid), that the payment box does not work. Each browser's help (Chrome, Firefox, Safari, Edge) explains how to view, block or delete a specific site's cookies and storage, and how to block only third-party ones.
6. Changes
If any non-necessary cookie were added in the future, this policy would be updated and prior consent would be requested before setting it. Each version of this policy bears its date of last revision in the header of this page. The panel's breakdown has its own version, which is stored together with the choice: the choice is asked again, at most, after one year —below the twenty-four months allowed by the Spanish Data Protection Agency— and whenever that breakdown changes.
Prevailing version
This document is an English translation of the original Spanish text, which is the one accepted and the one with contractual effect. In the event of any discrepancy between the two versions, the Spanish version prevails.