- Products ProductsLocation Services
Solve complex location problems from geofencing to custom routing
PlatformCloud environments for location-centric solution development, data exchange and visualization
Tracking & PositioningFast and accurate tracking and positioning of people and devices, indoors or outdoors
APIs & SDKsEasy to use, scaleable and flexible tools to get going quickly
Developer EcosystemsAccess Location Services on your favorite developer platform ecosystem
- Documentation DocumentationOverview OverviewServices ServicesApplications ApplicationsDevelopment Enablers Development EnablersContent ContentHERE Studio HERE StudioHERE Workspace HERE WorkspaceHERE Marketplace HERE MarketplacePlatform Foundation and Policy Documents Platform Foundation and Policy Documents
- Pricing
- Resources ResourcesTutorials TutorialsExamples ExamplesBlog & Release Announcements Blog & Release AnnouncementsChangelog ChangelogDeveloper Newsletter Developer NewsletterKnowledge Base Knowledge BaseFeature List Feature ListSupport Plans Support PlansSystem Status System StatusLocation Services Coverage Information Location Services Coverage InformationSample Map Data for Students Sample Map Data for Students
- Help
Data security and durability
The HERE platform protects your data using security and durability best practices.
Security
The HERE platform utilizes industry-standard data security best practices to protect your data:
- Data stored at rest in versioned layers, volatile layers, stream layers, index layers, interactive map layers and object store layers is encrypted using AES-256, a strong, proven, block cipher. This data protection includes data which has been persisted per the Time to Live (TTL) setting.
- Data in transit between the platform and your applications is encrypted using the TLS 1.2 cryptographic protocol and the strong AES-256-GCM cipher.
- Within the platform, data in transit is also encrypted using TLS 1.2. Additional or different protection mechanisms are employed as needed.
- HERE secures the platform website and API endpoints with trusted certificates issued by a well-known Certificate Authority (CA) and signed using a SHA-256 algorithm.
If you intend to cache private or sensitive data on an edge device, be aware that the data may be cached on the device without any protection. So, when the data is uploaded to the HERE platform, the data owner should encrypt any sensitive data before it is uploaded. This way, when the encrypted data is downloaded from the platform to an edge device, it is cached in encrypted form. The application on the edge device can then decrypt the data and consume it, but the data is protected while cached.
Learn more about HERE's compliance practices and certifications: https://legal.here.com/en-gb/compliance.
Durability
Your data is protected from loss due to corruption or system failure. The degree of durability depends on the layer type.
Versioned layers
Versioned layers are designed to provide 99.999999999% (11 nines) durability of data (both data and metadata) over a given year. This durability level corresponds to an average annual expected loss of 0.000000002% of data (blobs) and metadata (partitions). Data is stored in a single region by default, and versioned data is stored redundantly on multiple devices across a minimum of three independent network and power domains within that region.
Index layers
Index layers are designed to provide 99.999999999% (11 nines) durability of data over a given year. This durability level corresponds to an average annual expected loss of 0.000000002% of data (blobs). Data is stored in a single region by default and redundantly on multiple devices across a minimum of three independent network and power domains within that region. Index metadata is stored in a single region by default and redundantly on multiple devices across a minimum of three independent network and power domains within that region with an aggregate durability of 99.99998% (6 nines).
Volatile layers
Volatile data is temporal. Existing data is overwritten every time new data is written to a partition. Data redundancy depends on the layer configuration option selected:
- For
multi-instanceconfigured layers, data/metadata is stored redundantly on multiple devices across a minimum of three independent network and power domains within a single region. Failure of one device would be recovered by another. - For
single-instanceconfigure layers, data/metadata is stored only once on a single device within a single region. Failure of this device may result in irrecoverable loss of data.
For more information on volatile layer data redundancy, see Data redundancy
Stream layers
Stream data is replicated across multiple devices and across three independent network and power domains within a single region. Failure of one device will be recovered by another. Additionally, stream data is always written to an underlying filesystem. You can set how long this data is retained in the filesystem by using the TTL (Time To Live) setting. A best practice is to configure the stream data TTL long enough to ensure that data is not dropped in the event of a consumer group interruption (e.g. a pipeline restart) and while corrective actions are taken.
In addition to these data redundancy measures inside the HERE Workspace, the recommended best practice is to ensure regularly tested backups exist. Secure data backups, in the form of one or more duplicate catalogs, can be assigned a narrower set of permissions to further limit who can delete those backups.
Object store layers
Object store layers are designed to provide 99.999999999% (11 nines) durability of data over a given year (both data and metadata). This durability level corresponds to an average annual expected loss of 0.000000002% of data and metadata. Data and metadata are stored in a single region by default. Data in the object store is stored redundantly on multiple devices across a minimum of three independent network and power domains within that region.
