1. How to read this document
This page sits alongside the privacy policy, which covers personal data more broadly, and the terms of use, which describe acceptable behaviour on the site. Together they give you a rounded picture. If a word in this document feels unclear, you can request a plainer version by email, and we will do our best to provide one within a short window.
Practical summary. We only load analytics or marketing tools after you make a clear choice, except for items that the site could not work without, such as remembering that you have already seen the consent tool or that your session is still active while you type a long message.
2. What falls within scope
We use the word “cookie” in the wide sense. It includes HTTP cookies, HTML5 local storage, session storage, and similar client-side storage that a web page or script can read. It does not include data that stays only on our servers, such as a database row about an invoice, unless a cookie value on your device is used as a key to that row, in which case we describe the pairing in the privacy policy.
Domain scope
These notes apply to pages served from grozelonphodar.ddd. If you follow a link to a different domain, that operator’s own notice applies, even if the link was visible on our page.
3. What cookies and storage do in practice
A cookie is a small string that a site asks your browser to keep and send back on later requests to the same host or, for third parties, to their own host. Local storage is a small key-value area per origin that scripts can use when you have loaded the page. We may store your consent string in local storage so that a full round trip to a server is not required each time you open the site.
Strictly necessary and security
These keep forms stable, help prevent certain automated abuse of contact endpoints, and remember that you have closed the notice when we need a single, consistent flag. In many legal systems they do not require marketing-style consent, because the site cannot be delivered fairly without them, always within proportionate technical limits.
Preferences
Where we offer an optional user interface setting, such as reduced motion for animations, a preference key may be stored so the choice survives your next visit. We keep such keys to the minimum needed.
Analytics, if you allow them
Analytics help us see aggregated paths through the site, load time ranges, and rough device categories. We do not use this public site to make sensitive inferences, and we configure vendors, where we use them, to shorten IP addresses, respect regional settings, and allow deletion requests through their own dashboards in line with our data processing terms.
Marketing, if you allow them
Marketing or measurement tools may set identifiers that help us know whether a newsletter link was useful, and with your consent may support conversion measurement when you arrive from an online advertisement (for example, search or display campaigns in New Zealand or other regions). Vendors are selected and configured with limitations on retention and use, as described in our privacy policy. If we run no active campaign, some categories may remain effectively unused, but the consent architecture stays ready so you are not asked again from scratch the day we launch a small campaign about opening hours on Broadway.
4. High-level table of categories
The exact names in your browser will differ, but the categories below are what we show in the consent tool.
| Category | Can you switch it off | Storage location |
|---|---|---|
| Strictly necessary | No, without breaking basic functions | Short-lived server headers and essential client flags |
| Preferences | Yes, where offered | local storage, limited cookies |
| Analytics | Yes, via banner or later browser tools | first or third party, per product |
| Marketing | Yes | as configured with each vendor we onboard |
5. How consent and withdrawal work here
When you first visit, a banner may offer Accept all, Reject, and Cookie settings. Reject records a decision that does not turn on optional categories. Settings opens a small panel with checkboxes, including strictly necessary, which is always on. If you return after clearing your browser, you may see the banner again, because we have no way to know you are the same person without some storage, which is the paradox that consent design tries to manage fairly through layered notices.
We log the time of a consent change in our client state object so the interface does not keep nagging in the same session, but we do not use that as a long-term personal profile. For audit purposes on the server, where we have one, we may store a coarse aggregate count of how many people chose a category in a week, with no need to know individual identities on this marketing site by default.
Withdrawal. You can use the same banner, clear site data, or block categories with browser extensions, knowing that a heavy-handed block can sometimes stop login flows that rely on a temporary cookie in other products not described here.
Proof of record. If you need evidence of your choice for a dispute, tell us the approximate day and the email you used, and we will work from what our systems and suppliers can show without inventing new personal fields.
6. Browser and device tools
All major browsers let you list cookies, delete them for one site, or block third parties entirely. Mobile operating systems also include tracking limits for apps, which is separate from this site but can affect your overall expectations about measurement. We encourage you to review those help pages periodically because vendors update the paths often.
7. Cross-border tools
Some optional analytics or marketing scripts are hosted in other countries. When we enable them, we select processors who offer data processing terms and, for EU or UK data, standard clauses where appropriate, as set out in more detail in the privacy policy. The cookie that identifies you to the vendor, if any, is subject to that same framework.
8. Young visitors
This site is for adults planning a visit or a swim or mobility block. We do not design the consent experience to nudge children. If you are a parent and believe your child has been tracked in error, contact us and we will help you remove data held by us or ask our suppliers to do the same where they are processors for us.
9. Do-not-track and similar signals
Some browsers send a do-not-track header. Global standards have not fully converged on a single required reaction. We treat strong privacy signals with respect, but we also need a working site. For now, the consent tool is the clearest way to set categories for this property.
10. How we will update this page
When we add a new script with a new purpose, or change a vendor, we will update this text and may reset consent if the law of your region says we should. The dynamic date in the hero shows when you opened the page; we still maintain an internal “policy version” note for staff, which you can request in writing if you are researching a specific complaint.
11. How to contact us
Email: ask@grozelonphodar.world. Phone: +64 9 978 9400. Postal: Grozelonphodar, 277 Broadway, Newmarket, Auckland 1023, New Zealand. We can answer routine storage questions in plain language, and we will escalate anything that might involve our processor’s data protection team.