{"id":3,"date":"2024-01-22T10:03:15","date_gmt":"2024-01-22T10:03:15","guid":{"rendered":"https:\/\/riskknowhow.org\/?page_id=3"},"modified":"2024-02-15T14:51:30","modified_gmt":"2024-02-15T14:51:30","slug":"privacy-policy","status":"publish","type":"page","link":"https:\/\/riskknowhow.org\/privacy-policy\/","title":{"rendered":"Privacy policy"},"content":{"rendered":"\n
SAS TO REVIEW AND FINALISE FOR LAUNCH<\/strong><\/p>\n\n\n\n Our website address is: https:\/\/riskknowhow.org\/<\/a><\/p>\n\n\n\n Like most websites this website use \u2018cookies\u2019. These are small data files which are stored on your device in order to improve the functionality and management of the site.<\/p>\n\n\n\n Below is an explanation of the cookies we use on this site and elsewhere, and how we manage this information. As these cookies are commonly used across the web, we recommend disabling cookies in your browser if you do not wish them to be installed on your device.<\/p>\n\n\n\n We use Google Analytics to record anonymised data about how this website is used. This enables us to measure how many people use the website, how they reach the site, and what pages they visit.<\/p>\n\n\n\n This information helps us improve the website by understanding how people use it, and also enables us to report to funders about how well the site is performing.<\/p>\n\n\n\n Google Analytics does not allow us to view individual user details; it only enables us to analyse patterns of behaviour across multiple users. It collects users\u2019 IP addresses, but solely for the purpose of analysing where in the world people are using this site.<\/p>\n\n\n\n This website is built with WordPress. This relies on cookies for basic management tasks, such as identifying whether a user is logged into the website.<\/p>\n\n\n\n The Cookie Consent plugin uses cookies to identify whether a user has seen the pop-up notification.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.<\/p>\n\n\n\n We use the personal information you provide us to ensure that any services or information you have requested can be fulfilled.<\/p>\n\n\n\n We do not share your personal information with anyone.<\/strong><\/p>\n\n\n\n If you asked to receive more information about our activities and news, we will use the personal contact information you provided to stay in touch with you.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n Your data is secured by encryption, firewalls and Secure Socket Layer (SSL) technology. This is industry standard encryption technology which manages the security of messages transmitted across the internet. When we receive your data, we store it on secure servers which can only be accessed by the web developer Surface Impression<\/strong><\/a>.<\/p>\n\n\n\n Data breaches are rare but in the case of this happening they will pinpoint the exact details of the breach including the time, where it happened on the system, the cause of the breach, and the extent of the damage.<\/p>\n\n\n\n Additional security measures are monitored by the hosting provider.<\/p>\n","protected":false},"excerpt":{"rendered":" SAS TO REVIEW AND FINALISE FOR LAUNCH Who we are Our website address is: https:\/\/riskknowhow.org\/ Cookies Like most websites this website use \u2018cookies\u2019. These are small data files which are stored on your device in order to improve the functionality and management of the site. Below is an explanation of the cookies we use on […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":14,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_seopress_robots_primary_cat":"","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","footnotes":""},"acf":{"title_override":"","header_image":"","header_text_colour":"White"},"_links":{"self":[{"href":"https:\/\/riskknowhow.org\/wp-json\/wp\/v2\/pages\/3"}],"collection":[{"href":"https:\/\/riskknowhow.org\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/riskknowhow.org\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/riskknowhow.org\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/riskknowhow.org\/wp-json\/wp\/v2\/comments?post=3"}],"version-history":[{"count":3,"href":"https:\/\/riskknowhow.org\/wp-json\/wp\/v2\/pages\/3\/revisions"}],"predecessor-version":[{"id":1664,"href":"https:\/\/riskknowhow.org\/wp-json\/wp\/v2\/pages\/3\/revisions\/1664"}],"wp:attachment":[{"href":"https:\/\/riskknowhow.org\/wp-json\/wp\/v2\/media?parent=3"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Who we are<\/h2>\n\n\n\n
Cookies<\/h2>\n\n\n\n
Google Analytics<\/h3>\n\n\n\n
\n
WordPress<\/h3>\n\n\n\n
Embedded content from other websites<\/h2>\n\n\n\n
Who we share your data with<\/h2>\n\n\n\n
How long we retain your data<\/h3>\n\n\n\n
What rights you have over your data<\/h3>\n\n\n\n
Data protection laws provide you with the following rights to:<\/h5>\n\n\n\n
\n
How we protect your data<\/h3>\n\n\n\n
What data breach procedures we have in place<\/h3>\n\n\n\n