Cookie Policy

Cookies are small files a website stores on your device. This page explains the cookies engineering.pr uses and how you control them. It works alongside our Privacy Policy.

Your choices

We use a few strictly necessary cookies to run the site, plus optional analytics and marketing cookies. If you are in the European Economic Area, the United Kingdom, or Switzerland, the optional cookies load only after you opt in. Elsewhere, they load by default and you can turn them off at any time. Either way, you can review or change your choice with Cookie preferences.

Strictly necessary

Required for the site to work; these do not need consent.

• cc_cookie (first-party): remembers your cookie choices so we do not ask again. About 6 months.

Analytics (optional; consent required in the EEA, UK, and Switzerland)

These help us understand how the site is used, in aggregate, so we can improve it.

• _ga, _ga_* (Google Analytics 4): distinguish visitors and sessions for aggregated, non-identifying traffic measurement. Up to 2 years.

Marketing and contact (optional; consent required in the EEA, UK, and Switzerland)

These support our contact and scheduling tools and help measure their use.

• hubspotutk, __hstc, __hssc, __hssrc (HubSpot): support our contact forms and scheduler and measure visits. Session to roughly 6 months.

Browser storage (not cookies)

The site also saves a few small values in your browser's own storage (localStorage and sessionStorage) to remember interface preferences. These are not cookies: they are not attached to requests to our servers or to anyone else's. Values in local storage stay on your device until you clear this site's data. Values in session storage disappear when you close the tab.

• pre-hero-seen (session storage): records that you have already seen the home page headline animation, so on a later home page view in the same tab it appears in its final state instead of animating again. The value stored is "1". Until you close the tab.
• pre-lang (local storage): the language code on the last language link you clicked (for example "es" or "en"), used so the bilingual bar can present its line in the language you last chose. Until you clear site data.
• pre-ribbon-off (local storage): the date and time you dismissed the bilingual bar with its X. The bar stays hidden for 24 hours and then returns. The value itself stays until you clear site data.
• pre-bot-pages (session storage): a count of how many pages you have viewed in the current tab, used only to decide whether the chat teaser has earned the right to appear. Until you close the tab.
• pre-bot-nudge-shown (session storage): records that the chat teaser has already appeared, been opened, or been dismissed in this tab, so it appears at most once per visit. The value stored is "1". Until you close the tab.
• pre-bot-nudge-dismissed (local storage): the date and time you closed the chat teaser. The teaser is suppressed for 14 days. The value itself stays until you clear site data.
• pre-aff (local storage): a count, per guide topic (permits, hurricane and earthquake, flood, cadastre and title), of how many of those pages you have opened on this device, capped at 40 per topic, so the home page can put the guides most relevant to you first. Written only if you allow the Personalization category. Until you clear site data.
• pre-choice (session storage): the guide topic you selected yourself using the guide chooser on the home page. Written only if you allow the Personalization category. Until you close the tab.

We do not upload these values. One thing derived from them does leave your browser: when you send a message in the chat, the request includes the page you are on and the single guide topic that currently ranks highest for you, which may come from pre-aff or pre-choice when personalization is allowed, and otherwise only from the current visit. The stored values and counts themselves are not sent.

How to control them. pre-aff and pre-choice are tied to the Personalization category in Cookie preferences: if that category is not granted, the site does not write them and clears any existing values when it reads your choice. The site also treats a Global Privacy Control or Do Not Track signal from your browser as a refusal. The other six values are not covered by the cookie preferences dialog. To remove them, clear this site's data in your browser settings (the option is usually called something like "Cookies and other site data"), or browse in a private window. The session storage values clear themselves when you close the tab.

How blocking works

Until you accept the optional categories, where consent applies, the analytics and marketing scripts do not load and their cookies are not set. We also use Google Consent Mode, so Google tags respect your choice.

Managing cookies

Use Cookie preferences to accept or reject the optional categories at any time. You can also block or delete cookies in your browser settings, though some site features may then work less smoothly. For how we handle your information overall, see our Privacy Policy.