A cookie is a small text file that a website asks a browser to store, and the browser sends it back on a later request to the same site. Cookies let a site remember a choice, keep a session open, or count visits without identifying a person. This page describes the cookies Kansas Company Search uses, why each one exists, and how a reader can remove them.
The Kansas Company Search site is a set of reading pages, so it needs fewer cookies than a shop or a portal. Most of what appears below concerns measurement and the small files a hosting platform sets by default. A reader who blocks every cookie can still read every page.
Why This Page Exists
A reader is entitled to know what a site stores in a browser before agreeing to it. The page lists the categories in plain terms, names the services involved, and sets out the effect of turning each category off. It is written to be read alongside the privacy policy rather than instead of it.
The page covers cookies and similar technologies, including a local storage entry and a pixel. Those work in different ways, but they raise the same question for a reader, which is what a site keeps and for how long. Grouping them here keeps the answer in one place.
What a Cookie Contains
A cookie holds a name, a value, a domain, a path, and an expiry. It does not hold a program, and it cannot read a file on a device. A cookie set by one site is not sent to another site, although a third-party service embedded in a page can set its own cookie under its own domain.
A first-party cookie belongs to the site in the address bar. A third-party cookie belongs to a service that the page loads, such as an analytics script or an embedded video. The distinction matters because a browser may block third-party cookies by default while allowing first-party ones.
Strictly Necessary Cookies
Some cookies are required for the site to work. They keep a session valid for an administrator, remember a security token, and route a request to the correct server. These cookies do not track a reader across pages for marketing, and they are not used to build a profile.
A necessary cookie cannot be switched off through a consent banner without breaking the function it supports. A reader can still block it in the browser, but the affected function may stop working. For a public reader, the necessary set is small and does not include a login.
Analytics Cookies
Analytics cookies count visits and show which pages are read. They help identify a page that fails to load or a topic that readers abandon. The reports are aggregate, and the site does not use them to contact a reader or to personalize a page.
Where an analytics service sets its own cookie, the service is named in the table on this page. A reader who does not want the measurement can block the cookie, and the page will still load. The visit simply goes uncounted.
Advertising Cookies
Where advertising appears, the advertiser may set a cookie to limit how often an advertisement is shown or to measure a click. The site does not control that cookie and does not receive the data it holds. An advertiser’s own policy governs the use of that data.
The site does not allow an advertiser to place a cookie that follows a reader to another site for the purpose of building an interest profile. A placement that requires such a cookie is declined, because it would contradict the privacy policy.
Third-Party Services
A page may load a font, a script, or an embedded document from another domain. That domain can set a cookie when the resource loads, even if the reader never clicks anything. The services used on this site are limited to hosting, security, analytics, and, where present, advertising.
A reader who wants to avoid third-party cookies can use a browser setting that blocks them or an extension that blocks the request before it leaves the device. The text of a page does not depend on a third-party script, so the content remains available.
Local Storage and Pixels
Local storage works like a cookie but holds more data and is not sent with every request. A site may use it to remember a preference, such as a dismissed notice. The site uses it sparingly, and a reader can clear it through the browser’s site data settings.
A pixel is a tiny image or script that reports that a page was viewed. Where a pixel is used, it reports an aggregate event rather than a name. A reader who blocks images from third parties stops most pixels without affecting the page text.
What Cookies Are Not Used For
The site does not use a cookie to collect a name, an email address, or a filing number. No cookie here follows a reader to a different site, and none of the data is offered for sale. Those limits are part of the design, not a setting a reader has to find.
The site also does not use a cookie to decide which page a reader sees or to change a described fee. Every reader sees the same text, which is the point of a reference page.
Managing Cookies in a Browser
Every major browser offers a settings panel for cookies. The panel usually allows a reader to view the cookies stored for a site, delete them, block third-party cookies, and clear all data on exit. The exact wording differs, but the choices are the same.
A reader who deletes a necessary cookie is signed out of an administrative session, which does not affect a public page. A reader who blocks all cookies may find that a preference is forgotten on the next visit. Neither outcome prevents reading.
Consent and Choice
Where a cookie is optional, the site asks for consent before setting it. A reader can refuse without losing access to the text. A refusal is remembered so that the question is not asked again on every page.
A reader can change a choice later by clearing the site data and reloading the page. The new choice replaces the old one, and the site does not treat an earlier consent as permanent. Consent for one category does not imply consent for another.
Effect of Blocking Cookies
Blocking cookies does not hide a page, change a fee, or prevent a link from working. It may stop a visit from being counted, and it may reset a preference such as a text size. For a reader who only wants the content, blocking is a reasonable choice with no real cost.
Blocking a security cookie on an administrative login would prevent access to the dashboard. That affects the publisher rather than a reader, and it is the reason the necessary category exists at all.
Duration and Retention
A session cookie expires when the browser closes. A persistent cookie carries a date and remains until that date or until the reader deletes it. The table on this page states the duration for each category, because a cookie that lasts a year deserves a different decision from one that lasts a session.
An analytics cookie is usually set for a shorter period than an advertising cookie. Where a service changes its default duration, the table is updated rather than left with an earlier figure.
Cookies and Email
An email does not set a cookie in the same way a page does. A tracking pixel inside a newsletter can report that a message was opened, but this site does not send a newsletter and does not place such a pixel in a reply. A message to the site is handled as described in the privacy policy.
A reader who clicks a link in an email and lands on the site is then subject to the cookies described here. The earlier email stage is governed by the mail provider, which has its own policy.
Do Not Track and Browser Controls
Browsers can transmit a request to opt out of tracking. Because nothing here follows a reader between sites, the request has no visible effect, and the page behaves the same either way. A reader who wants a stronger control can block third-party cookies, which stops most tracking before it starts.
Some browsers offer a privacy mode that clears cookies when the window closes. That mode is a practical way to read a reference page without leaving a stored entry, and it does not change what the page displays.
Changes to This Policy
The table and the descriptions are revised when a service is added, removed, or reconfigured. The revision date at the top of the page changes at the same time. A reader can ask which cookie was removed by name, and the answer will state the service and the date it stopped loading.
A change that adds a new optional cookie is announced before it is set, so that a reader can refuse it. A change that removes a service is noted in the same way, because a reader may want to clear the old data. The site disclaimer page covers the limits that apply to the content itself.
Contact Information
Questions about a cookie, a request to clarify a table entry, or a report of a cookie that is not listed can be sent to the address below. Name the page, the browser, and the cookie if it appears in the browser’s list. A reply will identify the service and the purpose.
- Website: kansascompanysearch.us
- Email: info@kansascompanysearch.us
