{"id":895,"date":"2020-06-02T22:12:55","date_gmt":"2020-06-02T13:12:55","guid":{"rendered":"https:\/\/lab3d.kw.ac.kr\/?page_id=895"},"modified":"2020-06-02T23:24:04","modified_gmt":"2020-06-02T14:24:04","slug":"privacy-information","status":"publish","type":"page","link":"https:\/\/lab3d.kw.ac.kr\/ko\/privacy-information\/","title":{"rendered":"Privacy Information"},"content":{"rendered":"\nWho we are\n\nOur website address is: https:\/\/lab3d.kw.ac.kr.\n\nWhat personal data we collect and why we collect it\nIn this section you should note what personal data you collect from users and site visitors. This may include personal data, such as name, email address, personal account preferences; transactional data, such as purchase information; and technical data, such as information about cookies.\n\nPersonal data is not just created by a user\u2019s interactions with your site. Personal data is also generated from technical processes such as contact forms, comments, cookies, analytics, and third party embeds.\n\nBy default WordPress does not collect any personal data about visitors, and only collects the data shown on the User Profile screen from registered users. However some of your plugins may collect personal data. You should add the relevant information below.\n\nComments\nIn this subsection you should note what information is captured through comments. We have noted the data which WordPress collects by default.\n\nSuggested text:\nWhen visitors leave comments on the site we collect the data shown in the comments form, and also the visitor\u2019s IP address and browser user agent string to help spam detection.\n\nAn anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https:\/\/automattic.com\/privacy\/. After approval of your comment, your profile picture is visible to the public in the context of your comment.\n\nMedia\nIn this subsection you should note what information may be disclosed by users who can upload media files. All uploaded files are usually publicly accessible.\n\nSuggested text:\nIf you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.\n\nContact forms\nBy default, WordPress does not include a contact form. If you use a contact form plugin, use this subsection to note what personal data is captured when someone submits a contact form, and how long you keep it. For example, you may note that you keep contact form submissions for a certain period for customer service purposes, but you do not use the information submitted through them for marketing purposes.\n\nCookies\nIn this subsection you should list the cookies your web site uses, including those set by your plugins, social media, and analytics. We have provided the cookies which WordPress installs by default.\n\nSuggested text:\nIf 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.\n\nIf you visit our login page, 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.\n\nWhen 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 &#8220;Remember Me&#8221;, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.\n\nIf you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.\n\nEmbedded content from other websites\nSuggested text:\nArticles 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.\n\nThese 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.\n\nAnalytics\nIn this subsection you should note what analytics package you use, how users can opt out of analytics tracking, and a link to your analytics provider\u2019s privacy policy, if any.\n\nBy default WordPress does not collect any analytics data. However, many web hosting accounts collect some anonymous analytics data. You may also have installed a WordPress plugin that provides analytics services. In that case, add information from that plugin here.\n\nWho we share your data with\nIn this section you should name and list all third party providers with whom you share site data, including partners, cloud-based services, payment processors, and third party service providers, and note what data you share with them and why. Link to their own privacy policies if possible.\n\nBy default WordPress does not share any personal data with anyone.\n\nHow long we retain your data\nIn this section you should explain how long you retain personal data collected or processed by the web site. While it is your responsibility to come up with the schedule of how long you keep each dataset for and why you keep it, that information does need to be listed here. For example, you may want to say that you keep contact form entries for six months, analytics records for a year, and customer purchase records for ten years.\n\nSuggested text:\nIf you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.\n\nFor 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.\n\nWhat rights you have over your data\nIn this section you should explain what rights your users have over their data and how they can invoke those rights.\n\nSuggested text:\nIf 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.\n\nWhere we send your data\nIn this section you should list all transfers of your site data outside the European Union and describe the means by which that data is safeguarded to European data protection standards. This could include your web hosting, cloud storage, or other third party services.\n\nEuropean data protection law requires data about European residents which is transferred outside the European Union to be safeguarded to the same standards as if the data was in Europe. So in addition to listing where data goes, you should describe how you ensure that these standards are met either by yourself or by your third party providers, whether that is through an agreement such as Privacy Shield, model clauses in your contracts, or binding corporate rules.\n\nSuggested text:\nVisitor comments may be checked through an automated spam detection service.\n\nYour contact information\nIn this section you should provide a contact method for privacy-specific concerns. If you are required to have a Data Protection Officer, list their name and full contact details here as well.\n\nAdditional information\nIf you use your site for commercial purposes and you engage in more complex collection or processing of personal data, you should note the following information in your privacy policy in addition to the information we have already discussed.\n\nHow we protect your data\nIn this section you should explain what measures you have taken to protect your users\u2019 data. This could include technical measures such as encryption; security measures such as two factor authentication; and measures such as staff training in data protection. If you have carried out a Privacy Impact Assessment, you can mention it here too.\n\nWhat data breach procedures we have in place\nIn this section you should explain what procedures you have in place to deal with data breaches, either potential or real, such as internal reporting systems, contact mechanisms, or bug bounties.\n\nWhat third parties we receive data from\nIf your web site receives data about users from third parties, including advertisers, this information must be included within the section of your privacy policy dealing with third party data.\n\nWhat automated decision making and\/or profiling we do with user data\nIf your web site provides a service which includes automated decision making &#8211; for example, allowing customers to apply for credit, or aggregating their data into an advertising profile &#8211; you must note that this is taking place, and include information about how that information is used, what decisions are made with that aggregated data, and what rights users have over decisions made without human intervention.\n\nIndustry regulatory disclosure requirements\nIf you are a member of a regulated industry, or if you are subject to additional privacy laws, you may be required to disclose that information here.\n\n\u2191 Return to Top\nCopy this section to clipboardCopy suggested policy text from WordPress.\n \nSource: h5p\nWhat personal data we collect and why we collect it\nH5P\nSuggested text (&#8220;We&#8221; and &#8220;our&#8221; mean &#8220;you&#8221;, not &#8220;us&#8221;!):\n\nWe may process and store personal data about your interactions using xAPI. We use the data to learn about how well the interactions are designed and how it could be adapted to improve the usability and your learning outcomes. The data is processed and stored [on our platform|on an external platform] until further notice.\n\nWe may store the results of your interactions on our platform until further notice. The results may contain your score, the maximum score possible, when you started, when you finished, and how much time you used. We use the results to learn about how well you performed and to help us give you feedback.\n\nWe may store interactive content that you create on our platform. We also may send anonymized reports about content creation without any personal data to the plugin creators. Please consult the H5P tracking information page for details.\n\nIf you use interactive content that contains a video that is hosted on YouTube, YouTube will set cookies on your computer. YouTube uses these cookies to help them and their partners to analyze the traffic to their websites. Please consult Google&#8217;s Privacy policy for details. It is our legitimate interest to use YouTube, because we we need their services for our interactive content and would not be able to provide you with their video content features otherwise.\n\nIf you use interactive content that contains a Twitter feed, Twitter will set a cookie on your computer. Twitter uses these cookies to help them and their partners to make their advertizing more relevant to you. Please consult Twitter&#8217;s Privacy policy for details. It is our legitimate interest to use Twitter, because we need their services for our interactive content and would not be able to provide you with it otherwise.\n\nIf you use interactive content that contains speech recognition, Google Cloud will process your voice for converting it to text. Please consult Google&#8217;s Privacy policy for details. It is our legitimate interest to use Google Cloud, because we we need their services for our interactive content and would not be able to provide you with speech recognition features otherwise.\n\n\u2191 Return to Top\nCopy this section to clipboardCopy suggested policy text from h5p.\n \nSource: H5PxAPIkatchu\nWhat personal data we collect and why we collect it\nH5PxAPIkatchu\nWhen you use interactive content, we may collect data about your interaction using xAPI. The data may e.g. contain what answer was given, how long it took to answer, what score was achieved, etc. We use the data to learn about how well the interaction is designed and how it could be adapted to improve the usability and learning outcomes in general.\n\nHowever, if and only if you are logged in, this data will be tied to your full name, your email address, and your WordPress user id. In consequence, your interactions could be linked to you. Therefore, all personal data can be stripped to anonymize the data.\n<div style=\"text-align:right\">\n        <div class=\"share\">        \n            <a href=\"javascript:shareMessage('https:\/\/lab3d.kw.ac.kr\/ko\/privacy-information\/')\">\n            <img decoding=\"async\" src=\"https:\/\/lab3d.kw.ac.kr\/wp-content\/plugins\/kakao-tam\/icon\/kakaotalk_sharing_btn_small.png\"\n            alt=\"\uce74\uce74\uc624\ud1a1 \uacf5\uc720 \ubc84\ud2bc\" \/>\n            <\/a>    \n        <\/div>            \n    <\/div>","protected":false},"excerpt":{"rendered":"<p>Who we are Our website address is: https:\/\/lab3d.kw.ac.kr. What personal data we collect and why we collect it In this section you should note what&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_crdt_document":"","footnotes":""},"class_list":["post-895","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/lab3d.kw.ac.kr\/ko\/wp-json\/wp\/v2\/pages\/895","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lab3d.kw.ac.kr\/ko\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/lab3d.kw.ac.kr\/ko\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/lab3d.kw.ac.kr\/ko\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lab3d.kw.ac.kr\/ko\/wp-json\/wp\/v2\/comments?post=895"}],"version-history":[{"count":3,"href":"https:\/\/lab3d.kw.ac.kr\/ko\/wp-json\/wp\/v2\/pages\/895\/revisions"}],"predecessor-version":[{"id":908,"href":"https:\/\/lab3d.kw.ac.kr\/ko\/wp-json\/wp\/v2\/pages\/895\/revisions\/908"}],"wp:attachment":[{"href":"https:\/\/lab3d.kw.ac.kr\/ko\/wp-json\/wp\/v2\/media?parent=895"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}