PixelPay's Cookies Policy
Pixelpay’s Cookie Policy
We receive a lot of traffic on our website, which is why, to distinguish you from other users of our website, our website uses cookies. Cookies also help us provide you with a good experience when you browse our website and also allow us to improve our site.
What is a Cookie? It is a small file of letters and numbers that we store on your browser or the hard drive of your computer if you permit us. Cookies contain information that is transferred to your computer’s hard drive.
We use the following cookies:
Strictly necessary cookies. These are cookies that are required for the operation of our website. They include, for example, cookies that enable you to log into secure areas of our website, and complete the merchant onboarding process.
Analytical or performance cookies. These allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This helps us to improve the way our website works, for example, by ensuring that users can easily navigate our website.
Targeting cookies. These cookies record your visit to our website and how you interact with it, e.g. which feature picked your interest and which ones did not. We will use this information to make our website more relevant to your interests. We may also share this information with third parties for this purpose.
You can find more information about the individual cookies we use and the purposes for which we use them in the table below:
STRICTLY NECESSARY
Name of Cookie
Provider/Domain
Description
_GRECAPTCHA
www.google.com
This cookie is set by reCAPTCHA, a service provided by Google to protect websites from spam and abuse. It’s used to distinguish between human and automated traffic.
bugsnag_dashboard_logged_in
.mypixelpay.com
This cookie is likely used for managing user sessions and authentication when logged into the Bugsnag dashboard.
ANALYTICAL / PERFORMANCE
Name of Cookie
Provider/Domain
Description
sb
.facebook.com
It’s commonly associated with Facebook’s services and may be used for session management, tracking user activities, and enhancing security.
AnalyticsSyncHistory
This cookie is often related to advertising and may store information about user interactions with ads.
ajs_anonymous_id
This is used for tracking anonymous user behaviour and collecting statistical information
fr
.facebook.com
This is often a Facebook cookie and may be related to ad tracking and user analytics.
muc_ads
.twitter.com
This cookie is for advertising
guest_id
.twitter.com
This is used for user identification and session management
_uetvid
.mypixelpay.com
The “_uetvid” cookie is related to Microsoft Advertising (formerly known as Bing Ads). It is used for tracking user interactions and conversions on websites that use Microsoft Advertising services.
_ga
.twitter.com
The “_ga” cookie is commonly associated with Google Analytics, a popular web analytics service. It is used for tracking and identifying unique users on a website. This cookie generates a unique identifier for each user, allowing website owners to gather information about user interactions, such as page views, sessions, and user behavior.
intercom-id-x1mf39c9
.mypixelpay.com
The “intercom-id-x1mf39c9” cookie is associated with Intercom, a customer messaging platform used by businesses for customer communication and support. It may be used for tracking user interactions, such as chat sessions and user behaviour, to improve customer support and user experience.
intercom-device-id-x1mf39c9
.mypixelpay.com
The “intercom-device-id-x1mf39c9” cookie is associated with Intercom, a customer messaging platform used by businesses for customer communication and support. It may be used for tracking user interactions, such as chat sessions and user behaviour, to improve customer support and user experience.
intercom-session-x1mf39c9
.mypixelpay.com
The “intercom-session-x1mf39c9” cookie is associated with Intercom, a customer messaging platform used by businesses for customer communication and support. It may be used for tracking user interactions, such as chat sessions and user behaviour, to improve customer support and user experience.
_clsk
.mypixelpay.com
The “_clsk” cookie is often associated with the Clicky web analytics service. It is used for tracking user interactions and collecting data for analytics and performance monitoring.
_ga_PZDH5T7NDP
.mypixelpay.com
Its primary purpose is to collect data for website analytics and performance tracking, helping website owners understand how users interact with their site.
_ga_YR26QNHTFN
.mypixelpay.com
Its primary purpose is to collect data for website analytics and performance tracking, helping website owners understand how users interact with their site.
_ga_9CLHNPSJFD
.mypixelpay.com
Its primary purpose is to collect data for website analytics and performance tracking, helping website owners understand how users interact with their site.
_rdt_uuid
.mypixelpay.com
The “_rdt_uuid” cookie is associated with Reddit, a social media platform. It is typically used for tracking user interactions, analytics, and performance monitoring on the Reddit website. Its primary purpose is to gather data for website analytics and performance tracking, helping Reddit understand user interactions and behavior on their platform.
_hjSessionUser_3317445
.webflow.com
.The “_hjSessionUser_3317445” cookie is typically associated with Hotjar, a web analytics and user feedback service. It is used for tracking user interactions and behavior on websites to help website owners understand how users engage with their site. This cookie, specific to a Hotjar session, collects data for analytical and performance monitoring, allowing website owners to make improvements to the user experience. The unique identifier “3317445” likely represents a session or user ID for tracking purposes within the Hotjar analytics system.
_clck
.mypixelpay.com
It is commonly used for tracking user interactions and collecting data for analytics and performance monitoring.
mp_e5854cff5b0f64f97675738be1b2ed3a_mixpanel
.mypixelpay.com
The “mp_e5854cff5b0f64f97675738be1b2ed3a_mixpanel” cookie is associated with Mixpanel, an analytics and marketing automation platform. It is used for tracking user interactions and collecting data for analytics and marketing purposes.
_gcl_au
.mypixelpay.com
The “_gcl_au” cookie is associated with Google Ads and is used for tracking and measuring conversions related to Google Ads campaigns.
_ga_YR26QNHTFN
..mypixelpay.com
The “_ga_YR26QNHTFN” cookie is a variation of the standard “_ga” cookie and is typically associated with Google Analytics. Like the standard “_ga” cookie, its primary purpose is to track and identify unique users on a website. This unique identifier allows website owners to collect data for website analytics and performance monitoring, including information about user interactions, page views, and user behavior. The specific expiration of the “_ga_YR26QNHTFN” cookie may vary based on the settings and preferences of the website using Google Analytics, but it is commonly used to track user activity over time for analytical purposes.
_uetsid
..mypixelpay.com
The “_uetsid” cookie is typically associated with Microsoft Advertising (formerly Bing Ads). It is used for tracking user interactions and conversions on websites that use Microsoft Advertising services. This cookie generates a unique identifier for each user’s session, allowing website owners to monitor and measure the effectiveness of advertising campaigns. It helps track user behavior, including page views and conversions, to analyze and optimize the performance of advertising efforts.
_gcl_au
..mypixelpay.com
The “_gcl_au” cookie is associated with Google Ads and is primarily used for tracking and measuring conversions related to Google Ads campaigns. Its main function is to track and measure conversions, helping advertisers understand the performance and effectiveness of their advertising campaigns, particularly those conducted through Google Ads. The specific expiration of the “_gcl_au” cookie may depend on the settings and preferences of Google Ads and the website using these advertising services, but it is primarily used for performance analytics and tracking the impact of advertising efforts.
MUID
.clarity.ms and .bing.com
These cookies are used for advertising, site analytics, and other operational purposes.
TARGETING
Name of Cookie
Provider/Domain
Description
__Secure-3PAPISID
www.google.com
This cookie is associated with Google’s services. They are used for user security, authentication, and to prevent fraudulent activities.
__Secure-1PAPISID
www.google.com
This cookie is associated with Google’s services. They are used for user security, authentication, and to prevent fraudulent activities.
SSID
www.google.com
This cookie is associated with Google’s services. They are used for user security, authentication, and to prevent fraudulent activities.
SAPISID
www.google.com
These Google cookies are related to user authentication, security, and the functioning of Google services.
personalization_id
.twitter.com
It is often used by Twitter to identify and track users across different websites and deliver personalized content or advertisements based on user preferences and browsing behavior. The cookie may store a unique identifier that helps Twitter recognize a user’s device and browser.
guest_id_ads
.twitter.com
The cookie is commonly associated with Twitter and is used for tracking and personalization, particularly in the context of advertising. It helps Twitter identify and track users across different websites and deliver personalized advertisements based on user preferences and browsing behavior
_fbp
.mypixelpay.com
Its primary purpose is to track and deliver personalized advertising content to users based on their interactions and behavior, especially on Facebook.
guest_id_marketing
.twitter.com
The “guest_id_marketing” cookie is also commonly associated with Twitter and is typically used for tracking and personalization, especially in the context of marketing and advertising. It helps Twitter identify and track users across different websites to deliver personalized marketing content, including advertisements, based on user preferences and browsing behavior.
SECURITY
Name of Cookie
Provider/Domain
Description
datr
.facebook.com
The “datr” cookie is associated with Facebook and is used for user authentication and security. It helps Facebook identify and verify the authenticity of users’ sessions and accounts.
__cf_bm
.mypixelpay.com
The “__cf_bm” cookie is associated with the Cloudflare security and content delivery network (CDN) service. It is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.
cf_clearance
.mypixelpay.com
Its primary purpose is to enhance security by identifying and protecting individual client sessions accessing a website through the Cloudflare network.
HSID
www.google.com
The “HSID” cookie is typically associated with Google services. It is used for enhancing the security of user sessions and authentications, particularly when accessing Google’s various services. This cookie plays a vital role in protecting user data from unauthorized access and ensuring the security of user accounts. It helps in identifying and verifying user sessions, adding an additional layer of security to Google services.
SID
www.google.com
The “SID” cookie is associated with Google services and plays a pivotal role in security and authentication. It is used for enhancing the security of user sessions and authentications, particularly when accessing various Google services. This cookie helps protect user data from unauthorized access and ensures the security of user accounts. The “SID” cookie is instrumental in verifying and managing user sessions across Google’s ecosystem.
__Secure-3PSIDCC
www.google.com
The “__Secure-3PSIDCC” cookie is connected to Google services and is primarily employed for security and authentication. It plays a key role in ensuring the security of user sessions and authentications, especially when accessing various Google services. This cookie is essential for safeguarding user data from unauthorized access and maintaining the overall security of user accounts. “__Secure-3PSIDCC” is instrumental in verifying and managing user sessions within the Google ecosystem, and the “__Secure” prefix indicates that it is transmitted securely.
SAPISID
www.google.com
The “SAPISID” cookie is often associated with Google services and is primarily used for security and user authentication. Its main role is to enhance the security of user sessions and authentications when accessing various Google services. This cookie is essential for protecting user data from unauthorized access and ensuring the security of user accounts. “SAPISID” is integral to verifying and managing user sessions within Google’s ecosystem, adding an extra layer of security to the services provided.
__Secure-3PSID
www.google.com
The “__Secure-3PSID” cookie is closely related to Google services and serves a crucial role in security and user authentication. Its primary function is to bolster the security of user sessions and authentications, particularly when users access various Google services. This cookie plays a vital role in safeguarding user data from unauthorized access and ensuring the security of user accounts. The “__Secure” prefix indicates that it is transmitted securely, and “__Secure-3PSID” is essential for verifying and managing user sessions within the Google ecosystem.
SIDCC
www.google.com
The “SIDCC” cookie is typically associated with Google services and is primarily used for security and authentication purposes. Its primary role is to enhance the security of user sessions and authentications, particularly when accessing various Google services. This cookie is instrumental in protecting user data from unauthorized access and ensuring the overall security of user accounts. “SIDCC” is essential for verifying and managing user sessions within the Google ecosystem, adding an additional layer of security to the services provided.
APISID
www.google.com
The “APISID” cookie is commonly linked to Google services. It primarily serves as a security and authentication cookie, ensuring the protection of user sessions and verifying access to various Google services. This cookie is crucial for enhancing the security of user accounts, helping to prevent unauthorized access to user data. It plays a key role in user authentication and session management within Google’s ecosystem.
Cookie Type
Use
Owner
Third Party
Internal Owner
Personal Info
Referring to data collected through forms First Name, Last Name, …etc used to ensure our services are provided in a secure space to relevant partners/clients
Pixelpay
No
Engineering Department/ Sales /Marketing
Personal Data for analytics and customization
We also collect more data through third party app like mixpanel and intercom to help improve our service to users ranging from ip adressed, region and activity carried out on out site
Pixelpay
Yes
Engineering Department
Authentication Cookie data
Bits of cookie data like username and password are stored for authentication, and access management
Pixelpay
Yes
Engineering Department
Marketing Cookie Data
We are also able to track a users experience of our website to see features they picked interest on, and the ones they didnt
Pixelpay
Yes
Engineering Department