Privacy Statement (UK)

This privacy statement was last updated on 11/05/2021 and applies to citizens and legal permanent residents of the United Kingdom.

In this privacy statement, we explain what we do with the data we obtain about you via https://legaltechnology.com. We recommend you carefully read this statement. In our processing we comply with the requirements of privacy legislation. That means, among other things, that:

  • we clearly state the purposes for which we process personal data. We do this by means of this privacy statement;
  • we aim to limit our collection of personal data to only the personal data required for legitimate purposes;
  • we first request your explicit consent to process your personal data in cases requiring your consent;
  • we take appropriate security measures to protect your personal data and also require this from parties that process personal data on our behalf;
  • we respect your right to access your personal data or have it corrected or deleted, at your request.

If you have any questions, or want to know exactly what data we keep of you, please contact us.

1. Purpose, data and retention period

2. Cookies

Our website uses cookies. For more information about cookies, please refer to our Cookie Policy. We have concluded a data processing agreement with Google.Google may not use the data for any other Google services.

3. Security

We are committed to the security of personal data. We take appropriate security measures to limit abuse of and unauthorised access to personal data. This ensures that only the necessary persons have access to your data, that access to the data is protected, and that our security measures are regularly reviewed.

4. Third-party websites

This privacy statement does not apply to third-party websites connected by links on our website. We cannot guarantee that these third parties handle your personal data in a reliable or secure manner. We recommend you read the privacy statements of these websites prior to making use of these websites.

5. Amendments to this privacy statement

We reserve the right to make amendments to this privacy statement. It is recommended that you consult this privacy statement regularly in order to be aware of any changes. In addition, we will actively inform you wherever possible.

6. Accessing and modifying your data

If you have any questions or want to know which personal data we have about you, please contact us. You can contact us by using the information below. You have the following rights:

  • You have the right to know why your personal data is needed, what will happen to it, and how long it will be retained for.
  • Right of access: You have the right to access your personal data that is known to us.
  • Right to rectification: you have the right to supplement, correct, have deleted or blocked your personal data whenever you wish.
  • If you give us your consent to process your data, you have the right to revoke that consent and to have your personal data deleted.
  • Right to transfer your data: you have the right to request all your personal data from the controller and transfer it in its entirety to another controller.
  • Right to object: you may object to the processing of your data. We comply with this, unless there are justified grounds for processing.

Please make sure to always clearly state who you are, so that we can be certain that we do not modify or delete any data of the wrong person.

7. Automated decision-making

We make decisions on the basis of automated processing with respect to matters that may have (significant) consequences for individuals. These are decisions taken by computer programmes or systems without human intervention.

When a Legal IT Insider reader agrees becomes an identified subscriber and agrees to our policies, we will begin to create profiles of how they engage with our content and editorial on www.legaltechnology.com in doing so we will be able to better develop bespoke editorial content that is highly targeted and relevant to each individual reader. We do not broker our data, databases, readership or subscriber detail and we do not publish any paid for or sponsored content in keeping with our editorial policy found at www.legaltechnology.com/privacy

8. Submitting a complaint

If you are not satisfied with the way in which we handle (a complaint about) the processing of your personal data, you have the right to submit a complaint to the Information Commissioner's Office:Wycliffe House
Water Lane
Wilmslow
Cheshire
SK9 5AF

9. Data Protection Officer

Our Data Protection Officer has been registered with the Information Commissioner's Office. If you have any questions or requests with respect to this privacy statement or for the Data Protection Officer, you may contact Jeremy William Hill, https://legaltechnology.com/contact or via gdpr@legalitlexicon.com.

10. Children

Our website is not designed to attract children and it is not our intent to collect personal data from children under the age of consent in their country of residence. We therefore request that children under the age of consent do not submit any personal data to us.

11. Contact details

Legal IT Lexicon
71-75 Shelton Street
Covent Garden
London
City of London
WC2B 9JQ
United Kingdom
Website: https://legaltechnology.com
Email: privacy@legalitlexicon.com
Phone number: +44208142811

Annex

WordPress

Who we are

In this section, you should note your site URL, as well as the name of the company, organisation, or individual behind it, and some accurate contact information.

The amount of information you may be required to show will vary depending on your local or national business regulations. You may, for example, be required to display a physical address, a registered address, or your company registration number.

Suggested text: Our website address is: https://legaltechnology.com.

What personal data we collect and why we collect it

In 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.

You should also note any collection and retention of sensitive personal data, such as data concerning health.

In addition to listing what personal data you collect, you need to note why you collect it. These explanations must note either the legal basis for your data collection and retention or the active consent the user has given.

Personal data is not just created by a user’s interactions with your site. Personal data is also generated from technical processes such as contact forms, comments, cookies, analytics, and third-party embeds.

By 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.

Comments

In this subsection you should note what information is captured through comments. We have noted the data which WordPress collects by default.

Suggested text: 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.

An anonymised 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.

Media

In this subsection you should note what information may be disclosed by users who can upload media files. All uploaded files are usually publicly accessible.

Suggested text: 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.

Contact forms

By 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.

Cookies

In 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.

Suggested text: 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 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.

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.

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.

Embedded content from other websites

Suggested text: 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.

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.

Analytics

In 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’s privacy policy, if any.

By 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.

Who we share your data with

In 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.

By default WordPress does not share any personal data with anyone.

Suggested text: If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

In 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.

Suggested text: 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

In this section, you should explain what rights your users have over their data and how they can invoke those rights.

Suggested text: 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

In 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.

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.

Suggested text: Visitor comments may be checked through an automated spam detection service.

Your contact information

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.

Additional information

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.

How we protect your data

In this section you should explain what measures you have taken to protect your users’ 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.

What data breach procedures we have in place

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.

What third parties we receive data from

If your website receives data about users from third parties, including advertisers, this information must be included in the section of your privacy policy dealing with third-party data.

What automated decision making and/or profiling we do with user data

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.

Industry regulatory disclosure requirements

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.

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

Forminator Forms

Which forms collect personal data?

If you use Forminator PRO to create and embed any forms on your website, you may need to mention it here to properly distinguish it from other forms.

What personal data do we collect and why?

By default Forminator captures the IP Address for each submission to a Form. Other personal data such as your name and email address may also be captured, depending on the Form Fields.

Note: In this section you should include any personal data you collected and which form captures personal data to give users more relevant information. You should also include an explanation of why this data is needed. The explanation must note either the legal basis for your data collection and retention of the active consent the user has given.

Suggested text: When visitors or users submit a form, we capture the IP Address for spam protection. We also capture the email address and might capture other personal data included in the Form fields.

How long we retain your data

By default Forminator retains all form submissions forever. You can change this setting in Forminator » Settings » Privacy Settings

Suggested text: When visitors or users submit a form we retain the data for 30 days.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on the form submission.

Third Parties

If your forms utilize either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Forminator Forms can be configured to connect with these third parties:

  • Akismet. Enabled when you installed and configured Akismet on your site.
  • Google reCAPTCHA. Enabled when you added reCAPTCHA on your forms.
  • Mailchimp. Enabled when you activated and setup Mailchimp on Integrations settings.
  • Zapier. Enabled when you activated and setup Zapier on Integrations settings.
  • ActiveCampaign. Enabled when you activated and setup ActiveCampaign on Integrations settings.
  • Aweber. Enabled when you activated and setup Aweber on Integrations settings.
  • Campaign Monitor. Enabled when you activated and setup Campaign Monitor on Integrations settings.
  • Google Drive. Enabled when you activated and setup Google Drive on Integrations settings.
  • Trello. Enabled when you activated and setup Trello on Integrations settings.
  • Slack. Enabled when you activated and setup Slack on Integrations settings.

Suggested text:

We use Google reCAPTCHA for spam protection. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Akismet Spam for spam protection. Their privacy policy can be found here : https://automattic.com/privacy/.

We use Mailchimp to manage our subscriber list. Their privacy policy can be found here : https://mailchimp.com/legal/privacy/.

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

We use ActiveCampaign to manage our subscriber. Their privacy policy can be found here : https://www.activecampaign.com/privacy-policy/.

We use Aweber to manage our subscriber. Their privacy policy can be found here : https://www.aweber.com/privacy.htm.

We use Campaign Monitor to manage our subscriber. Their privacy policy can be found here : https://www.campaignmonitor.com/policies/#privacy-policy.

We use Google Drive and Google Sheets to manage our integration data. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Trello to manage our integration data. Their privacy policy can be found here : https://trello.com/privacy.

We use Slack to manage our integration data. Their privacy policy can be found here : https://slack.com/privacy-policy.

Forminator Polls

Which polls are collecting personal data?

If you use Forminator PRO to create and embed any polls on your website, you may need to mention it here to properly distinguish it from other polls.

What personal data do we collect and why?

By default Forminator captures the IP Address for each Poll submission.

