Privacy

This page explains what Cronpilot collects and why, in ordinary language. It is not dense legal copy, but it is meant to be accurate for our free soft launch.

Who we are

Cronpilot is operated by Jeff Berube / Rebel Signal. Contact: hello@cronpilot.io.

What we collect

• Account data: email, display preferences, and organization membership. Sign-in is magic-link only (no passwords).
• Monitor configuration: URLs, schedules, headers/bodies you enter, success criteria, and alert settings.
• Execution data: timestamps, outcomes, status codes, latency, and limited response metadata needed to show history and fire alerts.
• Operational logs: security and reliability signals (sign-in events, errors, abuse signals).
• Session cookies: to keep you signed in. We do not run third-party ad trackers on the product UI.

Why we collect it

To run the service you asked for: schedule and fire requests, show history, enforce plan limits, send alerts, secure accounts, and investigate abuse. We do not sell personal data.

Retention

Raw execution history is bounded by plan caps and age. Aggregates may outlive raw rows so dashboards stay useful. Account data stays while the account exists; after deletion we remove or anonymize operational data within a reasonable cleanup window, except records we must keep for security or legal reasons.

Processors

Infrastructure and email providers process data on our behalf to host the app and deliver notifications. They are not free to use your monitor configs for their own marketing.

Your choices

You can update account settings in the app, delete schedules, and request account closure by emailing hello@cronpilot.io. We will say what we can delete immediately versus what lingers briefly in backups.

Changes

If this policy changes in a material way, we will update this page and note it in the changelog when practical.