Data Processing Agreement

Our DPA, in public

When personal data in your use of Norcube belongs to your users or customers, you are the controller and we are your processor. This agreement applies automatically with the Terms of Service; a countersigned copy is available on request.

GDPR Article 28EU SCCs incorporatedData stored in the EUIncluded for every customer

Last updated: November 5, 2026

This Data Processing Agreement ("DPA") forms part of the Terms of Service and applies automatically when they are accepted; Article 28(9) GDPR permits this electronic form. No separate signature is required. If your procurement process requires a signed copy, email [email protected] and we will return a countersigned PDF within 5 business days at no charge.

#1. Parties and roles

This DPA is concluded between the customer that has accepted the Terms of Service on behalf of its Organization (the Controller) and Jetlio, s.r.o., ID No. (IČO) 09967231, Voroněžská 2547/1, 616 00 Brno, Czech Republic, registered in the Commercial Register kept by the Regional Court in Brno, file C 121887, operating Norcube (the Processor).

It governs the personal data contained in Customer Data that the Processor processes on the Controller's behalf when providing the Services. Personal data for which the Processor acts as an independent controller (Accounts, billing, security logs, website visitors) is described in the Privacy Policy and is outside the scope of this DPA.

Terms defined in the GDPR (Regulation (EU) 2016/679), such as personal data, processing, data subject and personal data breach, have the meanings given there. Other capitalized terms have the meanings given in the Terms of Service.

#2. Subject matter, duration, nature and purpose

The Processor processes the personal data described in Annex 1 for the purpose of providing the Services to the Controller, for the duration of the Terms of Service and until the data is deleted under section 8.

#3. The Processor's obligations

In accordance with Article 28(3) GDPR, the Processor shall:

  1. process personal data only on the Controller's documented instructions, including with regard to transfers to third countries, unless required to do so by EU or Czech law, in which case it informs the Controller before processing unless that law prohibits it. The Controller's instructions are these Terms and this DPA, the Controller's use and configuration of the Services, and any further written instructions agreed by the parties. Connecting a third-party service in the Services (for example the Controller's own GitHub repository, storage bucket or alert destination) is an instruction to transfer the relevant data to that service, which the Controller engages under its own agreement and which is not a subprocessor of the Processor;
  2. ensure that persons authorized to process the personal data are bound by confidentiality obligations that survive the end of their engagement;
  3. implement the technical and organizational measures described in Annex 2, as required by Article 32 GDPR;
  4. engage subprocessors only under the conditions of section 4;
  5. assist the Controller, taking into account the nature of the processing, in responding to requests from data subjects. Self-service tools for export and deletion are available in the Services; where the Controller needs assistance beyond them, the Processor provides it within 14 days of a written request, and forwards to the Controller any request it receives directly from a data subject;
  6. assist the Controller in ensuring compliance with Articles 32 to 36 GDPR, including breach notification under section 6;
  7. at the end of processing, delete or return the personal data under section 8;
  8. make available to the Controller the information necessary to demonstrate compliance with this DPA and allow for audits under section 7; and
  9. immediately inform the Controller if, in its opinion, an instruction infringes the GDPR or other data protection law.

#4. Subprocessors

4.1 The Controller grants the Processor general written authorization to engage the subprocessors listed on the Subprocessors page (Annex 3).

4.2 The Processor engages each subprocessor under a written agreement that imposes data protection obligations providing the guarantees required by Article 28 GDPR. For the current subprocessors, this is each provider's standard data processing agreement, which forms part of its service terms and was accepted by the Processor when it started using the service.

4.3 The Processor announces any intended addition or replacement of a subprocessor on the Subprocessors page at least 30 days before the change takes effect, and by email to Controllers who have asked to receive such notices at [email protected]. Where an urgent replacement is necessary to maintain the security or continuity of the Services, the Processor announces it as soon as possible. The Controller may object on reasonable data protection grounds within that period. The parties will seek a solution in good faith; if none is found, the Controller may terminate the affected Services without penalty.

4.4 The Processor remains fully liable to the Controller for the performance of each subprocessor's obligations, in accordance with Article 28(4) GDPR.

#5. International transfers

5.1 Customer Data is stored in the EU, in the AWS Europe (Frankfurt) region, eu-central-1.

5.2 Where a subprocessor processes personal data outside the European Economic Area, the transfer relies on an adequacy decision of the European Commission, including the EU-US Data Privacy Framework for certified recipients, and on the Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914. Module Three (processor to processor) of those clauses is incorporated by reference for onward transfers by the Processor, and applies automatically if a relied-upon adequacy decision ceases to be valid. Where a transfer from the Controller to the Processor itself requires them, Module Two (controller to processor) is incorporated by reference.

5.3 The location and transfer mechanism of each subprocessor are stated on the Subprocessors page.

#6. Personal data breaches

6.1 The Processor notifies the Controller of a personal data breach affecting the Controller's personal data without undue delay, and in any event within 48 hours of confirming it, so that the Controller can meet its own 72-hour notification obligation under Article 33 GDPR.

6.2 The notification is sent by email to the owners of the Controller's Organization and describes, to the extent then known, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. Information that is not available at first is provided as it becomes available.