In this section you should note what personal data you collected including which polls are available. You should also explan why this data is needed. Include the legal basis for your data collection and note the active consent the user has given.

Suggested text: When visitors or users submit a poll, we capture the IP Address for spam protection and to set voter limitations.

How long we retain your data

By default Forminator retains all votes and its IP Address forever. You can change this setting in Forminator » Settings » Privacy Settings

Suggested text: When visitors or users votes on a poll we retain the IP Address data for 30 days and anonymize it.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on votes.

Third Parties

If your polls utilize either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Forminator Polls can be configured to connect with these third parties:

  • Akismet. Enabled when you installed and configured Akismet on your site.
  • Zapier. Enabled when you activated and setup Zapier on Integrations settings.
  • Google Drive. Enabled when you activated and setup Google Drive on Integrations settings.
  • Trello. Enabled when you activated and setup Trello on Integrations settings.
  • Slack. Enabled when you activated and setup Slack on Integrations settings.

Suggested text:

We use Akismet Spam for spam protection. Their privacy policy can be found here : https://automattic.com/privacy/.

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

We use Google Drive and Google Sheets to manage our integration data. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Trello to manage our integration data. Their privacy policy can be found here : https://trello.com/privacy.

We use Slack to manage our integration data. Their privacy policy can be found here : https://slack.com/privacy-policy.

Forminator Quizzes

Which quizzes are collecting personal data?

If you use Forminator PRO to create and embed any quizzes on your website, you may need to mention it here to properly distinguish it from other quizzes.

What personal data do we collect and why?

By default Forminator captures NO Personally Identifiable Information for each Quiz submission.

In this section you should note what personal data you collected including which quizzes are available. You should also explain why this data is needed. Include the legal basis for your data collection and note the active consent the user has given.

Suggested text: When visitors or users submit a quiz's answer, we capture NO Personally Identifiable Information.

How long we retain your data

By default Forminator retains all quizzes answers and forever. You can change this setting in Forminator » Settings » Data

Suggested text: When visitors or users answer a quiz we retain the answers data for 30 days and then remove it from our system.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on answers.

Third Parties

If your quizzes utilize either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Forminator Quizzes can be configured to connect with these third parties:

  • Zapier. Enabled when you activated and setup Zapier on Integrations settings.
  • Google Drive. Enabled when you activated and setup Google Drive on Integrations settings.
  • Trello. Enabled when you activated and setup Trello on Integrations settings.
  • Slack. Enabled when you activated and setup Slack on Integrations settings.

Suggested text:

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

We use Google Drive and Google Sheets to manage our integration data. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Trello to manage our integration data. Their privacy policy can be found here : https://trello.com/privacy.

We use Slack to manage our integration data. Their privacy policy can be found here : https://slack.com/privacy-policy.

Beehive Pro

This website uses Google Analytics to track website traffic. Collected data is processed in such a way that visitors cannot be identified.

Hustle

Which modules collect personal data?

If you use Hustle to create and embed any Pop-up, Embed, Slide-in, or Social share module, you may need to mention it here to properly distinguish it from other plugins.

What personal data do we collect and why?

By default, Hustle captures the IP Address for each conversion and for each view only if the "tracking" functionality is enabled. Other personal data such as your name and email address may also be captured, depending on the form fields.

Note: In this section you should include any personal data you collected and which form captures personal data to give users more relevant information. You should also include an explanation of why this data is needed. The explanation must note either the legal basis for your data collection and retention of the active consent the user has given.

Suggested text: When visitors or users submit a form or view a module, we capture the IP Address for analyisis purposes. We also capture the email address and might capture other personal data included in the form fields.

How long we retain your data

By default Hustle retains all form submissions and tracking data forever. You can delete the stored data in Hustle » Settings » Privacy Settings, and under each module's settings.

Suggested text: When visitors or users submit a form or view a module we retain the data for 30 days.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on the form submission.

Third Parties

If your forms use either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Hustle optionally use these third party integrations:

  • ActiveCampaign. Enabled when you activate and setup ActiveCampaign on Email Collection settings.
  • Aweber. Enabled when you activate and setup Aweber on Email Collection settings.
  • Campaign Monitor. Enabled when you activate and setup Campaign Monitor on Email Collection settings.
  • Constant Contact. Enabled when you activate and setup Constant Contact on Email Collection settings.
  • ConvertKit. Enabled when you activate and setup ConvertKit on Email Collection settings.
  • e-Newsletter. Enabled when you activate and setup e-Newsletter on Email Collection settings.
  • GetResponse. Enabled when you activate and setup GetResponse on Email Collection settings.
  • HubSpot. Enabled when you activate and setup HubSpot on Email Collection settings.
  • iContact. Enabled when you activate and setup iContact on Email Collection settings.
  • Infusionsoft. Enabled when you activate and setup Infusionsoft on Email Collection settings.
  • Mad Mimi. Enabled when you activate and setup Mad Mimi on Email Collection settings.
  • Mailchimp. Enabled when you activate and setup Mailchimp on Email Collection settings.
  • MailerLite. Enabled when you activate and setup MailerLite on Email Collection settings.
  • Mautic. Enabled when you activate and setup Mautic on Email Collection settings.
  • reCAPTCHA. Enabled when you activate and setup reCAPTCHA on non-Social sharing modules.
  • Pinterest. Enabled when you activate and setup Pinterest in Social Share Module.
  • SendGrid. Enabled when you activated and setup SendGrid on Email Collection settings.
  • SendinBlue. Enabled when you activated and setup SendinBlue on Email Collection settings.
  • Sendy. Enabled when you activated and setup Sendy on Email Collection settings.
  • Zapier. Enabled when you activated and setup Zapier on Email Collection settings.

Suggested text:

We use ActiveCampaign to manage our subscriber lists. Their privacy policy can be found here : https://www.activecampaign.com/privacy-policy/.

We use Aweber to manage our subscriber. Their privacy policy can be found here : https://www.aweber.com/privacy.htm.

We use Campaign Monitor to manage our subscriber. Their privacy policy can be found here : https://www.campaignmonitor.com/policies/#privacy-policy.

We use Constant Contact to manage our subscriber. Their privacy policy can be found here : https://www.endurance.com/privacy.

We use ConvertKit to manage our subscriber. Their privacy policy can be found here : https://convertkit.com/privacy/.

We use e-Newsletter to manage our subscriber. You can learn more about it here https://premium.wpmudev.org/project/e-newsletter/.

We use GetResponse to manage our subscriber lists. Their privacy policy can be found here : https://www.getresponse.com/legal/privacy.html?lang=en.

We use HubSpot to manage our subscriber. Their privacy policy can be found here : https://legal.hubspot.com/legal-stuff.

We use iContact to manage our subscriber. Their privacy policy can be found here : https://www.icontact.com/legal/privacy.

We use Infusionsoft to manage our subscriber. Their privacy policy can be found here : https://www.infusionsoft.com/legal/privacy-policy.

We use Mad Mimi to manage our subscriber. Their privacy policy can be found here : https://madmimi.com/legal/terms.

We use Mailchimp to manage our subscriber list. Their privacy policy can be found here : https://mailchimp.com/legal/privacy/.

We use MailerLite to manage our subscriber. Their privacy policy can be found here : https://www.mailerlite.com/privacy-policy.

We use Mautic to manage our subscriber. Their privacy policy can be found here : https://www.mautic.org/privacy-policy/.

We use Pinterest to share media. Their privacy policy can be found here : https://policy.pinterest.com/privacy-policy/.

We use reCAPTCHA to protect your website from fraud and abuse. Their privacy policy can be found here : https://policies.google.com/privacy.

We use SendGrid to manage our subscriber. Their privacy policy can be found here : https://sendgrid.com/policies/privacy/.

We use SendinBlue to manage our subscriber. Their privacy policy can be found here : https://www.sendinblue.com/legal/privacypolicy/.

We use Sendy to manage our subscriber. Their privacy policy can be found here : https://sendy.co/privacy-policy.

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

Cookies

By default Hustle uses cookies to count how many times each module is visualized. Cookies might be used to handle other features such as display settings, used when a module should not be displayed for a certain time, whether the user commented before, whether the user has subscribed, among others, if their related settings are enabled.

Hummingbird

Third parties

Hummingbird uses the Stackpath Content Delivery Network (CDN). Stackpath may store web log information of site visitors, including IPs, UA, referrer, Location and ISP info of site visitors for 7 days. Files and images served by the CDN may be stored and served from countries other than your own. Stackpath’s privacy policy can be found here.

WP Smush

Plugin: Smush

Note: Smush does not interact with end users on your website. The only input option Smush has is to a newsletter subscription for site admins only. If you would like to notify your users of this in your privacy policy, you can use the information below.

