Terms of Use

Effective date: July 23, 2026 — Version 2.2

These terms govern your use of PulseWatch, a cron job and uptime monitoring service. By creating an account or using the service you agree to them.

• TL;DR: monitor only systems and URLs you own or have permission to monitor. No internal or private-network targets, no scanning or attacking anything.
• Keep ping and alert volumes reasonable. We may rate-limit or pause monitors that threaten the service.
• Abuse gets a warn → suspend → ban response, with an appeal contact.
• Billing is through Lemon Squeezy. Cancel anytime and keep paid features until the period ends.
• The service is provided "as is". Alert delivery is best effort and depends on third parties, so don't make PulseWatch your only safeguard.

The service

PulseWatch monitors scheduled jobs, through heartbeat pings your systems send us, and URLs, through HTTP checks we run. It notifies you through the alert channels you configure. Paid plans add capacity and features as described on the pricing page.

Your account

You are responsible for what happens under your account. Keep your sign-in method secure, keep your alert channels accurate, and don't share access with people you don't trust. You must provide a working email address.

Acceptable use

You agree that you will not:

- Monitor systems, URLs or endpoints you do not own or have explicit permission to monitor. - Target internal, private, loopback or link-local addresses, or cloud metadata endpoints. - Send abusive ping or request volumes, or use the service to load-test, scan, probe or attack anything. - Publish unlawful, deceptive or infringing content in monitor names, status-page slugs, incident notes, or anything else shown publicly. - Attempt to break, overload or probe PulseWatch itself, or to bypass plan limits or enforcement.

Plan limits are enforced technically, and we operate automated abuse protections. We may apply additional reasonable limits, and may rate-limit or pause monitors that threaten the service or other users. We will not use fair-use limits to hollow out what you paid for.

What you send us

You are responsible for the content you transmit in ping bodies, including your jobs' stderr and run-log output. We attempt to redact values that look like credentials before storing an excerpt, but that is best effort and not a guarantee. Do not send credentials, personal data, or anything you are not permitted to share. Excerpts are retained as described in the Privacy Policy and are never published on public status pages.

Enforcement and appeals

For most issues we follow a ladder: a warning, then suspension (your account becomes read-only while monitoring continues), then a ban (access blocked and monitors paused) for serious or repeated abuse. Where abuse actively harms other customers or third parties we may suspend or ban immediately. A banned account is shown an appeal path; to appeal, contact pulsewatch.dev@gmail.com from the account's email address.

API terms

API keys are issued per account and authenticate as you. Do not share or resell them, and keep them secret. They are stored only as a hash and cannot be recovered, so a leaked key must be revoked and replaced. API requests are rate-limited, and we may change published rate limits with reasonable notice. We version the API and avoid breaking changes to a published version where practical.

Plans, billing and refunds

Free and paid plans are described on the pricing page. Payments are processed by Lemon Squeezy as merchant of record, so your billing relationship for payment processing is with them. Subscriptions renew automatically until cancelled. You can cancel anytime from the billing page; cancellation takes effect at the end of the paid period and you keep paid features until then. If a downgrade leaves you over your new monitor limit, we pause the excess monitors rather than delete them.

Apart from billing errors and where required by law, fees already paid are non-refundable. If you believe you were billed in error, contact us within 14 days and we will sort it out. We may change prices with at least 30 days' notice, applying from your next renewal.

No SLA

PulseWatch is provided "as is" and "as available", without warranties of any kind. We do not guarantee any particular availability of the monitoring service itself, and we do not guarantee that every incident will be detected or that every alert will be delivered on time. Alert delivery depends on third parties, including email providers, Telegram, chat platforms and your own webhook endpoints. Do not use PulseWatch as your only safeguard for safety-critical, life-critical or damage-prone systems.

Liability

To the maximum extent permitted by law: we are not liable for indirect, incidental, special or consequential damages, or for lost profits, revenue or data, including losses caused by missed, delayed or false alerts. Our total aggregate liability for all claims arising out of the service is capped at the fees you paid us in the 12 months before the event giving rise to the claim, or $0 on the free plan. Nothing in these terms excludes liability that cannot lawfully be excluded.

Your content

You keep all rights to the data you put into PulseWatch. You grant us the limited license needed to store and process it to operate the service, and to display what you explicitly publish on your public status page.

Termination

You can stop using PulseWatch and delete your account at any time from Settings, which removes your data as described in the Privacy Policy. We may terminate or suspend the service or your account for material breach of these terms, with notice where practical.

Changes to these terms

We may update these terms. For material changes we will give you notice, by email or in-app, at least 14 days before they take effect; continuing to use the service after that constitutes acceptance. The effective date above always reflects the current version.

Changelog

- v2.2 — July 23, 2026. Shortened for readability, with no reduction in substance: removed internal enforcement mechanics and repeated explanation while keeping the acceptable-use rules, the enforcement ladder and appeal route, billing and refund terms, the no-SLA and liability clauses, and your responsibility for what you transmit. - v2.1 — July 22, 2026. Added responsibility for transmitted ping bodies. - v2.0 — July 21, 2026. Added acceptable use, the warn → suspend → ban ladder with an appeal contact, API terms, downgrade behavior and best-effort delivery language. - v1.0 — July 18, 2026. Initial terms.

Contact

Questions about these terms: pulsewatch.dev@gmail.com