Company Search
Availability scan – Maryland registry data, results in seconds

Privacy Policy – Maryland Company Search

Privacy Policy for Maryland Company Search, effective from the date shown at the end of this page. The policy describes what the site collects, why it keeps the data, how long it stays, and the choices a reader has. It is written for a reader who wants the short answer first and the detail second, and it applies to every page on the domain.

The site is a reference publication, not an account-based service. A reader can use every article without registering, and no page asks for a payment card or a filing reference. The only personal data Maryland Company Search receives is the data a server records automatically and the data a reader chooses to send in a message.

Who This Policy Covers

The policy covers a visitor to the public pages, a reader who sends a message, and a person who appears in a message. It does not cover a state portal or a commercial service that a reader reaches through a link, because each of those runs under its own policy. A reader should read the destination’s notice before submitting information there.

What Information Is Collected

The site collects the request data that a web server records and the aggregate data that an analytics tool reports. It collects the content of a message when a reader sends one, along with the email address used. It does not collect a government identifier, a bank detail, or a copy of a document. No field on the site asks for a Social Security number.

The site does not collect a special category of data, such as a health detail or a political view, and it does not ask for one. A message that contains such a detail is answered and then deleted on request. A reader should send only the detail the question needs, because a message is stored for as long as the correction file stays open.

Information You Send

A message holds the email address, the text, and any attachment the reader chooses to add. The content is used to answer the question and to correct a page. It is not published without permission and is not added to a mailing list. A reader who sends a document by mistake can ask for its deletion, and the attachment is removed with the message.

Log Data

The server records the Internet Protocol address, the browser type, the operating system, the referring page, the page requested, and the time of the request. Those fields are standard for web hosting, and they are used to diagnose an error, measure load, and detect abusive traffic. The site does not use the log to build a profile of an individual reader, and the log is rotated on a short schedule.

The log is used in aggregate and in a spot check when a page reports an error. An address is not matched to a name, and a log line is not sold or shared with an advertiser. The hosting provider keeps its own copy for a short period under its contract, and that copy is deleted on the same schedule. A reader who wants to know whether an address appears in a log can ask.

Cookies and Similar Technologies

The site sets a small number of cookies. Some are needed for the publishing system to work, and some measure page use in aggregate. A cookie is a text file stored by the browser, and a reader can delete it at any time. The cookies policy lists each category, its purpose, and the effect of blocking it.

Analytics

Aggregate reports show which pages are read, how a reader arrives, and which device class is in use. The reports guide a revision and a layout change, and they do not identify a person. The site does not join an analytics record to an email address or to a message. A reader who blocks the script still sees every page.

How Information Is Used

The data is used to serve a page, to answer a message, to correct an error, to keep the service secure, and to measure which material is useful. It is not used to make an automated decision about a reader, and it is not used to build a profile for advertising. A commercial partner does not receive a reader’s message or email address.

A page view tells the site which article is useful; a message tells it which sentence is wrong. The two are not joined, because the site does not know which reader opened which page. That separation is deliberate, and it limits what the site can learn about a person. A reader who sends a message can ask what is held and receive a straight answer.

Legal Basis for Processing

The site processes log data on the basis of a legitimate interest in keeping the service available and secure. It processes a message because the reader asked for an answer. Where a cookie is not strictly necessary, the site asks for consent before it is set, and a reader can withdraw consent by clearing the stored choice and adjusting the browser setting.

Sharing and Disclosure

The site shares data with the hosting provider, which stores the log and serves the pages, and with the analytics provider, which produces the aggregate report. A legal request from a court or an agency is answered to the extent the law requires, and the site notifies the reader when it is allowed to do so. No data is sold.

A processor is bound by a contract that names the purpose and the retention period. A legal request is reviewed before any data is released, and a request that is too broad is narrowed where the law allows. The site does not disclose a reader’s message to a commercial partner, and it does not publish a list of readers. A transparency note is added to this page if the practice changes.

Service Providers

A provider acts on written instructions and is limited to the purpose named in the contract. The hosting provider cannot use a log for its own marketing, and the analytics provider cannot resell a report. A change of provider is described on the cookies policy page before the new script is enabled. A provider that cannot meet the terms is replaced.

The hosting provider holds the server log and the message store, and its staff can reach the data only through a support case. The analytics provider receives a page path and a device class, and it does not receive an email address. A provider that needs access for maintenance is bound by the same confidentiality term as the site, and the access is logged.

Data Retention

Server logs are kept for a short period, usually no more than ninety days, and are then deleted or aggregated. Analytics records are kept in aggregate form for a longer period because they show a trend across years. A message is kept while the correction file is open and for a further period so that a repeated question is answered consistently. A reader can ask for earlier deletion.

A backup copy may persist for a short period after a deletion, and it is overwritten on the normal cycle rather than restored. The site does not restore a deleted message from a backup to answer a later question. An aggregate record that no longer identifies a person may be kept for trend analysis, and it is separated from the message store.

Security

The site is served over an encrypted connection, and access to the publishing system is limited to the people who maintain the pages. A password is held by the content management system in hashed form, and administrative access uses a second factor where the platform supports it. No system is perfectly secure, and the site does not claim otherwise. A suspected breach is investigated and disclosed where the law requires it.

Your Rights

A reader can ask what data the site holds, ask for a copy, ask for a correction, ask for deletion, or object to a processing activity. A reader can also ask that a processing activity be restricted while a request is reviewed. A request is answered within thirty days, and the site may ask for enough detail to locate the record. There is no charge unless a request is clearly unfounded or repetitive.

A request is verified with the email address used in the original message, and no other proof is demanded for a routine request sent through the contact page. A request made by a third party on a reader’s behalf needs written authority. The site answers in plain language and sets out any part of a request it cannot meet, rather than leaving the reader to guess.

Children

The site is written for adults who are researching a business, and it is not directed at a child under thirteen. It does not knowingly collect data from a child and does not run a feature that invites a child to submit information. A parent who believes a child has sent a message can ask for its deletion, and the request is honored.

International Visitors

The site is operated in the United States, and the data described here is stored on servers in that country. A reader who visits from another country accepts that the data is transferred to the United States. Where a local law grants an additional right, the site honors a reasonable request that matches the spirit of this policy.

External Links

An outbound click leaves this domain for a destination that the site does not control. The destination sets its own cookies and its own retention rule, and a reader should read its notice before submitting information. The site does not pass a reader’s message or email address to a linked destination.

A link is checked before it is published, and a destination that has moved is replaced rather than left broken. The site does not embed a third-party widget that would contact another server on load, and a linked destination is opened only on a click. A destination that changes its practice is reviewed, and the link is removed if the new practice is not acceptable.

Do Not Track

The site reads a browser’s Do Not Track signal where the platform supports it and limits analytics when the signal is present. A reader can also use a blocker, a private window, or a browser setting to reduce tracking. The site does not attempt to override a browser signal with a hidden script.

Changes to This Policy

When the policy changes, the new version appears here and the effective date moves forward. A shift in the categories of data or in the sharing arrangements is flagged in a short note at the top for a month. A reader who keeps using the site after that date is treated as having accepted the update, and a reader who does not agree can stop visiting and ask for deletion of a stored message.

Contact Information

Questions about this policy, a request for a copy of the data held, or a request for deletion can be sent to the address below. State the email address that was used and the action requested, and the reply will confirm what was done. A question about a page rather than personal data can go to the same address.

  • Website: marylandcompanysearch.us
  • Email: info@marylandcompanysearch.us