privacyaccount-deletiondata-retentiondata-accesssecurity

Account deletion, data retention, and privacy boundaries

What customers should know about deleting a CostRadar account, retained records, and data access boundaries.

Last reviewed 2026-05-04

CostRadar is designed to read Azure cost data, configured cost export files, resource metadata, and recommendations with read-only Azure permissions. It does not need permission to modify your cloud resources.

Data CostRadar reads

CostRadar reads billing and cost-management information, configured Azure Cost Management export files where enabled, connected subscription metadata, and Azure Advisor cost recommendations where available. It also stores account settings, support conversations, team membership, audit events, notification settings, and generated product records needed to operate the service.

CostRadar does not need Azure credentials that can create, update, stop, or delete Azure resources.

Account deletion

Account owners can request account deletion from account settings. Deletion is permanent for the active product account and should be used carefully.

Before deleting, export any reports or audit information your team needs for internal records.

Retention and legal records

Some records may need to be retained for legitimate business, security, billing, fraud prevention, dispute, or legal reasons. The support bot should not promise exact deletion timing for every record because retention can depend on the data type and legal obligations.

For privacy requests, data export questions, or legal requests, escalate to human support.

Access boundaries

CostRadar support should never ask for your Azure client secret in chat. If a credential expires, create a new secret in Azure and update it through the CostRadar connection flow.

If you believe someone has unauthorized access to your CostRadar account, revoke viewer access, rotate Azure credentials if appropriate, and contact support.