Skip to content
Rummo
Legal

Cookies

Which ones there are, what they do, and what you can refuse.

In force since

1.What is asked, and when

Article 5 of Portuguese Law 41/2004 requires prior consent for cookies that are not strictly necessary for the service the user asked for. “Prior” means before anything is written to your device — not afterwards, with a notice.

Inside the application there are none of those. No social, no profiling. You are never asked for anything there.

There is one exception, and only with the yes to advertising given on the website: the page that opens after creating a space tells Google Ads the space was created. No other page of the app loads it.

On the website there are two, named in clause 3, and each has its own question: measurement and advertising. Until you answer, neither loads. Declining is worth as much as accepting, and takes the same gesture.

2.The ones that exist

All strictly necessary, and none leaves this house:

  • a)Authentication session cookies — keep you signed in. They expire with the session.
  • b)`ctx` — remembers which mode you are working in (running the space, or training). Without it, every navigation would ask again.
  • c)`tenant_ativo` — remembers which space you are in, for those who belong to more than one.
  • d)`espaco_treino` — the same, on the athlete side.
  • e)`rummo_barra` — whether the top notice bar has been dismissed.
  • f)`rummo_periodo_encolhido` — whether you collapsed the trial period card on the space dashboard. Lasts a year.
  • g)`rummo_passagem` — before public launch, marks whoever has the site access code. It ceases to exist afterwards.
  • h)`rummo_medicao` — holds your answers to the two questions, measurement and advertising, plus the version of the questions. Lasts 6 months. Also strictly necessary: without it, the questions would come back on every page.

3.Measurement and advertising, each with its own question

Without a yes, the site loads no third-party tool and writes none of these cookies. Name, email, phone, member id and space id never leave in either of them.

Each question turns on its own tools, and a yes to one does not count for the other. All of them set cookies and send data to the United States:

  • a)Measurement: Google Analytics, by Google Ireland Limited — which pages are viewed, which buttons lead where, and by which route people arrive. Cookies `_ga` and `_ga_…`, up to 2 years. With the same yes, two moments that already happen inside the app — the account was created, the space was created — are counted by our server with the `_ga` identifier, without name, email or account id.
  • b)Advertising: the Meta pixel, by Meta Platforms Ireland Limited — which pages are viewed, to show ads to people who visited the site. Cookie `_fbp`, up to 3 months, and `fr` on Meta's domain.
  • c)Advertising, with the same yes: Google Ads, by Google Ireland Limited — which ad brought the visit, and whether it ended in a demo request, a message or a new space. Cookies `_gcl_au` and `_gcl_aw`, up to 3 months, and cookies on Google's domain. It loads on the website and on one page of the app: the one that opens after creating a space.
  • d)Without a yes to advertising, Google Ads does not load and is told nothing, not even without cookies.

4.Refusing, and changing your mind

Withdrawing the yes is as easy as giving it, which is what article 7(3) GDPR requires: at the bottom of this page are your answers and a button that erases them. Erased, the questions come back, and the cookies the tools left on this domain go with them.

The answers last six months. After that you are asked again — a yes from a year ago proves very little.

You can also block cookies in your browser, and that is where `fr` and the cookies on Google's domain go, since they are out of this site's reach. Blocking session cookies means the application can no longer keep you signed in: that is not a penalty, it is what a session cookie does.