Developer agreement
Effective from 16 November 2026
This is a translation. If the Danish and English versions differ, the Danish version applies.
When we write "we", "us" and "NemDisplay", we mean MGJ Development, CVR 31961742, Langstrengvej 13, 6100 Haderslev, Denmark, which operates NemDisplay. When we write "you" and "the developer", we mean the company that has a developer account with us.
"The platform" is the part of NemDisplay that lets developers build apps for NemDisplay screens: the developer account, the developer portal, the API, the SDK (nd-sdk.js, nd-tokens.css), the nd-app tool, the data proxy and the display of apps on the screens. An "app" is the package (manifest and files) you upload, with all its versions. "The data source" is the https address in the app's manifest that our server (the data proxy) calls to fetch the app's data. "The customer" is a NemDisplay customer who adds your app. An "installation" is one app added to one customer's account.
This agreement is an addendum to NemDisplay's terms and conditions, which also apply to the developer account. In the event of conflict, the data processing agreement with its addendum takes precedence, then this agreement, then the terms and finally the price list, as clause 10.1 of the terms states.
1. The developer account
1.1. You create the developer account yourself at nemdisplay.dk/udviklere/opret, in the same way as a business account: CVR number, contact person and an email address that you confirm with a link. At the same time you tell us what you have built before (for example links to products, customers or code), and which apps you expect to build, which data sources they use and who they are for.
1.2. We review the application and approve or reject the account. We aim to reply within 3 business days and may ask for more information. A rejection is briefly explained. Until the account is approved, you can log in and correct the application, but not create screens or apps.
1.3. A developer account can only be created by a company with an active CVR number. There can be one developer account per CVR number. The same user can also be a user on ordinary customer accounts. A developer account cannot be converted into a customer account.
1.4. The developer account is free. There is no subscription and no trial period that expires.
1.5. The account may only be used to develop, test and demonstrate apps – not to show content to others in daily operation. Screens on a developer account therefore always show the label "Developer account – not for production", which cannot be turned off.
1.6. The account can have at most 3 screens, unless we agree otherwise in writing.
1.7. All users on the account must log in with two-factor authentication, and this cannot be turned off. You keep API keys for the account safe and do not share them with others.
1.8. If the account has not been used for 180 days, we will write to the account's email address. If it is not used in the following 30 days either, we may pause it. It can be reopened by writing to us.
1.9. We show your company name and CVR number from the account and the support address from the manifest with your apps in the store and when a customer adds one of them.
2. Apps and review
2.1. An app only becomes visible to NemDisplay's customers when we have approved the version you submitted for review. Every new version must be approved, including fixes. Until then you can only use it on your own developer account.
2.2. We review each version according to the rules and the checklist on nemdisplay.dk/en/developers. We aim to reply within 3 business days, but do not promise it. A rejection is explained.
2.3. An approval only means that the app met the rules when we looked at it. It does not make NemDisplay responsible for the app's content or for the data the app shows. The store therefore says "Reviewed by NemDisplay", not "Approved".
2.4. You may not call your app "official", give the impression that it is made by NemDisplay, or use NemDisplay's name and logo in any way other than to say that the app works with NemDisplay.
2.5. Apps are free for customers until we offer paid apps. Paid apps require a separate addendum to this agreement.
2.6. The information in the manifest must be correct, in particular the developer's name, the support address, the data source's domains and the declaration about personal data in clause 5.3. The developer's name must be the company name the account was created with, or a name we have approved.
3. Rights
3.1. You keep all rights to your app. You grant us a non-exclusive, free, worldwide right to store, review, test, distribute and display the app to NemDisplay's customers and their screens for as long as the app is published, and during the phase-out period in clause 7.6.
3.2. Clause 2.5 of the terms (ideas and suggestions may be used freely) does not apply to your app's code or design.
3.3. You make sure that you have the rights to everything in the app, including fonts, images, icons and third-party code, and that the licences allow the app to be shown on NemDisplay screens.
3.4. NemDisplay, the platform, the SDK and the name belong to us. The SDK may be used freely in apps for NemDisplay.
4. Your obligations
4.1. The app must comply with Danish law and clause 2.2 of the terms. It must not contain malicious code, try to bypass the screen's security or sandbox, or collect information about the customer beyond what the app needs.
4.2. The app may only fetch data through the data source stated in its manifest, and only from the domains stated there. If you change which data the app fetches, or where from, this must be done in a new version that is approved.
4.3. The app must not show advertising for third parties unless we have agreed to it in writing.
4.4. You support your app towards the customers yourself. The support address in the manifest must work, and you must reply within 5 working days. Customers see the support address when they add the app.
4.5. If you discover a security flaw in your app, your data source or the platform, you write to support@nemdisplay.dk at once.
4.6. You run the data source yourself. It must only send the data the app shows, in the format the manifest describes. If you want to close the data source or change it so that the app stops working, you write to us and to the customers through the support address at least 30 days in advance, unless it is done for security reasons.
4.7. You indemnify us against claims that others, including customers and authorities, raise against us, to the extent that the claim is due to:
- the app's content, code or design, including if it infringes the rights of others,
- the data your data source delivers, for example wrong prices or allergens or unlawful content,
- your processing of information in the data source and your own systems, or
- your breach of this agreement or the law.
This does not apply to the extent that the claim is due to errors in the platform or the data proxy, to our having changed the app or its data, or to the customer's own content and settings. We will notify you of the claim without undue delay, let you take part in the case and not settle the claim without your consent.
5. Data and data protection
5.1. This is how data flows: the customer fills in the app's settings and keys in NemDisplay. Our server sends the settings and keys the manifest asks for to the data source, stores the latest response and sends the settings without keys and the response to the customer's screens. The app runs in a sandbox on the screen and cannot send anything out.
5.2. When we store the customer's settings and keys, fetch data from the data source, store the response and show it on the customer's screens, we do so as the customer's data processor under the data processing agreement and on the customer's instruction, which the customer gives by adding the app. You are not our sub-processor, and we are not yours. The data source is your own service. If it processes personal data for the customer, this is done under an agreement between you and the customer.
5.3. Until we state otherwise on the developer page, we only approve apps whose data source does not deliver personal data and whose settings do not ask the customer for personal data. You declare this in the manifest and make sure it is true for all responses from the data source. Names, email addresses, phone numbers, pictures of people and bookings with names are examples of personal data.
5.4. The app on the screen only receives its own settings without keys, the data source's latest response and its time, its language, its size and orientation, the account's colours and font and a pseudonymous id for the installation. It never receives the screen's name, the account's name or id, the users' information or login. The data source only receives the settings and keys stated in the manifest's address and headers, our server's IP address and the time. It does not receive the customer's name, account, screens or users.
5.5. Keys and other secrets that you or the customer store for the data source are kept encrypted by us and only used to fetch the app's data. They are never sent to the screens, to the customer's users or to you. You may only ask for keys in headers, not in the address, because addresses are often stored in logs.
5.6. You may only use the settings, keys and calls your data source receives from us to deliver the app's data and to operate and secure the data source. You may not sell them, use them for marketing or combine them to find out which customers use NemDisplay.
5.7. We store the customer's settings and keys and the data source's latest response for as long as the installation exists. We delete them when the customer removes the app, and at the latest when the customer's account is deleted under clause 5.2 of the terms. Errors from the data source are only stored as an error code. Our logs of calls to the API do not contain settings and keys.
5.8. We may keep statistics on how many screens use your app and on errors in it. The statistics never show which customers use it.
5.9. If the data source is located outside the EU/EEA, this must be stated in the manifest, and you are responsible for it being lawful.
6. The platform
6.1. The platform is provided as it is. We do not promise a particular uptime or that the platform is free of errors.
6.2. Changes to the SDK or the platform that make existing apps stop working are announced at least 60 days in advance on the developer page and to the account's email address, unless the change is necessary for security reasons.
6.3. We only support the platform, and only in writing.
6.4. We make sure that the data proxy only calls the domains stated in the manifest, that keys are stored encrypted, and that your app's code and your keys are only accessible to the employees at our company who review and operate apps. We fix errors in the platform and the data proxy as quickly as we can.
7. Emergency stop, rollback, unpublishing and termination
7.1. We may stop an app or a version on all screens immediately and without notice in the event of a security breach, unlawful content, malicious code, a data source that delivers wrong or harmful data, or a material breach of the agreement (emergency stop). In other cases we give 14 days' notice.
7.2. An emergency stop takes effect centrally at once. A screen that is online is notified at once and stops showing the app, normally within a minute, even in the middle of a slide. A screen that is offline keeps showing the latest programme it has received, including the app and its latest data, until it is online again (clause 6.2 of the terms). An emergency stop cannot reach a screen that is offline.
7.3. You can withdraw a version yourself in the developer portal, and we can do so in an emergency stop. The screens then get the latest previously approved version at the next programme update.
7.4. If there is no previously approved version, or it is not safe either, the screen skips the app and shows the rest of the playlist. If the playlist has nothing else to show, the screen shows the account's fallback content or the NemDisplay logo. The customer is notified in NemDisplay and by email.
7.5. If you want to unpublish an app, you do so in the developer portal. The app then disappears from the store at once, so that no new customers can add it.
7.6. If you unpublish an app, or the agreement ends, customers who already use the app are notified and can use it for 30 days (the phase-out period). During the phase-out period you keep the data source running and answer support under clause 4.4. After the period the screens stop showing the app. If we stop the app under clause 7.1, there is no phase-out period. If the data source stops responding anyway, the screen shows the last fetched data until it is older than the limit the manifest sets (24 hours by default). After that the screen skips the app, and we may stop the app early.
7.7. Either party may terminate the agreement without notice. The developer account is then closed under clause 5.2 of the terms, except that your published apps are phased out under clause 7.6. When the phase-out period is over, we delete the app's packages and your keys.
8. Liability
8.1. Clause 9 of the terms applies to the developer account. As the account is free, our total liability towards you is DKK 1,000 (the minimum amount in clause 9.2). The limitation does not apply in the case of intent or gross negligence (clause 9.5).
8.2. We are not liable for what your app shows, including if it shows wrong information, for example prices or allergens.
8.3. Our liability towards customers for errors in the platform and the data proxy follows the customer's terms. We will not make claims against you for losses caused by errors in the platform or the data proxy, for example that the proxy has passed on wrong data or shown one installation's data to another customer.
8.4. The cap in clause 8.1 only limits our liability. It does not limit your indemnity in clause 4.7, and clause 4.7 does not apply to losses we are responsible for ourselves under clause 8.3.
9. Other provisions
9.1. We may change the agreement with 30 days' notice to the account's email address. You may terminate before the change takes effect.
9.2. The agreement is governed by Danish law. Disputes that we cannot resolve together are settled by the District Court of Sønderborg (Retten i Sønderborg).
9.3. Questions about the agreement are sent to support@nemdisplay.dk.