Our website address is: https:\/\/www.wounded-heroes.org.<\/p>\n\n\n\n
When 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.<\/p>\n\n\n\n
An 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.<\/p>\n\n\n\n
If 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.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
If 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.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
If 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.<\/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
If 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.<\/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
Visitor comments may be checked through an automated spam detection service.<\/p>\n\n\n\n
European 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.<\/p>\n\n\n\n
Suggested text: <\/strong>Visitor comments may be checked through an automated spam detection service.<\/p>\n\n\n\n In 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.<\/p>\n\n\n\n If 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.<\/p>\n\n\n\n In 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.<\/p>\n\n\n\n In 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.<\/p>\n\n\n\n If 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.<\/p>\n\n\n\n If your web site provides a service which includes automated decision making – for example, allowing customers to apply for credit, or aggregating their data into an advertising profile – 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.<\/p>\n\n\n\n If 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.<\/p>\n\n\n\n This sample language includes the basics around what personal data your store may be collecting, storing and sharing, as well as who may have access to that data. Depending on what settings are enabled and which additional plugins are used, the specific information shared by your store will vary. We recommend consulting with a lawyer when deciding what information to disclose on your privacy policy.<\/p>\n\n\n\n We collect information about you during the checkout process on our store.<\/p>\n\n\n\n While you visit our site, we\u2019ll track:<\/p>\n\n\n\n We\u2019ll also use cookies to keep track of cart contents while you\u2019re browsing our site.<\/p>\n\n\n\n Note: you may want to further detail your cookie policy, and link to that section from here.<\/p>\n\n\n\n When you purchase from us, we\u2019ll ask you to provide information including your name, billing address, shipping address, email address, phone number, credit card\/payment details and optional account information like username and password. We\u2019ll use this information for purposes, such as, to:<\/p>\n\n\n\n If you create an account, we will store your name, address, email and phone number, which will be used to populate the checkout for future orders.<\/p>\n\n\n\n We generally store information about you for as long as we need the information for the purposes for which we collect and use it, and we are not legally required to continue to keep it. For example, we will store order information for XXX years for tax and accounting purposes. This includes your name, email address and billing and shipping addresses.<\/p>\n\n\n\n We will also store comments or reviews, if you choose to leave them.<\/p>\n\n\n\n Members of our team have access to the information you provide us. For example, both Administrators and Shop Managers can access:<\/p>\n\n\n\n Our team members have access to this information to help fulfill orders, process refunds and support you.<\/p>\n\n\n\n In this section you should list who you\u2019re sharing data with, and for what purpose. This could include, but may not be limited to, analytics, marketing, payment gateways, shipping providers, and third party embeds.<\/p>\n\n\n\n We share information with third parties who help us provide our orders and store services to you; for example —<\/p>\n\n\n\n In this subsection you should list which third party payment processors you\u2019re using to take payments on your store since these may handle customer data. We\u2019ve included PayPal as an example, but you should remove this if you\u2019re not using PayPal.<\/p>\n\n\n\n We accept payments through PayPal. When processing payments, some of your data will be passed to PayPal, including information required to process or support the payment, such as the purchase total and billing information.<\/p>\n\n\n\nYour contact information<\/h2>\n\n\n\n
Additional information<\/h2>\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
What third parties we receive data from<\/h3>\n\n\n\n
What automated decision making and\/or profiling we do with user data<\/h3>\n\n\n\n
Industry regulatory disclosure requirements<\/h3>\n\n\n\n
What we collect and store<\/h2>\n\n\n\n
Who on our team has access<\/h2>\n\n\n\n
What we share with others<\/h2>\n\n\n\n
Payments<\/h3>\n\n\n\n