Security

Authentication

crond.io uses passwordless magic-link authentication. We never store passwords. Magic links are single-use, expire after a short window, and are bound to the email address they were issued to.

Programmatic access is via revocable API keys, scoped to the issuing account. Keys are stored hashed; the plaintext value is shown only at creation.

Data in transit & at rest

All connections to crond.io are over TLS 1.2+. Pings, API calls, and dashboard traffic terminate at our edge with HSTS enforced.

Account data, monitor configuration, and ping history live in PostgreSQL with disk-level AES-256 encryption. Time-series data is stored in TimescaleDB hypertables on the same encrypted volumes.

Data we store

We store the minimum required to operate monitoring: your email, monitor metadata (name, schedule, alert rules), and ping records (timestamp, exit code, duration, optional stdout/stderr from the CLI agent).

We do not sell data. We do not enroll your accounts in marketing email lists by default.

Retention

Ping and event retention follows your plan: 7 days on Free, 90 days on Pro, 365 days on Enterprise. Account deletion is permanent and wipes all associated monitor and ping data within 30 days.

Open-source agent

The crond-agent CLI is open source. Anyone can audit exactly what data the agent transmits, when, and how it handles credentials. There is no telemetry beyond what is required to deliver the monitoring you configured.

Reporting a vulnerability

Found a security issue? Please report it directly to security@crond.io rather than filing a public issue. We respond within 2 business days and work in good faith with reporters on coordinated disclosure.