Politica privind cookies

1. Introducere

Prezenta  politica privind fișierele Cookies se aplica tuturor utilizatorilor paginii de internet www.lacra.blog . Informațiile prezentate in continuare  au ca scop informarea utilizatorilor acestui blog cu privire la plasarea și administrarea Cookies  de către mine, Lacramioara Mirela Grosu, administratorul  blogului https://lacra.blog, in contextul navigării utilizatorilor pe aceasta pagini de internet.

2. Ce sunt cookie-urile?

Modulele cookie și instrumentele asemănătoare se referă la tehnologii prin intermediul cărora pot fi colectate informații in mod automat.

Un internet cookie/ HTTP cookie/ cookie reprezintă un fișier de dimensiuni mici, format din cifre și litere , care va fi stocat pe computerul, terminalul mobil sau alte echipamente ale unui utilizator prin intermediul cărora se accesează Internetul.

Cookie-urile sunt instalate prin solicitarea emisă de un web-server către un browser( de ex. Chrome, Firefox ). Odată instalate au o durata de existența determinata, rămânând “ pasive”, ceea ce vrea sa spună ca nu conțin programe software, viruși sau spyware și nu vor accesa informațiile de pe hard driverele utilizatorului pe al cărui echipament au fost instalate.

Un cookie are un nume și un conținut . Tehnic vorbind, doar web-serverul care a trimis cookie-ul îl poateaccesa din nou in momentul in care un utilizator se întoarce pe pagina de internet asociata web-serverului respectiv.

3.Scopul utilizării Cookies in blog

In general, cookie-urile sunt utilizate pentru  a asigura buna funcționare  a blogului și pentru a furniza utilizatorilor o calitate cât mai buna a experienței de navigare și pentru a obține informații legate de preferințele individuale ale diverșilor utilizatori  vis-a-vis de diversele subiecte prezentate.

Cookies ajuta la furnizarea de statistici anonime cu privire la modul cum este utilizat blogul, ceea ce m-a ajuta pe mine, ca administrator al blogului, sa apreciez interesul sau dezinteresul fata de anumite subiecte ,  ceea ce îmbunătățește calitatea subiectelor și temelor abordate de către mine.

Cookies ajuta și la îmbunătățirea utilizării paginii de blog.

Blogul nu conține reclame, dar, in eventualitatea ca vor exista bannere , acestea vor ajuta la  anticiparea intereselor utilizatorilor.

Exista, totuși, banneru-ul cu mesajul de informare privind prezenta Cookies și cu rubrica ca acceptați sau nu utilizarea lor.

4. Durata de viața a cookies

Exista cookies de sesiune și cookies persistente. Primele se șterg automat când utilizatorul își Închide browserul. Cele persistente rămân stocate in serverul utilizatorului pana când atinge o anumită data de expirare ( minute, zile, luni ) sau pana la ștergerea acestuia de către utilizator folosind setările din browser.

5. Cookies plasate de terți

Anumite părți din blog pot fi furnizate prin intermediul așa numitilor terți  – Third party Cookies ( cookies de la parti terte ).

Terții trebuie , la rândul lor, sa respecte  legile in vigoare privind protecția datelor personale.

6.Cookies folosite in acest blog

Cookies funcționale  care memorează preferințele utilizatorilor acestui blog. Mai exact, prin Cookies plasate de către WordPress se rețin numele, adresa de email și site-ul completat in momentul publicării unui comentariu pe blog, astfel încât data viitoare sa găsiți aceste date deja completate. Pentru mai multe detalii puteți accesa WordPress și plugin-ul acestuia, Jetpack.

Din ceea ce înțeleg eu, WordPress a adăugat recent posibilitatea de a nu accepta acest cookie , iar date voastre nu vor fi completate automat in eventualitatea unui nou comentariu.

Un alt cookie plasat de blog retine ca ați văzut mesajul privind Politica de  cookie și ca ați acceptat-o sau nu, astfel încât acel mesaj sa nu va mai fie afișat data viitoare când accesați  blogul. 

