Who we are
We are the Kilnworx Climbing Centre, a Community Interest Company regulated by the Community Interest Companies regulator.
For any privacy-related questions, you can reach us at firstname.lastname@example.org.
What personal data we collect and why we collect it
Users that email us, or use any of the contact forms on our website, will have their email address, IP address, and any data provided in the contact form or body of the email stored.
We keep some communication indefinitely to help us provide support and improve our services. Individuals can request copies of any previous correspondence with us at any time.
Online Ordering and Booking
Users that order online with us will need to provide contact details so that we process the order.
We use Stripe.com to process our online payments, this is a third party payment gateway and the Kilnworx Climbing Centre does not see, retain or have any access to your credit/debit card details.
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you have an account and you log in to this site, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
Who we share your data with
We don’t ask you for personal information unless we truly need it.
We don’t share your personal information with anyone except to comply with the law or protect our rights.
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognise and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
How we protect your data
The security and reliability of our service is our number one priority. We train our staff and invest in our infrastructure to ensure that best practices are followed in everything that we do.
See wordpress.org/about/security for details on the security of the WordPress core itself.
What data breach procedures we have in place
Should any event occur where customer data has been lost, stolen, or potentially compromised, our policy is to alert our customers via email no later than 48 hours of our team becoming aware of the event. We will also report such incident to any required data protection authority. We will work closely with any customers affected to determine next steps such as any end-user notifications, needed patches, and how to avoid any similar event in the future.