{"id":2529,"date":"2016-07-27T10:08:07","date_gmt":"2016-07-27T10:08:07","guid":{"rendered":"https:\/\/wittyfutty.com\/?page_id=2529"},"modified":"2019-12-19T20:19:26","modified_gmt":"2019-12-19T20:19:26","slug":"privacy-policy","status":"publish","type":"page","link":"https:\/\/wittyfutty.com\/privacy-policy\/","title":{"rendered":"Privacy policy"},"content":{"rendered":"
This privacy policy is for this website wittyfutty.com and governs the privacy of its users who choose to use it.<\/p>\n
The policy sets out the different areas where user privacy is concerned and outlines the obligations & requirements of the users, the website and website owners. Furthermore the way this website processes, stores and protects user data and information will also be detailed within this policy.<\/p>\n
wittyfutty.com is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn fees by linking to Amazon.com and affiliated sites.<\/p>\n
What is personal information? Personal information is any information that allows someone to identify you, including, for example, your name, address, telephone and mobile numbers, email address, as well as any information about you that is associated with or linked to, or could be linked to, any of the foregoing data.<\/p>\n
Personal information that is provided by you will only be used for the purpose for which it is provided, unless you are informed otherwise at the time of giving the information.<\/p>\n
Wittty Futty will from time to time collect information from you for the purpose of creating de-personalised data that does not reveal your identity.<\/p>\n
Your personal information may be processed both in and outside the UK. When you submit your details in whichever country you are situated you agree to the information being processed in the UK.<\/p>\n
The Websites and our servers, wherever they are based, have appropriate technical and organisational measures in place to protect against unauthorised or unlawful use of your personal information as well as the accidental loss, destruction or damage of your personal information whilst under our control.<\/p>\n
However no data transmission over the internet can be guaranteed to be 100% secure and whilst we strive to protect your personal information, we cannot guarantee the security of any information you transmit to us and you do so at your own risk.<\/p>\n
Witty Futty processes personal information for the following purposes:<\/p>\n
We may disclose depersonalised data (such as aggregated statistics) about the users of our Websites in order to describe our sales, customers, traffic patterns and other site information to prospective partners, advertisers, investors and other reputable third parties and for other lawful purposes, but these statistics will include no personally identifying information.<\/p>\n
Under certain circumstances we may occasionally be required by law, court order or governmental authority to disclose certain types of personal information and we reserve the right to comply with any such legally binding request. Examples of the type of situation where this would occur would be:<\/p>\n
Other than this, Witty Futty will not disclose any of your personal information to any other third parties without your consent.<\/p>\n
This website and its owners take a proactive approach to user privacy and ensure the necessary steps are taken to protect the privacy of its users throughout their visiting experience. This website complies to all UK national laws and requirements for user privacy.<\/p>\n
This feature only records activities of a site\u2019s registered users, and the retention duration of activity data will depend on the site\u2019s plan and activity type.<\/p>\n
Data Used: To deliver this functionality and record activities around site management, the following information is captured: user email address, user role, user login, user display name, WordPress.com and local user IDs, the activity to be recorded, the WordPress.com-connected site ID of the site on which the activity takes place, the site\u2019s Jetpack version, and the timestamp of the activity. Some activities may also include the actor\u2019s IP address (login attempts, for example) and user agent.<\/p>\n
Activity Tracked: Login attempts\/actions, post and page update and publish actions, comment\/pingback submission and management actions, plugin and theme management actions, widget updates, user management actions, and the modification of other various site settings and options. Retention duration of activity data depends on the site\u2019s plan and activity type. See the complete list of currently-recorded activities (along with retention information).<\/p>\n
Data Synced (?): Successful and failed login attempts, which will include the actor\u2019s IP address and user agent.<\/p>\n
Data Used: This feature will send a hash of the user\u2019s email address (if logged in to the site or WordPress.com \u2014 or if they submitted a comment on the site using their email address that is attached to an active Gravatar profile) to the Gravatar service (also owned by Automattic) in order to retrieve their profile image.<\/p>\n
This feature is only accessible to users logged in to WordPress.com.<\/p>\n
Data Used: In order to process a post like action, the following information is used: IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID (on which the post was liked), post ID (of the post that was liked), user agent, timestamp of event, browser language, country code.<\/p>\n
Activity Tracked: Post likes.<\/p>\n
Data Used: A visitor\u2019s preference on viewing the mobile version of a site.<\/p>\n
Activity Tracked: A cookie (akm_mobile) is stored for 3.5 days to remember whether or not a visitor of the site wishes to view its mobile version. Learn more about this cookie.<\/p>\n
This feature is only accessible to registered users of the site who are logged in to WordPress.com.<\/p>\n
Data Used: IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code. Some visitor-related information or activity may be sent to the site owner via this feature. This may include: email address, WordPress.com username, site URL, email address, comment content, follow actions, etc.<\/p>\n
Activity Tracked: Sending notifications (i.e. when we send a notification to a particular user), opening notifications (i.e. when a user opens a notification that they receive), performing an action from within the notification panel (e.g. liking a comment or marking a comment as spam), and clicking on any link from within the notification panel\/interface.<\/p>\n
This feature is only available to sites on the Professional plan.<\/p>\n
Data Used: Any of the visitor-chosen search filters and query data in order to process a search request on the WordPress.com servers.<\/p>\n
Data Used: When sharing content via email (this option is only available if Akismet is active on the site), the following information is used: sharing party\u2019s name and email address (if the user is logged in, this information will be pulled directly from their account), IP address (for spam checking), user agent (for spam checking), and email body\/content. This content will be sent to Akismet (also owned by Automattic) so that a spam check can be performed. Additionally, if reCAPTCHA (by Google) is enabled by the site owner, the sharing party\u2019s IP address will be shared with that service. You can find Google\u2019s privacy policy here.<\/p>\n
Data Used: To initiate and process subscriptions, the following information is used: subscriber\u2019s email address and the ID of the post or comment (depending on the specific subscription being processed). In the event of a new subscription being initiated, we also collect some basic server data, including all of the subscribing user\u2019s HTTP request headers, the IP address from which the subscribing user is viewing the page, and the URI which was given in order to access the page (REQUEST_URI and DOCUMENT_URI). This server data used for the exclusive purpose of monitoring and preventing abuse and spam.<\/p>\n
Activity Tracked: Functionality cookies are set for a duration of 347 days to remember a visitor\u2019s blog and post subscription choices if, in fact, they have an active subscription.<\/p>\n
This feature is only accessible to registered users of the site with WordPress.com accounts.<\/p>\n
Data Used: User ID (local site and WordPress.com), role (e.g. administrator), email address, username and display name. Additionally, for activity tracking (see below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.<\/p>\n
Activity Tracked: The following usage events are recorded: starting the login process, completing the login process, failing the login process, successfully being redirected after login, and failing to be redirected after login. Several functionality cookies are also set, and these are detailed explicitly in our Cookie documentation.<\/p>\n
Data Synced (?): The user ID and role of any user who successfully signed in via this feature.<\/p>\n
Data Used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code. Important: The site owner does not have access to any of this information via this feature. For example, a site owner can see that a specific post has 285 views, but he\/she cannot see which specific users\/accounts viewed that post. Stats logs \u2014 containing visitor IP addresses and WordPress.com usernames (if available) \u2014 are retained by Automattic for 28 days and are used for the sole purpose of powering this feature.<\/p>\n
Activity Tracked: Post and page views, video plays (if videos are hosted by WordPress.com), outbound link clicks, referring URLs and search engine terms, and country. When this module is enabled, Jetpack also tracks performance on each page load that includes the Javascript file used for tracking stats. This is exclusively for aggregate performance tracking across Jetpack sites in order to make sure that our plugin and code is not causing performance issues. This includes the tracking of page load times and resource loading duration (image files, Javascript files, CSS files, etc.). The site owner has the ability to force this feature to honor DNT settings of visitors. By default, DNT is currently not honored.<\/p>\n
This feature is only accessible to registered users of the site who are also logged in to WordPress.com.<\/p>\n
Data Used: Gravatar image URL of the logged-in user in order to display it in the toolbar and the WordPress.com user ID of the logged-in user. Additionally, for activity tracking (detailed below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.<\/p>\n
Activity Tracked: Click actions within the toolbar.<\/p>\n
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor\u2019s IP address and browser user agent string to help spam detection.<\/p>\n
An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https:\/\/automattic.com\/privacy\/. After approval of your comment, your profile picture is visible to the public in the context of your comment.<\/p>\n
Data Used: Commenter\u2019s name, email address, and site URL (if provided via the comment form), timestamp, and IP address. Additionally, a jetpack.wordpress.com IFrame receives the following data: WordPress.com blog ID attached to the site, ID of the post on which the comment is being submitted, commenter\u2019s local user ID (if available), commenter\u2019s local username (if available), commenter\u2019s site URL (if available), MD5 hash of the commenter\u2019s email address (if available), and the comment content. If Akismet (also owned by Automattic) is enabled on the site, the following information is sent to the service for the sole purpose of spam checking: commenter\u2019s name, email address, site URL, IP address, and user agent.<\/p>\n
Activity Tracked: The comment author\u2019s name, email address, and site URL (if provided during the comment submission) are stored in cookies. Learn more about these cookies.<\/p>\n
Data Synced (?): All data and metadata (see above) associated with comments. This includes the status of the comment and, if Akismet is enabled on the site, whether or not it was classified as spam by Akismet.<\/p>\n
This feature is only accessible to users logged in to WordPress.com.<\/p>\n
Data Used: In order to process a comment like, the following information is used: WordPress.com user ID\/username (you must be logged in to use this feature), the local site-specific user ID (if the user is signed in to the site on which the like occurred), and a true\/false data point that tells us if the user liked a specific comment. If you perform a like action from one of our mobile apps, some additional information is used to track the activity: IP address, user agent, timestamp of event, blog ID, browser language, country code, and device info.<\/p>\n
Activity Tracked: Comment likes.<\/p>\n
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.<\/p>\n
This website uses cookies to better the users experience while visiting the website. Where applicable this website uses a cookie control system allowing the user on their first visit to the website to allow or disallow the use of cookies on their computer \/ device. This complies with recent legislation requirements for websites to obtain explicit consent from users before leaving behind or reading files such as cookies on a user's computer \/ device.<\/p>\n
Cookies are small files saved to the user's computers hard drive that track, save and store information about the user's interactions and usage of the website. This allows the website, through its server to provide the users with a tailored experience within this website.
\nUsers are advised that if they wish to deny the use and saving of cookies from this website on to their computers hard drive they should take necessary steps within their web browsers security settings to block all cookies from this website and its external serving vendors.<\/p>\n
Cookies used by this site for normal user experiance:<\/strong><\/p>\n