Smush sends images to the WPMU DEV servers to optimise them for web use. This includes the transfer of EXIF data. The EXIF data will either be stripped or returned as it is. It is not stored on the WPMU DEV servers.

Smush uses the Stackpath Content Delivery Network (CDN). Stackpath may store web log information of site visitors, including IPs, UA, referrer, Location and ISP info of site visitors for 7 days. Files and images served by the CDN may be stored and served from countries other than your own. Stackpath's privacy policy can be found here.

Ninja Forms

Ninja Forms allows you to collect personal information

If you are using Ninja Forms to collect personal information, you should consult a legal professional for your use case.

WordPress

Who we are

In this section, you should note your site URL, as well as the name of the company, organisation, or individual behind it, and some accurate contact information.

The amount of information you may be required to show will vary depending on your local or national business regulations. You may, for example, be required to display a physical address, a registered address, or your company registration number.

Suggested text: Our website address is: https://legaltechnology.com.

What personal data we collect and why we collect it

In 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.

You should also note any collection and retention of sensitive personal data, such as data concerning health.

In addition to listing what personal data you collect, you need to note why you collect it. These explanations must note either the legal basis for your data collection and retention or the active consent the user has given.

Personal data is not just created by a user’s interactions with your site. Personal data is also generated from technical processes such as contact forms, comments, cookies, analytics, and third-party embeds.

By 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.

Comments

In this subsection you should note what information is captured through comments. We have noted the data which WordPress collects by default.

Suggested text: 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.

An anonymised 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.

Media

In this subsection you should note what information may be disclosed by users who can upload media files. All uploaded files are usually publicly accessible.

Suggested text: 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.

Contact forms

By 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.

Cookies

In 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.

Suggested text: 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 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.

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.

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.

Embedded content from other websites

Suggested text: 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.

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.

Analytics

In 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’s privacy policy, if any.

By 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.

Who we share your data with

In 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.

By default WordPress does not share any personal data with anyone.

Suggested text: If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

In 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.

Suggested text: 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

In this section, you should explain what rights your users have over their data and how they can invoke those rights.

Suggested text: 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

In 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.

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.

Suggested text: Visitor comments may be checked through an automated spam detection service.

Your contact information

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.

Additional information

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.

How we protect your data

In this section you should explain what measures you have taken to protect your users’ 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.

What data breach procedures we have in place

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.

What third parties we receive data from

If your website receives data about users from third parties, including advertisers, this information must be included in the section of your privacy policy dealing with third-party data.

What automated decision making and/or profiling we do with user data

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.

Industry regulatory disclosure requirements

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.

Forminator Forms

Which forms collect personal data?

If you use Forminator PRO to create and embed any forms on your website, you may need to mention it here to properly distinguish it from other forms.

What personal data do we collect and why?

By default Forminator captures the IP Address for each submission to a Form. Other personal data such as your name and email address may also be captured, depending on the Form Fields.

Note: In this section you should include any personal data you collected and which form captures personal data to give users more relevant information. You should also include an explanation of why this data is needed. The explanation must note either the legal basis for your data collection and retention of the active consent the user has given.

Suggested text: When visitors or users submit a form, we capture the IP Address for spam protection. We also capture the email address and might capture other personal data included in the Form fields.

How long we retain your data

By default Forminator retains all form submissions forever. You can change this setting in Forminator » Settings » Privacy Settings

Suggested text: When visitors or users submit a form we retain the data for 30 days.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on the form submission.

Third Parties

If your forms utilize either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Forminator Forms can be configured to connect with these third parties:

  • Akismet. Enabled when you installed and configured Akismet on your site.
  • Google reCAPTCHA. Enabled when you added reCAPTCHA on your forms.
  • Mailchimp. Enabled when you activated and setup Mailchimp on Integrations settings.
  • Zapier. Enabled when you activated and setup Zapier on Integrations settings.
  • ActiveCampaign. Enabled when you activated and setup ActiveCampaign on Integrations settings.
  • Aweber. Enabled when you activated and setup Aweber on Integrations settings.
  • Campaign Monitor. Enabled when you activated and setup Campaign Monitor on Integrations settings.
  • Google Drive. Enabled when you activated and setup Google Drive on Integrations settings.
  • Trello. Enabled when you activated and setup Trello on Integrations settings.
  • Slack. Enabled when you activated and setup Slack on Integrations settings.

Suggested text:

We use Google reCAPTCHA for spam protection. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Akismet Spam for spam protection. Their privacy policy can be found here : https://automattic.com/privacy/.

We use Mailchimp to manage our subscriber list. Their privacy policy can be found here : https://mailchimp.com/legal/privacy/.

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

We use ActiveCampaign to manage our subscriber. Their privacy policy can be found here : https://www.activecampaign.com/privacy-policy/.

We use Aweber to manage our subscriber. Their privacy policy can be found here : https://www.aweber.com/privacy.htm.

We use Campaign Monitor to manage our subscriber. Their privacy policy can be found here : https://www.campaignmonitor.com/policies/#privacy-policy.

We use Google Drive and Google Sheets to manage our integration data. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Trello to manage our integration data. Their privacy policy can be found here : https://trello.com/privacy.

We use Slack to manage our integration data. Their privacy policy can be found here : https://slack.com/privacy-policy.

Forminator Polls

Which polls are collecting personal data?

If you use Forminator PRO to create and embed any polls on your website, you may need to mention it here to properly distinguish it from other polls.

What personal data do we collect and why?

By default Forminator captures the IP Address for each Poll submission.

In this section you should note what personal data you collected including which polls are available. You should also explan why this data is needed. Include the legal basis for your data collection and note the active consent the user has given.

Suggested text: When visitors or users submit a poll, we capture the IP Address for spam protection and to set voter limitations.

How long we retain your data

By default Forminator retains all votes and its IP Address forever. You can change this setting in Forminator » Settings » Privacy Settings

Suggested text: When visitors or users votes on a poll we retain the IP Address data for 30 days and anonymize it.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on votes.

Third Parties

If your polls utilize either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Forminator Polls can be configured to connect with these third parties:

  • Akismet. Enabled when you installed and configured Akismet on your site.
  • Zapier. Enabled when you activated and setup Zapier on Integrations settings.
  • Google Drive. Enabled when you activated and setup Google Drive on Integrations settings.
  • Trello. Enabled when you activated and setup Trello on Integrations settings.
  • Slack. Enabled when you activated and setup Slack on Integrations settings.

Suggested text:

We use Akismet Spam for spam protection. Their privacy policy can be found here : https://automattic.com/privacy/.

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

We use Google Drive and Google Sheets to manage our integration data. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Trello to manage our integration data. Their privacy policy can be found here : https://trello.com/privacy.

We use Slack to manage our integration data. Their privacy policy can be found here : https://slack.com/privacy-policy.

Forminator Quizzes

Which quizzes are collecting personal data?

If you use Forminator PRO to create and embed any quizzes on your website, you may need to mention it here to properly distinguish it from other quizzes.

What personal data do we collect and why?

By default Forminator captures NO Personally Identifiable Information for each Quiz submission.

In this section you should note what personal data you collected including which quizzes are available. You should also explain why this data is needed. Include the legal basis for your data collection and note the active consent the user has given.

Suggested text: When visitors or users submit a quiz's answer, we capture NO Personally Identifiable Information.

How long we retain your data

By default Forminator retains all quizzes answers and forever. You can change this setting in Forminator » Settings » Data

Suggested text: When visitors or users answer a quiz we retain the answers data for 30 days and then remove it from our system.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on answers.

Third Parties

If your quizzes utilize either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Forminator Quizzes can be configured to connect with these third parties:

  • Zapier. Enabled when you activated and setup Zapier on Integrations settings.
  • Google Drive. Enabled when you activated and setup Google Drive on Integrations settings.
  • Trello. Enabled when you activated and setup Trello on Integrations settings.
  • Slack. Enabled when you activated and setup Slack on Integrations settings.

Suggested text:

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

We use Google Drive and Google Sheets to manage our integration data. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Trello to manage our integration data. Their privacy policy can be found here : https://trello.com/privacy.

We use Slack to manage our integration data. Their privacy policy can be found here : https://slack.com/privacy-policy.

Beehive Pro

This website uses Google Analytics to track website traffic. Collected data is processed in such a way that visitors cannot be identified.

Hustle

Which modules collect personal data?

If you use Hustle to create and embed any Pop-up, Embed, Slide-in, or Social share module, you may need to mention it here to properly distinguish it from other plugins.

What personal data do we collect and why?

By default, Hustle captures the IP Address for each conversion and for each view only if the "tracking" functionality is enabled. Other personal data such as your name and email address may also be captured, depending on the form fields.

Note: In this section you should include any personal data you collected and which form captures personal data to give users more relevant information. You should also include an explanation of why this data is needed. The explanation must note either the legal basis for your data collection and retention of the active consent the user has given.

