Neat Pulse Data Residency
Last updated October 21, 2025.
Introduction
Status: Early field trials
Neat Pulse is a global cloud service for managing your Neat devices. To meet compliance requirements and ensure optimal performance, Pulse operates in multiple geographic zones, here referred to as Pulse Zones. Each zone corresponds to a specific data center region, giving you visibility into where your data is stored at rest.
For customers on a paid Pulse plan, Neat offers a Data Residency Guarantee, meaning your Pulse account data is stored only within your chosen zone and will never be moved.
What is a Zone?
A Pulse Zone is a geographic hosting location where your Pulse account data resides at rest.
- Each Pulse zone maps directly to exactly one Azure data center region (see below).
- Each Pulse account will be stored in exactly one Azure data center. Pulse account data is stored redundantly.
- All account-specific data is stored within that zone (see table below).
Zone mapping
Here’s how Pulse Zones map to Azure hosting regions:
| Pulse Zone | Azure Region | Jurisdiction |
|---|---|---|
| EU West | West Europe (Netherlands) | European Union (GDPR) |
| US West | West US 2 (Washington) | United States |
Data residency guarantee
- Free Pulse Plan: Residency is not guaranteed – your account data may be moved from time to time to ensure optimal performance of the Pulse service.
- Paid Pulse Plan: Residency is guaranteed – your account data will stay within a single zone and will never be moved. In addition, you have the option to move your data to another Pulse Zone.
What’s in scope
In scope for data residency guarantee:
- Device enrollment and configuration data
- Device health and monitoring data
- Account settings
- User account information
- Audit logs and activity history
- SAML configurations
Out of scope (may cross regions):
- Global authentication services (provided by Microsoft AD Azure B2C)
- Anonymised product analytics and telemetry used to improve Pulse
Backups remain within the same jurisdiction as your selected zone.
Compliance and security
- All customer data is encrypted at rest (AES-256) and in transit (TLS 1.2+).
- Accounts are isolated per zone to maintain jurisdictional boundaries.
- Pulse aligns with data privacy laws and regulations including, GDPR, CCPA, other U.S. State Privacy Laws, and International Data Transfer laws.
You can request a Data Residency Statement from Neat for your compliance team.
Frequently asked questions
Q: Can an existing Pulse account be move to another Pulse zone?
A: Currently, only new accounts can be created in the respective Pulse zone. Moving accounts will be possible in the future.
Q: Can you guarantee that my data never leaves my chosen jurisdiction?
A: Yes, for paid plans, all account data is stored only in your selected zone. Some global services (auth, analytics) may process minimal metadata outside your zone. If you are not on a paid plan (Pulse Starter), data residency is not guaranteed.
Q: Are backups also in the same jurisdiction?
A: Yes, backups remain within the same Azure region as your account.
Q: What happens if my zone experiences an outage?
A: Each zone is designed for high availability within its region. Pulse does not automatically fail over to another jurisdiction.
Q: Does Neat use sub-processors?
A: Yes, Neat leverages Microsoft Azure as our primary sub-processor. You can view the full list of Neat’s sub-processors in Exhibit C of the Data Processing Addendum (DPA)