This Cookie Policy explains the cookies and similar technologies used by the MoiMatch website and applications, what each of them is for, how long it lives and how you can remove it.

The short version: MoiMatch uses no analytics, advertising or tracking technologies of any kind. We store a handful of technical items that are needed to keep you signed in and to remember the choices you make yourself. This Policy forms part of the Privacy Policy.

1. What cookies and similar technologies are

A cookie is a small text file that a website asks your browser to store and sends back with later requests, so that the site can recognise the same browser.

Websites can also use technologies that work in a similar way:

local storage — a key-value store in the browser that keeps its contents until it is cleared;
session storage — the same, but tied to one browser tab and erased when the tab is closed;
a service worker — a small script the browser keeps in the background, which we use only to receive push notifications when the site is not open.

In this Policy the word “cookies” covers all of these unless a specific technology is named.

2. Why we use them

to keep you signed in between page loads, so that you do not have to enter your password on every screen;
to render the site in the language you have chosen, before any script runs;
to remember small interface preferences you set yourself, such as whether notification sounds are on;
to avoid asking you the same question twice, for example about permission for notifications;
to receive push notifications in the browser, if you have allowed them.

We do not use cookies to build a profile of you, to follow you across other websites, to measure audiences or to show advertising.

3. Categories we use

3.1. Strictly necessary

Without these the Service cannot work: they hold the tokens that keep your session alive. They are set only after you sign in, and removing them signs you out.

3.2. Functional

These remember a choice you made yourself — the interface language, the notification sound, the fact that a prompt has already been shown. Removing them costs you nothing but the preference: the Service keeps working and simply falls back to its defaults.

3.3. Analytics and advertising

None. The Service contains no analytics counters, no advertising networks, no marketing pixels and no third-party scripts. No cookie of ours is shared with anyone, and no third party sets a cookie through our pages.

4. Full list

Cookies

Name	Category	Lifetime	Purpose
`mm_lang`	Functional	1 year	The interface language you chose, or the language of your account. The server needs it before the page is rendered, which is why it is a cookie and not local storage.

That is the only cookie the website sets. The administration panel, which is not part of the public Service, uses its own session cookie on its own subdomain.

Local storage (kept until cleared)

Key	Category	Purpose
`mm_refresh`	Strictly necessary	The long-lived token that renews your session. Removing it signs you out on this browser.
`mm_sound`	Functional	Whether the sound for new messages is on or off.
`mm_push_offered`	Functional	Remembers that we have already offered to enable push notifications, so that the offer is not repeated.
`mm_push_ios_hint`	Functional	Remembers that the hint about adding the site to the iPhone home screen has been shown once.

Session storage (erased when the tab is closed)

Key	Category	Purpose
`mm_access`	Strictly necessary	The short-lived token attached to requests to our interface. It lives in the tab, not on disk.
`mm_unread`	Functional	The last known number of unread messages, so that the badge does not flicker while a page loads.

Service worker

If you allow notifications in the browser, a service worker is registered to receive them while the site is closed. It stores no information about you beyond what the push service needs to deliver a message. Revoking the notification permission in your browser stops it.

5. Mobile applications

The Android and iOS applications do not use cookies. They keep the same kind of information — session tokens, the chosen language and interface preferences — in the private storage that the operating system gives to an application. It is removed when you sign out or uninstall the application. The same is true of the Telegram bot, which stores only what is needed to link your Telegram account to your MoiMatch account.

6. Third parties and external requests

No third party sets cookies through our pages. All front-end libraries are served from our own servers rather than from a content delivery network, so opening a MoiMatch page does not make your browser contact anyone else — with two exceptions, both of which are functions of the Service rather than tracking:

map tiles. When a map is shown, your browser downloads map images directly from a public OpenStreetMap-based tile provider. That provider sees the request, including your IP address and the area displayed, under its own terms. No cookie of ours is sent with it and no account data is disclosed.
push registration. If you enable notifications, your browser contacts the push service in order to obtain a delivery token. This happens only after you allow notifications.

7. Consent

Because the Service uses no analytics or advertising technologies, there is no consent banner to click through. Every item listed above is either strictly necessary for a function you asked for (signing in, receiving notifications) or stores a preference at the moment you set it (language, sound). Where the law that applies to you requires consent for a particular item, that consent is given by the action that creates it, and you can withdraw it by clearing the item as described below.

8. Managing and deleting

8.1. In the browser

Every browser lets you view, block and delete cookies and site data. The controls are usually found under settings for privacy, site data or site permissions, and most browsers also let you clear the data of a single site. Private or incognito windows discard everything when they are closed.

Clearing our site data signs you out and resets your preferences to their defaults. The Service will keep working: you will simply be asked to sign in again, and the interface language will be chosen from your browser settings.

8.2. Notifications

Notification permission is managed in your browser or in the system settings of your device, and can be revoked at any time. Which categories of notification you receive is set in the MoiMatch menu.

Blocking storage entirely. If your browser is set to block all cookies and site storage, you will not be able to stay signed in: the Service has nowhere to keep your session, and every page will return you to the sign-in screen. The public pages — the landing page and these documents — remain fully readable.

9. Changes to this Policy

If we add or remove an item, we update this Policy and the date in its header. The current version is always published at moimatch.org/docs/cookies. Should we ever introduce analytics or any other non-essential technology, we will ask for your consent before it is used.

10. Contact

Questions about this Policy or about anything the Service stores on your device: info@moimatch.org.

Cookie Policy

Contents