Suggested text: When visitors or users submit a form or view a module, we capture the IP Address for analyisis purposes. We also capture the email address and might capture other personal data included in the form fields.

How long we retain your data

By default Hustle retains all form submissions and tracking data forever. You can delete the stored data in Hustle » Settings » Privacy Settings, and under each module's settings.

Suggested text: When visitors or users submit a form or view a module we retain the data for 30 days.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on the form submission.

Third Parties

If your forms use either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Hustle optionally use these third party integrations:

  • ActiveCampaign. Enabled when you activate and setup ActiveCampaign on Email Collection settings.
  • Aweber. Enabled when you activate and setup Aweber on Email Collection settings.
  • Campaign Monitor. Enabled when you activate and setup Campaign Monitor on Email Collection settings.
  • Constant Contact. Enabled when you activate and setup Constant Contact on Email Collection settings.
  • ConvertKit. Enabled when you activate and setup ConvertKit on Email Collection settings.
  • e-Newsletter. Enabled when you activate and setup e-Newsletter on Email Collection settings.
  • GetResponse. Enabled when you activate and setup GetResponse on Email Collection settings.
  • HubSpot. Enabled when you activate and setup HubSpot on Email Collection settings.
  • iContact. Enabled when you activate and setup iContact on Email Collection settings.
  • Infusionsoft. Enabled when you activate and setup Infusionsoft on Email Collection settings.
  • Mad Mimi. Enabled when you activate and setup Mad Mimi on Email Collection settings.
  • Mailchimp. Enabled when you activate and setup Mailchimp on Email Collection settings.
  • MailerLite. Enabled when you activate and setup MailerLite on Email Collection settings.
  • Mautic. Enabled when you activate and setup Mautic on Email Collection settings.
  • reCAPTCHA. Enabled when you activate and setup reCAPTCHA on non-Social sharing modules.
  • Pinterest. Enabled when you activate and setup Pinterest in Social Share Module.
  • SendGrid. Enabled when you activated and setup SendGrid on Email Collection settings.
  • SendinBlue. Enabled when you activated and setup SendinBlue on Email Collection settings.
  • Sendy. Enabled when you activated and setup Sendy on Email Collection settings.
  • Zapier. Enabled when you activated and setup Zapier on Email Collection settings.

Suggested text:

We use ActiveCampaign to manage our subscriber lists. Their privacy policy can be found here : https://www.activecampaign.com/privacy-policy/.

We use Aweber to manage our subscriber. Their privacy policy can be found here : https://www.aweber.com/privacy.htm.

We use Campaign Monitor to manage our subscriber. Their privacy policy can be found here : https://www.campaignmonitor.com/policies/#privacy-policy.

We use Constant Contact to manage our subscriber. Their privacy policy can be found here : https://www.endurance.com/privacy.

We use ConvertKit to manage our subscriber. Their privacy policy can be found here : https://convertkit.com/privacy/.

We use e-Newsletter to manage our subscriber. You can learn more about it here https://premium.wpmudev.org/project/e-newsletter/.

We use GetResponse to manage our subscriber lists. Their privacy policy can be found here : https://www.getresponse.com/legal/privacy.html?lang=en.

We use HubSpot to manage our subscriber. Their privacy policy can be found here : https://legal.hubspot.com/legal-stuff.

We use iContact to manage our subscriber. Their privacy policy can be found here : https://www.icontact.com/legal/privacy.

We use Infusionsoft to manage our subscriber. Their privacy policy can be found here : https://www.infusionsoft.com/legal/privacy-policy.

We use Mad Mimi to manage our subscriber. Their privacy policy can be found here : https://madmimi.com/legal/terms.

We use Mailchimp to manage our subscriber list. Their privacy policy can be found here : https://mailchimp.com/legal/privacy/.

We use MailerLite to manage our subscriber. Their privacy policy can be found here : https://www.mailerlite.com/privacy-policy.

We use Mautic to manage our subscriber. Their privacy policy can be found here : https://www.mautic.org/privacy-policy/.

We use Pinterest to share media. Their privacy policy can be found here : https://policy.pinterest.com/privacy-policy/.

We use reCAPTCHA to protect your website from fraud and abuse. Their privacy policy can be found here : https://policies.google.com/privacy.

We use SendGrid to manage our subscriber. Their privacy policy can be found here : https://sendgrid.com/policies/privacy/.

We use SendinBlue to manage our subscriber. Their privacy policy can be found here : https://www.sendinblue.com/legal/privacypolicy/.

We use Sendy to manage our subscriber. Their privacy policy can be found here : https://sendy.co/privacy-policy.

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

Cookies

By default Hustle uses cookies to count how many times each module is visualized. Cookies might be used to handle other features such as display settings, used when a module should not be displayed for a certain time, whether the user commented before, whether the user has subscribed, among others, if their related settings are enabled.

WP Smush

Plugin: Smush

Note: Smush does not interact with end users on your website. The only input option Smush has is to a newsletter subscription for site admins only. If you would like to notify your users of this in your privacy policy, you can use the information below.

Smush sends images to the WPMU DEV servers to optimise them for web use. This includes the transfer of EXIF data. The EXIF data will either be stripped or returned as it is. It is not stored on the WPMU DEV servers.

Smush uses the Stackpath Content Delivery Network (CDN). Stackpath may store web log information of site visitors, including IPs, UA, referrer, Location and ISP info of site visitors for 7 days. Files and images served by the CDN may be stored and served from countries other than your own. Stackpath's privacy policy can be found here.

Hummingbird

Third parties

Hummingbird uses the Stackpath Content Delivery Network (CDN). Stackpath may store web log information of site visitors, including IPs, UA, referrer, Location and ISP info of site visitors for 7 days. Files and images served by the CDN may be stored and served from countries other than your own. Stackpath’s privacy policy can be found here.

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

Ninja Forms

Ninja Forms allows you to collect personal information

If you are using Ninja Forms to collect personal information, you should consult a legal professional for your use case.

Ninja Forms

Ninja Forms allows you to collect personal information

If you are using Ninja Forms to collect personal information, you should consult a legal professional for your use case.

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

WP Smush

Plugin: Smush

Note: Smush does not interact with end users on your website. The only input option Smush has is to a newsletter subscription for site admins only. If you would like to notify your users of this in your privacy policy, you can use the information below.

Smush sends images to the WPMU DEV servers to optimise them for web use. This includes the transfer of EXIF data. The EXIF data will either be stripped or returned as it is. It is not stored on the WPMU DEV servers.

Smush uses the Stackpath Content Delivery Network (CDN). Stackpath may store web log information of site visitors, including IPs, UA, referrer, Location and ISP info of site visitors for 7 days. Files and images served by the CDN may be stored and served from countries other than your own. Stackpath's privacy policy can be found here.

Hummingbird

Third parties

Hummingbird uses the Stackpath Content Delivery Network (CDN). Stackpath may store web log information of site visitors, including IPs, UA, referrer, Location and ISP info of site visitors for 7 days. Files and images served by the CDN may be stored and served from countries other than your own. Stackpath’s privacy policy can be found here.

Hustle

Which modules collect personal data?

If you use Hustle to create and embed any Pop-up, Embed, Slide-in, or Social share module, you may need to mention it here to properly distinguish it from other plugins.

What personal data do we collect and why?

By default, Hustle captures the IP Address for each conversion and for each view only if the "tracking" functionality is enabled. Other personal data such as your name and email address may also be captured, depending on the form fields.

Note: In this section you should include any personal data you collected and which form captures personal data to give users more relevant information. You should also include an explanation of why this data is needed. The explanation must note either the legal basis for your data collection and retention of the active consent the user has given.

Suggested text: When visitors or users submit a form or view a module, we capture the IP Address for analyisis purposes. We also capture the email address and might capture other personal data included in the form fields.

How long we retain your data

By default Hustle retains all form submissions and tracking data forever. You can delete the stored data in Hustle » Settings » Privacy Settings, and under each module's settings.

Suggested text: When visitors or users submit a form or view a module we retain the data for 30 days.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on the form submission.

Third Parties

