Data Processing Addendum
Last updated: September 16, 2026
This Data Processing Addendum (the "DPA") supplements the Terms of Service and the Privacy Policy and forms a binding agreement between you (the "Controller") and NullRun (the "Processor", "we") once accepted. The DPA is incorporated into the Terms by reference on acceptance, in accordance with Terms §15.
Capitalised terms not defined here have the meaning given in the Terms or the Privacy Policy. The roles (Controller vs Processor) are determined per processing activity as set out in Privacy Policy §1; this DPA applies to the categories of Customer Data for which NullRun is the Processor.
1. Order of precedence and incorporation
This DPA is read together with the Terms and the Privacy Policy. On matters of data protection (controller/processor roles, processing instructions, sub-processor controls, cross-border transfers, breach notification, return or deletion of Customer Data, audit), this DPA prevails over the Terms. On all other matters (commercial terms, liability caps, governing law, dispute resolution), the Terms prevail.
Where this DPA references a section of the Terms or the Privacy Policy, the referenced section is incorporated by reference and may be updated from time to time in accordance with the change-notice rules in the document that contains the original section. Where this DPA contradicts the Privacy Policy on a data-protection matter, this DPA prevails.
2. What this DPA is and is not
This section states what this DPA covers and what it does not.
What NullRun commits to in this DPA:
- Standard controller-processor obligations aligned with the practice of the Fortress-eligible jurisdictions (Singapore PDPA, Turkey KVKK, Brazil LGPD, Japan APPI, Korea PIPA, Australia Privacy Act, etc.).
- The breach-notification process in Privacy Policy §10.
- The 30-day Customer Data export window on termination in Terms §11.
- The sub-processor governance in Privacy Policy §6 (30-day notice, right to object).
- The technical and organisational measures in Privacy Policy §9.
What this DPA does not currently cover:
- NullRun does not currently hold a SOC 2 Type II report or an ISO 27001 certification. Until those reports exist, this DPA cannot offer them as evidence.
- NullRun does not currently appoint a GDPR Article 27 EU representative. Because the Fortress geo-block prevents EU/EEA residents from becoming data subjects of the controller, and the controller is not established in the Union, Article 27 is not engaged under our current analysis (see Privacy Policy §7). If a future residency or customer-base change brings Article 27 into scope, this DPA will be updated before any in-scope processing begins.
- We have not commissioned a formal Transfer Impact Assessment per non-adequate sub-processor. We have considered the residual cross-border-transfer risk in our design (encryption in transit and at rest, Frankfurt residency by default, sub-region pinning to Fortress-eligible jurisdictions) and will provide a written summary of the considerations on request; this is not a substitute for a commissioned TIA.
- We do not currently operate a self-service audit portal, a self-service DSR portal, or a formal personnel training or background-check programme. The personnel who handle Customer Data are bound by confidentiality under the Terms §8 and applicable law; that is the full extent of the personnel controls today.
- We rely on the standard DPA terms each sub-processor publishes (DigitalOcean, Brevo, Polar, Slack, GitHub, Google). We do not hold bespoke paper DPAs with each sub-processor. For transfers from the European Economic Area, the United Kingdom, or Switzerland to a recipient outside those jurisdictions, the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914 of 4 June 2021, Module 2 controller-to-processor) are incorporated into this DPA by reference; the relevant sub-processor is engaged on terms that satisfy the corresponding SCC obligations. Where a published DPA term is insufficient for a particular transfer, we will work with the sub-processor to add supplementary terms before relying on that sub-processor for that transfer.
- This DPA does not currently include binding recovery-time commitments. The recovery objectives published in our security page are operational targets, not contractual service-level commitments. Customers who need contractual recovery guarantees negotiate them per-customer under the Terms §11 amendment process.
If any item in the second list is required for your procurement, please contact us at support@nullrun.io with subject "Enterprise DPA request"; we are happy to negotiate a stronger DPA on a per-customer basis.
3. Documented instructions
NullRun processes Customer Data only on the Controller's documented instructions, as set out in the Terms, this DPA, the Privacy Policy, and any signed order form or in-product configuration.
Acceptable channels for instructions. The Controller may give instructions through (a) actions in the NullRun control center (for example, creating or modifying a workflow, policy, or alert channel), (b) email to support@nullrun.io from an authorised contact on the account, or (c) a signed order form or amendment referencing this DPA.
What counts as "documented". An electronic record in the control center, an email from the address on file, or a signed paper or PDF amendment. Verbal instructions are not documented and we are not obliged to act on them.
Conflicting or out-of-scope instructions. Where an instruction would, if followed, take NullRun outside the scope of the Terms or this DPA, NullRun will (i) promptly inform the Controller, (ii) negotiate an amendment in good faith, and (iii) suspend the affected processing until the conflict is resolved. Where the instruction concerns routine technical configuration that is within scope (for example, "send Slack alerts to channel #ops-alerts"), the Controller may give the instruction unilaterally and NullRun will comply.
4. Confidentiality
Persons authorised by NullRun to process Customer Data are bound by confidentiality obligations under the Terms §8 and under applicable law. The Service is operated by Individual Entrepreneur Anatolii Maltsev (Republic of Armenia, TIN 20275845); the proprietor and any future personnel are bound by the confidentiality undertaking in the Terms §8 before access is granted.
NullRun does not currently maintain a formal personnel training programme, a formal background-check process, or a separate personnel certification regime. Where a customer requires such a programme, the request is handled under Terms §11 (per-customer amendment) and is priced separately.
5. Security measures
NullRun implements the technical and organisational measures set out in Privacy Policy §9 (TLS 1.3, AES-256 at rest via pgcrypto, Argon2id password hashing, application-layer per-tenant scoping on every tenant-scoped query — formal Postgres Row-Level Security policies are an active refactor; the outbox processor currently runs as a BYPASSRLS role, audited separately — hash-chained append-only audit log, PII redaction at the logging boundary, cookie hardening, CSRF double-submit, fail-closed enforcement paths, Fortress geo-block at the application edge, name/email sanctions screening at signup where the screening layer has been enabled for the deployment, restricted production access on a need-to-know basis).
NullRun may update the technical and organisational measures from time to time to reflect improvements in security practice. A material change that reduces the level of protection (for example, removing a control that was previously listed) will be notified to Controllers in advance in accordance with the change-notice rules in this DPA §11. A routine improvement that maintains or strengthens the level of protection does not require advance notice.
6. Sub-processors
The current list of sub-processors, the categories of Customer Data each sub-processor processes, and the country of establishment are published in Privacy Policy §6. The list is the authoritative list for the purposes of this §6.
Adding or replacing a sub-processor. NullRun will notify the Controller of any material change to the sub-processor list (an addition or replacement that processes Customer Data) at least 30 days before the change takes effect, by email to the Controller's primary contact and (where appropriate) by an in-product banner.
Right to object. The Controller may object to a material change on a data-protection ground. Where the objection is substantiated and NullRun cannot resolve it by offering a reasonable alternative (a different sub-processor, a regional residency option, or removal of the affected data category from the sub-processor's scope), the Controller may terminate the affected Service for cause in accordance with the Terms and receive a pro-rated refund of any prepaid fees for the unused portion of the subscription term.
Flow-down of obligations. Each sub-processor is engaged on terms that NullRun believes in good faith impose data-protection obligations no less protective than this DPA on the data categories that sub-processor processes. As noted in §2 above, today NullRun relies on the published standard DPA terms each sub-processor makes available rather than bespoke paper DPAs; where a sub-processor's published terms do not meet this standard for a particular transfer, NullRun will work with the sub-processor to add SCCs or supplementary terms before relying on that sub-processor for that transfer, or will route that transfer through a different sub-processor.
Liability for sub-processor acts. NullRun is fully liable to the Controller for the acts and omissions of each sub-processor as if they were NullRun's own, in accordance with the law of the Controller's jurisdiction.
7. International data transfers
Where NullRun transfers Customer Data across borders, the transfer is governed by the mechanisms described in this §7 and in Privacy Policy §7. NullRun prefers sub-processors established in Fortress-eligible jurisdictions; where a sub-processor is established elsewhere, we rely on the published DPA of the sub-processor, the sub-processor's standard contractual terms, the EU Standard Contractual Clauses (Decision 2021/914) where applicable, or another lawful transfer mechanism accepted under the law of the customer’s jurisdiction.
Frankfurt (Germany) and the European Union. The default data residency is Frankfurt, Germany (DigitalOcean FRA1). Because Frankfurt sits in the European Union, German BDSG applies directly to the hosting layer for any EU-located former customer or residual traffic (probes, partner-managed endpoints, or retrospective deletion requests). The Fortress geo-block at the edge prevents EU/EEA/UK residents from creating accounts, so the GDPR is not engaged as a controller regime under Art. 3(1) (no establishment of the controller in the Union) or Art. 3(2) (no targeting of EU data subjects) for the bulk of customer traffic. We nonetheless publish this DPA so the access path is unambiguous if an EU authority ever inquires about residual traffic. Cross-border transfers from Fortress-eligible jurisdictions to Frankfurt are supported under the recipient’s published DPA or the recipient’s standard contractual terms.
EU Standard Contractual Clauses. For any transfer of Customer Data from a data subject in the European Economic Area, the United Kingdom, or Switzerland to a recipient outside those jurisdictions (including any transfer from a Controller established in those jurisdictions to a NullRun sub-processor established elsewhere), the EU Standard Contractual Clauses — Commission Implementing Decision (EU) 2021/914 of 4 June 2021 — Module 2 (controller-to-processor) or Module 3 (processor-to-processor), as applicable, are incorporated into this DPA by reference. The clauses are deemed signed between the Controller and the relevant NullRun processor entity on acceptance of this DPA. The data-importer / data-exporter details, the list of sub-processors, the technical and organisational measures in §5, the retention rules in §11, and the dispute-resolution and governing-law clauses in the Terms §20 are read into Annexes I–III of the SCCs by reference. Where the SCCs require a separate written signature (for example, because the parties have not entered into the underlying commercial agreement as defined in the SCCs), the parties will sign a short-form SCC adoption agreement on the Controller’s request.
Activation of the SCC mechanism. The SCC mechanism described above is incorporated into this DPA prospectively. As of the effective date of this §7, the Fortress geo-block at the application edge continues to reject ingress from the European Economic Area, the United Kingdom, and Switzerland (see the Privacy Policy §16 and the Terms §16 for the canonical ineligible-jurisdiction list), so the controller-to-processor flow that would engage Module 2 from those jurisdictions is not currently exercised in production traffic. The SCC mechanism activates on the earlier of (a) NullRun removing a jurisdiction from the Fortress ineligible list and the corresponding removal of the Fortress geo-block entry for that jurisdiction, or (b) NullRun entering into a per-customer enterprise addendum under Terms §11 that admits a Controller established in an otherwise-ineligible jurisdiction. Until either (a) or (b) the SCC mechanism is dormant with respect to that jurisdiction.
United States sub-processors. Some of our sub-processors (Slack, GitHub, Google) are headquartered in the United States. We acknowledge that US national-security laws may permit US authorities to compel disclosure of personal data held by those sub-processors. We address this risk in the following layered way: (a) we rely on the published DPA of each US sub-processor; (b) we apply the security measures in §5 (encryption in transit and at rest with keys held outside the database tier); (c) where a US sub-processor offers a regional data-residency option that keeps Customer Data in a non-US region, NullRun uses that option by default.
APEC CBPR alignment. NullRun works towards alignment with the Asia-Pacific Economic Cooperation ("APEC") Cross-Border Privacy Rules ("CBPR") system. We honour the substantive APEC CBPR principles (preventing harm, notice, collection limitation, use of personal information, integrity, security safeguards, access and correction, accountability) in the cross-border transfer context until full APEC CBPR certification is achieved.
No transfers to comprehensively-sanctioned jurisdictions. We do not transfer Customer Data to, or store it in, any comprehensively-sanctioned jurisdiction (see the Privacy Policy §16 and the Terms §16 for the canonical list).
8. Assistance with data-subject requests
Where a data subject makes a request to the Controller that requires action by NullRun (for example, access to Customer Data, deletion, rectification, restriction, portability, or objection), NullRun will provide the following assistance.
Channels. Requests are accepted by email to support@nullrun.io with subject "DSR assistance", or via the Privacy action in the control center (where available). NullRun does not currently operate a self-service DSR portal; requests are handled via email and manual investigation.
Response times. NullRun will acknowledge a new request within 5 business days. Substantive action is taken within the time period required by the applicable law (typically 30 days in most Fortress-eligible jurisdictions), extendable once where the law permits and the request requires additional time. Where NullRun cannot meet the timeframe, NullRun will explain why and propose a new timeframe.
Scope of assistance. For an access or portability request, NullRun will export the relevant Customer Data in a machine-readable format (JSON) and deliver it via a signed download link. For an erasure request, NullRun will delete the relevant Customer Data from active processing and flag the backup copy for overwrite on the normal cycle. For a rectification request, NullRun will update the relevant rows and propagate the change to related tables; the audit log entry is preserved (the audit log is append-only and tamper-evident by design).
Cost. Assistance within a reasonable scope (up to 5 requests per Controller per calendar year) is provided at no additional charge. Excessive, manifestly unfounded, or repeated requests that require disproportionate effort may be charged at NullRun's documented hourly rate, with prior notice to the Controller.
9. Assistance with other Controller obligations
Where the Controller is required to conduct a data-protection impact assessment or to consult a competent authority, and the assessment or consultation requires information about NullRun's processing, NullRun will provide that information in writing on request. NullRun does not perform the assessment on the Controller's behalf and does not provide legal advice.
Where the Controller requires more substantial assistance, the request is handled under Terms §11 (per-customer amendment) and is priced separately.
10. Breach notification
NullRun will notify the Controller of a confirmed personal-data breach affecting the Controller's Customer Data in accordance with Privacy Policy §10: without undue delay and, where feasible, no later than 24 hours after NullRun has classified the breach as High or Medium severity. The notification will include the categories of data affected, the likely consequences, and the measures NullRun has taken or proposes to take.
Where a breach is required to be notified to a competent authority, NullRun will support the Controller in making that notification, including by providing the information the Controller needs to satisfy the relevant statutory window where feasible.
11. Return or deletion on termination
On termination of the Terms, the Controller may elect to receive a copy of its Customer Data (return) or to have the Customer Data deleted. The election must be communicated to NullRun within the 30-day data-export window in Terms §11. If no election is made within the window, NullRun will delete the Customer Data in accordance with Privacy Policy §5.
Return format. Customer Data is delivered as a single JSON archive. The archive is delivered via a signed download link with a 7-day expiry. The download link is single-account and is logged.
Deletion confirmation. Where the Controller elects deletion, NullRun issues a written confirmation within 30 days of the completion of deletion, identifying the categories of data deleted and the date of deletion.
Backup exception. Customer Data held in NullRun's rolling backups is overwritten on the normal 7-day cycle and is not restored to comply with a deletion request. Where the Controller requires confirmation that no Customer Data remains in backups, NullRun will provide a written statement to that effect after the next backup-overwrite cycle following the deletion request.
Legal retention exception. Where applicable law requires NullRun to retain certain records (for example, tax-invoice records, anti-money-laundering records, or records needed to defend a pending legal claim), NullRun will retain the minimum necessary, isolate the retained records from active processing, and delete them when the underlying obligation or claim is resolved.
12. Demonstration of compliance and audit
This section describes what NullRun currently offers. It is intentionally narrower than the audit rights that a mature compliance programme would offer; a Controller who needs stronger audit rights can request them under Terms §11 (per-customer amendment).
Written information on request. On the Controller's written request, NullRun will provide a written description of (a) the technical and organisational measures applied to the Controller's Customer Data, (b) the sub-processor list, (c) the locations where Customer Data is processed, and (d) the breach history for the trailing 12 months (limited to breaches affecting the Controller's Customer Data). NullRun will respond within 30 days of the request.
What NullRun does not currently offer. NullRun does not hold a SOC 2 Type II report or an ISO 27001 certification, does not operate a self-service audit portal, and does not provide on-demand audit access to live production systems.
Mutually-agreed third-party audit. Where the Controller requires an audit that cannot be satisfied by the written information above, NullRun will accept a mutually-agreed independent third-party auditor at the Controller's expense, on at least 30 days' written notice, no more than once per 12-month period. The audit scope is limited to the systems and records that process the Controller's Customer Data. The auditor must be qualified, must be bound by a confidentiality undertaking acceptable to NullRun, must conduct the audit during business hours, and must not interfere with NullRun's operations or access the data of other Controllers. Where the audit identifies a material non-compliance, NullRun will bear the reasonable cost of the audit and will agree a remediation plan with the Controller.
Competent-authority cooperation. NullRun will cooperate in good faith with a competent authority investigation, to the extent permitted by applicable law and the Terms.
13. Liability
The liability framework in Terms §13 (limitation of liability) and Terms §14 (indemnification) applies to claims under this DPA, including the data-breach carve-out in Terms §13.
Controller liability for instructions. The Controller is liable to NullRun for damages caused by an instruction that exceeds the scope of the Terms or this DPA, where NullRun has promptly informed the Controller that the instruction is out of scope and the Controller has insisted.
Sub-processor liability. NullRun is fully liable to the Controller for the acts and omissions of each sub-processor as if they were NullRun's own.
14. Effect of termination, survival
This DPA terminates automatically on termination of the Terms, except for the provisions that by their nature should survive (§§7, 10, 11, 12, 13, 15, and 16 of this DPA, together with the dispute-resolution and governing-law provisions of the Terms). The survival period extends while Customer Data remains in NullRun's backup cycle or in any legally-required retention, and for one year thereafter for the purpose of resolving any claim that arose during the term.
15. Jurisdictional addenda
Where the Controller is established in a Fortress-eligible jurisdiction whose data-protection law requires additional or different obligations beyond what is set out in this DPA, the parties will negotiate a jurisdiction-specific addendum that supplements this DPA. The standard addenda we maintain are:
- Singapore PDPA addendum — adds the PDPA's accountability, transfer-limitation, and notification obligations; aligns with the PDPC's published guidance.
- Turkey KVKK addendum — adds the explicit controller-processor contract language required by KVKK article 9; aligns with the KVKK Veri Sorumluları Envanteri guidance.
- Brazil LGPD addendum — adds the operator (operador) language required by LGPD art. 39; aligns with the ANPD's published guidance.
- Japan APPI addendum — adds the entrustment language required by APPI art. 22.
- South Korea PIPA addendum — adds the consignment language required by PIPA art. 26.
- Kazakhstan addendum — adds the cross-border-transfer consent / contract requirements under Kazakhstan's personal-data law.
- United States addendum (placeholder) — available on request. CCPA / CPRA-specific obligations (sale / share opt-out, sensitive personal information limits, consumer-rights disclosures) are evaluated per-customer and are not required for non-California-resident customers below the CCPA threshold. No automated addendum exists at this time.
- Canada addendum (placeholder) — available on request. PIPEDA-specific obligations and the Quebec Law 25 opt-in consent regime are evaluated per-customer; the Quebec Law 25 component is deferred until a Quebec-resident customer is onboarded (per the Cookies Policy §0 carve-out).
Customers may request any of these addenda by emailing support@nullrun.io. The addenda are priced at NullRun's standard per-customer amendment rate.
16. Acceptance, notices, contact
Acceptance. This DPA is accepted (a) by clicking the "Accept DPA" action in the NullRun control center, (b) by completing a checkout that references this DPA, or (c) by signing an order form that incorporates this DPA by reference. Acceptance binds the Controller to the Terms and this DPA from the date of acceptance.
Notices. Notices under this DPA (including audit requests, sub-processor objections, breach-related information, and DPA amendments) must be sent to support@nullrun.io with a subject line that describes the nature of the notice. NullRun may give notice to the Controller by email to the address associated with the account or by posting an in-product banner.
The Processor for the purposes of this DPA is:
Individual Entrepreneur Anatolii Maltsev
Country of establishment: Republic of Armenia
Tax identification: 20275845 (TIN / public service number)