HeimPulse

Acceptable Use Policy

Last updated: August 7, 2026

This policy describes what you may and may not do with HeimPulse's monitoring checks. It's part of our Terms of Service. Background on how the checks themselves behave is on the bot info page.

Permitted use

You may configure monitoring checks only against URLs, domains, and endpoints that you own, operate, or are otherwise explicitly authorized to monitor — for example, your own product's API, or a vendor's status endpoint you've been given permission to poll.

Prohibited use

  • Monitoring URLs or domains you don't own and aren't authorized to check.
  • Configuring checks intended to load-test, scan, or otherwise degrade a third party's infrastructure.
  • Using check payloads, headers, or assertions to attempt unauthorized access to a system.
  • Targeting endpoints for the purpose of harassment, denial of service, or evading another service's rate limits or access controls.
  • Using the Service to monitor or interact with anything illegal in the jurisdiction where you or the target operate.

Rate and shape of checks

Checks run at the interval you configure, with a platform-enforced minimum, and make a single request per configured endpoint per interval — no crawling, no asset fetching, no retried hammering of a single target. Full detail is on the bot info page.

Enforcement

We may disable a specific check, suspend, or terminate an account that violates this policy, with or without prior notice depending on severity. We cooperate with legitimate abuse reports about traffic originating from our monitoring infrastructure.

Reporting abuse

If you're receiving unwanted traffic from a HeimPulse check against your domain, email reports@heimpulse.com with the URL being checked — see the bot info page for what to expect from that traffic and how we handle these reports.

This is a generic draft template pending review by qualified legal counsel — it is not legal advice.