{"id":1351,"date":"2022-02-06T22:52:48","date_gmt":"2022-02-06T22:52:48","guid":{"rendered":"https:\/\/brilliantbikinies.com\/?page_id=1351"},"modified":"2022-02-06T23:41:05","modified_gmt":"2022-02-06T23:41:05","slug":"cookies-policy","status":"publish","type":"page","link":"https:\/\/brilliantbikinies.com\/es\/cookies-policy\/","title":{"rendered":"Cookies Policy"},"content":{"rendered":"

Cookies Policy<\/h1>\n
At Brilliant Bikinie\u2019s, we believe in being clear and open about how we collect and use data related to you. This Cookie Policy applies to any Brilliant Bikinie\u2019s product or service that links to this policy or incorporates it by reference. We use cookies and similar technologies such as pixels, local storage and mobile ad IDs (collectively referred to in this policy as \u201ccookies\u201d) to collect and use data as part of our Services, as defined in our Privacy Policy (\u201cServices\u201d) and which includes our sites, communications, mobile applications and off-site Services, such as our ad services and the \u201cApply with Brilliant Bikinie\u2019s\u201d and \u201cShare with Brilliant Bikinie\u2019s\u201d plugins or tags. In the spirit of transparency, this policy provides detailed information about how and when we use these technologies.
\nBy continuing to visit or use our Services, you are agreeing to the use of cookies and similar technologies for the purposes described in this policy.\n<\/div>\n
\n
What are cookies?<\/h5>\n

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 \u201cremember\u201d you and your preferences, either for a single visit (through a \u201csession cookie\u201d) or for multiple repeat visits (using a \u201cpersistent cookie\u201d). 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 \u201cfirst party cookies\u201d), or by third parties, such as those who serve content or provide advertising or analytics services on the website (\u201cthird party cookies\u201d).<\/p>\n

Both websites and HTML emails may also contain other tracking technologies such as \u201cweb beacons\u201d or \u201cpixels.\u201d 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.<\/p>\n<\/div>\n

\n
How we use cookies<\/h5>\n

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 \u201clike\u201d or \u201cfollow\u201d 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\u2019t 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, woocommerce.com, crowdsignal.com, gravatar.com, intensedebate.com, vaultpress.com, akismet.com, simplenote.com, simperium.com, leandomainsearch.com, cloudup.com, longreads.com, and happy.tools). 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. Types of Cookie The table below explains the types of cookies we use on our websites and why we use them.<\/p>\n<\/div>\n

Types of Cookie<\/h1>\n
The table below explains the types of cookies we use on our websites and why we use them.<\/div>\n

What technologies are used?<\/h1>\n\n\n\n
\n\n\n\n\n\n\n
Category of cookies<\/b><\/td>\nWhy we use these cookies<\/b><\/td>\n<\/tr>\n
Required<\/span><\/td>\nThese cookies are essential for our websites and services to perform basic functions and are necessary for us to operate certain features. These include those required to allow registered users to authenticate and perform account-related functions, store preferences set by users such as account name, language, and location, and ensure our services are operating properly.<\/span><\/td>\n<\/tr>\n
Analytics and Performance<\/span><\/td>\nThese cookies allow us to optimize performance by collecting information on how users interact with our websites, including which pages are visited most, as well as other analytical data. We use these details to improve how our websites function and to understand how users interact with them.<\/span><\/td>\n<\/tr>\n
Advertising<\/span><\/td>\nThese cookies are set by us and our advertising partners to provide you with relevant content and to understand that content\u2019s effectiveness. They may be used to collect information about your online activities over time and across different websites to predict your preferences and to display more relevant advertisements to you. These cookies also allow a profile to be built about you and your interests and enable personalized ads to be shown to you based on your profile.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

User Sites<\/h1>\n
In addition to the cookies set on our own sites, we utilize cookies for our Site Stats feature. 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.<\/div>\n

Examples<\/h1>\n
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.<\/p>\n

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.<\/p><\/div>\n

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Cookie<\/b><\/td>\nPurpose<\/b><\/td>\n<\/tr>\n
__ssid<\/td>\nFor processing payment and to aid in fraud detection.<\/td>\n<\/tr>\n
__stripe_sid \/ __stripe_mid<\/td>\nFor processing payment and to aid in fraud detection.<\/td>\n<\/tr>\n
_longreads_prod_new<\/td>\nAuthentication for Longreads.com Member accounts. Only active when logged in, on *.longreads.com domains.<\/td>\n<\/tr>\n
akm_mobile<\/td>\nStores whether a user has chosen to view the mobile version of a website.<\/td>\n<\/tr>\n
botdlang<\/td>\nUsed to track the language a user has selected to view popular blogs in.<\/td>\n<\/tr>\n
country_code<\/td>\nUsed 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.<\/td>\n<\/tr>\n
csrftoken<\/td>\nPython\/Ajax security cookie used on accounts.longreads.com.<\/td>\n<\/tr>\n
forterToken<\/td>\nFor processing payment and to aid in fraud detection.<\/td>\n<\/tr>\n
landingpage_currency<\/td>\nDefines the currency displayed in WordPress.com landing pages.<\/td>\n<\/tr>\n
pd_dashboard<\/td>\nRecords last used folder in Crowdsignal dashboard so it can be reopened upon user\u2019s next visit.<\/td>\n<\/tr>\n
PD_USER_AUTH<\/td>\nLogin cookie used to identify Crowdsignal user.<\/td>\n<\/tr>\n
sensitive_pixel_option<\/td>\nRemembers the state of visitor acceptance to the cookie banner. Only set when the visitor clicks Accept.<\/td>\n<\/tr>\n
twostep_auth<\/td>\nSet when the user is logged in using two factor authentication.<\/td>\n<\/tr>\n
wordpress_logged_in*<\/td>\nChecks whether or not the current visitor is a logged in WordPress.com user.<\/td>\n<\/tr>\n
wordpress_test_cookie<\/td>\nChecks if cookies are enabled to provide appropriate user experience.<\/td>\n<\/tr>\n
wp-settings-{user_id}<\/td>\nPersists a user\u2019s wp-admin configuration.<\/td>\n<\/tr>\n
wp_sharing_{id}<\/td>\nTracks whether or not a user has already performed an action.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
\n