Terms for submitting modules

When you submit a module for publication in Nubilux, the terms below apply. They apply between you and Visbiz AS, which provides Nubilux, in addition to the terms of use. “We” and “us” mean Visbiz AS.

You accept these terms by ticking the box when you submit. Which version you accepted, and when, is stored with the submission. If there is something you disagree with, you can still use the module privately in your own household.

What you give up

When the module is published, you transfer ownership of the module to Visbiz AS. This covers the code, the design, and the right to modify, develop, distribute and sell the module as part of Nubilux. The transfer is not time-limited, and it applies without us having to ask you about each individual change.

Ownership passes only on publication. A submission that is rejected, or that you withdraw, remains yours.

What you keep

You keep your own copy of the module, and you have the right to go on using and modifying it privately in your own household. You may not sell it or publish the same module elsewhere, because it is no longer yours. Modules you do not submit remain yours alone. You may at any time create new modules based on what you have learned.

Attribution

You are credited in the module catalogue for as long as the module is published. When you submit, you choose the name shown there: your full name, another name, or no name.

If we change the module substantially, we make sure you are not listed as the author of something you did not make. We may then mark the module as changed by us, or remove your name.

If you delete your account, your name is removed from the catalogue. Published modules remain, because they are no longer yours.

We may change or remove the module

We may fix, change, develop or remove a published module without obtaining your consent. This includes immediate deactivation if the module turns out to be unsafe or harmful.

You cannot withdraw a published module yourself, but you may ask us to consider removing it, and we will respond to the request.

Updating a published module

If you want to fix a bug or develop your module further, you submit it again and mark the submission as an update to the existing module. An update goes through the same review as a new module, and the same terms apply to it.

You are not obliged to maintain the module. If you choose to leave it be, we look after it from there.

What you get

You are credited in the module catalogue. In addition, we run a reward scheme that can give you a free Premium subscription for a period.

The scheme requires more than getting a module published: the module must be in use by other households and must have stayed published for a while. The current requirements, and how long a period they earn, are shown in Studio when you submit a module. We may adjust the requirements, but a period you have already earned runs its course — an adjustment applies going forward.

Other forms of reward may come later, but are not promised here.

If you drop down from Premium

If you move from Premium to Standard — because you cancel, or because an earned period runs out — you lose access to the modules that require Premium. Your data stays on your account. Settings, layout and content are left untouched, and everything is there again if you get Premium back later.

Your responsibility for the content

You are responsible for having the right to submit what you submit. The module must not contain code, text, images or data you are not allowed to share, and it must not be built to harm, track or deceive users.

If we receive a complaint about copyright or abuse, we take the module down first and assess the matter afterwards.

Modules built with AI

Code generated with artificial intelligence is treated exactly like code you wrote yourself. You are considered the submitter, and ownership passes to Visbiz AS on publication. You carry the same responsibility for the content, regardless of how it came about.

Data and privacy

A published module runs in other families' homes. It must therefore not collect or transmit personal data beyond what it needs to function, and it must request access to data in advance. We may reject or remove a module that does not meet this.

What other households see about the module in the catalogue is the name and description you wrote, the name you chose for attribution, and what the module asks for access to.

What happens after submission

The version you submitted is the one that is reviewed and published. It is locked on submission, so changes you make afterwards must be submitted as an update.

The module is reviewed before it is published. The criteria we assess against are the same for everyone, and they are written down. We may reject a module without giving a detailed justification, but you will always be told the main reason. You see the decision in Studio.

As long as the submission has not been decided, you can withdraw it. A submission that is rejected or withdrawn is not published, and it is deleted when your account is deleted.

Changes to these terms

We may change these terms. Changes apply to modules submitted after the change is published. The terms you accepted at submission apply to that submission.