Cookies Policy

At Brilliant Bikinie’s, 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’s 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 “cookies”) to collect and use data as part of our Services, as defined in our Privacy Policy (“Services”) and which includes our sites, communications, mobile applications and off-site Services, such as our ad services and the “Apply with Brilliant Bikinie’s” and “Share with Brilliant Bikinie’s” plugins or tags. In the spirit of transparency, this policy provides detailed information about how and when we use these technologies. By 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.
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, 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.

Types of Cookie

The table below explains the types of cookies we use on our websites and why we use them.

What technologies are used?

Category of cookies Why we use these cookies
Required These 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.
Analytics and Performance These 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.
Advertising These cookies are set by us and our advertising partners to provide you with relevant content and to understand that content’s 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.

User Sites

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.

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.
Cookie Purpose
__ssid For processing payment and to aid in fraud detection.
__stripe_sid / __stripe_mid For processing payment and to aid in fraud detection.
_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.
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.
csrftoken Python/Ajax security cookie used on accounts.longreads.com.
forterToken For processing payment and to aid in fraud detection.
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.
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_logged_in* Checks whether or not the current visitor is a logged in WordPress.com user.
wordpress_test_cookie Checks if cookies are enabled to provide appropriate user experience.
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.
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 tracking.  

Some analytics services we use, which place their own cookies or web tags on your browser, offer their own opt out choices. For example, you can opt out of Google Analytics by installing Google’s opt-out browser add-on, from Hotjar by using the Do Not Track header, and from Nielsen by clicking the opt out link found within Nielsen’s Privacy Statement.

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.

About

Help

© Brilliant Bikinie's. All rights reserved.