If your forms use either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Hustle optionally use these third party integrations:

  • ActiveCampaign. Enabled when you activate and setup ActiveCampaign on Email Collection settings.
  • Aweber. Enabled when you activate and setup Aweber on Email Collection settings.
  • Campaign Monitor. Enabled when you activate and setup Campaign Monitor on Email Collection settings.
  • Constant Contact. Enabled when you activate and setup Constant Contact on Email Collection settings.
  • ConvertKit. Enabled when you activate and setup ConvertKit on Email Collection settings.
  • e-Newsletter. Enabled when you activate and setup e-Newsletter on Email Collection settings.
  • GetResponse. Enabled when you activate and setup GetResponse on Email Collection settings.
  • HubSpot. Enabled when you activate and setup HubSpot on Email Collection settings.
  • iContact. Enabled when you activate and setup iContact on Email Collection settings.
  • Infusionsoft. Enabled when you activate and setup Infusionsoft on Email Collection settings.
  • Mad Mimi. Enabled when you activate and setup Mad Mimi on Email Collection settings.
  • Mailchimp. Enabled when you activate and setup Mailchimp on Email Collection settings.
  • MailerLite. Enabled when you activate and setup MailerLite on Email Collection settings.
  • Mautic. Enabled when you activate and setup Mautic on Email Collection settings.
  • reCAPTCHA. Enabled when you activate and setup reCAPTCHA on non-Social sharing modules.
  • Pinterest. Enabled when you activate and setup Pinterest in Social Share Module.
  • SendGrid. Enabled when you activated and setup SendGrid on Email Collection settings.
  • SendinBlue. Enabled when you activated and setup SendinBlue on Email Collection settings.
  • Sendy. Enabled when you activated and setup Sendy on Email Collection settings.
  • Zapier. Enabled when you activated and setup Zapier on Email Collection settings.

Suggested text:

We use ActiveCampaign to manage our subscriber lists. Their privacy policy can be found here : https://www.activecampaign.com/privacy-policy/.

We use Aweber to manage our subscriber. Their privacy policy can be found here : https://www.aweber.com/privacy.htm.

We use Campaign Monitor to manage our subscriber. Their privacy policy can be found here : https://www.campaignmonitor.com/policies/#privacy-policy.

We use Constant Contact to manage our subscriber. Their privacy policy can be found here : https://www.endurance.com/privacy.

We use ConvertKit to manage our subscriber. Their privacy policy can be found here : https://convertkit.com/privacy/.

We use e-Newsletter to manage our subscriber. You can learn more about it here https://premium.wpmudev.org/project/e-newsletter/.

We use GetResponse to manage our subscriber lists. Their privacy policy can be found here : https://www.getresponse.com/legal/privacy.html?lang=en.

We use HubSpot to manage our subscriber. Their privacy policy can be found here : https://legal.hubspot.com/legal-stuff.

We use iContact to manage our subscriber. Their privacy policy can be found here : https://www.icontact.com/legal/privacy.

We use Infusionsoft to manage our subscriber. Their privacy policy can be found here : https://www.infusionsoft.com/legal/privacy-policy.

We use Mad Mimi to manage our subscriber. Their privacy policy can be found here : https://madmimi.com/legal/terms.

We use Mailchimp to manage our subscriber list. Their privacy policy can be found here : https://mailchimp.com/legal/privacy/.

We use MailerLite to manage our subscriber. Their privacy policy can be found here : https://www.mailerlite.com/privacy-policy.

We use Mautic to manage our subscriber. Their privacy policy can be found here : https://www.mautic.org/privacy-policy/.

We use Pinterest to share media. Their privacy policy can be found here : https://policy.pinterest.com/privacy-policy/.

We use reCAPTCHA to protect your website from fraud and abuse. Their privacy policy can be found here : https://policies.google.com/privacy.

We use SendGrid to manage our subscriber. Their privacy policy can be found here : https://sendgrid.com/policies/privacy/.

We use SendinBlue to manage our subscriber. Their privacy policy can be found here : https://www.sendinblue.com/legal/privacypolicy/.

We use Sendy to manage our subscriber. Their privacy policy can be found here : https://sendy.co/privacy-policy.

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

Cookies

By default Hustle uses cookies to count how many times each module is visualized. Cookies might be used to handle other features such as display settings, used when a module should not be displayed for a certain time, whether the user commented before, whether the user has subscribed, among others, if their related settings are enabled.

Forminator Quizzes

Which quizzes are collecting personal data?

If you use Forminator PRO to create and embed any quizzes on your website, you may need to mention it here to properly distinguish it from other quizzes.

What personal data do we collect and why?

By default Forminator captures NO Personally Identifiable Information for each Quiz submission.

In this section you should note what personal data you collected including which quizzes are available. You should also explain why this data is needed. Include the legal basis for your data collection and note the active consent the user has given.

Suggested text: When visitors or users submit a quiz's answer, we capture NO Personally Identifiable Information.

How long we retain your data

By default Forminator retains all quizzes answers and forever. You can change this setting in Forminator » Settings » Data

Suggested text: When visitors or users answer a quiz we retain the answers data for 30 days and then remove it from our system.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on answers.

Third Parties

If your quizzes utilize either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Forminator Quizzes can be configured to connect with these third parties:

  • Zapier. Enabled when you activated and setup Zapier on Integrations settings.
  • Google Drive. Enabled when you activated and setup Google Drive on Integrations settings.
  • Trello. Enabled when you activated and setup Trello on Integrations settings.
  • Slack. Enabled when you activated and setup Slack on Integrations settings.

Suggested text:

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

We use Google Drive and Google Sheets to manage our integration data. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Trello to manage our integration data. Their privacy policy can be found here : https://trello.com/privacy.

We use Slack to manage our integration data. Their privacy policy can be found here : https://slack.com/privacy-policy.

Forminator Polls

Which polls are collecting personal data?

If you use Forminator PRO to create and embed any polls on your website, you may need to mention it here to properly distinguish it from other polls.

What personal data do we collect and why?

By default Forminator captures the IP Address for each Poll submission.

In this section you should note what personal data you collected including which polls are available. You should also explan why this data is needed. Include the legal basis for your data collection and note the active consent the user has given.

Suggested text: When visitors or users submit a poll, we capture the IP Address for spam protection and to set voter limitations.

How long we retain your data

By default Forminator retains all votes and its IP Address forever. You can change this setting in Forminator » Settings » Privacy Settings

Suggested text: When visitors or users votes on a poll we retain the IP Address data for 30 days and anonymize it.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on votes.

Third Parties

If your polls utilize either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Forminator Polls can be configured to connect with these third parties:

  • Akismet. Enabled when you installed and configured Akismet on your site.
  • Zapier. Enabled when you activated and setup Zapier on Integrations settings.
  • Google Drive. Enabled when you activated and setup Google Drive on Integrations settings.
  • Trello. Enabled when you activated and setup Trello on Integrations settings.
  • Slack. Enabled when you activated and setup Slack on Integrations settings.

Suggested text:

We use Akismet Spam for spam protection. Their privacy policy can be found here : https://automattic.com/privacy/.

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

We use Google Drive and Google Sheets to manage our integration data. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Trello to manage our integration data. Their privacy policy can be found here : https://trello.com/privacy.

We use Slack to manage our integration data. Their privacy policy can be found here : https://slack.com/privacy-policy.

Forminator Forms

Which forms collect personal data?

If you use Forminator PRO to create and embed any forms on your website, you may need to mention it here to properly distinguish it from other forms.

What personal data do we collect and why?

By default Forminator captures the IP Address for each submission to a Form. Other personal data such as your name and email address may also be captured, depending on the Form Fields.

Note: In this section you should include any personal data you collected and which form captures personal data to give users more relevant information. You should also include an explanation of why this data is needed. The explanation must note either the legal basis for your data collection and retention of the active consent the user has given.

Suggested text: When visitors or users submit a form, we capture the IP Address for spam protection. We also capture the email address and might capture other personal data included in the Form fields.

How long we retain your data

By default Forminator retains all form submissions forever. You can change this setting in Forminator » Settings » Privacy Settings

Suggested text: When visitors or users submit a form we retain the data for 30 days.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on the form submission.

Third Parties

If your forms utilize either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Forminator Forms can be configured to connect with these third parties:

  • Akismet. Enabled when you installed and configured Akismet on your site.
  • Google reCAPTCHA. Enabled when you added reCAPTCHA on your forms.
  • Mailchimp. Enabled when you activated and setup Mailchimp on Integrations settings.
  • Zapier. Enabled when you activated and setup Zapier on Integrations settings.
  • ActiveCampaign. Enabled when you activated and setup ActiveCampaign on Integrations settings.
  • Aweber. Enabled when you activated and setup Aweber on Integrations settings.
  • Campaign Monitor. Enabled when you activated and setup Campaign Monitor on Integrations settings.
  • Google Drive. Enabled when you activated and setup Google Drive on Integrations settings.
  • Trello. Enabled when you activated and setup Trello on Integrations settings.
  • Slack. Enabled when you activated and setup Slack on Integrations settings.

Suggested text:

We use Google reCAPTCHA for spam protection. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Akismet Spam for spam protection. Their privacy policy can be found here : https://automattic.com/privacy/.

We use Mailchimp to manage our subscriber list. Their privacy policy can be found here : https://mailchimp.com/legal/privacy/.

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

We use ActiveCampaign to manage our subscriber. Their privacy policy can be found here : https://www.activecampaign.com/privacy-policy/.

We use Aweber to manage our subscriber. Their privacy policy can be found here : https://www.aweber.com/privacy.htm.

