our cookie policy

This Cookie Policy explains how The New York Harbor Foundation d/b/a Billion Oyster Project ("BOP," "we," "us," or "our") uses cookies and similar technologies on billionoysterproject.org and related BOP webpages (the "Site"). It should be read with our Privacy Policy.

What These Technologies Are

Cookies are small text files stored by a browser. The Site may also use local storage, session storage, pixels, software development kits, and similar technologies. Some are set by BOP or our website platform, while others are provided by third parties whose services appear on the Site.

How We Use Them

We organize these technologies into the following categories:

• Strictly Necessary: required for security, network delivery, consent choices, requested authentication, payments, event registration, core map delivery on pages where the map is the requested experience, and other services a visitor asks us to provide. These cannot be disabled through our preference tool where they are essential to the requested service.
• Functional: remember choices or enable enhanced behavior such as saved filters, page transitions, display preferences, short-lived data caching, and donation-flow continuity.
• Analytics: help us understand how visitors use the Site and improve its performance and content.
• Marketing: support embedded third-party media or future advertising and campaign measurement when those services are classified in this category.

Closing or ignoring the consent notice does not grant consent. Functional, Analytics, and Marketing remain off until the visitor selects them. Necessary remains on because it supports delivery, security, saved consent choices, and services the visitor requests.

Technologies Identified for the Launch Site

The current implementation and technical audit identify:

• _cfuvid, a session cookie observed on the staging site and used by Webflow or Cloudflare for security, traffic management, and abuse protection. Category: Necessary. Its exact production-domain behavior must be confirmed after launch.
• trellis-consent:v1:<site identifier>, first-party local storage that records the selected categories, policy version, and decision timestamps. Category: Necessary. The Site is configured to request a fresh choice after 180 days or when the policy version changes.
• trellis-filter-state:*, first-party local storage that remembers permitted filter selections. Category: Functional. It is not written when Functional is denied and managed values are removed when Functional is withdrawn.
• bop_donate_pending, bop_donate_amount, and bop_donate_exit, first-party cookies used to remember an unfinished donation, selected gift amount, or dismissal of a reminder. Category: Functional. Retention: up to seven days. They are written only after relevant visitor interaction and when Functional is permitted; donation and payment remain available without them.
• bop:transition, first-party session storage used for a visual transition between pages. Category: Functional. It is consumed promptly, stale values are ignored after approximately six seconds, and normal navigation remains available without it.
• bop_tide_bar_v2, first-party session storage used to cache non-personal tide and weather display data. Category: Functional. Retention: up to approximately 30 minutes or the browser session. Live information may still be requested without saving the cache.
• bop:hero-intro-seen, first-party local storage used to remember that a visitor has seen an optional home-page introduction. Category: Functional. It has no fixed code-defined expiration. The Site removes it when Functional consent is withdrawn; otherwise it remains until the browser or Site removes it.
• _ga and a property-specific _ga_* cookie, which Google Analytics may use to distinguish visits and measure Site use. Category: Analytics. The Google script is not requested before Analytics consent. Exact production cookies and provider-controlled retention must be confirmed after launch.

The current BOP code audit did not find names, email addresses, authentication tokens, or payment-card information stored in the three BOP donation cookies or the three BOP browser-storage keys listed above.

Third-Party Services

The Site may connect to third-party services that use cookies, browser storage, device information, or normal network information such as IP address and user agent:

• Google Analytics for audience measurement. Category: Analytics. Its script and measurement requests remain off until Analytics is granted, and events generated while denied are not saved for later replay.
• Mapbox for interactive maps. Core map delivery is Necessary only on pages where a map is part of the requested experience, and Mapbox does not load on pages without a map widget. Mapbox receives ordinary network information when its resources are requested. Saved map and filter preferences remain Functional.
• YouTube and Vimeo for embedded video. Category: Marketing. Before Marketing is granted, the Site does not create the provider iframe and may instead show a poster or prompt to review choices. Native media served directly by the Site may still load where appropriate.
• The Site's website-data platform and Google Firebase for consent management, Site integrations, authentication, and private account features. Requested authentication and security handoffs are Necessary. Where these providers process personal information on BOP's instructions, they act as service providers or data processors for those functions. Authentication is not conditioned on Analytics or Marketing consent.
• Click & Pledge for requested donation processing. Category: Necessary after the visitor deliberately starts the transaction. The payment interface is not intended to load sitewide, and full payment-card information is handled by the payment provider rather than stored by BOP through the Site.
• Ticket Tailor for requested event booking. Category: Necessary when the visitor requests booking or registration. A plain outbound link does not set Site storage; an embedded checkout, if used, should load only after deliberate interaction.
• Mailchimp for a requested newsletter signup. Category: Necessary for that submitted request. The Site contacts Mailchimp after the visitor submits the signup form, not merely because the page loaded.
• Open-Meteo and NOAA Tides & Currents for weather and tide displays. These providers may receive ordinary network information when the relevant display requests live public data. Saving the resulting first-party session cache is Functional.
• Webflow and Cloudflare for site hosting, delivery, and security. Category: Necessary.

This list reflects the pre-launch audit and must be updated after the production-domain scan and whenever services materially change.

Your Choices

The consent tool lets you accept or reject optional categories and reopen Privacy Choices from a persistent footer control. Optional categories are off before a choice. Withdrawing consent stops future optional requests managed by the Site and removes category-controlled first-party cookies or storage that the Site can access. The Site may reload once to apply a withdrawal completely. A provider may retain information already received as described in its policy or as required by law.

Browser controls may also block or delete cookies, but disabling necessary or requested features may affect Site operation. Browser settings do not necessarily control local storage, embedded services, or every similar technology.

Changes to This Cookie Policy

We may update this Cookie Policy to reflect changes in technology, law, or our practices. The "Last updated" date identifies the most recent revision.

Contact Us

Questions about this Cookie Policy may be sent to info@billionoysterproject.org or mailed to:

The New York Harbor Foundation
d/b/a Billion Oyster Project
Governors Island
10 South Street, Slip 7
New York, NY 10004