Your privacy is critically important to us. At LB LounsBury Group we have a few fundamental principles:
- We don’t ask you for personal information unless we truly need it. (We can’t stand services that ask you for things like your gender or income level for no apparent reason.)
- We don’t share your personal information with anyone except to comply with the law, develop our products, or protect our rights.
- We don’t store personal information on our servers unless required for the on-going operation of one of our services.
- In our blogging products, we aim to make it simple for you to control what’s visible to the public, seen by search engines, kept private, and permanently deleted.
If you have questions about deleting or correcting your personal data please contact our support team.
LB LounsBury Group (“Lounsbury”) operates several websites including lounsburyrealestate.com and lgconstruction.ca. It is Lounsbury’s policy to respect your privacy regarding any information we may collect while operating our websites.
Like most website operators, Lounsbury collects non-personally-identifying information of the sort that web browsers and servers typically make available, such as the browser type, language preference, referring site, and the date and time of each visitor request. Lounsbury’s purpose in collecting non-personally identifying information is to better understand how Lounsbury’s visitors use its website. From time to time, Lounsbury may release non-personally-identifying information in the aggregate, e.g., by publishing a report on trends in the usage of its website.
Lounsbury also collects potentially personally-identifying information like Internet Protocol (IP) addresses for logged in users and for users leaving comments on WordPress.com blogs. Lounsbury only discloses logged in user and commenter IP addresses under the same circumstances that it uses and discloses personally-identifying information as described below, except that blog commenter IP addresses and email addresses are visible and disclosed to the administrators of the blog where the comment was left.