Data zones
OneSignal classifies data into three zones based on who controls it and what governs it.Zone 2
OneSignal Collected
OneSignal collects · Internal onlyUsage Data
- API activity logs
- Server delivery infrastructure
- SDK performance
- IP addresses and device IDs
- Service performance data
- AI infrastructure metrics
- Engagement predictions (ML-derived)
The only path out of Zone 2 is transformation into Zone 3.
Customer Content and Subscriber Data together are Customer Personal Data, the scope of the DPA. OneSignal Analytics Data is the only form in which Usage Data can leave OneSignal’s systems.
Data flows
| Data | Lands in |
|---|---|
| AI prompts | Zone 1 (Customer Content) |
| AI outputs | Zone 1 (Customer Content) |
| Campaign open rates / CTRs | Zone 1 (Customer Content) |
| MCP external data | Zone 1 (Customer Content) |
| AI evaluation and annotation logs | Zone 1 (Customer Personal Data) |
| AI infrastructure metrics | Zone 2 (Usage Data) |
| Engagement predictions (ML-derived) | Zone 2 (Usage Data) |
europe-west4), are accessible only to authorized OneSignal personnel for service quality review, are not used for model training, and are auto-purged at 90 days.
Detailed reference
Customer-Provided Data
You control · OneSignal processesCustomer Content: Messages and notifications you create and send through OneSignal, plus AI-generated content, Agent Conversation prompts, campaign performance analytics, and data accessed from external systems via MCP connections.
- Push notifications
- In-app messages
- Email and SMS content
- AI prompts and outputs
- Campaign analytics (open rates, CTRs, delivery rates for specific campaigns)
- MCP-accessed external data (from systems you authorize)
- Names
- Email addresses
- Phone numbers
- Custom attributes
OneSignal-Collected Data
OneSignal controlsUsage Data: Platform operational telemetry generated automatically by OneSignal’s systems. Does not include campaign-specific performance data (that is Customer Content) or Subscriber Data.
- IP addresses
- Device identifiers
- Advertising IDs
- API activity logs
- Service performance data
- SDK performance data
- AI infrastructure metrics
- Engagement predictions (ML-derived outputs)
- Platform benchmarks
- Delivery statistics
- Service performance
AI features and MCP data
AI and MCP data is not a separate category. It flows through the existing zones based on what the data is.What flows in (inputs)
- Customer Content used as AI prompts
- Subscriber attributes for targeting
- MCP context from external systems → Customer Content
What comes out (outputs)
- AI-drafted message copy → Customer Content
- Suggested segments → Subscriber Data
- Campaign open rates / CTRs → Customer Content
- AI infrastructure metrics → Usage Data (Zone 2)
- Engagement predictions (ML-derived) → Usage Data (Zone 2)
Key protection: OneSignal will not use Customer Content or Subscriber Data to train or fine-tune any machine learning or artificial intelligence model. OneSignal may use OneSignal Analytics Data for AI training, because that data is derived from platform operational data only, never from Customer Content or Subscriber Data. AI inputs drawn from Customer Content or Subscriber Data remain Customer Personal Data. DPA protections follow the data, not the technology used to process it.
europe-west4) remains Zone 1, Customer Personal Data. These logs may be reviewed by authorized OneSignal personnel for service quality purposes only. They are not used for model training and are not shared externally. Deletion rights are governed by DPA section 8.3 (automatic 90-day purge, not subject to individual deletion requests). For more detail, see AI Agent data practices.
Confidential Information
Confidential Information spans both customers and OneSignal and is governed by the confidentiality terms of the Agreement, not by the DPA.Customer's CI examples
- Business strategies and roadmaps
- Contract and pricing terms
- Internal analytics and KPIs
- Marketing campaign details
- Technical architecture
- Audience size and volumes
OneSignal's CI examples
- API architecture and source code
- Security documentation
- Pricing and discount structures
- Product roadmap
- Subprocessor details
- Audit reports
Legend
- Customer Content: Zone 1, Customer owns, DPA governs
- Subscriber Data: Zone 1, Customer owns, DPA governs
- Customer Personal Data: Zone 1, Customer Content + Subscriber Data, DPA scope
- Usage Data: Zone 2, OneSignal controls, internal only
- OneSignal Analytics Data: Zone 3, OneSignal owns, external-shareable
- AI / MCP: Flows through existing zones, not a separate category
- Confidential Information: Spans both sides, governed by confidentiality terms
Related pages
AI Agent data practices
What data the AI Agent uses, how long it is retained, and the controls you have.
Handling personal data
How OneSignal handles personal data and how you can meet GDPR and CCPA requirements.