Ask AI uses session data (such as session identifiers) to maintain conversation context without storing personally identifiable information in traditional cookies. This article explains what session data Ask AI uses, how long it is retained, and how to manage it for privacy compliance.
💡Quick answers
- What session data does Ask AI use? Technical session identifiers that maintain conversation context during a visitor's session; Ask AI does not use traditional HTTP cookies for session tracking.
- How long is Ask AI session data retained? Session data is typically retained for the duration of the browser session and expires when the visitor closes the tab or browser; specific retention details are in the Finalsite Intelligence privacy documentation.
- Does Ask AI session data include personally identifiable information? No; session identifiers are technical tokens used for context continuity and do not contain names, email addresses, or other personal data.
- Can admins configure Ask AI session data settings? Review the Ask AI configuration options in the Finalsite Intelligence settings; contact Finalsite Support for specific privacy configuration questions.
To ensure the Ask AI feature functions correctly and securely, certain technical identifiers must be allowed to run. This guide provides a technical breakdown of these identifiers and how to configure them within your selected Consent Management Platform (CMP).
Unlike many web tools, Ask AI does not use HTTP cookies to track users. Instead, it uses sessionStorage. This means all data is stored only within your current browser tab and is automatically deleted as soon as that tab or window is closed.
This article will show you how it works!
In this article
- Glossary: Session identifiers
- Ask AI data storage breakdown
- Why use sessionStorage instead of Cookies?
- Configure your consent manager
Glossary: Session identifiers
| Term | What it is | Role in Ask AI |
|---|---|---|
| Identifiers | Technical "tokens" or ID keys | Digital markers that allow the feature to recognize your specific chat session and maintain security. |
| Session Storage | Temporary local data | A private method of storing data only for the duration of a visit. All information is automatically deleted when the tab is closed. |
| Strictly Necessary / Essential | Compliance categories | Terms used interchangeably by CMPs to describe scripts that must run for a feature to work. Ask AI falls here because it cannot function without its session identifiers. |
Ask AI data storage breakdown
We use the following identifiers to ensure the feature functions smoothly during a visit. Because these are required for the feature to load and maintain a secure connection, they should be categorized as either Strictly Necessary or Essential.Â
| Key Name | Purpose | Duration |
|---|---|---|
| ASKAI_SESSION_ID | A unique ID that connects the chat window to our secure AI assistant and tracks the session. | Current tab only |
| ASKAI_SETTINGS | Remembers the feature's visual style (colors, layout, and configuration) during the visit. | Current tab only |
| ASKAI_CHAT_HISTORY | Temporarily stores the conversation history so the user doesn't lose their place if they refresh the page. | Current tab only |
| ASKAI_AT / ASKAI_RT | Security "tokens" (Access and Refresh) that verify the session is safe, private, and authorized. | Current tab only |
| ASKAI_SESSION_ID_COUNTER | Maintains a counter to track usage activity for the current session. | Current tab only |
Why use sessionStorage instead of Cookies?
Enhanced security: Because this data is never sent automatically with every web request (unlike cookies), it is much harder for malicious actors to intercept or use in "Cross-Site" attacks.
True privacy: Standard "cookies" can stay on your computer for days or months.
sessionStorageis strictly temporary—it is wiped clean the second you close the tab.No cross-tracking: This data cannot be seen by other websites you visit, keeping your interaction with our school's AI completely private to this session.
Configure your consent manager
Most CMPs (such as Termly, OneTrust, or CookieBot) may block unknown scripts by default. To ensure the feature is visible to your users, you must manually categorize the askai.finalsite.com script as Essential.
Option A: For Finalsite CMS users
If you use the Finalsite CMS, you likely manage site-wide compliance via Domain Settings.
In your CMP dashboard, move all
ASKAIidentifiers to the Strictly Necessary category.Ensure your CMP's "Auto-Blocker" is not suppressing the Ask AI script.
For a deeper dive into this process, check out the article, "Manage website cookies and essential scripts."Â
Option B: For Non-Finalsite websites
If you have added Ask AI to a third-party platform (such as WordPress or Wix), you must update your third-party CMP manually.
Scan your domain: Run a scan so your CMP detects the
askai.finalsite.comsource script.Manual categorization: Locate the ASKAI keys in your scan report and set them to Necessary/Essential. This ensures the Ask AI widget appears for all visitors immediately.
Comments
Please Sign in to leave a comment if you don't see the comment box below.