Data Processing Terms
The terms on which we process personal data on your behalf. They apply to every account automatically as part of the Terms of Service — you do not need to ask for a DPA to be covered by one.
This deployment has not declared its operator.
These documents name a company as a party to them, and this one has not been told which company that is. Set COMPANY_LEGAL_NAME and COMPANY_ADDRESS (and LEGAL_EFFECTIVE_DATE) in the environment before treating anything on this page as published.
Who is who
Where your jobs carry personal data through getNodi, you are the controller and the operator of getNodi is the processor. You decide what your jobs send and what your endpoints return; we execute those requests and store the results because you configured us to.
These terms are incorporated into the Terms of Service and apply to every account from the moment it is created. Where they conflict with the Terms on the handling of personal data, these terms win.
Data about your own account — your email, your billing details — is not covered here, because for that we are the controller rather than your processor. The privacy policy governs it.
What is being processed, and for how long
- Subject matter
- Execution of scheduled HTTP requests you configure, and retention of what those requests returned.
- Duration
- For as long as your account is open. Individual execution records are deleted at your project’s retention window; everything else is deleted when the account is closed.
- Nature and purpose
- Storage, transmission and retrieval — running the schedule, recording the outcome, showing it back to you, and alerting you when it fails. We do not analyse the content of your responses for any purpose of our own.
- Types of personal data
- Whatever you put in a job or your endpoints return. We do not set this. In practice it is request bodies, request headers, and the retained portion of a response body — plus the credentials you store, which are encrypted at rest.
- Categories of data subject
- Determined entirely by you. Commonly your own end users, staff or customers, depending on what the endpoints being called are for.
Because you choose all of that, you also carry the decision about whether special-category data should be flowing through here at all. The two controls that matter are your project’s retention window and your plan’s response-snippet limit — the second caps how much of any response body is ever written down, and setting it low is the most effective thing you can do to keep sensitive content out of our store.
We process only on your instructions
We process personal data only to provide the service and only as instructed by you. Your job configuration is the instruction: the URL, the method, the schedule, the retention window and the snippet limit are the documented instruction set, and changing them changes what we do.
If we are ever legally compelled to process beyond that, we will tell you before we do it unless the law forbids us from telling you.
If we think an instruction breaches data protection law, we will say so. We will not silently comply with something we believe is unlawful, and we will not silently refuse it either.
Confidentiality
Everyone with access to your data is bound to confidentiality, and access is limited to the people who need it to operate and support the service. Support staff do not read your execution records to pass the time; they look when you have asked for help with something and the record is how the question gets answered.
Security measures
The measures we apply are set out with their parameters on the security page, which is written to be checked rather than trusted. In summary:
- stored credentials are encrypted with AES-256-GCM under a key held outside the database, with a per-encryption IV and an authentication tag;
- secrets are write-only across the API — no endpoint returns one, and responses are built from an allow-list rather than by serialising the record;
- API keys are stored as SHA-256 digests and compared in constant time;
- outbound requests are validated against resolved addresses, refusing private, loopback, link-local and cloud-metadata ranges, and failing closed on anything unresolvable;
- requests can be signed with HMAC-SHA256 over
<timestamp>.<body>so your endpoint can verify origin and reject replays; - credential-bearing headers are redacted in operational logs and response snippets are truncated before storage;
- account suspension and privilege changes are re-read from the database on every request rather than trusted from a token, so revocation is immediate.
These are the measures as implemented today. We may change them, but not in a way that materially reduces the protection applied to your data.
Sub-processors
You authorise us to engage the sub-processors below. Each is bound by terms no less protective than these, and we remain responsible to you for what they do.
- Amazon Web Services (Cognito)
- Stores account credentials and sends verification and password-reset email. · As configured by the operator
- Razorpay Software Private Limited
- Takes payment and holds the payment instrument. Card details never reach us. · India
Only the two providers the software cannot run without are declared on this deployment. Its hosting, database and mail providers are missing — set LEGAL_SUBPROCESSORS in the environment. A sub-processor list that is short because nobody finished it reads exactly like one that is short because the stack is simple.
Before we add or replace one, we will give you 30 days’ notice by email. If you object on reasonable data-protection grounds within that period, tell us and we will either find another way or let you cancel and refund the unused part of your current period. What we will not do is add one quietly and update this page afterwards.
Requests from data subjects
If one of your data subjects contacts us directly, we will not answer on your behalf — we will tell them to contact you, and tell you it happened.
For requests you receive, most of what you need is already in your hands: the dashboard and the API let you read, export and delete jobs and execution records yourself, which usually makes an access or erasure request something you can complete without us. Where it is not, ask and we will help.
Telling you about a breach
If we become aware of a personal data breach affecting data we process for you, we will notify you without undue delay and in any case within 72 hours of establishing it, with what we know: what happened, what data was involved, the likely consequences, and what we are doing about it.
Reporting to a supervisory authority is your call as controller, and our notice is timed so you can make it inside your own deadline. We will give you what you need for that report.
Getting it back, and getting rid of it
You can export your data at any time through the dashboard and the API for as long as your account is open.
When the account closes, jobs stop and their data is deleted. Execution records that reached their retention window were already deleted before that, by the TTL index in the database rather than by a process that has to remember to run.
Backups are the honest exception. A record deleted from the live database can persist in a backup until that backup expires on its own cycle; it is not restored selectively and is not accessible in the ordinary course of running the service.
Demonstrating this
We will give you the information you reasonably need to show that we are meeting these obligations. The security page is the standing answer to most of it, and it is specific enough to check.
We hold no SOC 2 or ISO 27001 certification and will not gesture at one. If your process requires an audit report, say so early — we would rather tell you plainly that we cannot meet the requirement than have you find out at procurement. A security review is something we do individually on the Enterprise plan.
International transfers
The service is operated from India and data is processed there and in the regions the sub-processors above operate in. Transfers out of the EEA or UK, where they occur, rely on the Standard Contractual Clauses or the equivalent mechanism offered by the provider involved.
Liability
The limits in the Terms of Service apply to these terms too. They are one agreement with one cap, not two agreements with two.
Getting a signed copy
You are covered by these terms without asking. What has to be asked for is a countersigned copy, or execution of your own DPA template — that is a per-customer commitment we make on the Enterprise plan, along with a security review and an SLA.
Write to contact@higglerslab.com with what your process requires. We will tell you honestly whether we can meet it before you spend time on it.