Cookie Notice

Privacy settings

The homepage and Managed NDPA service pages load Google Ads measurement only after your acceptance; they do not load Meta Pixel. The scope form honours your Managed NDPA campaign choice. Optional advertising choices apply separately to the CAR campaign, Managed NDPA campaign and Exposure Check. You can accept or reject through the relevant control below, and return to change your choice.

• Change CAR campaign cookie preferences
• Change Managed NDPA campaign cookie preferences
• Change Exposure Check cookie preferences

Necessary storage and security

Exposure Check answers and scope contact details stay in page memory until you submit. Reloading the page clears these unsubmitted details. If you explicitly choose to carry Exposure Check answers into the scope form, organisational answers are saved temporarily in this tab’s session storage. They remain available to carry for one hour, then expire when read, and are cleared after successful scope submission or when the tab closes. Contact details are not saved in this transfer.

We store your optional tracking choice, notice version and timestamp in your browser’s local storage, separately for each campaign and the Exposure Check. These records remain until you change them, clear browser storage or a material notice change requires a new choice.

Cloudflare provides hosting and Turnstile abuse protection on submission forms. Security requests and any necessary security storage are separate from optional advertising consent. See the Cloudflare Turnstile Privacy Addendum.

Optional advertising and requested services

The Exposure Check uses Meta Pixel only after you accept analytics and advertising cookies. It may set _fbp and _fbc. Its consent-gated server-side conversion processing is described in the Exposure Check Privacy Notice. Marketing email opt-in is separate and optional. The scope form does not subscribe you to marketing.

The campaign page at /ndpa-car-filing stores your cookie choice in local storage. If you reject non-essential cookies, the Meta Pixel is not loaded and no campaign event is sent to Meta. If you accept, the page loads Meta Pixel and may set Meta cookies such as _fbp and _fbc. We use it to measure page views, video engagement, booking intent, calendar availability and completed bookings. We do not send booking-form values, names or email addresses from this page to Meta.

The Managed NDPA campaign uses the same consent-first approach with its own saved choice. Meta Pixel loads only after acceptance and may set _fbp and _fbc. It measures page views, engagement time, scroll milestones, video engagement, clicks to request scope, completed scope requests and booking-link clicks. The accepted or rejected choice is also stored in a first-party cookie so it can be honoured on the scope form at ndpa.blaecwood.ng. A separate Meta Pixel configured on the Managed NDPA Cal.com event records a confirmed booking as a Schedule event. We do not send company details, form answers, names or email addresses in browser event parameters. Rejecting optional tracking does not prevent a scope request or booking.

Managed NDPA, including the homepage and the /managed-ndpa and /ndpa-dpco advertising destinations, also uses Google Ads measurement after you accept analytics and advertising cookies, including on the scope form when that choice is present. Google may set advertising attribution cookies to connect an ad visit with later activity. We pass standard campaign parameters and Google ad-click identifiers to the Managed NDPA booking link; we do not include contact details or form answers in those parameters. You can withdraw this choice through the campaign’s Cookie preferences. See how Google uses information from sites that use its services.

The Cal.com calendar is requested only after you select a booking control. Cal.com may then store its own cookies to provide the calendar and booking flow whether or not you accepted Meta tracking.

You can revise the Meta choice at any time through “Cookie preferences” in the campaign-page footer. Withdrawing consent stops further Meta events from that page and removes the known first-party Meta cookies where the browser permits it.

Meta and Cal.com control their own technologies and retention practices. See their respective privacy and cookie information for details.

Read this alongside the Privacy Notice, which explains what personal data we collect and the rights you hold over it.