Who we are
I’m Andrea Gigliotti, owner of this website, and the website address is: https://viaggiareconandrea.com.
We will only collect and use your Personal Data where:
- we have lawful grounds to do so, including to comply with our legal obligations
- we are performing a contract with you for our services;
- we have legitimate interests in using your Personal Data and your interests and fundamental rights do not override those interests.
What personal data we collect and why we collect it
Personal Data we collect via our website [viagiareconandreaa.com] (the “Website”)
Personal Data that you provide to us
We only collect Personal Data where you choose to interact with us on the Website in the following ways:
Data that we collect automatically
We automatically collect certain information when you visit our Website – such as the type of browser and operating system you are using, and the domain name of your Internet service provider. We do not link this information with any Personal Data.
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.
This feature is only accessible to users logged in to WordPress.com.
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.
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.
This feature is only accessible to users logged in to WordPress.com.
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.
The activity tracked are comment likes.
The contact form submission data — IP address, user agent, name, email address, website, and message — is submitted to the Akismet service (also owned by Automattic) for the sole purpose of spam checking. The actual submission data is stored in the database of the site on which it was submitted and is emailed directly to the owner of the form (i.e. the site author who published the page on which the contact form resides). This email will include the submitter’s IP address, timestamp, name, email address, website, and message.
Post and post metadata associated with a user’s contact form submission are synced. If Akismet is enabled on the site, the IP address and user agent originally submitted with the comment are synced to the Askimet service, as well, as they are stored in post meta.
Post and post metadata associated with a user’s contact form submission may be synced. If Akismet is enabled on the site, the IP address and user agent originally submitted with the comment are synced, as well, as they are stored in post meta.
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 have an account and you log in to this site, 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.
The data used is about a visitor’s preference on viewing the mobile version of a site. 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.
This feature is only accessible to registered users of the site who are logged in to WordPress.com.
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 are used for notifications. 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.
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 are the tracked activities.
Embedded content from other websites
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.
Please refer to the appropriate Google Analytics documentation for the specific type of data it collects.
This feature sends page view events (and potentially video play events) over to Google Analytics for consumption.
This feature will send a hash of the user’s email address (if logged in to the site or WordPress.com — 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.
In order to record page views via WordPress.com Stats (which must be enabled for page view tracking here to work) with additional loads, the following information is 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.
Page views will be tracked with each additional load (i.e. when you scroll down to the bottom of the page and a new set of posts loads automatically). If the site owner has enabled Google Analytics to work with this feature, a page view event will also be sent to the appropriate Google Analytics account with each additional load.
Commenter’s name, email address, and site URL (if provided via the comment form), timestamp, and IP address are used as data. 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’s local user ID (if available), commenter’s local username (if available), commenter’s site URL (if available), MD5 hash of the commenter’s 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’s name, email address, site URL, IP address, and user agent.
The comment author’s name, email address, and site URL (if provided during the comment submission) are stored in cookies. Learn more about these cookies at https://automattic.com/cookies/
All data and metadata (see above) associated with comments are synced. 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.
In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user’s IP address, attempting user’s email address/username (i.e. according to the value they were attempting to use during the login process), and all IP-related HTTP headers attached to the attempting user.
Failed login attempts (these include IP address and user agent) are the tracked activity. We also set a cookie (jpp_math_pass) for 1 day to remember if/when a user has successfully completed a math captcha to prove that they’re a real human. Learn more about this cookie.
Failed login attempts, which contain the user’s IP address, attempted username or email address, and user agent information are synced data.
Data used for this feature are any of the visitor-chosen search filters and query data in order to process a search request on the WordPress.com servers.
To initiate and process subscriptions, the following information is used: subscriber’s 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’s 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.
Functionality cookies are set for a duration of 347 days to remember a visitor’s blog and post subscription choices if, in fact, they have an active subscription.
For video play tracking via WordPress.com Stats, the following information is used: viewer’s 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. If Google Analytics is enabled, video play events will be sent there, as well.
The activity tracked are video plays.
WordPress.com Secure Sign On
This feature is only accessible to registered users of the site with WordPress.com accounts.
This feature uses the following data: 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.
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.
The user ID and role of any user who successfully signed in via this feature are data synced.
Data Used by this feature are: 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 — containing visitor IP addresses and WordPress.com usernames (if available) — are retained by Automattic for 28 days and are used for the sole purpose of powering this feature.
This feature is only accessible to registered users of the site who are also logged in to WordPress.com.
The followind data are 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.
Click actions within the toolbar are tracked
Use of your Personal Data
We will only use your Personal Data when the law allows us to. Most commonly, we use your Personal Data to:
- process and manage your use of our website;
- respond to your questions, comments and requests;
- where you have opted-in to receive marketing from us, deliver communications that are relevant to your preferences / may be of interest to you;
- improve our services and Website through analysis of information.
Sharing of your Personal Data
We take your privacy seriously and will not share your Personal Data with others, except as permitted by applicable law or as set out below:
We share Personal Data as necessary with third parties who provide services or functions on our behalf and who require the information to provide those specific services to us. These third parties may include social media advertising platforms such as Facebook and Google Adwords for the purpose of custom audience generation and the development of targeting criteria for other audiences. Please note that we have appropriate data privacy safeguards in place with third parties with whom we share Personal Data as described above and who are providing services or functions on our behalf.
Keeping your Personal Data secure
We have implemented security policies and technical measures to safeguard the Personal Data we collect. We maintain physical, electronic and procedural safeguards that comply with applicable law, including the GDPR, to safeguard Personal Data from accidental loss, destruction or damage and unauthorised access, use and disclosure.
Retention periods for use of your Personal Data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
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.
This Website and our services are aimed at adults, and we do not knowingly collect any Personal Data relating to children aged under 15 years old. If you are under the age of 15, please do not provide us with any of your Personal Data, including your email address.
Access to and control over your Personal Data
You have legal rights under applicable law in relation to your Personal Data. You can ask the following questions, or take the following actions, at any time by contacting us via email at firstname.lastname@example.org.
- see what Personal Data we hold about you (if any), including why we are holding it and who it could be disclosed to;
- ask us to change/correct your Personal Data;
- ask us to delete your Personal Data;
- object to the processing of your Personal Data;
- ask us to restrict the processing of your Personal Data;
- withdraw any consents you have given us to the processing of your Personal Data;
- express any concerns you have about third parties’ use of your Personal Data.
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.
Change of purpose
We will only use your Personal Data for the purposes for which we collected it, unless we reasonably consider that we need to use it for another reason and that reason is compatible with the original purpose. If you wish to have an explanation as to how the processing for the new purpose is compatible with the original purpose, please contact us.
If we need to use your Personal Data for an unrelated purpose, we will notify you and we will explain the legal basis which allows us to do so.
Email for Privacy Questions: email@example.com