1. In short
- We use cookies to keep you signed in, keep the Service secure, and remember preferences such as your language and time zone.
- We set no advertising, tracking or analytics cookies, and we do not share cookie data with advertising networks.
- The Service works fully whether you accept or decline the banner.
2. What cookies are
A cookie is a small file a website stores on your device and reads on later visits. Similar technologies, such as browser local storage, do the same job in a different way; this policy covers both. Cookies set by the site you are visiting are “first-party”; all of the cookies in the table below are ours.
Strictly necessary cookies are required to deliver a service you asked for, such as signing in. Functional cookies remember a choice or setting to improve your experience.
3. Cookies we use
| Cookie | Purpose | Type | Expires |
|---|---|---|---|
sessionid |
Keeps you signed in and ties your requests to your session. | Strictly necessary | 2 weeks |
csrftoken |
Protects forms against cross-site request forgery. | Strictly necessary | 1 year |
messages |
Carries a one-off notice, such as "Settings saved", to the next page. | Strictly necessary | Until the notice is shown |
wm_cookie_consent |
Records your cookie choice so that we do not ask again. | Strictly necessary | 1 year |
django_language |
Remembers the language you selected. Set only when you choose one. | Functional | Until you close your browser |
wm_tz |
Your device's time zone, so that dates and times are shown in your local time. | Functional | Until you close your browser |
This table is generated from the application’s own configuration, so it stays accurate when a setting changes.
4. Other device storage
When you are signed in, the application stores a small amount of information in your browser’s local storage. It stays on your device, is not sent to us automatically with each request, and is cleared when you clear site data.
| Stored as | Purpose |
|---|---|
theme, contactView | Display preferences you choose, such as light or dark theme and how contacts are listed. |
profile_draft | Unsaved changes to your profile form, so they are not lost if the page reloads. |
notifications_user_disabled, notification_prompt_dismissed, notification_permission_state, lastNotificationSound | Your notification settings and whether you have already answered the notification prompt. |
fcm_device_id | Identifies this browser for push notifications. Created only if you turn on browser notifications. |
5. Your choices
Everything in the tables above is either strictly necessary for a service you requested or a preference set at your request. Under the ePrivacy rules those are exempt from the consent requirement, which is why the Service works fully whichever answer you give the banner.
We still ask, because analytics and product measurement would not be exempt, and because refusing must be as easy as agreeing. The banner offers both choices with equal prominence, nothing is pre-ticked, and dismissing it is not treated as agreement. If you decline, no non-essential cookie is set and no analytics identifier is created — today, none is created either way.
You can change your mind at any time:
- use the button below to clear your saved choice and see the banner again;
- delete the
wm_cookie_consentcookie in your browser; or - block or delete cookies in your browser settings — note that blocking cookies entirely will prevent signing in, because the session cookie is how being signed in works.
6. Third-party content
Some page resources are loaded from third-party networks. They do not set cookies for us, but the request itself discloses your IP address and the page you are viewing to that provider:
| Provider | Used for |
|---|---|
cdn.jsdelivr.net, unpkg.com, cdnjs.cloudflare.com, code.jquery.com | Page layout, icons and interface libraries |
fonts.googleapis.com, fonts.gstatic.com | Web fonts (Google Fonts) |
images.unsplash.com | Illustrative images on our home page |
www.gstatic.com | Firebase Cloud Messaging, loaded only in the signed-in application when browser notifications are used |
If a message contains a shared location, we show its coordinates and a link. We do not load a map image, so nothing is sent to a mapping provider unless you click the link.
7. Our mobile app
Our mobile applications do not use cookies. They store your session securely on the device and, if you enable notifications, a push token issued by the operating system’s notification service. See our Privacy Policy.
8. Changes
If we add a cookie or a new category, we will update this page and, where the law requires consent, ask for it before setting it. The version and effective date appear at the top of this page.
9. Contact
WAiMATE