Cookie Policy

Last updated: 29 March 2026 · Effective: 29 March 2026

1. What We Use Instead of Cookies

EngageLive uses browser localStorage and sessionStorage — not HTTP cookies — to store session state. This data never leaves your device except where explicitly described below. It is not accessible to any third party.

2. localStorage Data (Functional — Required)

The following keys are written to your browser's localStorage. This storage persists until you clear your browser data or click "Clear Data" in the EngageLive menu.

Key	Contents	Purpose	Duration
`el_host_info`	Email address, session name	Restore host session if page is refreshed	Until browser data cleared
`el_sess_*`	Session activities, responses, branding	Session persistence across page reloads	Until session ends or data cleared
`el_pending_tpl`	Template data	Load template into new session	Cleared immediately after use
`el_solo_tpl`	Template data	Solo preview mode	Session only

3. sessionStorage Data (Functional — Required)

The following keys are written to sessionStorage. This data is automatically deleted when the browser tab is closed.

Key	Contents	Purpose
`el_host`	Serialised session state	Active host session data
`el_tpl_buy_intent`	Template purchase intent	Redirects after payment

4. Third-Party Technologies

The following third-party services are used by EngageLive. Each may set their own cookies or store data according to their own privacy policies.

Service	Purpose	Data Shared	Policy
Google Firebase Strictly Necessary	Real-time message passing between host and participants during a live session	Session code, activity data (deleted at session end), Firebase SDK cookies for WebSocket auth	firebase.google.com/support/privacy
Google Fonts Functional	Load Inter and Fraunces typefaces for the interface	Your IP address is sent to Google's font servers on page load	policies.google.com/privacy
PayPal Payment Only	Process card and PayPal payments for session boosts	Payment details processed by PayPal — we receive only transaction confirmation. PayPal sets its own cookies on their payment page.	paypal.com Privacy
PayU Money Payment Only	Process card payments (India) for session boosts	Payment details processed by PayU — we receive only transaction confirmation	payu.in/privacy-policy
Google AdSense Advertising	Display non-personalised ads on the participant view (free tier only). Ads are removed with an Ad-Free subscription.	Google may set advertising cookies. We have configured AdSense in non-personalised mode where possible. Ad-Free subscribers see no AdSense code at all.	Google Ad Technologies
Cloudflare Strictly Necessary	CDN, DDoS protection, email obfuscation	IP address, request metadata. Sets `__cflb` load-balancing cookie (session only).	cloudflare.com/privacypolicy

5. Consent and Your Rights

Under GDPR and UK GDPR:

Strictly Necessary storage (localStorage session data, Firebase WebSocket) is used on the legal basis of legitimate interests / contractual necessity to provide the service you requested. No consent is required.
Google AdSense may be subject to consent requirements. We display a consent notice on first visit and provide an opt-out.
Google Fonts: If you wish to prevent IP disclosure to Google's servers, you may install the fonts locally on your network or use a privacy-preserving proxy.
You can clear all EngageLive data from your browser at any time using the ⟳ button in the navigation bar, or via your browser's developer tools under Application → Storage.

For enterprise deployments: If you are deploying EngageLive for use by employees within a corporate network, you may self-host the application or configure your network to route Google Fonts requests through an internal proxy to prevent external IP disclosure. Contact support@postlister.com for enterprise deployment guidance.

6. Contact

For cookie-related questions or to exercise your rights under GDPR: support@postlister.com

Postal address: EngageLive / postlister.com · India