terms of service

who can use heartbeet

you need to be at least 16 years old to use heartbeet.

your account

you sign in with a one-time email link, or with Google or GitHub; there's no password to manage. keep access to your email or OAuth account secure, since anyone who can sign in can see and change your projects. you can stop using heartbeet and ask me to delete your account at any time.

what heartbeet is, and what it isn't

heartbeet is a silence monitor (a dead-man's switch): your jobs prove they're alive by sending heartbeats, and I alert you when an expected heartbeat doesn't arrive. it is a best-effort safety net, not a guaranteed alerting system, and it carries no uptime guarantee. please don't rely on it as the only safeguard for anything where a missed or late alert could cause harm or loss; pair it with other protections for critical or life-safety systems.

subscriptions and payment

every account gets a generous free plan with no credit card. the optional paid plans — backer, which lifts the limits and unlocks extra controls, and team, which additionally pages extra recipients and keeps history forever — are billed monthly or yearly and renew automatically at the end of each period. payments are processed by Lemon Squeezy, my merchant of record. you can cancel any time from the customer portal; cancellation takes effect at the end of the current period, and there's no refund for time already paid. see the refund policy for the details.

fair use

the paid plans are flat-rate and deliberately generous: unlimited teammates, projects, and jobs, and (on team) history kept for as long as you subscribe. they're meant for a single team or organization monitoring its own jobs. if an account's usage goes far beyond that, for example running an entire multi-team organization's fleet through one subscription, or usage heavy enough to materially affect the service for everyone else, I may get in touch to find a fair arrangement. I'd always reach out first; nothing is throttled or cut off automatically.

acceptable use

• don't use heartbeet for anything illegal, or to monitor or support unlawful activity.
• don't abuse the ingest endpoint (for example, flooding it to disrupt the service), and don't probe, break, or overload heartbeet outside of coordinated, good-faith security disclosure.
• don't resell or sublicense access.
• only send heartbeats for jobs you're entitled to monitor.

your data

your projects, jobs, and configuration are yours. I store and process them only to provide the service (monitoring, dashboards, and alerting), as described in the privacy notice.

availability and warranties

heartbeet is provided on an as-is and as-available basis, without warranties of any kind and without an uptime or delivery guarantee. features may change or be discontinued.

limitation of liability

to the extent the law allows, heartbeet is not liable for indirect, incidental, or consequential damages, or for missed or delayed alerts; and my total liability is limited to the amount you paid me in the 12 months before the claim. nothing here removes rights you have under mandatory consumer law.

governing law

these terms are governed by Norwegian law, with disputes handled by the courts of Oslo, unless mandatory consumer law assigns another venue.

changes

I'll update these terms as the product and the law evolve; the date at the top reflects the current version, and continuing to use heartbeet means you accept the current terms.