Privacy and cookies policy

This post is also avai­la­ble in: Italian

Dataninja​.it is com­mit­ted to pro­tec­ting and respec­ting your pri­va­cy. This page tells you the data pro­tec­tion and pri­va­cy prac­ti­ces for Dataninja​.it, spe­ci­fi­cal­ly:

  • What per­so­nal­ly iden­ti­fia­ble infor­ma­tion is col­lec­ted
  • Which orga­ni­sa­tion is col­lec­ting this infor­ma­tion
  • How this infor­ma­tion is used
  • Our poli­cy on sha­ring this infor­ma­tion
  • How we pro­tect your infor­ma­tion
  • How you can cor­rect any inac­cu­ra­cies in this infor­ma­tion

Note: this page is inspi­red by the pri­va­cy and coo­kies poli­cy of CookieLawInfo​.com, author of the WordPress plu­gin used in this web­si­te.


We take your pri­va­cy very seriou­sly.

Children (under 18s) are not eli­gi­ble to use our ser­vi­ces and should not sub­mit any per­so­nal infor­ma­tion to Dataninja​.it.

Dataninja​.it does not acti­ve­ly track you as an indi­vi­dual.

Should you send us an email via the con­tact form on the side­bar, your name, email address and mes­sa­ge will be emai­led to us (as you would expect). This infor­ma­tion is kept pri­va­te. We will sto­re this infor­ma­tion within our own email system so that we are able to respond to you.

Should you com­ment on a blog post or web page on this site, then your name, email address, IP address and mes­sa­ge will be sto­red in our web­si­te data­ba­se (as you would expect). This makes your name, web­si­te address and com­ment (but not your email address) viewa­ble by the gene­ral public on the web­si­te.

The web­si­te does use some coo­kies when you bro­w­se this web­si­te. These are used to ensu­re pro­per run­ning of this web­si­te, to help us impro­ve your expe­rien­ce when bro­w­sing, and also to col­lect stric­tly aggre­ga­ted and ano­ni­mous usa­ge sta­ti­stics. If you don’t know what coo­kies are or if you would like to find out more, you sim­ply need to read Wikipedia.


The coo­kies we use are detai­led below:

Analytics Cookie by GoogleFirst-Party2 years (_ga) or 10 minu­tes (_gat)The Google Analytics JavaScript libra­ries use HTTP Cookies to “remem­ber” what a user has done on pre­vious pages / inte­rac­tions with the web­si­te. The analytics.js JavaScript libra­ry is part of Universal Analytics and uses fir­st-par­ty coo­kies to: distin­gui­sh uni­que users, throt­tle the reque­st rate. Please read the Google offi­cial docu­men­ta­tion for fur­ther details.
Gravatar Cookie by AutomatticThird-PartyUknownAutomattic uses coo­kies to help Automattic iden­ti­fy and track visi­tors, their usa­ge of Automattic web­si­te, and their web­si­te access pre­fe­ren­ces. Automattic visi­tors who do not wish to have coo­kies pla­ced on their com­pu­ters should set their bro­w­sers to refu­se coo­kies befo­re using Automattic’s web­si­tes, with the dra­w­back that cer­tain fea­tu­res of Automattic’s web­si­tes may not func­tion pro­per­ly without the aid of coo­kies. Please read the Automattic offi­cial pri­va­cy poli­cy for fur­ther details.
Social Cookie by TwitterThird-PartyUnknownTwitter uses coo­kies and other simi­lar tech­no­lo­gies, such as pixels or local sto­ra­ge, to help pro­vi­de you with a bet­ter, faster, and safer expe­rien­ce. […] Twitter uses the­se tech­no­lo­gies on our own web­si­tes and ser­vi­ces and on other web­si­tes that have inte­gra­ted our ser­vi­ces. This inclu­des our adver­ti­sing and plat­form part­ners’ web­si­tes and sites that use Twitter but­tons or wid­ge­ts, like our Tweet or fol­low but­tons. Third par­ties may also use the­se tech­no­lo­gies, for exam­ple, when you inte­ract with their con­tent from within our ser­vi­ces, like when you click a link or stream media on Twitter from a third-par­ty ser­vi­ce, and to help with the deli­ve­ry of ads sho­wn on and off of Twitter. Please read the offi­cial docu­men­ta­tion for fur­ther details.
WP Commenters CookieFirst-Party1 yearWhen visi­tors com­ment on this blog, they too get coo­kies sto­red on their com­pu­ter. This is pure­ly a con­ve­nien­ce, so that the visi­tor won’t need to re-type all their infor­ma­tion again when they want to lea­ve ano­ther com­ment. Three coo­kies are set for com­men­ters: com­ment_au­thor, com­ment_au­thor_e­mail, com­ment_au­thor_url. The com­men­ter coo­kies are set to expi­re a lit­tle under one year from the time they’re set. Please read the offi­cial docu­men­ta­tion for fur­ther details.
WP Logged in users CookieFirst-Party14 daysOn login, word­press uses the wordpress_[hash] coo­kie to sto­re your authen­ti­ca­tion details. Its use is limi­ted to the admin con­so­le area, /wp-admin/. After login, word­press sets the wordpress_logged_in_[hash] coo­kie, whi­ch indi­ca­tes when you’re log­ged in, and who you are, for most inter­fa­ce use. WordPress also sets a few wp-settings-{time}-[UID] coo­kies. The num­ber on the end is your indi­vi­dual user ID from the users data­ba­se table. This is used to custo­mi­ze your view of admin inter­fa­ce, and pos­si­bly also the main site inter­fa­ce. Please read the offi­cial docu­men­ta­tion for fur­ther details.
WPML Multilanguage CookieFirst-PartyUnknownThe Wordpress plu­gin WPML uses coo­kies to mana­ge mul­ti­lan­gua­ge con­ten­ts and remem­ber the user pre­fer­red lan­gua­ge. Please read the offi­cial docu­men­ta­tion for fur­ther details.


