Submit a Ticket

Loading support form...
Skip to content
  • There are no suggestions because the search field is empty.

How Does uConnect Store and Protect Data from AI Search?

When students use AI Search, they're generating a new type of data on your platform — their questions, the responses they received, and their feedback. This article explains what data is generated, how it's stored, who can see it, and what protections are in place.

This is the article to reference when your IT department, legal team, or institutional leadership asks about AI Search and data governance.

What Data AI Search Generates

When a student uses AI Search, three types of data are created:

  • Student queries — the questions and prompts that students type into the AI Search panel.
  • AI Search responses — the answers generated and the citation links included in each response.
  • Feedback — the thumbs up or thumbs down rating a student provides after receiving a response (where they choose to give feedback).

How Long Data Is Stored

Search history is stored indefinitely — it does not automatically expire or age out. Students have full control over their own search history:

  • Students can delete their own search history at any time from their account settings, but it does not remove their search history from our records.
  • If a student deletes their account entirely, their associated search history is also removed.

Who Can See Student Search Data

At Launch

• Students can view and delete their own search history

• Staff and admin users cannot view individual student search histories

• Aggregate analytics are not yet available in the admin dashboard

On the Roadmap

• Aggregate analytics dashboard for admins (search volume, feedback trends)

• Query-level visibility to inform content strategy

• Individual student search history visibility for staff

Data Isolation and Security

  • Tenant isolation — Your institution's data is strictly separated from all other institutions. No other uConnect client can access your students' search data, and your team cannot access another institution's data.
  • No cross-institutional data sharing — Student queries and responses are never shared across institutions or used to inform another institution's AI Search experience. However, in aggregate, the data collected from student usage in AI Search will improve the feature overall.
  • SOC 2 compliance — uConnect maintains SOC 2 compliance with continuous monitoring and rigorous governance frameworks covering all platform data, including AI Search.
  • Permission boundaries — Content and data access in AI Search respects your institution's existing permission controls. SSO-protected content is never surfaced to unauthorized users.

Common Questions from IT and Legal Teams

Please refer to our privacy policy documents:

Pro Tip: If your IT or legal team has specific compliance documentation requirements — including FERPA applicability, data processing agreements, or HECVAT responses — contact your CSM to connect with the appropriate uConnect team members. We recommend initiating these conversations proactively rather than waiting for a formal procurement review cycle.