Version 2.1 · 27 August 2026
Informational version. In the event of any discrepancy between this page and a translation, the Spanish version prevails.
A cookie is a small file that a website stores in your browser when you visit it. It lets the site remember information between pages or visits: that you have signed in, which language you want to read in, or to tell you apart from an automated program. Alongside cookies there are other technologies with the same function — browser local storage, device identifiers — and this policy applies to all of them alike.
| Cookie | Owner | Purpose | Duration |
|---|---|---|---|
| NEXT_LOCALE | RedyRedes | Remember the chosen language so we do not ask again | Session |
| __cf_bm | Cloudflare, on behalf of our identity provider | Tell a person from a robot and stop automated attacks | 30 minutes |
| __client | Clerk | Keep you signed in to the Dashboard | 1 year |
| __client_uat | Clerk | Tell the server whether there is an active session, to decide what to serve | 1 year |
| __session | Clerk | Token of the current authenticated session | Session |
That table is the full list. There are no others.
Payment takes place outside this website. When you sign up, we take you to a page hosted by Stripe (checkout.stripe.com) to enter your card details. There, Stripe sets its own fraud-prevention cookies under its own policy and responsibility; we do not set them, cannot read them, and they never reach this site. We say so here because it is part of the journey and you have the right to know before taking the step.
The five cookies in the previous section are technical and security cookies: without them you cannot sign in, the session cannot be kept open and we cannot tell you apart from an automated program. They are essential to provide the service you asked for, so the law does not require your consent to set them: it only requires that we inform you about them, which is what this page does.
We do not use analytics cookies or third-party tools that identify the person: no Google Analytics, no session recording. The only measurement is the aggregated visit count of our hosting provider, which uses neither cookies nor identifiers. It is a decision, not an oversight. Nor do we use advertising cookies or profile anyone for advertising purposes.
If you came here looking for the cookie notice, there is none, and it is not an oversight: a consent banner only makes sense when there is something to consent to. Since all our cookies are strictly necessary, there is nothing to accept or reject. If one day we added a cookie that does require your permission, you will see it: a notice will appear with accept and reject options equally accessible, nothing will be set before you choose, and we will update this page. Regardless of the above, your browser lets you block or delete cookies from its settings; blocking those on this list will prevent signing in and operating the Dashboard.
Clerk is established in the United States and Cloudflare provides its service from a distributed network. The regime for those transfers, with the specific safeguard covering each one, is set out in the Privacy Policy and in the provider list published at redyredes.com/legal/subencargados.
Stripe does not appear in that list because it does not set cookies on this site: its cookies are set on its own payment page, as explained in section 2.
When the cookies we use change, we will update this page and the version that identifies it. If a cookie requiring consent is ever added, consent will be requested before setting it. For any question: adm@redyredes.com.