Terms of Service

getNodi is operated by the operator of getNodi. By creating an account or using the service you agree to these terms. If you are agreeing on behalf of a company, you are confirming you may bind it, and “you” below means that company.

Three other documents form part of this agreement and are worth reading with it: the privacy policy, the data processing terms and the refund and cancellation policy. Where any of them says something more specific than this page does, the more specific one wins.

You give us a URL, a schedule and — usually — a credential. We make the HTTP request on that schedule, retry it according to your settings, record what came back, and tell you when it fails. That is the whole product, and everything below is about the edges of it.

Schedules are honoured on a best-effort basis. Your plan sets the finest interval you may configure — from hourly on Free down to ten seconds on Enterprise — but an interval is a floor on how often a job may be scheduled, not a promise about the second it fires. Runs can be delayed by queue depth, by a slow target, or by our own maintenance, and a delayed run is not a failed one.

We do not promise your endpoint will be reachable, that a run will succeed, or that a notification will arrive before you would rather have known. getNodi tells you what happened to a request it made; it is not a substitute for your own alerting on anything where a missed check is the difference between a bad day and a serious one.

You need an account, and the account needs a working email address — it is where run failures, billing notices and password resets go, so an address you do not read is a decision with consequences. Passwords are held by Amazon Cognito rather than by us, as described on the security page.

You are responsible for what happens under your account, including anything done with an API key you issued or by someone you invited to a project. If you think a key or a session has been taken, revoke the key from the dashboard and tell us.

You must be old enough to enter a contract where you live, and you must not use the service if we have previously terminated your account.

This is the part that matters most, because a scheduler that calls arbitrary URLs on a schedule is a useful tool and — pointed at the wrong thing — an attack. You agree that for every job you create, you either control the target or are authorised by whoever does.

You must not use getNodi to:

• send traffic to a system you do not have permission to send traffic to, including load testing someone else’s service, credential stuffing, or probing for vulnerabilities;
• generate volume intended to degrade a target — a scheduler is a poor denial-of-service tool and using it as one will end your account rather than the target;
• work around the address restrictions described on the security page, including by pointing a hostname you control at a private or metadata address;
• collect data in breach of a site’s terms, applicable law, or a robots directive you are bound by;
• send unlawful, infringing or unsolicited content through a job or a notification channel;
• resell raw capacity as a competing scheduling service, or run a shared account on behalf of unrelated third parties in place of buying seats.

Running jobs for your own clients is expressly fine — the Agency plan exists for exactly that, and lets you take our name off the public run pages you show them.

Every plan carries explicit limits: how many jobs, how often they may run, how long history is kept, how many channels, keys and seats. They are listed on the pricing page and enforced by the API rather than described and hoped for. Free allows 3 jobs at hourly intervals; the paid tiers raise those numbers.

Beyond the numbered limits we ask only that a single account behave like a single customer. If usage is degrading the service for other people we will contact you before doing anything about it, unless the load is severe enough that waiting would be irresponsible.

We also apply rate limits to the API and to unauthenticated endpoints such as sign-up and password reset. Hitting one returns 429 and is not an incident.

Paid plans are subscriptions. They renew automatically at the end of each billing period — monthly or yearly, whichever you chose — and continue to renew until cancelled. Payment is taken by Razorpay on their own hosted page; card, UPI and netbanking details never reach getNodi.

Prices shown in rupees are inclusive of 18% GST. A tax invoice is available from your billing settings for every payment, and will carry your GSTIN if you have entered one. Customers outside India are billed in US dollars; a service exported from India is zero-rated, so those amounts carry no GST.

Payments are non-refundable. Cancelling stops the next charge and leaves the period you have already paid for running to its end; it does not return that payment. The narrow exceptions — a charge we should not have taken, and a period cut short by us rather than by you — are set out in the refund policy linked below.

If a renewal payment fails, Razorpay retries it. A subscription that stays unpaid ends, and the account returns to the Free plan with Free’s limits — including its shorter retention, which is the part people are surprised by. Cancellation, refunds and what happens to your data afterwards are covered in the refund and cancellation policy.

We may change prices. If a change affects a subscription you already hold, we will tell you at least 30 days before it applies to you, and it takes effect at your next renewal rather than mid-period. You can cancel before then, which is the entire point of the notice.

The first 100 accounts to make a payment hold a lifetime price lock at the amount they first paid. That promise is recorded on the account at the payment that grants it and is not recalculated afterwards — if a locked subscription later lapses, the lock stays with the account rather than being handed to someone else.

Everything you put into getNodi stays yours: your job definitions, your credentials, your execution history. We do not sell it, and we do not use the contents of your responses to train anything. We process it to run the service, as set out in the data processing terms.

The service itself — the software, the interface, the name and the marks — stays ours. You get a licence to use it for as long as this agreement lasts, and nothing more.

Feedback you send us we can act on freely. That is not a claim over anything you built; it means we do not owe you a royalty for fixing something you told us was broken.

The service is provided as it is. We do not warrant that it will be uninterrupted, that every scheduled run will fire, or that it is fit for a particular purpose beyond what is described here.

There is no uptime SLA on the self-serve plans, and we are not going to imply one with a number nobody measured — the security page is equally blunt about this. An SLA with response-time commitments is something we agree individually and in writing on the Enterprise plan.

We will give reasonable notice of planned maintenance that we expect to interrupt runs. Unplanned interruptions get told about after the fact, honestly.

Neither side is liable to the other for indirect or consequential loss, loss of profit, loss of revenue, or loss of anticipated savings, however it arises.

Our total liability to you in connection with this agreement, in aggregate over any twelve month period, is limited to the amount you paid us in that period. On the Free plan that amount is zero, which is a real consequence of a free service and worth understanding before you make one load-bearing.

Nothing here excludes liability that cannot lawfully be excluded — including for fraud, or for death or personal injury caused by negligence.

You will cover us against third-party claims arising from your use of the service in breach of the acceptable-use section above — which is the practical consequence of pointing a scheduler at something you were not entitled to.

You can stop at any time: cancel the subscription from your billing settings, and close the account by writing to us.

We can suspend an account that is breaching the acceptable-use section, that is not paying for what it is using, or that we are legally required to suspend. Where the circumstances allow it we will tell you first and give you a chance to fix it; where the harm is ongoing we will suspend and then explain. Suspension takes effect immediately rather than at the next sign-in, because the check is made against the database on every request rather than read from a token.

We can also end this agreement on 30 days’ notice if we decide to stop offering the service. If we do that while you are in a paid period, you get back the unused part of what you paid.

When an account ends, jobs stop, and its data is deleted on the schedule described in the privacy policy. Export anything you want to keep before you close it.

We will change these terms occasionally. Substantive changes get an email to the address on the account and take effect no sooner than 30 days later; corrections and clarifications take effect when posted. The date this version took effect is at the top of the page.

If you do not accept a change, cancel before it takes effect. Continuing to use the service after that date is acceptance.

This agreement is governed by the laws of India. The seat of jurisdiction has not been declared on this deployment — set LEGAL_JURISDICTION in the environment.

Before either of us goes to court, we should talk. Most of what reaches this section is a misunderstanding about a limit or an invoice, and those are faster to fix by email.

Notices under this agreement go to contact@higglerslab.com. Anything operational — a job behaving oddly, an invoice that looks wrong — is better sent to support@higglerslab.com.