Rosenberg Responds

Legal Disclaimer

The City of Rosenberg (City) Web site,, is provided as a public service.  This site is managed by the City’s Information Services Division (IS).  PLEASE NOTE that users of this Web site are responsible for checking the accuracy, completeness, currency and/or suitability of all information.  The City makes no representations, guarantees, or warranties as to the accuracy, completeness, currency and/or suitability of the information provided via this Web site.  IS specifically disclaims any and all liability for any claims or damages that may result from providing the City Web site or the information it contains, including any Web sites maintained by third parties and linked to the City Web site.  The responsibility for contents rests with the organizations that are providing the information.  The inclusion of links from this site does not imply endorsement by the MIS or the City.  Specific questions regarding a document should be directed to the appropriate organization and not necessarily to the City Webmaster.  The City makes no effort to independently verify, and does not exert additional  editorial control over, information on pages outside of the “” domain.  The City does not endorse any of the products, vendors, consultants, or documentation referenced in the Web site.  Any mention of vendors, products, or services is for informational purposes only.  The City does not collect or track personal information from the City Web site visitors.  Generic information from server logs may be used to track the number of hits to the site and to find out what types of browser software are used by visitors.  This information will be used only in aggregate form, and use for solely for improving Web site design.  Please review the following City of Rosenberg Privacy Policy Notice for futher

Privacy Statement

The city of Rosenberg (City) Information Services Division maintains the City’s Web site as a public service.  The following is the privacy policy for this site (all pages starting with The City does not use cokes to collect information.  Note: a cookie file contains unique information a Web site can use to track such things as passwords, lists of pages you’ve visited, and the date when you last looked at a specific page or to identify your session at a particular Web site.  A cookie is often used in commercial sites to identify the items selected for a specific shopping cart application.  If you send the City an electronic mail message with a question or comment that contain personally identifying information, or fill out a form that e-mails us this information, we will only use the personally identifying information to respond to your request and analyze trends.  We may redirect your message to another county or person whi is in a better position to answer your question.  For site management functions, information is collected for analysis and statistical purposes.  This information is not reported or used in any manner that would reveal personally identifiable information, and will not be released to any outside parties unless legally required to do so in connection with law enforcement investigations or other legal proceedings.  We use log analysis tools to create summary statistics, which are used for purposes such as assessing what information is of most interest, determining technical design specifications, and identifying system performance or problem areas.  The following information is collected for this analysis: User Client hostname – The hostname (or IP address if DNS is disabled) of the user/client requesting access; HTTP header, “user agent” – The user-agent information includes the type of browser, its version, and the operating system it’s running on, HTTP header, “referrer” – The referrer specifies the page from which the client access the current page; System date – The date and time of the user/client request; Full request – The exact request the user/client made; Status – The status code the server returned to the user/client; Content length – The content length, in bytes, of the document sent to the user/client; Method – The request method used; Universal Resource Identifyier (URI) – The location of a resource on the server; Query string of the URI – Anything after the question mark in a URI.  Protocol – The transport protocol and version used.  Questions should be directed to

Printer Friendly Versionprinter friendly

Powered by the PIER System