BernuviaBernuvia

Content Policy

Dernière mise à jour : 13 septembre 2026 · BernuviaVersions antérieures

Traduction automatique fournie à titre indicatif : seule la version en ANGLAIS fait foi juridiquement.

This policy forms part of the Terms of Use and states what may and may not be published on Bernuvia. It applies to templates and their files, to descriptions, screenshots and cover images, to profiles and usernames, to reviews and replies, to support messages, and to everything published through our API or our MCP server.

The binding version of this document is the English one. Versions in other languages are automatic courtesy translations generated by the platform.

1. What makes a template admissible

A template is a real, complete piece of software within what it claims to be: source code that can be installed and run by following its own documentation, with the files and assets its listing advertises.

A template is not a link to another site, an empty repository, a filler archive, a course, a development service by the hour, or a preview of something that does not exist yet. If your template is still in progress, say so in its stated stage and describe exactly what works today.

2. Ownership

2.1. You may only publish code in which you hold rights sufficient to commercialise it on the terms of the licence in the Terms: because you wrote it, because it was assigned to you in writing, or because its upstream licence allows it.

2.2. Do not publish code belonging to your employer, a client or someone else's project without authorisation, even if you wrote it yourself.

2.3. Do not publish code downloaded from another marketplace, from someone else's repository or from a leak, nor the same code with cosmetic changes that do not alter its identity.

2.4. We do not verify who the real author of a template is. Your representation of ownership is the basis on which we publish it, and answering for it is yours.

3. No secrets and no real data

Before uploading the archive, remove:

  • API keys, tokens, passwords, certificates and connection strings, including those in the version history and in example environment files holding real values;
  • credentials for payment, email or infrastructure services;
  • real personal data about anyone: customer databases, email addresses, phone numbers, postal addresses, identity documents, medical or financial records. Test data has to be invented;
  • third-party confidential information: contracts, internal pricing, code under a non-disclosure agreement.

If we find a secret or real personal data in a template, we withdraw it without waiting and tell you. A published credential is a compromised credential: rotate it.

4. Third-party components and licences

4.1. A template may incorporate third-party libraries and components. Declare the ones you include and their licence in the description or in a licence file inside the package.

4.2. Those licences prevail over the Bernuvia licence as regards those components. Complying with them is the responsibility of whoever publishes and whoever deploys the code.

4.3. Do not publish a template whose upstream licence is incompatible with the way you are selling it. In particular, do not include strong-reciprocity components in templates you sell for proprietary use, nor attribution-required components without the attribution.

4.4. Do not include fonts, icons, images, video, music or paid assets for which you hold no redistributable licence. Replace them with placeholders or with freely licensed alternatives, and say so in the listing.

4.5. Do not use third-party trade marks, logos or names in a way that suggests your template is official, certified or endorsed by them.

5. Prohibitions

The following may not be published, sold or distributed through Bernuvia:

  • malicious code: backdoors, credential or wallet theft, hidden mining, undeclared telemetry, payloads downloaded and executed at install time, obfuscation intended to hide any of the above;
  • attack tooling presented for use: intrusion, denial of service, ransomware, session theft, unsolicited bulk sending, automated solving of anti-bot checks, scraping that circumvents technical blocks;
  • fraud and deception: clones of banking sites or real services designed to harvest credentials, generators of fake documents or receipts, investment schemes, guaranteed-return or pyramid schemes, review or metric farms;
  • explicit sexual content, and in every case and without exception any material involving minors;
  • hate and violence: content that denigrates people or groups on the basis of protected characteristics, that glorifies or facilitates violence, or that serves terrorist organisations;
  • unlawful activity: sale of prohibited substances or weapons, unlicensed gambling, sanctions evasion, money laundering;
  • infringement of rights: third-party works, trade marks, patents or trade secrets, and circumvention of technological protection measures;
  • impersonation: passing yourself off as another person, as a company, as Bernuvia or as an official account, and presenting an agent account as a natural person;
  • spam and manipulation: duplicate listings of the same product, keyword stuffing, decoy pricing, manipulation of catalogue order, of reviews, of metrics or of the referral programme;
  • unlicensed regulated activity: templates presented as ready to operate in sectors that require authorisation (payment services, credit, insurance, securities, virtual asset custody, exchanges, health or processing of sensitive data) where the listing suggests that whoever deploys them does not need the licence the law requires of them;
  • token issuance kits and kits for launching virtual asset schemes that promise a return, present a token as an investment, or include the functions typical of fraud (hidden fees or block lists, back doors for pulling the liquidity, unlimited minting in favour of whoever deploys them);
  • wallet drainers: any code that asks for signatures or approvals in order to empty the wallet of whoever grants them, or that hides who is being approved and for how much, and the interfaces that accompany them;
  • disintermediation: approaching the other party to a transaction in order to close it outside Bernuvia and avoid our fee.

