Privacy Policy

deadpost (“deadpost”, “we”, “us”) provides cron and heartbeat monitoring — a “dead man’s switch” that alerts you when a scheduled job stops checking in. This policy explains what data we collect, why, and the choices you have. We keep it short and plain because the product is too.

1. Information we collect

Account information

When you create an account we collect your email address, an optional display name, and a password. Passwords are stored only as a salted hash — we never see or store your plaintext password.

Sign in with Google (optional)

If you choose “Continue with Google”, we receive your Google account’semail address, basic profile (name and profile picture), and a stable Google account identifier, which we use solely to create and authenticate your deadpost account. We never receive your Google password. See the “Google user data” section below for how we limit this use.

Monitoring data

To run the service we store the monitors and workspaces you configure (names, schedules, alert routing) and the ping events your jobs send us — timestamps, success/failure outcomes, and the source IP address of each ping. Source IP addresses are automatically erased after at most 90 days. The ping history itself (without the IP) is kept for your plan’s ping-history window — 7 days on Hobby, 90 days on Solo, 1 year on Business — after which those records are permanently deleted, except for a small number of the most recent check-ins per monitor, which we keep so your monitor’s timeline stays readable. Uptime and incident history are derived separately and are not affected by this.

Billing information

Paid plans are processed by our payment provider. We receive a customer reference and your plan status, but we do not collect or store full payment-card details — those are handled by the payment provider under their own security standards.

Communications and diagnostics

We keep records of transactional emails we send you (verification, password reset, alerts) and basic error/diagnostic telemetry needed to keep the service running and secure.

2. How we use information

• To create and secure your account and authenticate you.
• To run the monitoring service: evaluate schedules, detect missed pings, and deliver alerts.
• To send transactional email (verification, password reset, monitor alerts).
• To operate, debug, and protect the service against abuse.
• To process payments and manage subscriptions for paid plans.
• To comply with legal obligations.

We do not sell your personal data, and we do not use it for third-party advertising or behavioral profiling.

3. Google user data (Limited Use)

deadpost’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, the profile and email information we receive through Google Sign-In is usedonly to provide and improve the deadpost login and account features you request. We do not use it for advertising, we do not sell it, and we do not share it with third parties except as needed to provide the service or as required by law.

4. Cookies and local storage

We use a small number of strictly necessary cookies and browser storage items:

• Session cookie — keeps you signed in. Essential.
• OAuth state cookie — a short-lived security token used during “Continue with Google” to prevent cross-site request forgery. Essential.
• Theme preference — remembers light/dark mode in your browser’s local storage. Stays on your device.

We don’t use third-party advertising or cross-site tracking cookies.

5. Who we share data with (sub-processors)

We rely on a small set of infrastructure providers to run deadpost. Each processes data only to provide their service to us:

• Hetzner — server hosting (EU / Germany).
• Neon — managed PostgreSQL database.
• Cloudflare — DNS, CDN, and edge security/proxy.
• Resend — transactional email delivery.
• Google — optional “Sign in with Google” authentication.
• Sentry — error and performance monitoring.
• A payment provider — billing and subscriptions for paid plans.

We may also disclose information if required by law, to enforce our terms, or to protect the rights, safety, and security of our users and the service.

6. Data retention

We keep account and monitoring data for as long as your account is active. Ping source IP addresses are erased within 90 days. If you delete your account, we delete or anonymize your personal data, except where we must retain limited records to comply with legal, tax, or security obligations.

7. Security

Data is encrypted in transit (TLS). Passwords are hashed, and sensitive integration secrets are encrypted at rest. We apply least-privilege access, rate limiting, and other safeguards. No system is perfectly secure, but we work to protect your data in proportion to its sensitivity.

8. Your rights

Depending on where you live (including under the EU/UK GDPR), you may have the right to access, correct, export, or delete your personal data, to restrict or object to certain processing, and to withdraw consent. You can exercise most of these directly from your account settings, or by contacting us at the address below. You also have the right to lodge a complaint with your local data protection authority.

9. Where your data is processed

deadpost hosts and processes your data in the European Union (Germany). Some sub-processors listed above may process data in other countries; where they do, they rely on appropriate safeguards (such as Standard Contractual Clauses) for those transfers.

10. Children

deadpost is a developer tool not directed to children. We do not knowingly collect personal data from anyone under 16. If you believe a child has provided us data, contact us and we will delete it.

11. Changes to this policy

We may update this policy as the product evolves. When we make material changes we’ll update the “Last updated” date above and, where appropriate, notify you by email or in the app.

12. Contact us

Questions or requests about your data? Email privacy@deadpost.dev.