Site notice ยท 2026-10-10
Cookies keep a small record of your site choices.
This notice explains the cookies and browser storage used with Fairway municipal information, advertising traffic, and the City of Fairway contact route.
choicesite notice
Cookies and consent
Plain answers for Fairway municipal information.
These answers apply to the live website at fairwaykansase.com. They cover a visitor who reads the Fairway Kansas municipal code information, checks Fairway City Council meetings, or uses the City of Fairway contact route. They also explain the advertising traffic that arrives through Google Ads, Microsoft Advertising, and Meta Ads.
Cookies are not a payment route. Nothing on this site creates an account, asks for card data, or turns a question about Fairway ordinances or Fairway building permits into a purchase.
When did this notice take effect?
This cookie notice took effect on . That date is the reference point for the categories, storage keys, advertising identifiers, consent controls, and retention periods described here.
The site is a practical public route for Fairway municipal information. A cookie statement does not change the separate rules in the Privacy page or the service limits in the Terms of Use.
What kinds of cookies are in use?
Strictly necessary storage supports the page, the consent control, and a return to an open support chat. It does not decide a permit, approve a licence, or replace a municipal record.
Analytics storage helps measure visits and page activity after a visitor allows it. Advertising storage supports measurement for paid clicks and campaign journeys. These categories are kept separate in the consent controls. Advertising and analytics storage are denied before permission.
google ads, Microsoft Advertising, and Meta Ads send traffic here today. A campaign click can carry an identifier so the operator can understand which route brought a visitor to Fairway municipal information. The site does not claim that any platform has reviewed, approved, or verified it.
What do you keep?
The table names the cookie and browser storage keys used by this site and gives their retention period. A browser may also retain ordinary technical data needed to load a page; the detailed server records are described in the Privacy page.
| Name | Who sets it | What it is for | How long it lasts |
|---|---|---|---|
site_consent_v2 | City of Fairway site | Stores the visitor's accept or decline choice for consent controls. | 12 months |
fairway_chat_token | City of Fairway site | Returns a visitor to the support chat conversation in this browser. | 12 months |
gclid | Google Ads | Identifies a Google Ads click for campaign measurement when permitted. | Set by the platform and subject to its policy |
msclkid | Microsoft Advertising | Identifies a Microsoft Advertising click for campaign measurement when permitted. | Set by the platform and subject to its policy |
fbclid | Meta Ads | Identifies a Meta Ads click where a campaign runs there. | Set by the platform and subject to its policy |
The support chat token is a browser token, not an account password. The inquiry form itself writes its submitted fields to the operator's inquiry system; it is not a cookie.
Which advertising identifiers arrive with a click?
Paid traffic from google ads may arrive with gclid. Microsoft Advertising may attach msclkid. Meta Ads may attach fbclid where a campaign runs there. Those identifiers help distinguish a campaign visit from a direct visit to the Fairway government website.
Google Ireland Ltd / Google LLC receives the relevant consent signals for Google Ads. Microsoft Ireland Operations Ltd handles Microsoft Advertising. Meta Platforms Ireland Ltd handles Meta Ads. The platforms' own policies govern their processing after a permitted advertising interaction.
Identifiers do not make this site a shop. A visitor can read Fairway council agendas and minutes, Fairway ordinances, or Fairway permit information without sending an inquiry.
How does Consent Mode v2 work?
Our consent mode is Consent Mode v2. It starts with ad_storage, ad_user_data, ad_personalization, and analytics_storage denied. Those four signals remain denied until the visitor allows storage through the consent banner or the cookie settings control.
When a visitor accepts, the site updates the relevant consent signals to granted and measurement can operate within the platform rules. When a visitor declines or later withdraws permission, the site sets all four signals back to denied. The change is not held open for a later visit.
The Sec-GPC header is honoured as an opt-out without asking again. A browser setting cannot provide a permit approval, alter the Municipal Code, or change the content of a meeting record.
How do I give, change, or withdraw consent?
Use Accept on the banner to allow advertising and analytics storage, or use Decline to keep those categories denied. The banner does not block the page. It sits at the bottom while a visitor reads Fairway municipal information.
After the banner closes, choose Cookie settings in the footer on any public page. That control lets the visitor change the choice and withdraw consent. A new choice updates the four Consent Mode v2 signals and replaces the site_consent_v2 browser record.
Deleting site data in the browser also removes the local choice. The next visit can show the banner again. A withdrawal does not erase an inquiry already sent; use the data request route in Privacy and data requests for that.
What happens if I decline?
The pages continue to work. A visitor can read Fairway Kansas municipal code information, Fairway City Council meetings, Fairway ordinances, agendas and minutes, building permit guidance, and licensing portal guidance. The phone number, email address, navigation, accessibility route, and inquiry form remain available.
Advertising and analytics storage stop. The site sets ad_storage, ad_user_data, ad_personalization, and analytics_storage back to denied. Campaign measurement that depends on permitted storage does not continue, and the site does not replace that refusal with a cookie wall.
Strictly necessary operation can still use the small amount of browser storage needed for the consent choice or support chat. Declining is not a disadvantage in asking the City of Fairway a question.
Where can I read the platforms' policies?
Microsoft's privacy statement is available at privacy.microsoft.com. Google's policy information is available at policies.google.com. Meta's privacy information is available at Meta privacy policies.
Those links describe the platforms' own services, including their handling of campaign identifiers and consent signals. They do not mean a platform has reviewed or approved this website. For the city's records, contact the operator directly.
Who can answer a cookie question?
Ask about a specific cookie, identifier, or browser record by contacting Fairwaykansase at [email protected] or 913-262-0350. Written correspondence can be sent to 6136 Mission Rd, Fairway, Kansas 66205, Fairway, Kansas, United States.
Say which page you visited and name the storage key if you can. Do not send a password or card number. The Privacy page explains the data request route and the periods used for inquiries, chat transcripts, logs, and consent records.
Need municipal information instead? The cookie control is separate from a city question. Use Contact Fairway for Fairway building permits, Fairway licensing portal guidance, meeting material, or a City of Fairway contact request.