Privacy Policy
Draft — pending approval. This page describes, in plain language, how InsightStream AI handles data today. It has not yet been reviewed by counsel or by each client's contract terms, and its final wording may change before publication.
What InsightStream AI is
InsightStream AI is a staff-facing analytics and case-management platform for higher-education student success teams. It is not a student-facing product — students do not sign in to it, and this policy describes how the platform handles data on behalf of the advisors, specialists, and administrators who use it.
Where your institution's data lives
Each client institution's student-level data is stored only in a Snowflake account dedicated to that institution, separate from every other institution's data. Student records are not copied into a shared or cross-institution store. During the current pilot period, pilot institutions are served by the environment our team calls "staging", which reads each pilot institution's dedicated account. Development, demonstration, and training workspaces run on synthetic, made-up records and do not read any institution's data.
How you sign in
Sign-in runs through WorkOS, a third-party identity provider. For institutions with their own single sign-on, WorkOS hands the sign-in off to your institution's identity system — InsightStream never sees or stores your campus password. For demo and training workspaces (which hold no real student data), sign-in uses a one-time code sent to a verified email address instead.
Your signed-in session is represented by a sealed, encrypted cookie in your browser — its contents can't be read or altered by the browser or by a third party. Sessions can be revoked (for example, if you sign out or an administrator removes your access), which immediately ends access on that session going forward.
What is logged
InsightStream keeps operational logs to run and troubleshoot the platform — records of requests, errors, and system events. These logs are structured to automatically remove or mask fields that could identify a person before they're written — for example, email addresses, session tokens, and similar sensitive values are redacted rather than stored in the clear. Logs are used for operating the platform, not for tracking individual staff activity for its own sake.
Who can see what
Access inside the platform is scoped by role and, for many staff, by an assigned caseload — an advisor generally sees only their own students and cases, not the whole institution's data. Each institution's data is isolated from every other institution's; nobody outside your institution's own authorized staff can see your institution's records through InsightStream.
FERPA
Because InsightStream handles education records on behalf of colleges and universities, it is built with FERPA (the Family Educational Rights and Privacy Act) in mind: student data stays within each institution's dedicated account, access is scoped to the staff who need it for their role, and development, demonstration, and training workspaces use synthetic, made-up records only.
Questions
For questions about this policy or about how your institution's data is handled, contact your institution's InsightStream administrator.