Website privacy and optional Google Ads measurement

This disclosure describes this website's optional advertising measurement. It is separate from the firm's general privacy notice and from permission to respond to an appointment request.

Your choice

On the home, use-cases, request-appointment, and privacy-disclosure pages, the Google Ads base tag library loads before a choice is made, in the top-level page context. All consent types default to denied. While there is no saved choice or after Decline, all consent types remain denied, but Advanced Consent Mode may send limited cookieless consent-mode page_view pings with fixed canonical metadata. Accept grants only ad_storage; ad_user_data, ad_personalization, analytics_storage, functionality_storage, personalization_storage, and security_storage remain denied. Equally prominent Accept and Decline choices are available on each page, along with a persistent Manage privacy settings link.

The choice is stored in this browser's local storage and is specific to this browser profile and device. If storage is unavailable or the saved choice cannot be read, all consent types remain denied; limited cookieless consent-mode pings may still be sent. Changing away from Accept immediately updates consent to denied and reloads the page, which destroys the prior top-level tag context; denied consent-mode pings may continue. A reload can clear unsubmitted appointment details. It cannot recall requests already sent.

What the optional tag does

The base tag initializes on the home, use-cases, request-appointment, and privacy-disclosure pages with fixed canonical metadata. On the appointment page, canonicalization happens before the tag loads. A base page_view may be sent as a limited cookieless consent-mode ping while consent is denied; it is not an appointment conversion. A saved Accept grants only ad_storage. The appointment page may send one generic conversion event only after its service returns HTTP 201 with accepted: true and a nonempty string request ID, and only while advertising consent is still accepted. The request ID is checked locally and is not sent to Google; the event contains only the configured destination and no appointment data. The code does not configure enhanced conversions or remarketing audiences. It keeps ad_user_data and ad_personalization denied and sets non-personalization and restricted-data-processing controls.

Each tag route supplies only its fixed canonical page location, fixed page title, and an empty referrer. URL queries and fragments, the browser's current title or referrer, form inputs, and form values are not used as tag metadata. The appointment page reload clears a noncanonical query, fragment, and referrer before its tag loads. The appointment name, email address, phone number, preferred dates and times, liquidity selection, scheduling-contact authorization, form submission payload, and tax slider interactions are not passed to or sent to Google by this tag.

Phone links are ordinary telephone links and do not trigger a Google Ads click conversion. No click-based or phone conversion is configured on these pages. Changing away from Accept immediately updates consent to denied and reloads the page; limited cookieless consent-mode pings may continue. It cannot recall requests already sent.

The appointment POST to /api/appointment-requests, its API handling, and the related email and calendar workflows are not instrumented or sent to Google by this tag. PDFs, images, robots.txt, sitemap.xml, and APIs are not tracked pages. This code's controls do not determine every data practice of Google or other services.

Every request to Google's tag or measurement endpoints, including a cookieless consent-mode ping, exposes technical connection information such as the connecting IP address and browser/request metadata. Google's handling of that information is also subject to Google's own policies and controls.

Pages and services that are separate

The appointment page's contact authorization is only for scheduling follow-up; it is separate from optional advertising consent. The tag does not instrument appointment field interactions or send the submission payload; its base page_view is distinct from the accepted-request conversion described above. It does not change the site's private request, email, or calendar workflow. The disclosure page itself is included in the four-page scope, follows the same consent choice, and uses the same top-level tag context.

InvestedFlex pages continue to request Google Fonts for typography. Those Google-hosted font stylesheet and font-file requests are separate from Google Ads measurement and may involve technical connection data when a page loads. An ad_storage denied state does not mean the site makes no Google-hosted requests; the tag may still send limited cookieless consent-mode pings.

General firm privacy notice

The existing Quantum Capital Investments Privacy Policy (PDF) remains available for the firm's general information-handling practices. This website-specific disclosure supplements rather than replaces it.

A code-based Google Ads conversion action is configured for the generic accepted-request event described above. Campaign status, attribution, and qualified-lead measurement still depend on Google Ads receiving and processing an eligible event.