Cookie Policy
1. What are cookies?
Cookies are small text files stored on your computer or mobile device when you visit a website. They are widely used to make websites work, to keep sessions secure, and to help site owners understand how their pages are used.
This policy also covers similar technologies, in particular your browser's local storage. Local storage is not a cookie, but it holds data on your device in much the same way, so we treat it under the same rules and list it alongside our cookies below.
This policy applies to the Meadow website and to the tenant and landlord portal you sign in to.
2. Categories we use
Strictly Necessary
Required to sign you in, keep your session secure, protect our forms from abuse, and remember your cookie choice. These cannot be switched off.
Analytics
Help us understand how the site is used so we can improve it. These stay off until you choose "Accept all".
Preferences
Browser local storage only, no cookies. Remembers display choices such as the filters and sorting you set on tables in your portal.
A fourth group, marked Third party in the table below, covers cookies that Google sets on its own google.com domain when your browser loads the reCAPTCHA and Google Tag resources our pages embed. They are Google's cookies rather than ours, so we describe them for transparency but cannot set, read or delete them.
We run no advertising tags and set no advertising, remarketing or ad-personalization cookies of our own. The advertising storage permissions used by Google's consent framework — ad_storage, ad_user_data and ad_personalization — are kept switched off on every page load, whichever choice you make.
3. Cookies in detail
| Cookie | Purpose | Type | Duration |
|---|---|---|---|
| meadow_session | Signs you in and keeps your session stable across pages. Sent over HTTPS only and not readable by scripts. | 320 minutes | |
| XSRF-TOKEN | Protects forms and API requests against cross-site request forgery. | 320 minutes | |
| laravel_token | Encrypted token that lets the signed-in app make API requests on your behalf. | 320 minutes | |
| remember_web_* | Set only if you tick "Remember me" when signing in, so you stay signed in on this device without entering your password again. The name ends in a hash identifying the login guard. | 30 days | |
| _GRECAPTCHA | Set by Google reCAPTCHA on our sign-up, sign-in and contact forms to tell real people from bots. | Up to 6 months | |
| meadow_cookie_consent | Local storage. Records the cookie choice you made so we do not ask again on every visit. | Until you clear browser storage | |
| tracker_identifier | First-party identifier used to count visits and understand which pages and referral sources bring people to Meadow. | About 6 days | |
| _ga | Set by Google Analytics to tell one browser apart from another. Only set once you accept. | 2 years | |
| _ga_FH59QLBTL5 | Set by Google Analytics 4 to keep session state for our measurement property. Only set once you accept. | 2 years | |
| SID | Set by Google on google.com to hold your signed-in Google account state and verify that requests genuinely come from you. | About 13 months | |
| __Secure-1PSID | Set by Google on google.com to hold your signed-in Google account state and verify that requests genuinely come from you. | About 13 months | |
| __Secure-3PSID | Set by Google on google.com to hold your signed-in Google account state and verify that requests genuinely come from you. | About 13 months | |
| HSID | Set by Google on google.com as a security cookie, used together with SID to confirm a sign-in is genuine and block forged requests. | About 13 months | |
| SSID | Set by Google on google.com as a security cookie, used together with SID to confirm a sign-in is genuine and block forged requests. | About 13 months | |
| APISID | Set by Google on google.com so its own services can recognise your account. | About 13 months | |
| SAPISID | Set by Google on google.com so its own services can recognise your account. | About 13 months | |
| __Secure-1PAPISID | Set by Google on google.com so its own services can recognise your account. | About 13 months | |
| __Secure-3PAPISID | Set by Google on google.com so its own services can recognise your account. The 3P variants apply when a Google resource is loaded inside another site, as it is here. | About 13 months | |
| SIDCC | Set by Google on google.com as a security cookie that protects your account data from unauthorised access. | About 1 year | |
| __Secure-1PSIDCC | Set by Google on google.com as a security cookie that protects your account data from unauthorised access. | About 1 year | |
| __Secure-3PSIDCC | Set by Google on google.com as a security cookie that protects your account data from unauthorised access. | About 1 year | |
| NID | Set by Google on google.com to remember your Google preferences, such as language and search settings, and for security. | About 6 months |
Our analytics tags are delivered through Google Tag Manager and report into Google Analytics 4. Our forms are protected by Google reCAPTCHA v3. Cookies set by Google are subject to Google's own terms; you can read how Google uses cookies on its cookie technologies page. If we add or change a tag in future, we will update this table and, where the change affects non-essential cookies, ask for your consent again.
The entries marked Third party deserve a word of explanation. They are Google's own cookies, stored against google.com rather than Meadow, and we never set, read or receive them. They appear only if you are already signed in to a Google account in that browser, and they travel with the requests your browser makes for the reCAPTCHA and Google Tag resources our pages embed. reCAPTCHA protects our sign-up, sign-in and contact forms, so that request happens whichever cookie choice you make; the Google Tag request follows your analytics choice.
Because these cookies are not ours, our consent banner cannot delete them. You can control them through your browser's third-party cookie settings or from your Google account. Whatever their presence, our tags keep Google's advertising permissions denied, so nothing on Meadow grants them for advertising or personalization.
Alongside the entries above, the portal keeps small display preferences in your browser's local storage, such as the filters and sorting you last used on a table. These stay on your device, are never sent to us, and are cleared when you clear your browser storage.
4. Managing cookies
You can change your choice at any time on this page using Cookie Settings. This reopens the consent banner so you can accept or reject analytics. You can reach this page from the Cookie Policy link in the footer of every page.
You can also control cookies through your browser, which lets you block or delete them for any site. Blocking strictly necessary cookies will stop you from signing in and will break parts of the portal.
Because your choice is stored in your browser's local storage, clearing that storage also clears the choice. The banner will then appear again on your next visit, and analytics stay off until you make a new selection. Your choice is stored per browser and per device, so you will need to set it separately elsewhere.
5. Your consent
Analytics cookies are switched off by default. When you first visit Meadow you will see a cookie banner, and until you choose Accept all no analytics storage is permitted. Choosing Reject keeps it switched off. Strictly necessary cookies are always set, as the site cannot operate without them.
We use Google Consent Mode v2 to enforce this, so the choice you make is passed to Google's tags on every page load rather than only at the moment you click. You can withdraw or change your consent whenever you like using Managing cookies above.
6. Contact us
If you have any questions about our use of cookies or other technologies, please contact us via email at:
[email protected]