Un alt cookie tine statistica și este asigurat de Google Analytics. Aceasta statistica arată cât trafic e pe blog, ce pagini au fost vizitate, de unde au venit cititorii și încotro au plecat.

7. Alte informații stocate in cookies

Cokies păstrează informații intr-un fișier text de dimensiuni mici care permit recunoașterea browserului. Aceasta pagina de internet recunoaște browserul pana când Cookies sunt șterse sau expira.

8.Particularizarea setărilor browserului in ceea ce privește cookies

Dacă  echipamentul folosit pentru navigare pe blogul meu este folosit doar de o singura persoana, atunci se pot seta termene lungi  de expirare pentru stocarea istoricului de navigare. In caz opus, dacă echipamentul este folosit de către mai multe persoane,  se poate efectua setarea pentru ștergerea datelor individuale de navigare de fiecare data când browser-ul  este închis.

10. Cum pot fi oprite Cookies ?

Dezactivarea si refuzul de a primi Cookies pot face dificila navigarea pe acest blog.

Toate browserele moderne oferă posibilitatea de a schimba setările Cookies in secțiunea “ opțiuni” sau in meniul de “ preferințe “ al browserului tău .

 

Mai multe informatii despre cookies folosite pe acest site gasiti mai jos.

Folositi unealta GOOGLE TRANSLATE din bara laterala a site-ului pentru a traduce .

Cookie Policy

Our Privacy Policy explains our principles when it comes to the collection, processing, and storage of your information. This policy specifically explains how we, our partners, and users of our services deploy cookies, as well as the options you have to control them.

What are cookies?

Cookies are small pieces of data, stored in text files, that are stored on your computer or other device when websites are loaded in a browser. They are widely used to “remember” you and your preferences, either for a single visit (through a “session cookie”) or for multiple repeat visits (using a “persistent cookie”). They ensure a consistent and efficient experience for visitors, and perform essential functions such as allowing users to register and remain logged in. Cookies may be set by the site that you are visiting (known as “first party cookies”), or by third parties, such as those who serve content or provide advertising or analytics services on the website (“third party cookies”).

Both websites and HTML emails may also contain other tracking technologies such as “web beacons” or “pixels.” These are typically small transparent images that provide us with statistics, for similar purposes as cookies. They are often used in conjunction with cookies, though they are not stored on your computer in the same way. As a result, if you disable cookies, web beacons may still load, but their functionality will be restricted.

How we use cookies

We use cookies for a number of different purposes. Some cookies are necessary for technical reasons; some enable a personalized experience for both visitors and registered users; and some allow the display of advertising from selected third party networks. Some of these cookies may be set when a page is loaded, or when a visitor takes a particular action (clicking the “like” or “follow” button on a post, for example).

Many of the cookies we use are only set if you are a registered WordPress.com user (so you don’t have to log in every time, for example), while others are set whenever you visit one of our websites, irrespective of whether you have an account.

For more information on the choices you have about the cookies we use, please see the Controlling Cookies section below.

Where we place cookies

We set cookies in a number of different locations across our services. These include:

  • On our websites (including automattic.com, wordpress.com, vip.wordpress.com, jetpack.com, gravatar.com, intensedebate.com, vaultpress.com, and akismet.com).
  • In the administrative dashboards of our websites, such as Calypso and wp-admin.
  • On sites we host for our users.
  • On sites that use our plugins (e.g. Jetpack).
  • In the emails we send.

User Sites

In addition to the cookies set on our own sites, we utilize cookies for our Site Statsfeature. This tallies the unique numbers of visitors to a site, as well as the number from specific geographic locations. A visitor is counted when we see a user or browser for the first time in a given period.

Examples

Below are examples of the cookies set by Automattic, with explanations of their purpose. Some of these cookies are set across our whole network, whereas some are specific to individual services (e.g. WordPress.com, Longreads, etc). Please note that this is not an exhaustive list, but rather aims to be representative. Information about cookies that may be set by third parties, such as our ads partners, is below. Additionally, we occasionally set referrer cookies on Jetpack connected sites, using WooCommerce.

