[Usage] Unknown apps appear on the Usage dashboard and how to delete catalogs

Unexpected HERE system applications appear on the Usage dashboard
-----------------------------------------------------------------

### Symptoms

You may observe one or more of the following on the HERE platform Usage dashboard:



An unfamiliar application ID appears under Data Storage usage.
Usage is attributed to an application that your organization did not create.
An exclamation-mark icon identifies an application as a HERE system app needed to support core service functions.
Usage appears after viewing platform data or rendering a custom catalog in the HERE Platform Portal.
Data Storage metrics remain visible even when no customer application explicitly accesses the catalog.
You need to determine whether an unfamiliar application can be deleted or disabled.

Answer
------

These entries are expected when HERE platform system applications access platform services on your behalf. They do not necessarily indicate an unauthorized customer application or compromised credentials.

Use the application name, application ID, usage category, project, and catalog information on the HERE platform Usage dashboard to identify the service responsible for the usage.

Identified system applications
------------------------------

### HERE Platform Portal

Application ID: YQijV3hAPdxySAVtE6ZT
Application name: HERE Platform Portal
Purpose: Records service usage generated through actions performed in the HERE Platform Portal.
Example: HERE Style Editor may render a HERE map without using a customer-created application. The resulting service usage can be attributed to the HERE Platform Portal system application.

### DS Interactive Map Service

Application ID: 7ZYLPTnZnUCLZ01iRdt4
Application name: DS Interactive Map Service
Purpose: Supports interactive visualization of map layers from custom catalogs in the Data section of the HERE Platform Portal.
Example: Opening or exploring a custom catalog layer on the interactive map can generate usage attributed to this system application.

### Metrics Accounting Credentials

Application ID: W3w9ifoid5AcyaYgBvJB
Application name: Metrics Accounting Credentials
Purpose: Supports the Data Metrics Service.
Details: The service monitors and reports data-store metrics used for usage accounting, billing, and customer-facing metrics.

Additional HERE system applications may appear as platform capabilities evolve. An entry marked as a system application should be investigated by its displayed name, usage category, project, catalog, and reporting period rather than treated as a customer-created application.

Root cause
----------

Some HERE platform functions use HERE-managed system applications to call services, render data, or collect usage metrics. The Usage dashboard attributes these calls to the responsible system application. Therefore, usage can appear under an application ID that is not present among your organization’s customer-created applications.

Data Storage usage is generally associated with stored data and service operations involving catalogs, layers, partitions, schemas, indexes, or related platform resources. Viewing data through portal tools can also invoke platform services and contribute to reported usage.

Impact
------

System-application usage may:

Contribute to the usage shown for your organization.
Be included in usage accounting or billing, depending on the applicable service and commercial plan.
Continue while the associated catalogs, data, or workflows remain active.
Make usage analysis more difficult when application IDs are not recognized.

The presence of a HERE-managed application ID alone does not demonstrate unauthorized access.

Recommended actions
-------------------

1. Open the HERE platform Usage dashboard.
2. Select the relevant reporting period and review the usage category, application name, application ID, project, and other available dimensions.
3. Compare the unfamiliar entry with the identified HERE system applications in this article.
4. Open the Data section of the HERE Platform Portal and identify custom catalogs that may be generating the reported Data Storage usage.
5. If the catalog belongs to a project, review it in Project Manager and verify its owner, purpose, dependencies, and access permissions.
6. Contact the catalog owner or your development team before changing or deleting any resource.
7. Check whether applications, pipelines, services, maps, or users still depend on the catalog.
8. Delete a catalog only when it is no longer required and its owner has approved the deletion.

Deletion is permanent and can interrupt applications, pipelines, data processing, map rendering, or other consumers. Do not delete a catalog solely because an unfamiliar HERE system application appears on the Usage dashboard.

Catalog deletion options
------------------------

If an unused catalog has been identified and deletion has been approved, use one of the supported methods:

Delete a catalog with the Data API
Delete a catalog with the Data Client Library for Java and Scala
Delete a catalog with the OLP CLI
Delete the catalog or its containing project through the HERE Platform Portal when the portal presents that option and you have the required permissions.

Before deletion:

Confirm that the selected catalog or project is the correct resource.
Review Access and permissions to identify owners and users.
Confirm with affected development and operations teams that the resource is no longer needed.
Preserve or export any data that must be retained.
Consider contractual, retention, audit, and recovery requirements.
Review dependent applications, pipelines, schemas, layers, and credentials.







Deleting stored data may reduce subsequent Data Storage usage, but it does not retroactively remove usage that has already been recorded for an earlier reporting period.

Expected behavior
-----------------

HERE-managed system applications can appear on the Usage dashboard.
The exclamation-mark icon can identify an application as a HERE system app supporting core service functions.
Portal actions, interactive map rendering, metrics collection, and stored-data operations can generate usage.
Previously recorded usage remains visible for its reporting period after a resource is deleted.

Unexpected behavior
-------------------

Contact HERE Support if:

An application is not identified as a HERE system application and no one in your organization recognizes it.
Usage continues for a deleted resource after allowing for normal dashboard reporting latency.
The usage category, project, or catalog does not match any known activity.
Usage increases substantially without a corresponding platform operation.
You suspect credentials or permissions have been used without authorization.

Provide the application ID, application name, usage category, reporting period, project or catalog identifier, and relevant dashboard screenshots. Do not include secrets, access tokens, private keys, or passwords.

Products and applicability
--------------------------

HERE platform
HERE Platform Portal
Usage dashboard
Data Storage
Data Metrics Service
HERE Style Editor
Data API
Data Client Library for Java and Scala
OLP CLI

The portal interface and displayed system applications can change over time. Use the labels and explanatory icons currently displayed on the Usage dashboard as the primary source for classification.

Keywords
--------

HERE platform, Usage dashboard, unknown application, system application, application ID, Data Storage, HERE Platform Portal, DS Interactive Map Service, Metrics Accounting Credentials, Data Metrics Service, custom catalog, catalog deletion, billing usage, HERE Style Editor, OLP CLI