Cookie Type Duration Description

Cookies dura­tion may vary from few minu­tes to years. To manual­ly dele­te the coo­kie used to remem­ber if you have viewed this poli­cy or not, click here: Delete Cookies. To find out how to dele­te all coo­kies, plea­se read the AboutCookies​.org gui­de.

How this information is used

If you have cho­sen to share it with us, we use your email address to con­tact you in reply to your mes­sa­ge, or to send you our new­slet­ter. If you have ente­red your email address to lea­ve a com­ment on the blog, it is used to iden­ti­fy your com­ment, howe­ver it is not displayed on the web­si­te or shared with any third par­ty.

We may also use your email to help resol­ve issues or dispu­tes, for exam­ple if you tell us that you can­not see any of your posts on the web­si­te, we would pro­ba­bly sear­ch our data­ba­se using your email address to help dia­gno­se the pro­blem.

Our disclosure of this information

We do not share your per­so­nal infor­ma­tion or email address with third par­ties.

Email opt-out

Just like you, we hate spam. We do not send you spam emails. You may opt-out of our emails at any time. An unsub­scri­be link is inclu­ded in all of our email new­slet­ters.

Protection of your information

Dataninja​.it uses best endea­vour to safe­guard the con­fi­den­tia­li­ty of your per­so­nal­ly iden­ti­fia­ble infor­ma­tion but we do not use encryp­tion (such as SSL) or firewalls to fur­ther pro­tect the infor­ma­tion as it tra­vels across the Internet. We do not belie­ve that the per­so­nal infor­ma­tion we col­lect war­ran­ts this level of secu­ri­ty. It is impor­tant to be aware that the­re is no such thing as “per­fect inter­net secu­ri­ty”.

How to correct inaccurate information

Once posted, you can­not chan­ge or remo­ve any com­men­ts you have sub­mit­ted on our web­si­te pages and/or posts. However, if you would like to have this infor­ma­tion remo­ved plea­se con­tact us and we will do this for you.

You should know that becau­se of tech­ni­cal con­strain­ts, all infor­ma­tion is never com­ple­te­ly remo­ved from our data­ba­ses. Therefore, you should not expect that all of your per­so­nal­ly iden­ti­fia­ble infor­ma­tion will be com­ple­te­ly remo­ved from our data­ba­ses in respon­se to your requests that it be remo­ved. We will aim to remo­ve all publi­cly-facing infor­ma­tion.

How to contact us

Please use the con­tact form on this site to con­tact us.

Changes to the Privacy Policy

From time to time we may upda­te this Privacy Policy in line with web­si­te chan­ges that may affect the per­so­nal infor­ma­tion we gather about you. It is assu­med that you accept such chan­ges if you con­ti­nue to use the site and ser­vi­ces. If you do not accept such chan­ges then you should stop using’s web­si­te and ser­vi­ces, and con­tact us (details abo­ve) if you would like any infor­ma­tion remo­ved.