6.3 The Processor takes the measures necessary to contain the breach and mitigate its effects, and assists the Controller with notifications to supervisory authorities and data subjects.

#7. Audits

7.1 The Processor demonstrates compliance primarily through documentation: this DPA, the Subprocessors and Security pages, and its answers to reasonable security questionnaires.

7.2 Where this documentation is insufficient, the Controller may audit the Processor's compliance with this DPA, itself or through an independent auditor bound by confidentiality who is not a competitor of the Processor: at most once per year, unless following a confirmed personal data breach, with 30 days' written notice, during business hours and without disrupting the Services, at the Controller's cost. If the audit reveals material non-compliance, the Processor bears the reasonable cost of the audit.

#8. Deletion and return

8.1 The Controller can export Customer Data at any time while the Terms of Service are in effect.

8.2 When the Controller closes its Organization or the Terms of Service end, the Processor deletes the personal data within 30 days. Residual copies in encrypted infrastructure backups are purged within 90 days and remain protected by this DPA until then. Data the Processor must retain by law is kept for the statutory period only. The Processor confirms deletion in writing on request.

#9. Liability, term and governing law

9.1 Liability under this DPA is governed by the Terms of Service, including their limitation of liability and its statutory exceptions. Nothing in this DPA limits liability that cannot be limited under data protection law, including Article 82 GDPR.

9.2 This DPA remains in effect for as long as the Processor processes personal data on the Controller's behalf. It is governed by the laws of the Czech Republic.

9.3 Order of precedence. In case of conflict: (1) the Standard Contractual Clauses, where they apply, prevail; (2) this DPA prevails over the Terms of Service in matters of personal data protection; (3) the Terms of Service prevail in all other matters.

#Annex 1: Description of the processing

Data subjects: the Controller's users, customers, employees, contacts and other persons whose personal data the Controller places in Customer Data; members of the Controller's Organization; people who subscribe to the Controller's status page.

Categories of personal data: any personal data contained in Customer Data, which the Controller determines, including in particular:

  • Backup: the contents of the databases the Controller connects, including any personal data stored in them, and the connection credentials;
  • LangSync: translation keys, source texts and translations, glossaries and custom prompts;
  • DomainRadar: domain lists, monitored brand names, name-generator descriptions and the domain registration data returned for them;
  • Norcube CMS: the content of connected repositories and the content authors edit, page discussions and history;
  • Monitor: monitored URLs, request settings and secrets, check results, alert contacts including email addresses and phone numbers, and status page content, which is public once published;
  • Monitor status page subscribers: the email address, language, chosen components and sign-up and confirmation times of each person who subscribes to the Controller's status page. These people are the visitors of the Controller's page, so the Controller is the controller of this data. The Processor sends the email on the Controller's behalf, under the page's name, through Mailgun from mg.norcubestatus.com. The Controller can see, export and remove addresses in the Services. Unsubscribing deletes the address, an address that isn't confirmed is deleted after 7 days, and all of a page's addresses are deleted when the page or the Organization is deleted;
  • all Services: names and email addresses of Organization members as they appear in activity records.

Special categories: the Services are not designed for special categories of personal data. The Controller is responsible for any such data it places in Customer Data.

Processing operations: storage, retrieval, copying, encryption, compression, transmission to the Controller's chosen destinations, restoring backups into temporary databases to test them, sending status page email to subscribers, AI-assisted translation and content suggestions (for the features the Controller uses), display in the dashboard and APIs, export and deletion.

#Annex 2: Technical and organizational measures

  • Encryption in transit: TLS for all connections to the Services; mutual TLS between internal services.
  • Encryption at rest: storage and databases are encrypted at rest. Database credentials stored for Backup, and Monitor's secret headers, Slack and Discord URLs and webhook signing secrets, are encrypted with AES-256-GCM under keys managed in AWS KMS. API keys are stored only as HMAC-SHA256 hashes, and passwords only as bcrypt hashes.
  • Access control: role-based permissions within each Organization; strict separation of Organizations in every Service; access to production systems limited to authorized personnel and logged.
  • Network: Services run in private network segments; inbound traffic is restricted to the necessary endpoints.
  • Logging and monitoring: request bodies are not logged. Service logs are retained for 30 to 400 days depending on the service. Security audit logs are retained for one year, and deleted with the Organization's other data if it is closed sooner.
  • Availability and resilience: managed cloud infrastructure in the EU (AWS eu-central-1), except public status pages, which Cloudflare stores and serves worldwide; automated, encrypted backups of our own databases; restore testing as part of the Backup service.
  • Secure development: code review before deployment, separated environments, no production credentials in source code, timely dependency updates.
  • Organizational measures: confidentiality obligations for all persons with access to personal data; a documented incident-response process; data protection by design and by default in the development of new features.

The Processor may update these measures provided that the overall level of security is not reduced.

#Annex 3: Subprocessors

The current list of subprocessors, with their purposes, locations and transfer mechanisms, is maintained at norcube.com/subprocessors.

Effective from 27 October 2026

// tick. tick. tick.
0 ticks since founding
Coming soon

Join the PromptHub waitlist

PromptHub is in active development. Leave your email and we'll invite you as soon as it opens, with a free tier and no credit card.

One email when access opens. No newsletter, no spam.