- We do not read email content, OneDrive/SharePoint files, Teams messages, or student content.
- We collect configuration + metadata via Microsoft Graph / admin endpoints.
- We store only the minimum required to generate reports and trend deltas.
Data boundaries designed for education governance.
EduPulse 365 analyzes configuration and metadata, not student content. The platform is built for least privilege, auditable access, and practical compliance support.
Data Access & Boundaries
We collect:
- Configuration settings and policy state
- Identity/security posture metadata
- Operational scan deltas and remediation status
We do not collect:
- Email bodies and mailbox content
- OneDrive/SharePoint file content
- Teams chat/message content and student content
Data Flow
Text-based architecture summary for initial review.
- Encryption in transit and at rest
- Access controls and auditable administrative access
- Minimum necessary data retention for reporting and deltas
Permissions & Least Privilege
- Read-only by default
- Write actions only with explicit approval and scoped role
- Permission matrix available on request
Retention
- Default retention: 12 months for reports and trend deltas
- Retention windows can be configured by customer policy
- Customer can request deletion at any time
Security FAQ
Common trust and data-boundary questions from education buyers.
Do you read student email, files, or Teams messages?
No. EduPulse does not read email content, OneDrive or SharePoint file contents, Teams message content, or other student content.
What data does EduPulse collect?
EduPulse collects configuration and security posture metadata through Microsoft Graph and admin endpoints to generate reports, trends, and remediation tracking.
Are write actions performed automatically?
No. Read-only access is standard, and write actions require explicit approval with scoped roles and governed execution.
Can we request data deletion?
Yes. Customers can request deletion at any time, and retention windows can be aligned to customer policy requirements.