What this means in practice
If you publish the site exactly as it currently exists, it should not set marketing or analytics cookies because there are no such scripts loaded. That is the cleanest possible starting point from a privacy and performance perspective.
When this page should change
You should update this privacy notice if you later add a contact form provider, CRM embed, analytics tool, session replay, advertising pixel, chat widget, or any embedded third-party content that stores identifiers in the browser or sends behavioral data to another service.
Recommended policy for the next version
Keep the marketing site cookieless unless there is a concrete business reason to add tracking. If you need basic traffic reporting, use a privacy-first analytics setup configured to avoid cross-site tracking. If you later add tools like Google Tag Manager, HubSpot, or ad retargeting, introduce a consent manager before those scripts run.