Cookies Policy for Michigan Company Search. This page lists the cookies the site sets, the purpose of each category, how long a cookie lasts, and the choices a reader has. It is written alongside the privacy policy, which covers the other data the site receives. A cookie is a small text file that a site stores in a browser, and it is neither a program nor a virus.
The site keeps the number of cookies small. Most readers will meet only the cookies the publishing platform needs and the cookies that measure page use in aggregate. No cookie set by Michigan Company Search stores a name, an email address, or a filing reference, and none is used to build an individual advertising profile.
Why This Page Exists
A reader is entitled to know what a site stores on a device before the site does it. This page names the categories, the providers, and the duration, so that a reader can decide whether to allow them. It also sets out what happens when a category is blocked, because a blocked cookie can change how a page behaves, and the privacy policy covers the data that sits outside a cookie.
What a Cookie Contains
A cookie carries a short value that a site can read on a later request. It can remember that a browser has seen a notice, keep a publishing session open, or tell an analytics tool that a page was viewed. A cookie cannot read a file on a device and cannot install software. A reader who clears cookies removes the stored values, and a site may then treat the browser as a new visitor.
Strictly Necessary Cookies
The publishing platform sets cookies that keep a session working and protect a form submission against a cross-site request. Those cookies are needed for the site to function, and blocking them can prevent a page from loading correctly or a message from being sent. They do not track a reader across other sites, and they expire when the session ends or within a short period.
One cookie keeps a form token valid for a short period, and another keeps a publishing session alive for an editor. Neither carries a reader’s message content. A cookie of this kind is set even before a consent choice, because the site cannot serve a form safely without it. A reader who blocks it can still read every article and can reach the site by email instead.
Analytics Cookies
Analytics cookies record a page view, the referring source, and the device class in aggregate. The reports show which articles are read and which pages need revision, and they do not identify an individual. A reader who blocks the analytics script still sees every page, and the site records one fewer view. The analytics cookie usually lasts for a session or for a short fixed period.
The report is read once a month to see which pages are growing and which are being abandoned. A page that loses readers is revised rather than deleted, and a page that draws a repeated question gets a new section. The metrics are counts, not identities, and the site does not use them to target a message or an advertisement.
Advertising Cookies
The site does not set an advertising cookie itself and does not run a behavioral advertising network. A page may carry a link to a commercial service, and the destination may set its own cookie when a reader clicks. No message and no email address travels with the click, and the destination’s own notice governs the visit.
Third-Party Services
A third-party cookie is set by a domain other than this one. The analytics tool and a linked destination are the two sources a reader may meet. The site does not control the duration or the content of a third-party cookie, and a change to a provider’s policy appears on the provider’s own page. The site reviews a provider before it is used and avoids one that resells reader data.
A provider is reviewed before it is enabled, and the review covers the retention period, the sub-processors, and the sale of data. A provider that cannot answer a question about retention is not used. The site keeps a short internal note of the review so that a later change can be compared with the original terms.
Local Storage and Pixels
The site does not use a tracking pixel in an email and does not store a reader’s data in local storage beyond what the publishing platform needs for a form. A pixel is a tiny image that reports an open, and a reader who blocks images blocks it. Local storage is cleared with the browser’s site data, in the same way as a cookie.
A consent choice may be stored in the browser’s local storage rather than in a cookie, and it is cleared with the same site data control. The site does not use a pixel in a page, and it does not use one in a reply. A reader who clears site data removes the choice and sees the banner again on the next visit.
What Cookies Are Not Used For
The site does not use a cookie to fingerprint a device, to read a canvas image, or to follow a reader from one site to another. It does not set a cookie that stores a name, an email address, or a search term. It does not run a retargeting tag for a retailer or a data broker. A reader who sees such a cookie on a page should report it.
Managing Cookies in a Browser
Every major browser allows a reader to view, block, and delete cookies. The setting usually sits under privacy or site data, and it can be applied to all sites or to this one. A private window discards cookies when it closes, which is a simple way to test the site without leaving a record. A blocker extension allows finer control.
A phone browser usually hides the setting under privacy or under the site settings for a single domain. A reader can clear the data for this site without clearing the rest, which keeps other sessions intact. After a clear, the consent banner returns and the analytics script starts again unless the reader blocks it.
Consent and Choice
Where a consent banner appears, the choice is stored in a cookie so that the site does not ask on every page. The record holds the category that was accepted and the date, and it does not hold an identity. A reader can change the choice through the link in the banner or by clearing the stored choice, and the banner returns after a clear.
Effect of Blocking Cookies
Blocking the necessary cookies can prevent a page from saving a form entry and can end a publishing session. Blocking analytics has no visible effect. Blocking a third-party cookie may change what a linked destination remembers about a visit. The article text remains available in every case, and the site does not degrade a page on purpose when a cookie is missing.
A blocked form can be replaced by an email, and a blocked session only affects an editor rather than a reader. A page does not show an error when a cookie is missing, and the article text is never hidden behind a consent wall. The site tests the main pages with cookies blocked before a release so that a reader is not trapped.
Duration and Retention
A session cookie is removed when the browser closes. A persistent cookie stays for a fixed period, which may run from a day to a year depending on its purpose. The analytics cookie is usually short, while a consent cookie lasts longer so that the reader is not asked again on every visit. The exact duration is visible in the browser’s cookie list.
A cookie that carries a consent choice is refreshed when the policy changes, so an old choice does not outlive the notice it answered. An expired cookie is ignored rather than renewed. The site does not extend a cookie lifetime without a corresponding change to this page, and the browser list remains the authority on what is stored.
Cookies and Email
The contact route does not set a cookie beyond the one that validates the form. A message is sent over an encrypted connection and stored on the server under the privacy policy. Clearing the browser store after sending does not remove the message, and a deletion request has to arrive by email. A reply does not carry a tracking pixel.
Do Not Track and Browser Controls
When the platform supports a Do Not Track header, the site trims its analytics for that visit. A blocker, a private window, or a profile that wipes data on exit gives a reader more control still. No hidden script is used to work around a browser choice, and a blocked script is not fetched from a second domain.
Changes to This Policy
If the cookie list or a provider changes, this page is updated and the date at the top moves. A new category is flagged in a note above the list for a month, and the terms and conditions govern the rest of the arrangement. Browsing on after the update counts as acceptance, and a reader can withdraw a consent at any time by clearing the stored choice and setting the browser to block the category.
Contact Information
For a cookie question, a consent withdrawal, or a category that should not be set, write to the address below. Give the browser and the page, and describe the entry that appeared. A report about a cookie that is not on this list is treated as a priority, because it would sit outside the policy.
- Website: michigancompanysearch.us
- Email: info@michigancompanysearch.us
