Cookie Policy
Last updated: 2026-04-13
This Cookie Policy explains how B-Sense uses cookies and similar technologies on https://b-sense.hismis.com.
1. What We Use Cookies For
We use cookies and similar technologies to:
- keep essential website functions working
- support login, membership, and checkout-related session handling
- measure website usage and improve the service where analytics is enabled or accepted
2. Cookie Categories
Current v1 category model:
NecessaryAnalytics
We do not currently define separate public cookie categories for marketing cookies.
3. Current Inventory Snapshot
Based on the current audit of the main website flows (/, /plans/, /membership-checkout/, /login/, /membership-account/), the website may use the following items.
Necessary
PHPSESSID
– Purpose: session handling on membership / checkout-related flows – Source: website/session handling – Duration: session
googtrans
– Purpose: keep the selected or auto-detected website translation state for the GTranslate widget – Source: GTranslate / Google Translate – Duration: session in the current main-flow audit
gt_autoswitch(localStorage)
– Purpose: remember the current GTranslate auto-switch state – Source: GTranslate / Google Translate – Duration: local browser storage until cleared
wpEmojiSettingsSupports(sessionStorage)
– Purpose: WordPress/browser capability detection – Source: WordPress frontend runtime – Duration: session
bsense_consent_v1
– Purpose: store your analytics consent choice – Source: B-Sense consent flow – Duration: persistent for the configured consent lifetime
bsense_consent_id_v1
– Purpose: pseudonymous identifier used for consent logging – Source: B-Sense consent flow – Duration: persistent for the configured consent lifetime
Analytics
_ga
– Purpose: Google Analytics website measurement – Source: Google Analytics 4 – Duration: persistent, subject to provider/browser behavior
_ga_M27KNN2884
– Purpose: Google Analytics 4 property-specific measurement – Source: Google Analytics 4 – Duration: persistent, subject to provider/browser behavior
pmpro_visit
– Purpose: visit/view tracking related to the membership plugin stack – Source: Paid Memberships Pro – Duration: session – Current audit note: not observed in the 2026-04-13 main-flow audit, but kept in the inventory because the PMPro stack may emit it on membership/report-related flows when analytics is allowed
4. Analytics
The current site stack includes Google Analytics 4.
Current v1 behavior:
- analytics is intended to load only when analytics is allowed
- for EU/EEA/UK and unknown-country traffic, analytics is intended to stay blocked until consent
- for out-of-scope traffic, analytics may load without the consent banner
Current main-flow audit snapshot (2026-04-13):
- before consent and after
Use necessary only, the audited flows did not show_ga*cookies or Google Analytics / Google Tag hosts - after
Accept analytics, the audited flows showed_gaand_ga_M27KNN2884
5. How To Control Cookies
In the current v1 design, users in scope should be able to:
- accept analytics cookies
- continue with necessary cookies only
- reopen cookie settings later from the website interface
You can also manage cookies through your browser settings.
6. Third-Party Services Linked To Cookies
Current audited examples include:
- GTranslate / Google Translate (
cdn.gtranslate.net,translate.google.com,translate.googleapis.com,translate-pa.googleapis.com) - Google Analytics / Google Tag (
googletagmanager.com,google-analytics.com) - Paid Memberships Pro-related site functionality
If additional cookie-setting services are introduced later, this policy must be updated before or together with rollout.
7. Changes
We may update this Cookie Policy from time to time to reflect legal, technical, or product changes.
8. Contact
Questions about cookies or privacy:
Kovacs Etelka EV Hungary, 2071 Paty, Napfeny utca 11/1 info@b-sense.hismis.com