At the Wildlife Trust for Lancashire, Manchester and North Merseyside (LWT) we respect your privacy and do not disclose members' information to third parties unless it is for the purpose of the delivery of goods or services such as magazines, newsletters or welcome calls. When you complete a registration form with LWT, we collect your name, mailing address, email address and telephone number for contact purposes. We also maintain a record of our contact with you, should we or you ever need this for reference.
The Way We Use Information
We use the information you provide for the purpose of contacting you for the following reasons
- Administering your membership, donations or legacies
- Fulfilment of orders for goods and services
- Communications about conservation and campaigns
- Fundraising
- Member satisfaction surveys / research
We do not share this information with outside parties except to the extent necessary to get any information or material to you.
Consent
By providing personal data you consent to its processing as described in this Privacy Policy. We respect your privacy and will not sell your personal data to any third party.
If you wish to opt out of certain communications please contact the membership department: 01772 324129 email: membership@lancswt.org.uk, in person or post: The Barn, Berkely Drive, Bamber Bridge. Preston PR5 6BY. This would not affect your magazine or event guide mailings, unless specified.
Access To Your Own Information
You can contact us anytime by letter or telephone to change or update your details, or obtain a copy of your record. If you have any problems or queries about your data, please contact us.
Financial Security
All LWT forms which request credit card or bank details use the SSL (Secure Sockets Layer) protocol for encryption. Most browsers (Microsoft Explorer, Mozilla Firefox, Safari, etc) support SSL. The link between your browser and the server is secure if your browser displays a small padlock or key symbol somewhere in the frame, or the address bar shows a web address beginning https:// (rather than http://).
