Cookie policy

What is stored in your browser when you use Remitide. It isn’t much, and we can list all of it.

Last updated: 5 October 2026

This translation is provided for convenience. The Spanish version is the legally binding one. Read the Spanish version

You choose whether we measure

Technical cookies keep you signed in and protect the connection with Stripe. The three analytics cookies of our own are only created if you click “Accept” in the analytics notice or “Accept analytics” on this page, and Remitide works exactly the same if you reject them. Until you choose, no analytics code is loaded and nothing is sent.

Article 22.2 of Spain’s Information Society Services Act (LSSI) requires consent before cookies are installed, with an exception for those strictly necessary to provide the service you have asked for. The session cookie is exactly that: without it you would have to type your password on every screen.

Our analytics does not use Google Analytics, advertising pixels or third-party identifiers. If you accept it, it records: where you came from (the link’s UTM parameters and the domain of the previous page, never its full address), the first and the last time you arrived from another site, the page, guide or feature you are reading, how far you read an article or guide (25, 50, 75 or 100%), clicks on “Try it free”, “Talk to the team”, pricing and the guarantee, whether you use the calculator or the collections check-up (not what you type into them), your device type, the country indicated by the network, your browser’s main language and whether you go on to create an account. It does not store your IP address. Events needed to provide the service, such as an integration being connected, are recorded as operational account activity, not through these cookies.

Current status: no choice made yet.

Cookie-free read counts

Separately from the optional analytics, we count how many times each article, each guide and the main public pages (home, pricing, features, collections check-up…) are opened, even if you reject analytics. This doesn’t need your permission because it doesn’t read or store anything in your browser and doesn’t process data that identifies you:

The count happens on our server when it serves the page you asked for. There is no cookie, no local storage, no identifier in the address and no code running on your device for this.
Each page opened adds one to a daily counter. The only breakdowns are the domain you came from (for example “google.es” or “direct”, without the full address), the device type (mobile, tablet or computer) and the country indicated by the network, if it indicates one.
Your IP address and browser are not stored. The browser is checked at that moment only to tell whether it is a mobile device or a bot, and then discarded. The IP address is used only to stop anyone inflating the figures by reloading: it is encrypted with a random key that lives in the server’s memory, forgotten after ten minutes and never written anywhere.
Your device’s characteristics are not combined to recognise you (what is known as “fingerprinting”), your path from one page to another is not tracked, and there is no way to know whether two reads come from the same person.
Bots and search engines that identify themselves as such are not counted, nor are browser prefetches or visits by the Remitide team.
The counters are kept for 25 months, so each month can be compared with the same month the year before, and then deleted.

The legal basis is our legitimate interest in knowing which content is read so we can improve it (Article 6.1.f of the GDPR, the EU General Data Protection Regulation); the details are in the privacy policy.

What a cookie is, briefly

A small file that a website stores in your browser so it can recognise it on the next page you open. Some are essential for a website to work, such as keeping you signed in or remembering a basket, and some are used to measure traffic or for advertising. The first kind needs no permission; the second does.

Cookies we use

Cookie	First or third party	Purpose	Duration
remitide_stripe_state	First party (Remitide)Technical (security)	Links the start and the return of the Stripe authorisation to protect your account’s connection. It is only created when you start that process.	Up to 10 minutes; deleted when the return is handled
remitide_session	First party (Remitide)Technical and necessary	Keeps you signed in so you aren’t asked for your password on every page. The application can’t be used without it.	30 days, or until you sign out
remitide_equipo	First party (Remitide)Technical (internal team only)	For the Remitide team only: set when a team member signs in to the internal dashboard with two-factor authentication, so that their own visits aren’t counted in the statistics. It contains a “1” and nothing else.	12 hours, or until sign-out
remitide_idioma	First party (Remitide)Technical and necessary (language preference)	Remembers which language you read the website in (“es” or “en”). It is set when you read a page available in both languages or switch language with the selector, so that sign-up and sign-in appear in the same language. It contains nothing else.	1 year
remitide_vid	First party (Remitide)Own analytics, optional	Tells visits apart pseudonymously, to measure which pages, campaigns and buttons lead to a sign-up. It is a random identifier: it contains no name, email address or bank details.	13 months, unless you withdraw consent sooner
remitide_origen	First party (Remitide)Own analytics, optional	Remembers the first and the last time you arrived from another site: the source (for example “linkedin” or a search engine’s domain), the medium and campaign of links with UTM parameters, the landing page and the date. It tells us which campaigns bring sign-ups.	13 months, unless you withdraw consent sooner
remitide_sid	First party (Remitide)Own analytics, optional	Groups the pages viewed during a single visit to calculate the funnel without third-party analytics services.	30 minutes

The session cookie is marked httpOnly, so no script can read it, and SameSite=Lax, so another website can’t use it to submit forms or requests on your behalf; it is only sent when you open a link to Remitide, so you arrive signed in. It contains a random identifier, and our servers don’t even store that identifier, only a cryptographic hash of it.

Other things stored in your browser

These aren’t cookies, but they are worth mentioning because they also stay on your computer:

remitide-tema — if you choose the light or dark theme, your choice is remembered in the browser’s local storage. It never reaches any server and doesn’t identify anyone.
remitide-avisos-ocultos — inside the application, the list of notices you have closed (for example, the free trial one) so they aren’t shown to you again. It doesn’t reach any server either.
remitide-analitica — stores locally whether you accepted or rejected analytics, so your choice is respected. On its own it doesn’t identify a person and it isn’t sent to the server.
remitide-asistente — inside the application, whether you had the assistant panel open, so it stays open when you move to another screen. It is kept in the tab’s storage and disappears when you close the tab.
remitide:event:… — only if you accept analytics: a marker in the tab’s storage so the same page isn’t counted twice when you reload. It disappears when you close the tab.

How to delete or block them

When you leave for Stripe or another provider to authorise an integration or to pay, that provider’s own cookie policy applies. Remitide’s connection cookie is httpOnly, SameSite=Lax and Secure over HTTPS; it contains a signed state linked to the user and their organisation. It doesn’t contain Stripe’s secret keys. These identifiers may be personal data even though they don’t include your name.

Every browser lets you view, delete and block cookies from its privacy settings. If you block Remitide’s cookie you won’t be able to stay signed in: signing out does exactly that, it deletes it.

And the same goes for emails

Reminders sent from the email account you connect carry no tracking pixel: they don’t record whether the recipient opened the email. We do record whether they clicked the payment link, because that is a visit to a page and we need it to know whether the reminder worked.

More details

What data is processed, on what legal basis, who else handles it and how to exercise your rights is set out in the privacy policy. For any questions, soporte@remitide.com.