We use Campaign Monitor to manage our subscriber. Their privacy policy can be found here : https://www.campaignmonitor.com/policies/#privacy-policy.

We use Google Drive and Google Sheets to manage our integration data. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Trello to manage our integration data. Their privacy policy can be found here : https://trello.com/privacy.

We use Slack to manage our integration data. Their privacy policy can be found here : https://slack.com/privacy-policy.

WordPress

Who we are

In this section, you should note your site URL, as well as the name of the company, organisation, or individual behind it, and some accurate contact information.

The amount of information you may be required to show will vary depending on your local or national business regulations. You may, for example, be required to display a physical address, a registered address, or your company registration number.

Suggested text: Our website address is: https://legaltechnology.com.

What personal data we collect and why we collect it

In 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.

You should also note any collection and retention of sensitive personal data, such as data concerning health.

In addition to listing what personal data you collect, you need to note why you collect it. These explanations must note either the legal basis for your data collection and retention or the active consent the user has given.

Personal data is not just created by a user’s interactions with your site. Personal data is also generated from technical processes such as contact forms, comments, cookies, analytics, and third-party embeds.

By 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.

Comments

In this subsection you should note what information is captured through comments. We have noted the data which WordPress collects by default.

Suggested text: 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.

An anonymised 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.

Media

In this subsection you should note what information may be disclosed by users who can upload media files. All uploaded files are usually publicly accessible.

Suggested text: 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.

Contact forms

By 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.

Cookies

In 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.

Suggested text: 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 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.

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.

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.

Embedded content from other websites

Suggested text: 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.

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.

Analytics

In 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’s privacy policy, if any.

By 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.

Who we share your data with

In 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.

By default WordPress does not share any personal data with anyone.

Suggested text: If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

In 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.

Suggested text: 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

In this section, you should explain what rights your users have over their data and how they can invoke those rights.

Suggested text: 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

In 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.

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.

Suggested text: Visitor comments may be checked through an automated spam detection service.

Your contact information

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.

Additional information

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.

How we protect your data

In this section you should explain what measures you have taken to protect your users’ 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.

What data breach procedures we have in place

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.

What third parties we receive data from

If your website receives data about users from third parties, including advertisers, this information must be included in the section of your privacy policy dealing with third-party data.

What automated decision making and/or profiling we do with user data

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.

Industry regulatory disclosure requirements

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.

WordPress

Who we are

In this section, you should note your site URL, as well as the name of the company, organisation, or individual behind it, and some accurate contact information.

The amount of information you may be required to show will vary depending on your local or national business regulations. You may, for example, be required to display a physical address, a registered address, or your company registration number.

Suggested text: Our website address is: https://legaltechnology.com.

What personal data we collect and why we collect it

In 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.

You should also note any collection and retention of sensitive personal data, such as data concerning health.

In addition to listing what personal data you collect, you need to note why you collect it. These explanations must note either the legal basis for your data collection and retention or the active consent the user has given.

Personal data is not just created by a user’s interactions with your site. Personal data is also generated from technical processes such as contact forms, comments, cookies, analytics, and third-party embeds.

By 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.

Comments

In this subsection you should note what information is captured through comments. We have noted the data which WordPress collects by default.

Suggested text: 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.

An anonymised 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.

Media

In this subsection you should note what information may be disclosed by users who can upload media files. All uploaded files are usually publicly accessible.

Suggested text: 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.

Contact forms

By 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.

Cookies

In 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.

Suggested text: 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 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.

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.

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.

Embedded content from other websites

Suggested text: 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.

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.

Analytics

In 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’s privacy policy, if any.

By 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.

Who we share your data with

In 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.

By default WordPress does not share any personal data with anyone.

Suggested text: If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

In 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.

Suggested text: 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

In this section, you should explain what rights your users have over their data and how they can invoke those rights.

Suggested text: 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

In 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.

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.

Suggested text: Visitor comments may be checked through an automated spam detection service.

Your contact information

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.

Additional information

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.

How we protect your data

In this section you should explain what measures you have taken to protect your users’ 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.

What data breach procedures we have in place

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.

What third parties we receive data from

If your website receives data about users from third parties, including advertisers, this information must be included in the section of your privacy policy dealing with third-party data.

What automated decision making and/or profiling we do with user data

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.

Industry regulatory disclosure requirements

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.

Ninja Forms

Ninja Forms allows you to collect personal information

If you are using Ninja Forms to collect personal information, you should consult a legal professional for your use case.

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

WP Smush

Plugin: Smush

Note: Smush does not interact with end users on your website. The only input option Smush has is to a newsletter subscription for site admins only. If you would like to notify your users of this in your privacy policy, you can use the information below.

Smush sends images to the WPMU DEV servers to optimise them for web use. This includes the transfer of EXIF data. The EXIF data will either be stripped or returned as it is. It is not stored on the WPMU DEV servers.

Smush uses the Stackpath Content Delivery Network (CDN). Stackpath may store web log information of site visitors, including IPs, UA, referrer, Location and ISP info of site visitors for 7 days. Files and images served by the CDN may be stored and served from countries other than your own. Stackpath's privacy policy can be found here.

WordPress

Who we are

In this section, you should note your site URL, as well as the name of the company, organisation, or individual behind it, and some accurate contact information.

The amount of information you may be required to show will vary depending on your local or national business regulations. You may, for example, be required to display a physical address, a registered address, or your company registration number.

Suggested text: Our website address is: https://legaltechnology.com.

What personal data we collect and why we collect it

In 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.

You should also note any collection and retention of sensitive personal data, such as data concerning health.

In addition to listing what personal data you collect, you need to note why you collect it. These explanations must note either the legal basis for your data collection and retention or the active consent the user has given.

Personal data is not just created by a user’s interactions with your site. Personal data is also generated from technical processes such as contact forms, comments, cookies, analytics, and third-party embeds.

By 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.

Comments

In this subsection you should note what information is captured through comments. We have noted the data which WordPress collects by default.

Suggested text: 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.

An anonymised 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.

Media

In this subsection you should note what information may be disclosed by users who can upload media files. All uploaded files are usually publicly accessible.

Suggested text: 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.

Contact forms

By 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.

Cookies

In 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.

Suggested text: 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 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.

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.

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.

Embedded content from other websites

Suggested text: 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.

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.

Analytics

In 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’s privacy policy, if any.

By 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.

Who we share your data with

In 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.

By default WordPress does not share any personal data with anyone.

Suggested text: If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

In 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.

Suggested text: 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

In this section, you should explain what rights your users have over their data and how they can invoke those rights.

Suggested text: 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

In 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.

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.

Suggested text: Visitor comments may be checked through an automated spam detection service.

Your contact information

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.

Additional information

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.

How we protect your data

In this section you should explain what measures you have taken to protect your users’ 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.

What data breach procedures we have in place

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.

What third parties we receive data from

If your website receives data about users from third parties, including advertisers, this information must be included in the section of your privacy policy dealing with third-party data.

What automated decision making and/or profiling we do with user data

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.

Industry regulatory disclosure requirements

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.

Forminator Forms

Which forms collect personal data?

If you use Forminator PRO to create and embed any forms on your website, you may need to mention it here to properly distinguish it from other forms.

What personal data do we collect and why?

By default Forminator captures the IP Address for each submission to a Form. Other personal data such as your name and email address may also be captured, depending on the Form Fields.

Note: In this section you should include any personal data you collected and which form captures personal data to give users more relevant information. You should also include an explanation of why this data is needed. The explanation must note either the legal basis for your data collection and retention of the active consent the user has given.

Suggested text: When visitors or users submit a form, we capture the IP Address for spam protection. We also capture the email address and might capture other personal data included in the Form fields.

How long we retain your data

By default Forminator retains all form submissions forever. You can change this setting in Forminator » Settings » Privacy Settings

Suggested text: When visitors or users submit a form we retain the data for 30 days.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on the form submission.

Third Parties

If your forms utilize either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Forminator Forms can be configured to connect with these third parties:

  • Akismet. Enabled when you installed and configured Akismet on your site.
  • Google reCAPTCHA. Enabled when you added reCAPTCHA on your forms.
  • Mailchimp. Enabled when you activated and setup Mailchimp on Integrations settings.
  • Zapier. Enabled when you activated and setup Zapier on Integrations settings.
  • ActiveCampaign. Enabled when you activated and setup ActiveCampaign on Integrations settings.
  • Aweber. Enabled when you activated and setup Aweber on Integrations settings.
  • Campaign Monitor. Enabled when you activated and setup Campaign Monitor on Integrations settings.
  • Google Drive. Enabled when you activated and setup Google Drive on Integrations settings.
  • Trello. Enabled when you activated and setup Trello on Integrations settings.
  • Slack. Enabled when you activated and setup Slack on Integrations settings.

Suggested text:

