Doc. 12Cookie policy

Nothing that tracks you is stored until you press Allow.

This cookie policy lists every cookie and browser storage key that duke.us.org uses, who sets it, what it is for and when it expires. The notes in the margin carry the clocks and definitions.

Last updated September 28, 2026. Operator: Duke, trading at duke.us.org, Durham, NC.

Effective date

This notice takes effect on September 28, 2026. It replaces any earlier cookie statement on this site from that date.

Three categories, one of them always on

Strictly necessary. Two storage keys the site cannot work without. One remembers whether you allowed or declined storage. The other lets the support chat find your conversation again when you come back. Neither is shared with anyone, and neither is used for advertising.

Analytics. Counts of visits and pages, used to see which pages people actually read and where they give up. Off until you allow it.

Advertising. Cookies set by Google, Microsoft and Meta that connect a paid click to a later inquiry. Off until you allow it. We use them to decide which ads to keep running and which to stop paying for.

Every key, by name

The list below is the whole of it. If your browser shows a cookie from this site that is not on this table, write and tell us which one.

NameSet byPurposeLasts
site_consent_v2duke.us.org, local storageStrictly necessary. Records Allow or Decline12 months
Chat conversation tokenduke.us.org, local storage, via jadi0e5.phpStrictly necessary. Reopens your chatUntil you clear it; transcript kept 12 months
_ga, _ga_*GoogleAnalytics. Distinguishes visitsUp to 2 years
_gcl_auGoogle AdsAdvertising. Links a gclid click to an inquiry90 days
_uetsidMicrosoft AdvertisingAdvertising. Session for msclkid1 day
_uetvid, MUIDMicrosoft AdvertisingAdvertising. Returning visitor for msclkidUp to 13 months
_fbp, _fbcMeta AdsAdvertising. Stores the fbclid click90 days

Advertising platforms and their click identifiers

Google Ads, Microsoft Advertising and Meta Ads send paid visitors to this site now. When you click one of those ads, the platform adds an identifier to the link: gclid for Google Ads, msclkid for Microsoft Advertising and fbclid for Meta Ads. If you allow storage, the platform's tag saves the identifier in one of the cookies above so that an inquiry sent later can be counted against the ad. If you decline, the identifier sits in the address bar and goes no further than a cookieless ping.

Consent Mode v2 on this site

The very first script on every page sets Google's consent mode to denied for four signals: ad_storage, ad_user_data, ad_personalization and analytics_storage. That happens before the banner appears. Pressing Allow sets all four to granted. Pressing Decline, or withdrawing later, sets all four back to denied immediately, on that page, without a reload. Microsoft and Meta tags follow the same choice.

Giving, changing and withdrawing consent

The banner at the bottom of the screen offers two buttons of the same size: Allow and Decline. It does not cover the page, and you can read and use the whole site while it is showing. Ignoring it counts as no choice, which means denied.

To change your mind, press Cookie settings in the footer legal row of any page. The banner opens again and your new answer replaces the old one. Clearing your browser's site data for duke.us.org also resets it.

If you decline

Everything a visitor needs still works. Every page loads, the inquiry form sends, the route and timeline checker runs and the support chat opens. What stops is measurement and ad matching: no analytics cookies, no advertising cookies, and the platforms cannot tie your visit to your browser. You may still see Duke ads elsewhere, because those are shown by the platforms, but they will not be based on this visit.

The platforms' own documents

Each platform explains what it does with what its cookies collect:

Asking about a specific cookie

Write to [email protected] with the cookie's name and the page you saw it on. A screenshot of your browser's storage panel helps. You can also call (919) 684-5600 or write to BOX 90502 705 BROAD STREET, DURHAM, NC 27708. To see or delete what we hold about you, use the data request page.