In addition, people and companies that use our services to publish or host their own sites may place additional cookies. We provide more information on these cookies below.

Advertising

Cookie Purpose
ads Tracks if a visitor has clicked an ad before.
lr_nw Counts and tracks pageviews on Longreads.com. Used to determine whether or not to show our Membership popup message.
wordpress_eli Reduces the display of ads for repeat visitors.

Please also see the section below on third party advertisements that you may see on our sites or sites that use our services.

Analytics and Performance

Cookie Purpose
__pdvt Used in log of Crowdsignal survey data to aid in debugging customer problems
ab Used for “AB testing” of new features.
nux_flow_name Identifies which user signup flow was shown to the user.
tk_ni / tk_ai / tk_qs Gathers information for our own, first party analytics tool about how our services are used. A collection of internal metrics for user activity, used to improve user experience.
tk_*r Referral cookies used to analyse referrer behavior for Jetpack connected sites using WooCommerce.
wp-affiliate-tracker Remembers the ID of the affiliate that referred the current user to WordPress.com
utma / utmb / utmc / utmt / utmz / ga / gat / gid Google Analytics. Gathers information that helps us understand how visitors interact with our websites, which allow us to create a better experience for our visitors. Our users may also implement Google Analytics on their own websites.

Functionality

Cookie Purpose
_longreads_prod_new Authentication for Longreads.com Member accounts. Only active when logged in, on *.longreads.com domains.
akm_mobile Stores whether a user has chosen to view the mobile version of a website.
botdlang Used to track the language a user has selected to view popular blogs in.
landingpage_currency Defines the currency displayed in WordPress.com landing pages.
pd_dashboard Records last used folder in Crowdsignal dashboard so it can be reopened upon user’s next visit.
PD_USER_AUTH Login cookie used to identify Crowdsignal user.
wordpress_logged_in* Checks whether or not the current visitor is a logged in WordPress.com user.
wp-settings-{user_id} Persists a user’s wp-admin configuration.
wp_sharing_{id} Tracks whether or not a user has already performed an action.

Security

Cookie Purpose
csrftoken Python/Ajax security cookie used on accounts.longreads.com.

Strictly Necessary

Cookie Purpose
country_code Used in order to determine whether or not the cookie banner should be shown. Set immediately on page load and retained for 6 hours to remember the visitor’s country.
sensitive_pixel_option Remembers the state of visitor acceptance to the cookie banner. Only set when the visitor clicks Accept.
twostep_auth Set when the user is logged in using two factor authentication.
wordpress_test_cookie Checks if cookies are enabled to provide appropriate user experience.

Advertisements from Third Parties Through Automattic’s Ads Program

Our mission is to democratize publishing. So that we can offer free access to create a website using WordPress.com, we show ads on some of our users’ sites. Our users may also choose to place ads on their site through our ads program. Additionally, we also show ads from our ads program on some of our own websites (e.g. longreads.com), and in emails.

We operate our ads program in partnership with third party vendors. As part of the operation of our ads program, we use cookies to collect certain information. Advertising cookies enable us and our partners to serve ads and to personalize those ads based on information like visits to our sites and other sites on the Internet.

Below is a representative list of our advertising program partners, along with information on the cookies that that each partner sets. The partners we work with change from time to time, and this is not an exhaustive list. Your choices to control cookies related to our ads program are described below.

Partner Cookie Info
Amazon https://www.amazon.co.uk/gp/help/customer/display.html/ref=footer_iba?ie=UTF8&nodeId=201909150
AppNexus https://www.appnexus.com/en/company/cookie-policy
BidSwitch http://www.bidswitch.com/cookie-statement/
FreeWheel http://freewheel.tv/privacy-policy/
Google (AdSense, DoubleClick Ad Exchange “AdX”) https://policies.google.com/technologies/ads
OATH https://policies.oath.com/us/en/oath/privacy/topics/cookies/index.html
Polymorph https://getpolymorph.com/privacy-policy/
PowerInBox https://powerinbox.com/privacy-policy/
Pubmatic https://pubmatic.com/legal/website-cookie-policy/
Rubicon https://rubiconproject.com/privacy/consumer-online-profile-and-opt-out/
Skimlinks https://skimlinks.com/user-cookies and https://skimlinks.com/privacy-policy

