Cookie & storage policy

1. Cookies and similar technologies

Cookies are small values stored by a browser. Local storage and session storage are other browser storage mechanisms. This website uses them for privacy preferences and consented first-party campaign measurement. The same privacy choice applies regardless of the storage technology.

You can browse the website and submit a rental enquiry without accepting analytics. We do not treat scrolling, continued browsing, or submitting an enquiry as consent.

2. Essential preference storage

mcm_cookie_consent_v3 stores separate Apteva Analytics and Meta advertising choices, the policy version, and expiry timestamp on this website’s origin. Both options start off. It is used only to remember and enforce your choices and is valid for 180 days, after which the website asks again. Earlier consent does not enable Meta advertising measurement.

mcm_display_currency stores USD or EUR only when you choose a display currency. This functional preference remains until you change it or clear site data; it is not an analytics identifier. If storage is blocked, the selection works for the current page. EUR values are estimates and do not change USD billing.

If browser storage is unavailable, analytics remains off until a choice can be saved. Hosting infrastructure may separately use storage that is strictly necessary for security or access control; any such production storage must be disclosed before public launch.

3. Optional Apteva Analytics

Only after you enable Apteva Analytics and save your preferences do we send optional measurement through our own server to Apteva Analytics. The older external analytics tag is no longer loaded. We do not include form names or emails in browser interaction events.

mcm_attribution_v1 stores first and latest campaign details in local storage for up to 30 days from the initial capture. It includes allowlisted UTM labels, campaign/ad-set/ad IDs, a page path, a referring origin, and timestamps. Internal or direct navigation does not replace the latest campaign. Consented attribution is linked to the CRM enquiry when you submit it.

mcm_measurement_session_v1 is a random identifier in session storage, lasting for the tab session. Analytics consent withdrawal or expiry clears it and the campaign storage when detected. The legacy apa_sid identifier is also removed.

Meta advertising is a separate optional setting. If enabled, the Meta pixel may set _fbp and _fbc cookies for browser and ad-click recognition, commonly lasting up to 90 days. It sends PageView and, only after a successful interest submission, Lead. No Purchase event is sent. We disable automatic event configuration and do not provide advanced-matching form fields. You can withdraw this choice independently; the site revokes pixel consent, clears site-accessible Meta cookies, and reloads to unload the script. Cookies on Meta-owned domains remain subject to Meta and your browser controls.

4. Change or withdraw your choice

Select Cookie settings in the footer, choose Apteva Analytics and/or Meta advertising, and save your preferences, or choose Essential only. Both optional checkboxes start unchecked. You can withdraw either choice independently. Withdrawing analytics clears campaign and session measurement storage. Withdrawing Meta unloads the pixel. Another open tab reloads when it receives the updated preference.

A reload can clear an unfinished form, so save anything you need before changing an existing analytics choice. Events already sent while consent was active are not recalled. Ask the privacy contact about previously collected information.

You can also delete site data in your browser. This removes the saved preference and the website will ask again. Blocking analytics does not prevent the separate CRM request needed when you submit an enquiry.