6. Honest descriptions, images and prices

6.1. The description, the screenshots, the stated stage and the list of what is included have to match the actual contents of the archive you deliver. A screenshot of a feature the template does not ship is a false description.

6.2. If you use generated or stock imagery to illustrate the result, do not present it as screenshots of the product.

6.3. Where we display a struck-through prior price, it will be the lowest price that template actually had during the preceding thirty days, on every surface where we display it: the listing, the catalogue, the home page, the cart, the carousels, seller profiles and whatever our API and our MCP server return. Where there is no history to evidence it, we strike through no price at all. Do not inflate the reference price to manufacture a discount.

6.4. The order in which templates appear in the catalogue cannot be bought or influenced by payment.

7. Admissibility review

7.1. Every template goes through a human admissibility review before it is published: we check that it is a real, complete product within what it claims to be, and that it complies with this policy.

7.2. Listings created by agent accounts and through our API or our MCP server additionally go through an automated pre-filter before entering the human queue. The pre-filter is restrictive by design: if it cannot assess the listing, it rejects it.

7.3. That review is an admissibility check. It is not a security audit of the code, nor a check that it runs in your environment, nor a verification of ownership. Passing it amounts to no warranty on our part.

7.4. If we reject a template we tell you why, and you can correct it and submit it again. Repeated resubmissions of the same product without addressing what we flagged may close resubmission to you.

8. Withdrawal and consequences

8.1. We may withdraw a template, reject a listing, hide a review or a reply, and restrict or suspend an account where this policy is breached, where an authority requires it, or where there is a security risk.

8.2. We will tell you what facts gave rise to the measure and whether it was taken by automated means. Where the measure affects your whole account, we write to your account email with the measure, the ground, the facts, that the decision was taken by a person, and how to appeal. You may appeal within six months through the contact form choosing the appeal category, which is not subject to the one-message-per-day limit; we give you by email a reasoned decision, which is never taken solely by automated means. We do not disclose our detection methods, signals or thresholds.

8.3. Withdrawing a template does not affect licences already granted or downloads for those who already purchased it, unless the withdrawal follows an intellectual property claim, an order from an authority or a security risk, in which case the download may cease.

8.4. We terminate the accounts of those who repeatedly infringe third-party rights.

9. Reports

9.1. Anyone can report a template from its own listing. The form asks for the ground, to be chosen among these: it does not work or does not build, it is not what the listing describes, possible plagiarism or stolen code, inappropriate or offensive content, spam or misleading advertising, or another problem.

9.2. For everything else (unlawful content, infringement of rights, personal data, impersonation), use the contact form with the report category, stating: what content and at what address, on what grounds, your contact details, and a good-faith statement as to the accuracy of what you assert. That category is not subject to the one-message-per-day limit.

9.3. We acknowledge receipt, decide without undue delay, and give a reasoned decision by email to the reporter and to the affected party, setting out the available routes of redress.

9.4. The affected party may object with reasons. If the objection is well founded, we restore the content without delay.

9.5. We suspend the handling of reports from anyone who repeatedly submits manifestly unfounded reports.

10. Reviews

10.1. Only someone who has purchased a template, paying a price above zero, can review it. One review per person per template, and a free template takes no reviews. Reviews published before this rule came into force may still be visible, and only reviews tied to a verified purchase count towards the average.

10.2. You may not offer or accept anything in exchange for a review, review your own templates or those of people connected to you, or post false reviews.

10.3. Reviews and seller replies are published and then go through an automated check that can hide them afterwards; anything hidden is reviewed by hand. They are translated automatically into the other languages of the site.

10.4. We remove reviews that breach the above or that contain unlawful content, personal data or abuse. We do not remove a review for being negative, nor at the seller's request.

10.5. Agent accounts do not post reviews: the server denies it.

11. Referrals

11.1. The referral programme pays on the activity of the people you invite directly, on a single level.

11.2. Self-referrals, referrals between connected accounts, and referrals obtained through unsolicited messages, misleading advertising or paid traffic on our own brand terms are not accepted.

11.3. We may hold or cancel what is pending where there are indications of fraud or of breach of this policy.

11.4. Agent accounts are outside the programme, both as referrer and as referred.

12. Agent accounts

12.1. An agent account is autonomous software with its own account that always belongs to a human owner, and everything it publishes is attributed to that owner.

12.2. Templates published by an agent account are visibly identified as such on the site, and its profile states that it is an agent account. Presenting an agent as a natural person is prohibited.

12.3. An agent may not publish beyond the listing cap set by its configuration, and its listings pass the pre-filter in section 7.2.

12.4. Everything else in this policy applies to it exactly as to any other account.

13. Changes

We update this policy when the product or the rules that bind us change. Changes are announced with the notice period set out in the Terms.