We use Google reCAPTCHA for spam protection. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Akismet Spam for spam protection. Their privacy policy can be found here : https://automattic.com/privacy/.

We use Mailchimp to manage our subscriber list. Their privacy policy can be found here : https://mailchimp.com/legal/privacy/.

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

We use ActiveCampaign to manage our subscriber. Their privacy policy can be found here : https://www.activecampaign.com/privacy-policy/.

We use Aweber to manage our subscriber. Their privacy policy can be found here : https://www.aweber.com/privacy.htm.

We use Campaign Monitor to manage our subscriber. Their privacy policy can be found here : https://www.campaignmonitor.com/policies/#privacy-policy.

We use Google Drive and Google Sheets to manage our integration data. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Trello to manage our integration data. Their privacy policy can be found here : https://trello.com/privacy.

We use Slack to manage our integration data. Their privacy policy can be found here : https://slack.com/privacy-policy.

Forminator Polls

Which polls are collecting personal data?

If you use Forminator PRO to create and embed any polls on your website, you may need to mention it here to properly distinguish it from other polls.

What personal data do we collect and why?

By default Forminator captures the IP Address for each Poll submission.

In this section you should note what personal data you collected including which polls are available. You should also explan why this data is needed. Include the legal basis for your data collection and note the active consent the user has given.

Suggested text: When visitors or users submit a poll, we capture the IP Address for spam protection and to set voter limitations.

How long we retain your data

By default Forminator retains all votes and its IP Address forever. You can change this setting in Forminator » Settings » Privacy Settings

Suggested text: When visitors or users votes on a poll we retain the IP Address data for 30 days and anonymize it.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on votes.

Third Parties

If your polls utilize either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Forminator Polls can be configured to connect with these third parties:

  • Akismet. Enabled when you installed and configured Akismet on your site.
  • Zapier. Enabled when you activated and setup Zapier on Integrations settings.
  • Google Drive. Enabled when you activated and setup Google Drive on Integrations settings.
  • Trello. Enabled when you activated and setup Trello on Integrations settings.
  • Slack. Enabled when you activated and setup Slack on Integrations settings.

Suggested text:

We use Akismet Spam for spam protection. Their privacy policy can be found here : https://automattic.com/privacy/.

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

We use Google Drive and Google Sheets to manage our integration data. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Trello to manage our integration data. Their privacy policy can be found here : https://trello.com/privacy.

We use Slack to manage our integration data. Their privacy policy can be found here : https://slack.com/privacy-policy.

Hustle

Which modules collect personal data?

If you use Hustle to create and embed any Pop-up, Embed, Slide-in, or Social share module, you may need to mention it here to properly distinguish it from other plugins.

What personal data do we collect and why?

By default, Hustle captures the IP Address for each conversion and for each view only if the "tracking" functionality is enabled. Other personal data such as your name and email address may also be captured, depending on the form fields.

Note: In this section you should include any personal data you collected and which form captures personal data to give users more relevant information. You should also include an explanation of why this data is needed. The explanation must note either the legal basis for your data collection and retention of the active consent the user has given.

Suggested text: When visitors or users submit a form or view a module, we capture the IP Address for analyisis purposes. We also capture the email address and might capture other personal data included in the form fields.

How long we retain your data

By default Hustle retains all form submissions and tracking data forever. You can delete the stored data in Hustle » Settings » Privacy Settings, and under each module's settings.

Suggested text: When visitors or users submit a form or view a module we retain the data for 30 days.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on the form submission.

Third Parties

If your forms use either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Hustle optionally use these third party integrations:

  • ActiveCampaign. Enabled when you activate and setup ActiveCampaign on Email Collection settings.
  • Aweber. Enabled when you activate and setup Aweber on Email Collection settings.
  • Campaign Monitor. Enabled when you activate and setup Campaign Monitor on Email Collection settings.
  • Constant Contact. Enabled when you activate and setup Constant Contact on Email Collection settings.
  • ConvertKit. Enabled when you activate and setup ConvertKit on Email Collection settings.
  • e-Newsletter. Enabled when you activate and setup e-Newsletter on Email Collection settings.
  • GetResponse. Enabled when you activate and setup GetResponse on Email Collection settings.
  • HubSpot. Enabled when you activate and setup HubSpot on Email Collection settings.
  • iContact. Enabled when you activate and setup iContact on Email Collection settings.
  • Infusionsoft. Enabled when you activate and setup Infusionsoft on Email Collection settings.
  • Mad Mimi. Enabled when you activate and setup Mad Mimi on Email Collection settings.
  • Mailchimp. Enabled when you activate and setup Mailchimp on Email Collection settings.
  • MailerLite. Enabled when you activate and setup MailerLite on Email Collection settings.
  • Mautic. Enabled when you activate and setup Mautic on Email Collection settings.
  • reCAPTCHA. Enabled when you activate and setup reCAPTCHA on non-Social sharing modules.
  • Pinterest. Enabled when you activate and setup Pinterest in Social Share Module.
  • SendGrid. Enabled when you activated and setup SendGrid on Email Collection settings.
  • SendinBlue. Enabled when you activated and setup SendinBlue on Email Collection settings.
  • Sendy. Enabled when you activated and setup Sendy on Email Collection settings.
  • Zapier. Enabled when you activated and setup Zapier on Email Collection settings.

Suggested text:

We use ActiveCampaign to manage our subscriber lists. Their privacy policy can be found here : https://www.activecampaign.com/privacy-policy/.

We use Aweber to manage our subscriber. Their privacy policy can be found here : https://www.aweber.com/privacy.htm.

We use Campaign Monitor to manage our subscriber. Their privacy policy can be found here : https://www.campaignmonitor.com/policies/#privacy-policy.

We use Constant Contact to manage our subscriber. Their privacy policy can be found here : https://www.endurance.com/privacy.

We use ConvertKit to manage our subscriber. Their privacy policy can be found here : https://convertkit.com/privacy/.

We use e-Newsletter to manage our subscriber. You can learn more about it here https://premium.wpmudev.org/project/e-newsletter/.

We use GetResponse to manage our subscriber lists. Their privacy policy can be found here : https://www.getresponse.com/legal/privacy.html?lang=en.

We use HubSpot to manage our subscriber. Their privacy policy can be found here : https://legal.hubspot.com/legal-stuff.

We use iContact to manage our subscriber. Their privacy policy can be found here : https://www.icontact.com/legal/privacy.

We use Infusionsoft to manage our subscriber. Their privacy policy can be found here : https://www.infusionsoft.com/legal/privacy-policy.

We use Mad Mimi to manage our subscriber. Their privacy policy can be found here : https://madmimi.com/legal/terms.

We use Mailchimp to manage our subscriber list. Their privacy policy can be found here : https://mailchimp.com/legal/privacy/.

We use MailerLite to manage our subscriber. Their privacy policy can be found here : https://www.mailerlite.com/privacy-policy.

We use Mautic to manage our subscriber. Their privacy policy can be found here : https://www.mautic.org/privacy-policy/.

We use Pinterest to share media. Their privacy policy can be found here : https://policy.pinterest.com/privacy-policy/.

We use reCAPTCHA to protect your website from fraud and abuse. Their privacy policy can be found here : https://policies.google.com/privacy.

We use SendGrid to manage our subscriber. Their privacy policy can be found here : https://sendgrid.com/policies/privacy/.

We use SendinBlue to manage our subscriber. Their privacy policy can be found here : https://www.sendinblue.com/legal/privacypolicy/.

We use Sendy to manage our subscriber. Their privacy policy can be found here : https://sendy.co/privacy-policy.

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

Cookies

By default Hustle uses cookies to count how many times each module is visualized. Cookies might be used to handle other features such as display settings, used when a module should not be displayed for a certain time, whether the user commented before, whether the user has subscribed, among others, if their related settings are enabled.

Forminator Quizzes

Which quizzes are collecting personal data?

If you use Forminator PRO to create and embed any quizzes on your website, you may need to mention it here to properly distinguish it from other quizzes.

What personal data do we collect and why?

By default Forminator captures NO Personally Identifiable Information for each Quiz submission.

In this section you should note what personal data you collected including which quizzes are available. You should also explain why this data is needed. Include the legal basis for your data collection and note the active consent the user has given.

Suggested text: When visitors or users submit a quiz's answer, we capture NO Personally Identifiable Information.

How long we retain your data

By default Forminator retains all quizzes answers and forever. You can change this setting in Forminator » Settings » Data

Suggested text: When visitors or users answer a quiz we retain the answers data for 30 days and then remove it from our system.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on answers.

Third Parties

If your quizzes utilize either built-in or external third party services, in this section you should mention any third parties and its privacy policy.

By default Forminator Quizzes can be configured to connect with these third parties:

  • Zapier. Enabled when you activated and setup Zapier on Integrations settings.
  • Google Drive. Enabled when you activated and setup Google Drive on Integrations settings.
  • Trello. Enabled when you activated and setup Trello on Integrations settings.
  • Slack. Enabled when you activated and setup Slack on Integrations settings.

