Cookie Policy
Current consent state:
Please read this Cookie Policy in conjunction with our Privacy Policy, which sets out additional details on how we use personally identifiable information.
What are cookies?
Cookies are small pieces of text sent by your web browser by a website you visit. A cookie file is stored in your web browser and allows the site or a third-party to recognize you and make your next visit easier and the site more useful to you. Essentially, cookies are a user's identification card for the PhishingBox servers. Web beacons are small graphic files linked to our servers that allow us to track your use of our site and related functionalities. Cookies and web beacons allow us to serve you better and more efficiently, and to personalize your experience on our site.
How PhishingBox uses cookies
PhishingBox uses or may use cookies and/or web beacons to help us determine and identify repeat visitors, the type of content and sites to which a user of our site links, the length of time each user spends on any particular area of our site, and the specific functionalities that users choose to use. To the extent that cookie data constitutes personally identifiable information, we process such data on the basis of your consent. We use both session and persistent cookies on the site and we use different types of cookies to run the site:
Essential: Necessary for the operation of the site. We may use essential cookies to authenticate users, prevent fraudulent use of user accounts, or offer site features.
Analytical: Necessary for the operation of the site. We may use essential cookies to authenticate users, prevent fraudulent use of user accounts, or offer site features.
Targeting: Necessary for the operation of the site. We may use essential cookies to authenticate users, prevent fraudulent use of user accounts, or offer site features.
If you'd like to delete cookies or instruct your web browser to delete or refuse cookies, please visit the help pages of your web browser. Please note, however, that if you delete cookies or refuse to accept them, you might not be able to use some or all of the features we offer. You may not be able to log in, store your preferences, and some of our pages might not display properly.
Cookies Table
The tablebelow list some of the internal and third-party cookies we use. As the names, numbers, and purposes of these cookies may change over time, this page may be updated to reflect those changes.
| Category | Name | Site/System | Source | Description |
|---|---|---|---|---|
| Essential | __cf_bm | support.phishingbox.com | CloudFlare | Used to maximize network resources, manage traffic, and protect our Customers' sites from malicious traffic. |
| Essential | __cfruid | support.phishingbox.com | CloudFlare | Cloudflare cookie used in cases where multiple users are hidden behind the same client IP address. Each user will have a unique cookie to help prevent a case of rate limiting all users if one particular user hits the rate limit threshold. |
| Essential | __zlcmid | portal.phishingbox.com | ZenDesk | Used to store a unique user ID. |
| Essential | _cfduid | support.phishingbox.com | CloudFlare | Cloudflare cookie used for security restrictions. |
| Targeting | _fbp | www.phishingbox.com | Used to identify unique users. | |
| Analytical | _ga | www.phishingbox.com | Google Analytics | Used to identify unique users. |
| Analytical | _gat | support.phishingbox.com | Google Analytics | Used to distinguish users. |
| Analytical | _gid | www.phishingbox.com | Google Analytics | Used to identify unique users. |
| Essential | _help_center_session | support.phishingbox.com | ZenDesk | Stores unique session key for Help Center product. |
| Targeting | AnalyticsSyncHistory | www.phishingbox.com | Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries. | |
| Essential | AWSALBCORS | portal.phishingbox.com | Amazon | AWS Application Load Balancer Cookie. |
| Targeting | Bcookie | www.phishingbox.com | Browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform. | |
| Targeting | fr | www.phishingbox.com | Used to enable ad delivery or retargeting. | |
| Essential | FRONT_END_AUTH[user_id] | school.phishingbox.com | PhishingBox | Stores unique session key for course information. |
| Targeting | gclid | www.phishingbox.com | Google Ads | Used to identify unique users. |
| Targeting | lang | www.phishingbox.com | Provide targeted marketing to visitors. | |
| Targeting | li_sugr | www.phishingbox.com | Used to make a probabilistic match of a user's identity outside the Designated Countries. | |
| Targeting | lidc | www.phishingbox.com | To optimize data center selection. | |
| Essential | machine_uuid | www.phishingbox.com | PhishingBox | Used to keep track of user session. |
| Essential | PHPSESSID | portal.phishingbox.com school.phishingbox.com | PhishingBox | Used to keep track of user session. |
| Essential | PHPSESSION_PHISHINGBOXCOM | www.phishingbox.com | PhishingBox | Used to keep track of user session. |
| Targeting | test_cookie | www.phishingbox.com | Used to check if the user's browser supports cookies. | |
| Targeting | U | www.phishingbox.com | Not Identified | Collects unidentifiable data that is sent to an unidentifiable source. The source's identity is kept secret by the company, Whois Privacy Protection Service, Inc. |
| Targeting | UserMatchHistory | www.phishingbox.com | LinkedIn Ads ID syncing |