Logtura privacy policy

This policy covers the Logtura website and hosted service, open-source CLI, libraries and forwarder, and Claude Code / Codex skill. Updated October 6, 2026.

Open-source software and agent skill

The skill is a package of instructions and reference files. It has no hosted backend, tracking code, or credential store. Your coding agent processes prompts, project files, and command output under its own provider's policies and permissions. Installing the skill does not create a Logtura account.

Standalone CLI configuration and credentials stay in the files and environment you choose. Commands that discover resources or deploy a forwarder contact the selected hosting providers. Your forwarder reads logs from your configured sources and sends them to your configured destinations; those providers receive the data needed for those operations. Standalone use does not require sending your configuration or logs to logtura.com.

Website and linked deployments

GitHub sign-in supplies your GitHub identifier, login, profile name, avatar URL, and available email address. Logtura stores this account information, connection and destination settings, deployment manifests, authorization records, and deployment status and metrics to operate your account. Session cookies maintain sign-in; CLI access tokens authorize linked commands.

Provider and destination credentials submitted to the service are encrypted in storage and used to discover resources, generate configurations, and perform operations you request. Linking the CLI synchronizes configuration with the service. Configured heartbeats and metrics send deployment health and counters to the service. Log forwarding destinations are determined by your configuration, including any Logtura-related source or destination you explicitly select.

The website runs on Cloudflare. Provider integrations contact the providers you select. Deployment alert emails, when enabled, use Postmark and include your email address and deployment status. These services and your coding agent have their own privacy policies. Hosting infrastructure may process request metadata and operational diagnostics.

Retention and control

Local configuration, generated bundles, and forwarder checkpoints remain under your control. You can remove website resources, revoke CLI access in the website, and revoke provider credentials at the provider. Removing configuration does not by itself stop a running forwarder or delete data already delivered to another service.

Account and deployment records are stored to support the service; this policy does not specify a fixed retention period for account records, operational diagnostics, or infrastructure backups. For account deletion or privacy questions, use the support page to request a private contact channel. Do not post credentials, logs, or personal information in a public issue.