cracktro

Vloop Package License, version 1

1. Scope

This license applies to the packages, skill packs and skins (packages) that you get from the Vloop Store, worldwide. The publisher of each package grants it to you. The store operator is not the licensor of another publisher's package. This license does not replace the store's separate service terms.

You are the person or the organization, such as a company, that gets a package. A publisher, too, is a person or an organization.

You accept each version of this license once, for all packages that you get or publish under that version. As a publisher, you offer those packages under this license and the options you choose. If you act for an organization, you confirm that you may bind it. Acceptance for an organization does not cover your personal rights.

Buying a personal right for another person, including a gift, does not accept this license on their behalf. The recipient accepts it through their own account before their first download under that version, unless they have already accepted it. That acceptance covers all packages they already have and later obtain under that version, on all their devices.

An automated user is a program, such as a build server, with its own store account. A person authorized to operate that account may sign in to it and accept through it.

2. Package terms

The publisher picks one option of section 4 for each major version of a package (for example, all 1.x releases). The store writes the package terms from that option.

When you get a release yourself, you accept the terms shown when you confirm it. If someone obtains it for you, the terms recorded for that acquisition apply when you accept this license. They stay with that release: a payment that completes later, a later download or a later change of the terms takes nothing from you.

If the publisher changes the terms later:

• When the change only gives you more, it applies to the releases that you already have, and you do not need to accept anything. If a new permission has conditions, they apply only when you use that permission.
• When the change takes away anything that you have, it does not apply to the releases that you already have. It applies only to an update that you accept. If you do not accept, you keep your releases and their permissions, but you do not get the updates that come with those terms.

Example: you get release 1.0 under "Personal forks only". The publisher then picks "Paid redistribution". From then on you may sell forks of 1.0 under the payment rule of section 4, and you do not accept anything. Later the publisher picks "Personal forks only" again and publishes 1.1. You can still sell forks of 1.0. To get 1.1, you accept its terms; if you do not, you keep 1.0.

3. Use

Each right to a package covers one user: a person, or an automated user such as a build server, with a store account of its own. Every user of a package needs their own right. With it, they may install, use and change their copy for their work in any project, and keep personal forks of it. A fork is a copy of a package or of a substantial part of it, changed or not.

An organization holds the rights that it gets for its employees, contractors and automated users. They use those rights under the organization's acceptance and do not accept this license separately. The organization is responsible for their compliance with this license and the package terms. It may move a right from one user to another; the first user then stops using the package under that right. Apart from that, nobody may sell or give away a right, except where applicable law allows a transfer despite this restriction, including exhaustion of rights in a software copy. Such a transfer must meet that law's conditions, including stopping use and making retained copies unusable where required. A package that someone gets for you as a gift is your own right from the start, subject to your acceptance under section 1.

Sharing a fork with users who each hold a right to its package, for example in a project that colleagues share, is not redistribution.

What you make with a package, such as code, text or designs, is not covered by this license: the publisher claims no rights in it, and you may use it for any purpose, commercial work and work for clients included. Output that reproduces the package or a substantial part of it is a fork, though, and follows section 4.

4. Publisher options

The publisher chooses one of these options for redistribution:

1. Personal forks only: you must not redistribute the package or forks of it.

2. Free redistribution: you may redistribute forks free of charge.

3. Paid redistribution: you may sell forks under one of these payment rules. The package terms name the rule and its values, which the publisher sets in advance. The surplus is the price of your fork minus the price of the package's major version; it is below zero when your fork costs less.

   • Source amount plus surplus: you choose the surplus, at or above the minimum surplus that the publisher sets, if any. From each sale, the publisher gets the price of the package and you get the surplus.
   • Percentage share: the surplus is at least the minimum surplus that the publisher sets. A minimum below zero lets your fork cost less than the package. From each sale, the publisher gets the percentage that it sets and you get the rest.

   The store's normal commission applies to each part. If the publisher changes the package price, the store changes the price of your fork with it, so you keep your surplus, but never below the store's lowest paid price. You must not redistribute forks free of charge.

4. Free or paid redistribution: you may redistribute forks free of charge or for a price. When you sell a fork, you kick back what you wish: you choose the share of each sale that goes to the publisher, from nothing up. The publisher may decline it; then you keep it.

Where an option allows redistribution, it allows it only through the Vloop Store. The publisher may allow other ways separately from this license. When you redistribute a fork, keep the notices and the attribution of the package that it comes from. Whoever gets a fork redistributed under these options needs no separate right to the packages that it copies from, but gets the packages that it requires to run separately.

5. Third-party parts

A package can contain parts from third parties, for example code under the MIT, Apache-2.0 or BSD licenses. These parts keep their own licenses and notices. This license and the package terms do not replace them. Keep their notices when you redistribute a package or a fork.

6. No warranty, limited liability

Packages are supplied "as is" and "as available", without warranties of any kind, including warranties of merchantability, quality, accuracy, fitness for a purpose and non-infringement. Packages that work with AI models give results that vary from run to run and can be wrong, incomplete or unsafe; check those results before you rely on them. This license promises no support, maintenance, new releases, reviews or audits.

This section protects the publisher, the package's authors and contributors, the store operator and people acting for them (the protected parties); each of them may rely on it.

Except for loss that they cause intentionally, the protected parties are not liable for any loss or damage from a package or its use, on any legal ground, including indirect or consequential loss and lost profit, data or work. Where the law does not allow that exclusion, their liability is limited in total to the amount paid to obtain the affected package. Each exclusion and limit in this section applies as far as the law that applies under section 8 allows; where one goes further, it applies to the extent that law allows, and the rest of this section and of this license stays in force.

Where the law of a country of the European Union or the European Economic Area, of Switzerland or of the United Kingdom applies, or you get a package as a consumer in one of these countries, the following replaces the previous paragraph. For intent and gross negligence, for injury to life, body or health, under product liability law and under a guarantee, the protected parties are liable as the law provides. For ordinary negligence, they are liable only for breaching an obligation that is essential to the contract, one needed to perform it and on which you can normally rely, and only for loss that was foreseeable and typical when the contract was made. Otherwise, their liability for ordinary negligence is excluded.

Rights that the law does not allow to be excluded or limited, such as mandatory consumer rights, are not affected.

7. End of the license

If you break this license or the package terms of a package and do not put it right within 30 days after the publisher or the store tells you, your rights to that package end. Your rights to other packages stay.

8. Courts, law and language

A dispute about this license goes to the courts of the country where the party that is sued lives or has its seat, and the law of that country decides it. A counterclaim may go to the same court. If you get a package as a consumer, outside your trade or profession, this takes away none of the protection that the law of your own country gives you, including any right to bring a claim in your own country's courts.

This license is written in English. A translation helps you read it; the English text prevails.