Terms of service

Last updated 23 October 2026

These terms are the agreement between you and HURYN Sp. z o.o., ul. Hoża 29, 00-521 Warszawa, Poland (KRS 0000893173, NIP 7011027727, REGON 388627882), “we”, for your use of Staygreen. By creating an account, you accept them.

1. What Staygreen is

A monitoring service for apps you build. You add an app and the monitors that watch it. Staygreen checks each monitor’s target on its schedule from Toronto (Canada) and San Francisco (US), records what it found, and opens an incident when a failure is confirmed, which it sends as an alert by email and to the Telegram chats you connect, with another when it recovers. A heartbeat monitor works the other way round: your scheduled job calls a URL Staygreen gives you, and a run that is missed, fails or gets stuck opens one. You can publish a status page that shows your users the state of what you choose to put on it.

Scheduled checks haven’t started for new workspaces yet, so a monitor you add isn’t checked until they do, and nothing receives heartbeat pings yet, so no heartbeat opens an incident.

The one-time scan reads public app responses and optional service health using the credentials you supply. It creates no monitors and is not a security audit or a guarantee that everything works. Unknown or skipped checks mean no conclusion was reached. Supply only credentials you are authorized to use. The widget shows published status data; if that data is unreachable, it shows nothing.

2. Accounts

• You sign in through Clerk, our sign-in provider. Your account works inside a workspace, and a new account gets a workspace of its own.
• Keep your sign-in to yourself. You are responsible for what happens under your account.
• You can authorize a coding agent through Clerk or give a pipeline a workspace API token. Choose its access carefully and keep tokens private. Its permitted changes act for your workspace; incident updates it drafts still need you to publish them.
• A workspace’s admins decide who joins it, and are responsible for what the workspace monitors and publishes.
• You must be at least 16, or have your guardian’s permission.

3. What you monitor, and your content

Monitor only what you run, or are allowed to test. Checks send requests to the targets you add, on the schedule you set, from the locations above, and a test or a suggested check you start from the dashboard sends one from our hosting provider’s servers. You are responsible for having the right to send them. Staygreen refuses targets on private networks.

What you put into Staygreen stays yours: names, addresses, incident updates, images, and what your jobs send. You give us only the permission we need to run the service: to store it, to use it to check your targets, to show it to your workspace, to publish what you choose to publish, and to pass it to the processors named in our privacy policy.

A status page is public unless you make it members-only. Anyone who has its address can read it: its name and logo, a link to the homepage you set (at first, your app’s address), the components you put on it with their state and daily uptime, and every incident update you publish. So can anyone who sees its README badge, which shows the page’s name and its overall state. An update you haven’t published, and a monitor you haven’t put on the page, never appear there. Members-only pages require sign-in to their workspace and have no public summary or badge. Attach only a custom domain you control; its certificate records are public. Making a page private cannot recall copies someone already saved while it was public.

Alerts go where you send them. Every member of a workspace who can see its monitors gets its alerts by email. Add someone else’s email address, or connect a Telegram chat other people are in, only with their agreement: an address gets nothing until its owner confirms it, and anyone who gets an alert can stop them from the alert itself.

A heartbeat’s URL is its only credential. Anyone who has it can report for your job. Keep it like a password, and make a new one if it leaks: the old one stops working at once.

Connect only Stripe accounts and Supabase projects you may monitor. Supply a restricted Stripe key with Events and Webhook Endpoints read access only, or a Supabase publishable key. Stripe delivery alerts cover the account, not a particular endpoint. A Supabase name that stops resolving may be paused or deleted; health checks alone do not keep its database awake.

4. What you may not do

• Break the law, or use Staygreen to harass, threaten or defame anyone.
• Point monitors at systems you aren’t allowed to test, or use Staygreen to flood, scan or attack anyone’s service.
• Publish on a status page someone else’s personal data, or anything you have no right to publish.
• Use alerts to send email or messages to anyone who hasn’t agreed to get them.
• Attempt to reach a workspace or account that isn’t yours, or to work around a plan limit or a rate limit.
• Attack Staygreen itself: flooding it, scraping it at scale, probing it for vulnerabilities without our written permission, or interfering with anyone else’s use of it.
• Resell access to Staygreen.

We may remove content from a status page, or suspend a workspace, that breaks these terms or the law, and we will say why when we can.

5. Plans and payment

The limits for your plan are the ones listed on the pricing page.

• The Free plan allows commercial use. No card is required, and it doesn’t expire.
• The Builder plan adds more apps and monitors, faster checks and the features listed on the pricing page; anything marked Coming soon there isn’t part of it yet.
• Builder is billed by Clerk through Stripe, and we never see your card details. Prices are in US dollars, and the price Clerk’s checkout shows before you pay is what you are charged.
• Cancel at any time; Builder runs to the end of the period you paid for. Statutory consumer withdrawal rights are unaffected.
• If we change a price, we tell you before it applies to you, and you may cancel instead.
• If Staygreen shuts down, you get a refund for the unused part of your plan.

6. Keeping your data

Deleting a monitor, an app or a status page deletes it at once, with everything under it; the privacy policy says what that is. Deleting a whole workspace isn’t built yet, and deleting your account or your organization in Clerk doesn’t delete what the workspace holds, so its status pages would stay public. Until it is built, we delete a workspace on request.

7. Availability

We work to keep Staygreen up but don’t promise uninterrupted service on any plan, and we may take it down for maintenance. There is no service level agreement unless we have signed one with you.

A monitoring service can miss a failure, report one that isn’t there, or report late. Don’t make Staygreen the only thing that tells you about a failure that could harm someone.

8. Liability

9. Ending it

You may stop using Staygreen at any time. We may suspend or close a workspace that breaks these terms or the law. When a workspace is closed, what it holds is deleted as the privacy policy describes.

10. Law and disputes

Polish law governs these terms, and the courts of Warsaw have jurisdiction. If you are a consumer, this doesn’t deprive you of the protection of the mandatory law of the country you live in, and you may bring proceedings where you live.

11. Changes

We may update these terms. The date at the top changes with them, and we tell workspace admins by email before a material change applies to them. Continuing to use Staygreen after that means you accept them.

12. Contact

HURYN Sp. z o.o., ul. Hoża 29, 00-521 Warszawa, Poland, or contact@staygreen.io.