TOC
- Why Simpplr uses Cookies?
- Cookie Categories
- Simpplr Application Cookies
- Yellow.ai Virtual Assistant Cookies
- Analytics Cookies
- Other Integrations
-
Key Notes
Why Simpplr Uses Cookies
Simpplr uses cookies to help you sign in securely, keep your data safe, improve app performance, and understand usage through analytics. On this page, you’ll find details about the cookies we use, why we use them, how long they stay, and whether they come from Simpplr or a trusted third party.
Cookie Categories
Cookies used in Simpplr fall into the following categories:
- Strictly Necessary Cookies – Required for core functionality such as login, authentication, and security.
- Preferences Cookies – Store user settings such as language or display options.
- Statistics Cookies – Collect analytics on usage patterns to improve the platform.
- Marketing Cookies – Track activity for personalization and targeted communications.
Each cookie can be either:
- Persistent – Remains stored until expiry or manual deletion.
- Session – Deleted when the browser session ends.
Cookies may also be:
- First-party – Set directly by Simpplr.
- Third-party – Set by partner services integrated into Simpplr.
Simpplr Application Cookies
| Cookie name | Purpose | Duration | Provenance | Usage | Notes |
|---|---|---|---|---|---|
| token | Strictly Necessary (Authentication) | Persistent (can be set to Session) | First party | Authentication | Can be made session-based via Security > Session Settings |
| ftoken | Strictly Necessary (Authentication) | Persistent (default | First party | Authentication | Can be session-based, see Security settings |
| csrfid | Strictly Necessary (Security) | Persistent (default | First party | Protects against CSRF attacks | If session cookies are set to non-persistent, this follows |
Yellow.ai Virtual Assistant Cookies
| Cookie name | Purpose | Duration | Provenance | Domain | Usage | Notes |
|---|---|---|---|---|---|---|
| ym_xid | Strictly Necessary (Virtual Assistant sessions) | 8 hrs (agent role) / 24 hrs (mobile app) | Third party |
.cloud.abc.ai, .hjk.ai
|
Tracks login sessions | Mandatory; platform does not function without it |
| _hjSession, _hjSessionUser, ph_phc*, _cfuvid, G_ENABLED_IDPS | Statistics & Tracking | Session/Persistent (varies) | Third party | .uvw.ai |
Analytics, personalization | Set by Yellow.ai partner integration |
Note: Yellow.ai does not provide end-user cookie choice only if the integration is enabled for the tenant . Documentation is limited as these are internal to Yellow.ai.
Analytics Cookies
| Cookie name | Purpose | Duration | Provenance | Domain | Usage | Notes |
|---|---|---|---|---|---|---|
| rl_anonymous_id, rl_page_init_referrer, rl_session, rl_user_id, rl_trait | Statistics | Persistent | First party |
.abc.com, .uvw.xyz
|
App analytics | Set by RudderStack integration |
| _cf_bm | Bot management | Persistent | Third party | .lmn.com |
Cloudflare bot management | Not related to analytics |
Other Integrations
- Google Analytics 4 (GA4) – Cookies set only if enabled by the customer. See GA4 Help.
- Aisera – Cookies set only if enabled by the customer.
Key Notes
- Cookie persistence can be controlled via Security > Session Settings in Simpplr. This option is availble behind a feature flag. Connect with support to enable it.
- Third-party integrations (e.g., Yellow.ai, GA4) may have their own cookie policies.
Comments
Please sign in to leave a comment.