Where these cookies are used
Protectiv Prism helps website owners manage automated traffic. When a protected website asks your browser to complete a security challenge, Prism uses cookies to keep track of that attempt and recognize a successful check on later requests.
These are first-party cookies: they are set on the hostname of the website you are visiting. They are used when that site's protection policy invokes the challenge flow. Visiting a site that uses Prism does not necessarily mean you will receive every cookie listed below.
Cookies used by Prism
| Cookie | Purpose | Lifetime |
|---|---|---|
ab_attempt | Associates requests with a browser's challenge attempt and helps limit repeated attempts. | Session; no fixed expiry is set. Browser session-restore settings may keep it across restarts. |
protectiv_success | Records a successfully completed challenge while Prism validates the result and issues clearance. | Up to 2 minutes; removed when exchanged for clearance. |
protectiv_clearance | Lets Prism recognize a previously completed challenge on subsequent requests to the same hostname. | 30 minutes by default. The website's protection policy can select 1, 6, 12, or 24 hours instead. |
The attempt cookie contains a randomly generated identifier. The success and clearance cookies contain signed security tokens with an expiry and validation data derived from the visitor's IP address. The clearance is also tied to the hostname that issued it.
All three cookies are set by the server and marked HttpOnly, which prevents page JavaScript from reading them, and SameSite=Strict, which restricts when browsers send them with cross-site requests. The success and clearance cookies are also marked Secure, so browsers send them only over HTTPS.
After a successful challenge
Prism exchanges the short-lived success cookie for a clearance cookie, then removes the success cookie. A valid clearance allows requests through the challenge check for its lifetime; other security rules may still apply.
You may be asked to complete another challenge when clearance expires, you clear the cookie, your IP address changes, or the website's security configuration invalidates an earlier clearance. Clearance from one hostname does not provide clearance on another.
Information used for bot protection
Cookie values are only part of the security check. Prism also processes request and browser information, such as IP addresses, browser and device characteristics, and challenge results, to help identify automated activity and investigate abuse. A random identifier or signed token does not make the associated security data anonymous.
Cookie expiry describes how long a value remains usable in your browser. It does not describe how long related security logs are kept. For information about personal data, processing roles, and retention, please see our Privacy Policy and the privacy notice of the website you are visiting.
Managing these cookies
You can view or delete these cookies through your browser's settings for the protected website. Blocking them may prevent a challenge from completing or cause the website to ask you to verify again. Deleting a cookie does not delete security records already processed.
If a challenge keeps repeating, allowing cookies and JavaScript for that website may help. If the problem continues, the website owner can help review access to their site.
For website owners
If you use Prism's challenge protection, your visitor-facing privacy or cookie notice should explain this security use, identify the cookies that apply to your deployment, and describe their lifetimes. The clearance lifetime in your notice should match your protection policy.
This reference can support that notice. Disclosure and consent requirements depend on the applicable law and how the service is deployed. For personal information in customer traffic, Protectiv processes data on behalf of the website owner, as described in our Privacy Policy.
Cookies on protectiv.ph
The Cookie preferences control on protectiv.ph manages optional Google Analytics and PostHog analytics for our own website. It does not control Prism's security checks on other websites. Our Privacy Policy explains those analytics choices and the contact form's abuse-prevention checks.
Questions
For questions about Protectiv's use of security cookies, you can reach us at privacy@protectiv.ph. If your question concerns a particular protected website or access to it, please contact that website's owner.