Security and data handling
Read-only by default.
Neoview sees a lot of what matters in a client's tenant, so the rules for what we take, what we keep and what we never touch are the product. Here they are in plain language.
Access
One multi-tenant Microsoft Entra application, consented by each client, with read permissions to Microsoft Graph and the Office 365 Management Activity API, plus a read-only role group in Microsoft Purview ("Neoview Readers", View-Only roles) to read the configuration. No write scopes, no Microsoft Entra admin role, no interactive sessions in the tenant.
Ingest
Only a whitelist of fields leaves the pipeline. Detected sensitive values and file contents are dropped at ingest. For emails with DLP activity we keep the subject line, so your team can tell which message was blocked or overridden. We never store email bodies, attachments or recipients.
Isolation
Every row is tagged with its client and MSP, and isolation between tenants is enforced in the database before any client data is processed.
Residency
Neoview will run on Microsoft Azure in the United States; client data will be stored and processed there.
Retention
Raw audit records are kept 90 days. Normalized events (counts, policy, rule, action, outcome) are kept 13 months.
Offboarding
Revoke the app or ask us to disconnect. All data for that tenant is deleted 30 days after offboarding, and we confirm when it's done.
What we collect, and why
| Data | Source | Why | Kept |
|---|---|---|---|
| DLP audit events: policy, rule, action, location, outcome, override flag | Office 365 Management Activity API | Count, trend and explain incidents; feed recommendations | Raw 90 days; normalized 13 months |
| Label events: label applied, changed or removed | Office 365 Management Activity API | Label usage and coverage over time | 13 months |
| Configuration snapshots: DLP policies and rules, sensitivity labels and policies | Microsoft Graph and Security & Compliance (read-only) | Point-in-time evidence; change history | 13 months |
| Licenses: assigned plans per user and tenant | Microsoft Graph | License-aware assessment and gap report | 13 months |
| Users: user principal name, department, job title | Microsoft Graph | Attribute incidents and coverage to teams; names can be hidden in reports | While connected |
| MSP account: your users, roles, logo, contact details | You | Sign-in, roles and branded reports | While you're a customer |
How we run it
Neoview is in preview and processes no client data yet. These controls are in place before the first client onboards:
- Secrets and certificates live in a managed key vault and are rotated on a schedule.
- Staff access to client data is role-based, limited to support cases, and logged every time.
- Every change to the product goes through automated tests before it ships.
- Backups are encrypted and kept inside the same region.
- Terms of service, DPA and privacy policy are published before any client onboards, and the DPA lists every sub-processor.
Questions about a specific control or a security questionnaire? Write to hello@getneoview.com.