Below is a representative list of the cookies that may be set by our ads partners in connection with ads that appear in emails.

Cookie Purpose
pi-userid Used to personalize email-based ads.
eid_ Used in email-based ads to track if a visitor has clicked an ad and report to advertisers how their ads performed.

Visitors to Sites with Jetpack installed

Below are examples of the cookies set for visitors to sites with the Jetpack plugin installed. For more details on the cookies set for administrators, please see https://jetpack.com/support/cookies/.

Jetpack Comments

Cookie Name Purpose
comment_author_{HASH} Remembers the value entered into the comment form‘s name field. Specific to the site from which it is set. This cookie mirrors one set by the core WordPress software for commenting purposes.
comment_author_email_{HASH} Remembers the value entered into the comment form‘s email field. Specific to the site from which it is set. This cookie mirrors one set by the core WordPress software for commenting purposes.
comment_author_url_{HASH} Remembers the value entered into the comment form‘s URL field. Specific to the site from which it is set. This cookie mirrors one set by the core WordPress software for commenting purposes

Mobile Theme

Cookie Name Purpose
akm_mobile Remembers whether or not a user wishes to view the mobile version of a site.

Subscriptions

Cookie Name Purpose
jetpack_comments_subscribe_{HASH} Remembers the state of the post and comment subscription checkboxes.
jetpack_blog_subscribe_{HASH} Remembers the state of the post and comment subscription checkboxes.

Controlling Cookies

Visitors may wish to restrict the use of cookies or completely prevent them from being set. Most browsers provide for ways to control cookie behavior such as the length of time they are stored – either through built-in functionality or by utilizing third party plugins. If you disable cookies, please be aware that some of the features of our service may not function correctly.

To find out more on how to manage and delete cookies, visit aboutcookies.org. For more details on your choices regarding use of your web browsing activity for interest-based advertising you may visit the following sites:

On a mobile device, you may also be to adjust your settings to limit ad tracking.

You can opt out of Google Analytics by installing Google’s opt-out browser add-on.

Our Internal Analytics Tool

In order to better understand how our services are used, we monitor certain user activities that take place within our products, including page views and clicks on any links used when managing a site via our dashboards.

We call each one of these actions an “event.” Analytics events are attached to your WordPress.com account and are handled via a first party system that Automattic owns and maintains. In general, we record the following data for each event: IP address, WordPress.com user ID and username, WordPress.com-connected site ID (for sites not hosted on WordPress.com), user agent, referring URL, timestamp of event, browser language, and country code.

We use this information to improve our products, make our marketing to you more relevant, personalize your experience, and for the other purposes described in our Privacy Policy.

You may opt out of our analytics program through your user settings. By doing so, you won’t share information with our analytics tool about events or actions that happen after the opt-out, while logged in to your WordPress.com account. Note that opting out does not disable the functionality of the actions we track – for example, if you publish a post, we will still have record of that (don’t worry!), but for an event or action after you opt out, we will not have other data associated with that action or event in the analytics tool.

For our Simplenote Users: We use our first party analytics tool in Simplenote to help us better understand how Simplenote is used and improve the app for our users. You may opt-out through your privacy settings in the app. By doing so, you won’t share information with our analytics tool about events or actions that happen after the opt-out. One more thing–For Simplenote users who log onto Simplenote using their WordPress.com login, if you’d like to opt-out of our analytics tool on Simplenote, you’ll also need to opt out on the Simplenote app–not on your WP.COM Account Privacy Settings.

Contact Us

If you have any questions about our use of cookies, you can find the most relevant contact details in our Privacy Policy.