How to delete your HyperDX account

About deleting your HyperDX account

HyperDX is an observability platform designed to consolidate logs, metrics, and traces into a single searchable interface for developers. By providing deep insights into application performance and error tracking, it handles sensitive production data, including stack traces, request metadata, and potentially PII (Personally Identifiable Information) captured within application logs. Users often seek to delete their accounts when migrating to different observability stacks, downsizing infrastructure, or minimizing the security footprint of their development environment.

Key reasons to consider deleting your HyperDX account include:

• Mitigating the risk of exposing sensitive production environment variables or secret keys erroneously logged to the platform.
• Reducing the attack surface by ensuring that historical request data and system metadata are purged.
• Improving compliance with internal data lifecycle policies that mandate the removal of observability data older than a specific retention period.

What happens to your data

When you initiate the deletion of your HyperDX organization, the service targets the removal of the project-specific database entries and indexed log sets. Because HyperDX functions as a data processing pipeline for telemetry, the removal process ensures that incoming data streams from your instrumented applications are terminated. Data categories typically subject to removal include:

• Structured log events and associated metadata attributes.
• Custom metrics and time-series data points collected from your services.
• Distributed trace identifiers and span data captured during transaction execution.
• User account configurations and integration settings linked to your organization.

Note that while HyperDX performs account-wide purges, some log fragments might exist in intermediate cache buffers or distributed backup snapshots for a brief period before final sanitization. Always verify that your application SDKs have been updated to stop pushing telemetry to the HyperDX endpoint before finalizing the account closure.

Privacy considerations

Using HyperDX involves granting access to your internal service traffic, which naturally carries privacy implications regarding how your application data is handled. Unlike platforms that monetize user behavior through tracking, HyperDX primarily processes machine data; however, developers must be wary of 'accidental logging' where users mistakenly transmit emails or session tokens as log parameters. To maintain your privacy while using or leaving the service, consider the following:

• Scrub your application logs of PII before they leave your servers, even if you trust the observability provider.
• Audit the specific environment variables and configuration files integrated with the HyperDX SDK to ensure no sensitive credentials are being forwarded.
• Request a formal data deletion confirmation from the HyperDX support team if your organization falls under strict regulatory requirements like GDPR or SOC2.

Frequently Asked Questions

Will deleting my HyperDX organization stop billing immediately?

Yes, deleting your organization account through the console settings terminates the subscription and halts future billing cycles for that project.

Does HyperDX retain my log data for analytical purposes after deletion?

HyperDX generally purges your indexed data upon account deletion, though you should check their current Data Processing Agreement for specific backup retention timelines.

Can I recover my HyperDX project after the deletion is triggered?

Deletion is typically a destructive, irreversible action; ensure you have exported any necessary historical logs or metrics before proceeding.

What if I cannot find the delete button in the HyperDX dashboard?

Permissions settings might prevent certain roles from accessing the deletion path; contact your organization administrator or reach out to HyperDX support via their contact email.

Does deleting my account also revoke the HyperDX SDK access tokens?

Yes, once the organization is removed from the backend, the associated API and ingestion keys become invalid and will no longer authorize data transmission.