Skip to content
Start free
← Back to Home

Privacy Policy

Effective Date: September 22, 2026

Introduction

This policy explains what CronRadar collects and why when you use the automation reliability monitoring service or visit the public website. CronRadar is designed to receive bounded execution evidence, not application logs or job payloads.

Information We Collect

Information You Provide

  • Account information: Email address, display name, and authentication-provider identifier when you choose GitHub, Google, or Microsoft sign-in.
  • Workspace configuration: Team, application, automation, schedule, ownership, alert-destination, investigation-link, and collaborator settings.
  • Execution context: Monitor keys, opaque run identifiers, retry numbers, optional bounded failure messages, and configured numeric or boolean outcome expectations and results that you choose to send.
  • Billing information: Subscription, invoice, and plan status. Stripe processes card details; CronRadar does not store card numbers.
  • Support communications: Information included when you contact us.
  • Contextual product feedback: Your selected feedback category, helpfulness response, optional comment, the product moment or documentation path where you responded, and whether you permit follow-up. Do not include secrets, payloads, customer records, or other sensitive data.
  • Customer evidence permissions: When an authorized workspace contact reviews proposed public proof, CronRadar records the exact content version, requested uses (testimonial, screenshot, case study, or logo), decision, approver, and consent or withdrawal time. Feedback and follow-up permission are not publication consent.

Information Collected When You Use the Service

  • Monitoring events: Start, completion, failure, and heartbeat event types; receipt timestamps; derived duration and health state; source integration; and expected schedule.
  • Security and operational data: IP address, request metadata, authentication events, rate-limit counters, and bounded service logs needed to secure and operate the service.
  • Essential browser data: Session and preference cookies used for authentication, security, and theme settings.
  • First-party product measurement: On selected high-intent public pages, CronRadar records a qualified visit only after 10 seconds of visible engagement. The bounded record may include a one-way hash of a random browser identifier, page category, selected integration, and sanitized UTM source, medium, and campaign. In the authenticated product, CronRadar records bounded setup, activation, return-use, collaboration, billing, and cancellation milestones and fixed failure codes. It does not record sessions, keystrokes, cursor movement, page contents, full URLs, IP addresses, user agents, customer telemetry, or free-form analytics properties.

CronRadar is not a log, metrics, or tracing service. Outcome values are limited to five configured numbers or booleans per run. Do not place credentials, personal data, full logs, customer records, or job payloads in monitor keys, failure messages, outcome keys, or alert settings.

CronRadar deliberately does not retrieve source repository contents or the content behind customer-provided runbook and log-search links.

How We Use Information

We use this information to provide monitoring and alerts, authenticate users and SDKs, enforce plan limits, process billing, provide support, secure and operate the service, understand qualified demand and product activation, diagnose faults, and comply with legal obligations. We do not sell personal information.

CronRadar uses customer outcomes publicly only after an operator verifies the bounded evidence and an authorized customer contact approves the exact proposed text, attribution, and individual asset uses. Editing approved material requires new consent. Withdrawal disables publication.

Retention

  • Ping, run, and outcome-evaluation history: 30 days on Free, 90 days on Grow.
  • Alert history and per-channel delivery evidence: 90 days on Free, 180 days on Grow.
  • Raw first-party product and funnel analytics: 180 days by default.
  • Resolved or archived contextual feedback: 365 days by default, configurable from 30 to 730 days. Open feedback remains until triaged or the account is deleted.
  • Customer evidence and its consent record: while the workspace remains active or as reasonably needed to document permission and withdrawal. Revoked material is not publicly displayed.
  • Account and configuration data: while the account remains active.
  • Security, operational, support, fraud-prevention, legal, and payment records: for as long as reasonably needed for those purposes or required by law.

History follows the billing owner's effective plan and is removed by daily cleanup. Longer history applies prospectively and cannot restore deleted records. When a downgrade becomes effective, the next cleanup applies the shorter window. Operational settings may extend these windows up to 365 days, but cannot shorten the history included in a plan.

Account deletion requests are currently handled through support. CronRadar does not promise a deletion-completion deadline. Canceling a paid subscription does not delete the account.

Security and Secret Handling

Production public endpoints use HTTPS. Application API keys are generated with a cryptographically secure random source and stored as SHA-256 hashes; the raw key is shown when created or rotated and is not retained for later display. Magic-link tokens are also stored as hashes. Slack OAuth bot tokens are protected with ASP.NET Core Data Protection.

Customer-configured webhook URLs, Slack and Discord webhook URLs, and PagerDuty integration keys are stored as team or application configuration so CronRadar can deliver alerts. CronRadar does not make a blanket claim that every database field is application-encrypted. Keep API keys and alert destinations in an appropriate secret store, restrict access, and revoke or replace them after suspected exposure.

No security control eliminates all risk. CronRadar does not claim a compliance certification or contractual security warranty. See Security, Reliability, and Service Status for the current architecture, operational practices, availability evidence, and limits.

External Services and Disclosures

CronRadar uses these service categories to operate requested functionality:

  • Cloudflare: TLS termination, tunnel ingress, proxying, and edge protection. Public web and API requests pass through Cloudflare. See Cloudflare's Privacy Policy.
  • Stripe: Paid-plan billing and payment processing. Stripe receives payment information directly when you choose a paid plan. See Stripe's Privacy Policy.
  • GitHub, Google, or Microsoft: Identity information when you choose that sign-in provider.
  • SMTP or Mailgun: Magic links, account messages, reliability summaries, and email alerts. See Mailgun's Privacy Policy.
  • Customer-selected alert destinations: Slack, Discord, PagerDuty, or an HTTPS webhook receive bounded incident information only when you enable that destination.

The Security, Reliability, and Service Status page describes the role and data boundary for each category. Information may also be disclosed when required by law, to protect the service and its users, with your consent, or as part of a business transfer subject to appropriate safeguards.

International Processing

The service is operated from the United States. Providers may process data in other locations under their own terms. If you use CronRadar elsewhere, information may be transferred to and processed in the United States or other locations used by the applicable provider.

Your Choices and Requests

You may update account information in the service, revoke application API keys, change alert destinations, disconnect optional integrations, cancel a subscription, or request account deletion. You may also request access, correction, or a portable copy of personal information where applicable. Legal rights vary by location.

Authorized workspace administrators can approve, decline, or later withdraw customer-evidence permission in product settings. Withdrawal prevents further public display; it does not rewrite historical backups or copies lawfully made before withdrawal.

You may clear the random first-party marketing identifier through your browser storage controls. Authentication and security cookies are required for the signed-in service.

Children

CronRadar is not directed to children under 13 and does not knowingly collect personal information from them.

Changes

We may update this policy as the service changes. The effective date above identifies the current version. Material changes will be communicated when required.

Contact

For privacy questions or requests, email [email protected] or use the contact page. Do not include API keys, tokens, job payloads, or customer records in a request.