JSESSIONID cookie
Set by New Relic.
What it does
New Relic performance monitoring session.
- Cookie name
- JSESSIONID
- Category
- Analytics
- Provider
- New Relic
- Duration
- session
- Data source
- Kukie.io
Consent
JSESSIONID is in the Analytics category. In the EU and the UK, analytics cookies need the visitor's consent before they are set. California's CCPA works differently: it lets residents opt out of the sale or sharing of their personal information.
- GDPR and ePrivacy (EU)
- Prior consent is needed before setting JSESSIONID. Analytics cookies are not covered by the strictly necessary exemption; only a few regulators (for example France's CNIL) allow a narrow exemption for first-party audience measurement under strict conditions.
- UK GDPR and PECR
- Consent is needed before setting JSESSIONID. The ICO treats analytics cookies as non-essential.
- CCPA and CPRA (California)
- Disclose JSESSIONID in your privacy policy and honour opt-out requests, including the Global Privacy Control signal, if the analytics data is shared or sold.
Managing JSESSIONID with a consent banner
A consent banner can keep the script that sets JSESSIONID waiting until the visitor accepts analytics cookies. Kukie.io's cookie scanner finds JSESSIONID and sorts it into a category. The banner holds back known trackers by default, and any other script you tag with its category waits too.
- NRBA_SESSION Essential
Find every cookie your website sets, sorted into categories.
Questions about JSESSIONID
Does the JSESSIONID cookie need consent?
How long does the JSESSIONID cookie last?
Who sets the JSESSIONID cookie?
How do I block or delete the JSESSIONID cookie?
Ask before cookies like this are set.
Kukie.io finds the cookies on your website, sorts them into categories and holds back known trackers until visitors agree.
Disclaimer
Kukie.io provides tools to collect and record consent. It is not legal advice, and using it does not by itself make a website compliant with any law.
