Relorca

Cookies Policy

Version 1.1. Effective from 2 September 2026.

This document explains which cookies and similar technologies the Service uses, why they are needed and how to refuse the ones you can do without. What We do with data in general is described in our Privacy Policy.

"Service" means the website relorca.app and the Relorca mobile application. You can reach us at support@relorca.app.

Cookies are small files a website stores in your browser. They usually contain nothing that points to a person directly. We do not keep sensitive data — a postal address, a password — in cookies; the Service does not collect such data at all.

1. What exactly We set

The full list is below. Names are given so that you can check them in your browser settings.

Cookie Set by Lifetime Purpose
relorca_refresh Us persistent: survives closing the browser, until your sign-in expires Strictly necessary: keeps you signed in
relorca_consent Us 12 months Stores your choice from the banner
ph_…_posthog Our analytics script on this same domain up to 12 months Analytics: tells one visit from another

2. Strictly necessary cookies

relorca_refresh is how the Service remembers that you signed in. Without it every page would treat you as a new visitor and your account would stop working: this cookie is exactly what saves you from typing your nickname and password again on every visit.

It is persistent, not a session cookie: it survives closing the browser, which is the whole point. It is not readable by page scripts (httpOnly) and is never sent to other websites.

This cookie needs no consent and cannot be switched off in the banner: without it We cannot provide the very thing you created an account for. You can only remove it through your browser — and sign-in will then stop working.

relorca_consent stores your choice itself. Without it We would have to ask you on every visit.

3. Analytics cookies

ph_…_posthog is set by an analytics script running on our own domain — it is not a third-party advertising cookie. It holds an anonymous identifier that tells one visit from another. We do not link it to your nickname or account: visitor identification in analytics is not enabled on our side.

This cookie is not strictly necessary, therefore:

What happens if you do not agree. We keep counting anonymous visit statistics: how many people opened a page, which onboarding steps they went through, where they went next. Nothing at all is written to your device while We do it — no cookie, no browser local storage. Visits are told apart by a temporary anonymous fingerprint computed on the analytics service's side, which cannot recognise you on your next visit. Such counting requires no consent: consent is needed for storing things on your device, not for the act of measuring.

There is exactly one difference between agreeing and not: with the cookie We can see that the same browser came back, without it We cannot.

There are no ad networks, advertising trackers, Google Analytics or cross-site tracking in the Service.

4. Similar technologies: local storage

Besides cookies, the web client uses your browser's local storage, which is never sent to our server and stays on your device. It holds: your onboarding draft (answers you gave but have not saved to an account), a cache of the country reference so the app works faster and offline, and a note of which hints you have already dismissed.

If you agreed to the analytics cookie, the analytics script also puts a record of that choice there (__ph_opt_in_out_…) along with its anonymous identifier. If you did not agree, it puts nothing there.

Separately and importantly: the signals the Service uses to match countries — income, profession, family status, ancestry, urgency — also live only here and never reach our server (see the Privacy Policy).

5. The mobile app uses no cookies

The application uses no cookies at all. Signing in there relies on a device key, not on a browser file.

6. Your choice

Browser instructions: Chrome, Safari, Firefox, Edge.

7. Changes to this document

We may update it. A new version is published on this page with a new date. If the set of cookies that require consent changes, We will ask you again.

8. How to contact Us

support@relorca.app