Helio

Policy

Operational policy.

The practical product policies for Helio usage, log handling, ingestion limits, restricted data, and responsible operation.

Last updated

June 18, 2026

Logging policy

Helio is intended for application logs, error events, request context, service metadata, and operational diagnostics. Logs should be useful, scoped, and reasonably sized. Customers are responsible for deciding what their applications log before the data is sent to Helio.

Restricted data

Do not intentionally send raw passwords, access tokens, refresh tokens, private keys, authorization headers, session cookies, payment card data, health records, government identifiers, or other highly sensitive regulated data unless Zynnode has agreed in writing that the service is configured for that use case.

Ingestion limits

Helio may enforce request, batch, payload, retention, and daily usage limits to protect reliability and control costs. Limits can vary by plan, project, environment, and abuse risk. Requests that exceed limits may be rejected with a clear API error.

Fair use

  • Do not intentionally overload ingestion endpoints or send duplicate/high-cardinality noise that harms platform stability.
  • Do not use Helio as a general file store, event warehouse, data lake, backup system, or analytics database.
  • Do not attempt to bypass rate limits, project boundaries, authentication checks, or retention controls.
  • Do not send data that violates law, third-party rights, or your own obligations to users and customers.

Retention and deletion

Log retention is governed by project settings, plan limits, and technical constraints. Expired or deleted logs may remain in backups for a limited period before they are overwritten or removed through normal backup lifecycle processes.

Operational incidents

We will use reasonable efforts to communicate material outages, degraded ingestion, dashboard incidents, security issues, and maintenance through the status page, support channels, or direct customer notices when appropriate.

Enforcement

We may throttle, reject, quarantine, suspend, or delete traffic that creates reliability, security, legal, abuse, or cost risk. Where practical, we will contact affected customers before taking broad action, but urgent risks may require immediate mitigation.

Contact

Policy questions can be sent to hey@zynnode.com.