Suggested text:

We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

We use Google Drive and Google Sheets to manage our integration data. Their privacy policy can be found here : https://policies.google.com/privacy?hl=en.

We use Trello to manage our integration data. Their privacy policy can be found here : https://trello.com/privacy.

We use Slack to manage our integration data. Their privacy policy can be found here : https://slack.com/privacy-policy.

Hummingbird

Third parties

Hummingbird uses the Stackpath Content Delivery Network (CDN). Stackpath may store web log information of site visitors, including IPs, UA, referrer, Location and ISP info of site visitors for 7 days. Files and images served by the CDN may be stored and served from countries other than your own. Stackpath’s privacy policy can be found here.

WordPress

Who we are

In this section, you should note your site URL, as well as the name of the company, organisation, or individual behind it, and some accurate contact information.

The amount of information you may be required to show will vary depending on your local or national business regulations. You may, for example, be required to display a physical address, a registered address, or your company registration number.

Suggested text: Our website address is: https://legaltechnology.com.

What personal data we collect and why we collect it

In 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.

You should also note any collection and retention of sensitive personal data, such as data concerning health.

In addition to listing what personal data you collect, you need to note why you collect it. These explanations must note either the legal basis for your data collection and retention or the active consent the user has given.

Personal data is not just created by a user’s interactions with your site. Personal data is also generated from technical processes such as contact forms, comments, cookies, analytics, and third-party embeds.

By 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.

Comments

In this subsection you should note what information is captured through comments. We have noted the data which WordPress collects by default.

Suggested text: 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.

An anonymised 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.

Media

In this subsection you should note what information may be disclosed by users who can upload media files. All uploaded files are usually publicly accessible.

Suggested text: 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.

Contact forms

By 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.

Cookies

In 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.

Suggested text: 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 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.

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.

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.

Embedded content from other websites

Suggested text: 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.

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.

Analytics

In 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’s privacy policy, if any.

By 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.

Who we share your data with

In 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.

By default WordPress does not share any personal data with anyone.

Suggested text: If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

In 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.

Suggested text: 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

In this section, you should explain what rights your users have over their data and how they can invoke those rights.

Suggested text: 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

In 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.

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.

Suggested text: Visitor comments may be checked through an automated spam detection service.

Your contact information

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.

Additional information

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.

How we protect your data

In this section you should explain what measures you have taken to protect your users’ 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.

What data breach procedures we have in place

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.

What third parties we receive data from

If your website receives data about users from third parties, including advertisers, this information must be included in the section of your privacy policy dealing with third-party data.

What automated decision making and/or profiling we do with user data

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.

Industry regulatory disclosure requirements

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.

Hummingbird

Third parties

Hummingbird uses the Stackpath Content Delivery Network (CDN). Stackpath may store web log information of site visitors, including IPs, UA, referrer, Location and ISP info of site visitors for 7 days. Files and images served by the CDN may be stored and served from countries other than your own. Stackpath’s privacy policy can be found here.

WP Smush

Plugin: Smush

Note: Smush does not interact with end users on your website. The only input option Smush has is to a newsletter subscription for site admins only. If you would like to notify your users of this in your privacy policy, you can use the information below.

Smush sends images to the WPMU DEV servers to optimise them for web use. This includes the transfer of EXIF data. The EXIF data will either be stripped or returned as it is. It is not stored on the WPMU DEV servers.

Smush uses the Stackpath Content Delivery Network (CDN). Stackpath may store web log information of site visitors, including IPs, UA, referrer, Location and ISP info of site visitors for 7 days. Files and images served by the CDN may be stored and served from countries other than your own. Stackpath's privacy policy can be found here.

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

Ninja Forms

Ninja Forms allows you to collect personal information

If you are using Ninja Forms to collect personal information, you should consult a legal professional for your use case.

WordPress

Who we are

Suggested text: Our website address is: https://legaltechnology.com.

Comments

Suggested text: 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.

An anonymised 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.

Media

Suggested text: 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.

Cookies

Suggested text: 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 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.

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.

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.

Embedded content from other websites

Suggested text: 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.

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.

Who we share your data with

Suggested text: If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

Suggested text: 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

Suggested text: 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

Suggested text: Visitor comments may be checked through an automated spam detection service.

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

Really Simple SSL

Really Simple SSL and Really Simple SSL add-ons do not process any personal identifiable information, so the GDPR does not apply to these plugins or usage of these plugins on your website. You can find our privacy policy here.

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

Really Simple SSL

Really Simple SSL and Really Simple SSL add-ons do not process any personal identifiable information, so the GDPR does not apply to these plugins or usage of these plugins on your website. You can find our privacy policy here.

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

Really Simple SSL

Really Simple SSL and Really Simple SSL add-ons do not process any personal identifiable information, so the GDPR does not apply to these plugins or usage of these plugins on your website. You can find our privacy policy here.

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

Really Simple SSL

Really Simple SSL and Really Simple SSL add-ons do not process any personal identifiable information, so the GDPR does not apply to these plugins or usage of these plugins on your website. You can find our privacy policy here.

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

WooCommerce

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.

We collect information about you during the checkout process on our store.

What we collect and store

While you visit our site, we’ll track:

  • Products you’ve viewed: we’ll use this to, for example, show you products you’ve recently viewed
  • Location, IP address and browser type: we’ll use this for purposes like estimating taxes and shipping
  • Shipping address: we’ll ask you to enter this so we can, for instance, estimate shipping before you place an order, and send you the order!

We’ll also use cookies to keep track of basket contents while you’re browsing our site.

Note: you may want to further detail your cookie policy, and link to that section from here.

When you purchase from us, we’ll 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’ll use this information for purposes, such as, to:

  • Send you information about your account and order
  • Respond to your requests, including refunds and complaints
  • Process payments and prevent fraud
  • Set up your account for our store
  • Comply with any legal obligations we have, such as calculating taxes
  • Improve our store offerings
  • Send you marketing messages, if you choose to receive them

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.

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.

We will also store comments or reviews, if you choose to leave them.

Who on our team has access

Members of our team have access to the information you provide us. For example, both Administrators and Shop Managers can access:

  • Order information like what was purchased, when it was purchased and where it should be sent, and
  • Customer information like your name, email address, and billing and shipping information.

Our team members have access to this information to help fulfill orders, process refunds and support you.

What we share with others

In this section you should list who you’re 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.

We share information with third parties who help us provide our orders and store services to you; for example --

Payments

In this subsection you should list which third party payment processors you’re using to take payments on your store since these may handle customer data. We’ve included PayPal as an example, but you should remove this if you’re not using PayPal.

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.

Please see the PayPal Privacy Policy for more details.

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

Really Simple SSL

Really Simple SSL and Really Simple SSL add-ons do not process any personal identifiable information, so the GDPR does not apply to these plugins or usage of these plugins on your website. You can find our privacy policy here.

WooCommerce

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.

We collect information about you during the checkout process on our store.

What we collect and store

While you visit our site, we’ll track:

  • Products you’ve viewed: we’ll use this to, for example, show you products you’ve recently viewed
  • Location, IP address and browser type: we’ll use this for purposes like estimating taxes and shipping
  • Shipping address: we’ll ask you to enter this so we can, for instance, estimate shipping before you place an order, and send you the order!

We’ll also use cookies to keep track of basket contents while you’re browsing our site.

Note: you may want to further detail your cookie policy, and link to that section from here.

When you purchase from us, we’ll 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’ll use this information for purposes, such as, to:

  • Send you information about your account and order
  • Respond to your requests, including refunds and complaints
  • Process payments and prevent fraud
  • Set up your account for our store
  • Comply with any legal obligations we have, such as calculating taxes
  • Improve our store offerings
  • Send you marketing messages, if you choose to receive them

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.

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.

We will also store comments or reviews, if you choose to leave them.

Who on our team has access

Members of our team have access to the information you provide us. For example, both Administrators and Shop Managers can access:

  • Order information like what was purchased, when it was purchased and where it should be sent, and
  • Customer information like your name, email address, and billing and shipping information.

Our team members have access to this information to help fulfill orders, process refunds and support you.

What we share with others

In this section you should list who you’re 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.

We share information with third parties who help us provide our orders and store services to you; for example --

Payments

In this subsection you should list which third party payment processors you’re using to take payments on your store since these may handle customer data. We’ve included PayPal as an example, but you should remove this if you’re not using PayPal.

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.

Please see the PayPal Privacy Policy for more details.

Really Simple SSL

Really Simple SSL and Really Simple SSL add-ons do not process any personal identifiable information, so the GDPR does not apply to these plugins or usage of these plugins on your website. You can find our privacy policy here.

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

Akismet

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).