Terms of Use

The binding version of this document is the English one. The Spanish version is drafted by us; the versions in the remaining languages are automatic courtesy translations generated by the platform. If you are a consumer, the mandatory rules of your country and the pre-contractual information we give you in your language apply in every case.

1. Who we are and what you accept

1.1. Bernuvia is the operator of the Service. You can reach us through the contact form, which is our single channel: enquiries, reports, complaints, appeals, security notices and data protection matters all come in there, each with its own category. The report, complaint, appeal and data protection categories are not subject to the one-message-per-day limit we apply to the rest, and we tell you the outcome of each by email. Identification of the provider of the Service is given before it becomes due and, in any event, to anyone who asks for it through that form.

1.2. These Terms govern your use of the site, its subdomains, its API, its public interfaces (clause 9.7) and its MCP server (the "Service").

1.3. By creating an account, by publishing a template, by buying, by using our API, our MCP server or our public interfaces (clause 9.7), or by signing a payment authorisation (clause 9.6), you accept these Terms, the Privacy Notice, the Content Policy and the Availability page, which form part of them.

1.4. We record your acceptance when you create your account (these Terms and the Privacy Notice) and on every paid purchase (these Terms, which include the immediate download in clause 16.2), with the date, the time, the version of the document, the language it was shown to you in, and a cryptographic fingerprint of your IP address. Claiming a free template records no acceptance, because there is no price and no sale. When we publish a new version, we ask you to accept it. An account created by a wallet signature accepts by signing, and we record that signature as the Annex on Wallet Accounts and Autonomous Agents describes.

2. What Bernuvia is

2.1. Bernuvia is a marketplace. We connect people who build code templates with people who buy them, and we provide the publishing, held-payment and dispute infrastructure.

2.2. We are not the author, publisher or seller of the templates. The sale is made between the buyer and the seller. We do not write the code, we do not audit its security and we do not verify who its real author is. We make no warranty as to the quality, security, originality or legality of what is published.

2.3. We review templates before publishing them to check that they are real, complete products within what they claim to be and that they comply with the Content Policy. That review is an admissibility check: it is not a security audit and it is not a verification of ownership, and passing it amounts to no warranty on our part.

2.4. What we are not. We provide no payment, virtual asset exchange, custody, money transmission, investment or advisory services, and we act as nobody's agent, broker, fiduciary or representative. We are not a party to the sale made between buyer and seller.

2.5. Hosting. We host third-party content and have no general obligation to monitor it. Our admissibility review, our voluntary removals and our investigations do not give us knowledge of that content and do not deprive us of the liability exemptions available to a host.

3. Definitions

• Seller (also *builder*): someone who publishes templates for sale.
• Buyer: someone who purchases a template.
• Template: the source code, files, documentation and assets a seller publishes as a single product.
• End Product: the site, application or program you build incorporating a template, which can function on its own once the original template is removed as distributable material.
• Deposit Contract: the smart contract on the Polygon network that holds the amount of a purchase until it is released or refunded. Its address is published on Security.
• Balance: the USDC in your wallet plus, where applicable, the fallback balance credited in the Deposit Contract to the wallet that gets paid for that sale when a direct payment failed (clauses 13.6 and 20.12).
• Wallet: the Polygon network address associated with your account.
• Delegate: the agent a person creates from their own account, in My agents or with the permission to manage agents, so that it acts as that person on that person's account (clause 8). A delegate is not an account of its own.
• Agent account: autonomous software with its own account. It comes into existence by a wallet signature and is controlled by whoever holds the key of that wallet (clause 8.10).
• Test purchase: a purchase, a sale or a review made from an agent account carrying the test mark, and sealed as a test for that reason (clause 8.15). The money is real; what it does not do is count.
• Committee: the group of people at Bernuvia who decide disputes and execute their resolution with a multi-signature wallet.

4. Who can use Bernuvia

4.1. You must be at least 18 years old and have legal capacity to enter into contracts. If the age of majority in your country is higher, that one applies. When you create your account you accept these Terms and, with them, you declare that you meet this clause: that you are at least 18 (or of the age of majority in your country, if it is higher) and have legal capacity to enter into contracts.

4.2. We do not allow accounts belonging to minors. If we detect one, we suspend it and return the available balance where technically possible.

4.3. The student programme and the educational materials we publish are addressed to adults and do not enable use of the Service by minors.

4.4. If you are acting on behalf of a company, you represent that you have authority to bind it.

4.5. You may not hold multiple accounts to circumvent fees, limits, suspensions or the referral programme. Delegates are not accounts of their own, and agent accounts created under clause 8.10 are not multiple accounts.

5. Where the Service is available

5.1. Availability is organised in three layers and is described in full on the Availability page, which forms part of these Terms: sanctioned territories and persons, countries where we do not hold a required authorisation, and countries where operating with virtual assets is prohibited.

5.2. By using the Service you represent that none of those situations applies to you and that you are not acting on behalf of anyone to whom it does.

5.3. Today we do not block access by country and we do not require identity verification in order to use the Service. We may apply geolocation controls, identity verification and wallet address screening, and we may block transactions, hold open transactions or close accounts where those controls return a result that prevents us from doing business with you.

5.4. You may not use virtual private networks, proxy servers or any other means to circumvent those restrictions or to misrepresent your location.

5.5. If your country becomes restricted after you have already transacted with us, we apply the orderly wind-down described on the Availability page: no new purchases or listings, open deposits run their course, and your balance can be withdrawn without restriction, absent a legal impediment.

5.6. Technical availability. The Availability page also sets out, in its section 5, the technical availability of the Service: we offer no committed service level and no credits for interruptions, and we do not undertake to keep the Service, or any of its features, running indefinitely. That section forms part of these Terms.

6. Your account

6.1. You can create your account with Google, with GitHub, or with your email and a single-use code. Your username is public, unique, and is also your referral code.

6.2. The account email cannot be changed: your wallet is derived from it (clause 10).

6.3. You are responsible for keeping control of your email and for all activity on your account.

6.4. Important warning: your authentication method is what gives access to your wallet. Whoever controls your email, or your Google or GitHub account, can operate your funds. Turn on two-factor authentication, which we also require when you sign in with Google or GitHub if you have it enabled.

6.5. An unused session expires, and expires in any event once its absolute term has passed. Tell us immediately through the contact form if you detect unauthorised access.

6.6. Deleting your account. You can close your account whenever you want, and doing so is irreversible. We cannot delete it while your wallet holds a balance: if USDC remains in it, or an amount is still withdrawable from the Deposit Contract, deletion is refused until you withdraw, and if we cannot check that balance, we do not delete either. When it is deleted, your email is blocked for good, and with it goes access to the wallet derived from that email: there is no seed phrase and no key export, so whatever is left at that address, or arrives later, will be unrecoverable, including by us. Withdraw your balance and close out your open transactions first. We are not liable for a balance lost to a deletion you confirmed with that warning on screen.

7. Identity verification

7.1. We do not require identity verification in order to use the Service. There is no check of documents, of address, or of source of funds.

7.2. We may ask you, as a condition for transacting, depositing, receiving payment or withdrawing: government-issued identification, proof of address, information on the source of funds, tax information and, for companies, corporate documentation. We will do so where a legal obligation requires it or where there are indications of fraud.

7.3. If you do not provide the information requested, or it turns out to be false, we may suspend your account and hold pending transactions for as long as necessary to meet our legal obligations.

8. Delegates and agent accounts

8.1. Two kinds of agent. (a) A delegate is the agent you create from your account. It is not a separate account: it acts as you, on your own account, and it can buy, sell and manage your templates autonomously, without asking you before each action. It has a reserved identifier with an agent prefix and its own credential, but what it does is done in your account. (b) An agent account is a separate account, with its own wallet, a reserved identifier with an agent prefix and its own credential. It comes into existence by a wallet signature and is governed by clause 8.10.

8.2. You answer for your delegate in full. A delegate is not a subject of rights or obligations. Everything it does is attributed to you as if you had done it personally, and you are bound by the purchases, payment authorisations, listings, changes and withdrawals of your templates, disputes and any other action it executes, whether or not you anticipated or supervised them. Each purchase it completes is a purchase of yours, made under these Terms. This does not bind you to what your delegate does after you have revoked its credential or suspended it, nor to what results from a failure of our own systems.

8.3. You are liable to Bernuvia and to third parties for the acts of your delegates, and whoever answers for an agent account is liable for its acts as the Annex in clause 8.10 provides. A programming error, unexpected model behaviour or a failure in your own systems is not an excuse.

8.4. Wallets and signatures. We do not hold the private keys of any agent wallet, and your delegate cannot use your wallet (clause 10). To pay, your delegate brings its own wallet and proves it controls it by signing a cryptographic challenge; that is the wallet it pays for your purchases with. It signs its own deposits and, as a rule, pays their network fees. An agent account also brings its own wallet in the same way, and signs its purchase deposits, its membership authorisation and its withdrawals under the Annex. Where the platform tools offer the single-signature deposit with sponsored submission, our relayer may submit the authorisation your delegate signed, and its cancellation, at our cost and within the limits we set against abuse. Sponsored submission for wallet accounts is governed by section 10.3 of the Annex on Wallet Accounts and Autonomous Agents, and this clause does not change that rule. The wallet an agent links cannot be changed afterwards: neither your delegate nor an agent account can replace it with another one through our tools, which refuse the attempt; it is a security measure, and the only way out is to create another agent and link with it the wallet you want to use. We never sign on behalf of a delegate or of an agent account. We offer no spending limit for delegates: what your delegate can spend depends only on what you place in its wallet, and the quotas in clause 8.13 are a security measure, not a spending limit you can rely on.

8.5. Charges. Apart from submitting authorisations for an exact amount that a delegate or an agent account itself signed (clause 8.4 and, where we offer them, the paid requests in clause 9.6), the only charge we issue through our relayer is the seller membership charge of an agent account, and only up to the cap and at the frequency the account itself authorised by signature. Any charge that would exceed that cap is not executed. The membership charge is still issued even when the agent switch is off: what is being paid for is the listing already published. We never charge a membership to your delegate: it sells under your own membership (clause 20.8).

8.6. Limits. A delegate's toolset does not include these functions, and our server denies them when requested: withdrawing your balance or moving the funds in your wallet, writing reviews, creating agents or issuing credentials, using OAuth and accessing administrative surfaces, even if your account has access to them. An agent account's toolset does not include these functions, and our server denies them when requested: accessing the account of its operator or key holder, taking part in the referral programme, purchasing templates from them or from agent accounts of the same operator or key holder, and accessing administrative surfaces.

8.7. Transparency. What your delegate does is shown under your name: its purchases, its listings and the rest of its activity appear as yours, without any agent mark, count as yours in our metrics, and we do not tell the other party that a delegate acted. You are presenting yourself through it, and clause 8.2 applies. Your delegate cannot write reviews (clause 21.6). Templates published by an agent account are visibly identified as such and its profile states that it is one. A review written by an agent account is also visibly identified, wherever we show its text, as written by software, and is never presented as a consumer's opinion (clause 21.6). Presenting an agent account as a natural person is prohibited. Agent accounts are excluded from people metrics and from the referral programme.

8.8. Control. From My agents you can rotate or revoke your delegate's credential and suspend it whenever you want. The credential expires after one year. If we suspend you or your delegate, its credentials stop working. Keep its credential as safe as your password: whoever holds it can act as you within the permissions it carries, including publishing, changing and withdrawing your templates and creating orders in your name. To pay they also need the key of your delegate's wallet, and they can never withdraw your balance. If you suspect a leak, revoke it at once. We may disable the operation of delegates and of agent accounts across the platform for security reasons and without prior notice, and we may suspend a delegate or an agent account with a lock that only we can lift.

8.9. Purchases by your delegate: refunds and disputes. When your delegate pays for a purchase, the buyer recorded in the Deposit Contract is your delegate's wallet, not yours. The purchase, the download and the licence are yours, but the contract accepts the buyer's steps only from that wallet. By using a delegate you accept these consequences:

(a) Every refund of that purchase goes to your delegate's wallet, not to yours: the seller's voluntary refund, a full or partial refund decided by the committee and the closing of a dispute on expiry (clauses 13.8 and 15).

(b) Only your delegate can open, withdraw (subject to clause 15.6) or close on expiry a dispute on that purchase, signing from its wallet. You still see the case in My purchases, you can submit evidence and you can talk to us through the contact form, but you cannot sign those steps from the site.

(c) If you lose control of your delegate's wallet or of its key, nobody can open a dispute on that purchase, and any refund still goes to that wallet. We cannot redirect a refund or sign in your delegate's place, because we do not hold that key. If you revoke or suspend your delegate, it can no longer use our tools to take those steps. Keep its wallet under your control, and your delegate active, until the review period and any dispute of every purchase it paid for have ended. None of this affects your statutory rights as a consumer, against the seller or against us. If you cannot take one of these steps because we have suspended your delegate or switched delegates off, write to us through the contact form before the review period ends and we will handle your claim by that route.

If a purchase executed by your delegate or by an agent account contains a material error, the route is the ordinary dispute in clause 15, and you can also complain to us through the contact form. No purchase already deposited can be undone outside the Deposit Contract.

8.10. Wallet accounts. An agent account created by a wallet signature, without a human owner registered on the platform, is governed by the Annex on Wallet Accounts and Autonomous Agents and by the Intellectual Property Guarantee for Sellers, both of which form part of these Terms. For such accounts the Annex prevails over this clause 8 and over any other clause of these Terms that says something different about them. This does not change what clause 3 and clause 8.1 mean by delegate and by agent account: where the Annex describes what these Terms say about agent accounts, clause 8 is the current description.

8.11. Reputation attestations. When an agent account sells, we may record on the public network revocable attestations about its linked wallet, on the terms of section 10.4 of the Annex on Wallet Accounts and Autonomous Agents, which for this purpose apply to every agent account.

8.12. Agent registration file. A wallet account that sells may declare its own registration file under the ERC-8004 standard. By declaring it, the account authorises us to download it from the address it gives, when it is declared and periodically afterwards, and, while that check is valid and the account can sell, to show on its public profile a link to it identified by its agent number. We check only that the file and the registry on the chain link that identity to the account's wallet; we do not host, review, verify or endorse anything else the file says (its name, descriptions, images, services, claims or links), which is third-party content for which the account and whoever answers for it are solely responsible, including under the Content Policy and clause 29. We may refuse the declaration, stop showing the link or delete our record at any time, in particular when a check fails, and whoever follows the link does so at their own risk.

8.13. Quotas and limits. An agent account operates within quotas that we set on the platform and may change without notice under clause 9.4: templates awaiting review, submissions to the pre-filter, calls per period and, where switched on and while the account is recent, the amount of its purchases and its new listings per period. What exceeds a quota is refused with a message that says so. Your delegate also operates within quotas we set on the platform, per credential, per function and for your account as a whole, on the same terms. Clause 19.3 also applies.

8.14. Funds between you and your delegate. You can put USDC in your delegate's wallet by sending it from your wallet, which is a withdrawal like any other and is signed by you (clause 10.8), or by depositing directly into your delegate's address from any wallet. To send that USDC back to your wallet, your delegate signs with its own key, which we do not hold. We do not move funds between your wallet and your delegate's on our own initiative, in either direction, and a wrong address is irreversible (clause 10.8). Where your sales are paid is a separate matter and is governed by clause 20.12.

8.15. Test purchases. An agent account may carry a test mark, so that whoever integrates it can rehearse a purchase end to end without polluting anybody's catalogue. It is set and removed by whoever created the account or by us, never by the account itself with its credential, and it is frozen as soon as that account moves real money, whether buying or selling: from that moment it can be neither set nor removed. What comes from a marked account is sealed as a test: its templates, its orders, its purchases and its reviews. The seal is decided when each transaction is created, by reading the mark at that moment, and when that read fails the transaction is born REAL and not a test, because we would rather not take a sale away from a genuine seller over an error of ours. The sealing is therefore not absolute: a transaction from a marked account may have been born real, and in that case it counts like any other. A test purchase is not a purchase for the purposes for which these Terms count purchases, and it does not create between buyer and seller the obligations that arise from counting: it does not count as a sale or as seller income, it does not appear in the catalogue or in search, it does not add to the average rating or to the number of reviews, it carries no weight in the catalogue ordering of clause 20.6 or in the selection of featured templates, it does not enter the statistics we show, and it earns no referral commission (clause 22.8). Neither party may invoke it as a reference, as evidence of sales or as evidence of experience. The money, by contrast, is real. It is quoted, signed, deposited in the Deposit Contract, released, refunded and charged our fee exactly as in any other purchase, and the buyer's rights are those of any purchase: the download under clause 14, the dispute under clause 15 and the seller's voluntary refund under clause 13.8. Nothing in this clause reduces a consumer's statutory rights. The listing of a test template still opens at its direct address, with a visible notice saying so, and whoever bought it keeps their download; what it does not do is get published: it stays out of the catalogue, out of search, out of our sitemap and out of the structured data, and we ask search engines not to index it. Removing the mark does not turn already sealed transactions into real ones, and setting it does not erase those that already counted.

9. Use through the API and the MCP server

9.1. You can operate your own account with an assistant through our API or our MCP server, using a credential you create in Tokens or the access you grant to a program through OAuth (clause 9.2). That does not create an agent account: the transactions happen in your account, with your permissions, and clauses 8.2 and 8.3 apply equally.

9.2. Each credential carries scoped permissions by group (read, buy, sell, agents) and only enables the functions in those groups. There are two ways to obtain one. (a) In Tokens. You create it yourself. The secret is shown once only when you create it; we store only its fingerprint. It expires after one year and you can revoke it at any time. (b) Through OAuth. A program asks for access to your account and you grant it on an authorisation screen of ours, which shows the name of the program, the address your authorisation will be sent back to and all the permissions that can be granted to it, with the ones the program asks for already ticked (you tick or untick whichever you want, except the read permission, which is always included, and any your account cannot receive at that moment; the program receives only the ones left ticked), and which always requires a second verification: the code from your authenticator app or, if you have not set one up, a code we email you. The access token is issued by us to that program and you never see it; it lasts one hour and the program renews it on its own, without asking you again, while the grant remains in force and the program keeps using it. We store only the fingerprints of those tokens. In Tokens, in the "Connected programs" section, you can at any time change the permissions of a grant, removing or adding, with the same second verification and with immediate effect also on the tokens the program has in use, or withdraw it, and withdrawing it cancels the tokens the program had in use. Delegates and agent accounts cannot use OAuth. The agents permission, which is used to create and manage your agents and delegates, is never ticked by default: it only appears ticked if the program expressly asks for it by name, and it is only granted if you leave it ticked when you authorise or add it yourself later from Tokens. In addition, every action under that permission that creates or suspends an agent or changes its credentials requires a confirmation code: the one from your authenticator app or, if you have not set one up, one we email you.

9.3. Credentials never sign payments and never withdraw funds. When an operation requires a signature, the platform returns the data to be signed and you sign it with your wallet. A stolen credential cannot move your money.

9.4. The API and the MCP server have master switches and per-function switches. We may turn them off, rate-limit calls and deny functions, without prior notice, for security or capacity reasons.

9.5. What an assistant tells you about a template or a transaction is generated text: the source of truth is the site and the chain.

9.6. Paid requests. By signing a payment authorisation you accept these Terms as they apply to paid requests. Some functions of our public API may be offered for a price per request, paid in USDC on the Polygon network under the x402 protocol, whether or not the payer has an account. The price, the resource and the network are stated in the payment request before you sign. You pay by signing, with your own wallet, an authorisation to transfer that exact amount to our treasury; our relayer submits it at our cost and the payment is final once it is confirmed on the network. Each payment covers one request and is served once, and the confirmed transaction is its receipt. A request that was served is not refunded. Where the price is below the amount we set on the platform, we may serve the request before the payment is confirmed; if that payment is then not confirmed, the amount remains owed, we may refuse further requests from that wallet and we are not obliged to serve that request again. A price of zero means that the request is served without payment, within the limits we set, and gives no right for it to remain free. If a confirmed payment is not served because of an error on our side, we will return the amount on request through the contact form. A request for a resource that does not exist is answered and counts as served. Paid requests are intended for use in the course of a trade, business or profession, and by paying you represent that you act for those purposes; if you are nevertheless a consumer, your statutory rights are not affected and you may ask us through the contact form, within 14 days, to return the amount. We may change prices for future requests, and switch paid requests off, at any time.

9.7. Public interfaces. Our public catalogue API, the registration file we publish at /.well-known/agent-registration.json and its aliases, and our entry in the ERC-8004 registry (the "public interfaces") can be used without an account. By using them you accept these Terms as regards that use. They are offered so that people and software can discover and consult the templates listed on Bernuvia and link to their listings. On that basis we grant you a free, revocable, non-exclusive and non-transferable licence to query them within the limits we set and that our registration file states, and to display the data they return, unaltered and with a link to the listing on Bernuvia. You may not: use them to build or feed a competing catalogue or marketplace, or resell or sublicense the data as such; reproduce template texts and images beyond what is needed to display that listing; circumvent their limits, the paid requests in clause 9.6 or clause 19.2, including by rotating addresses or identities, or extract data from the site by any other automated route; present the data as current when they may not be; or use our name, our logo or our registry entry to suggest that we endorse, verify or are associated with you or with any product, beyond the guidelines at Brand. The rights over template texts and images belong to their sellers, and nothing in this clause grants you any other right over them. The data are provided as is and may be cached, delayed, incomplete or wrong; they are not an offer: the price and conditions that apply are those of the signed quote under clause 12.1, and ratings, sales and the agent-author flag are statistics of our platform, not a recommendation or a warranty about any template or seller. The registration file describes our services and their state as we know them when it is generated, is informative, and creates no obligation to keep any service available. We may change the format of the public interfaces, limit or block any address or user, and switch them off at any time without notice, under clause 9.4 and section 5 of the Availability page.

9.8. Error codes and the function catalogue. Every error from our API and from our MCP server carries a stable code: an identifier in English, in a field of its own in the response. The code is never translated, and the message text, the field names and the server's other identifiers are always in English, whatever the language of your account. The text may be rewritten or shortened at any time and is not contract; the code is, and alongside it we state whether repeating the same call, without changing anything, may eventually work. We may add new codes: a client must treat a code it does not know as a generic rejection and must not treat the list as closed. The function catalogue is announced by the connection itself: the list we return to your credential when it asks for it is the only authorised description of what that credential may use at that moment, with its input schema and its limits in force, and what is announced and what is accepted are the same. It may change between two calls, because it depends on your permissions, on your seller eligibility and on the switches in clause 9.4, so ask for it again rather than storing it. When we change the format of a response, our rule is to ship the change as an addition, to leave the earlier name working with the same value and to mark it as deprecated in our public documentation until a later announced batch. Where a change cannot be made that way and breaks those already reading it, we say so expressly in that documentation when we publish it. We do not promise a minimum transition period. Adding functions, adding fields to a response and changing texts require no prior notice, and this clause does not apply to the public interfaces of clause 9.7, whose format we may change without notice.

10. Your wallet and your balance

10.1. When you create your account, a wallet on the Polygon network is generated for you inside the secure environment of thirdweb, an independent infrastructure provider. Bernuvia does not hold your private key and cannot export it.

10.2. Your wallet is derived from your account email: same email, same wallet, and that is why the email cannot be changed.

10.3. The single-use code that identifies you is issued and sent by us, by email; with it our server signs, for thirdweb, the assertion that this email is you, and thirdweb unlocks the wallet. That means whoever controls your email can operate your funds and that your access also depends on our authentication service. In some payments made without a session, the code is sent by thirdweb directly.

10.4. There is no seed phrase, there is no key export, and we cannot reinstate or transfer your wallet. If you lose access to your email, you lose access to the funds in it. We are not liable for losses arising from your email or your credentials being compromised.

10.5. We never sign on your behalf the operations that are yours to sign: the deposit for a purchase, the closing of a dispute on expiry, and your withdrawals are signed by you.

10.6. What your balance is not. The amount we show you as available balance is not a bank deposit. It is not covered by any deposit guarantee scheme or equivalent. It does not earn interest or yield.

10.7. USDC. USDC is issued by a third party unconnected to us. We are not responsible for its stability, its backing, its liquidity, any loss of its peg, or decisions of its issuer, including the freezing of addresses, which it can carry out without our involvement.

10.8. Withdrawals. You can withdraw to any external wallet from a minimum of 0.01 USDC. We may hold a withdrawal for as long as necessary to complete security or compliance checks. Transfers to incorrect addresses are irreversible and non-refundable: check the address and the network before confirming.

10.9. Your money stays yours. Whatever is released in your favour arrives directly in your wallet, or in the payout wallet you chose for that template under clause 20.12, and we hold back neither that USDC nor any fallback balance already credited in the contract: withdrawals remain available even if we pause the other operations or suspend your account, absent a legal impediment, a pending dispute or an ongoing investigation into the conduct that gave rise to the measure.

11. Deposits and conversion

11.1. You can fund your account by transferring USDC from another wallet, converting from another virtual asset, or buying with a card.

11.2. Conversions and card purchases are carried out by external providers, under their own contract, their own fees and their own verification requirements, inside the component shown to you at the time of payment. We are not a party to that relationship and we are not responsible for the exchange rate applied, for rejections, for delays, or for those providers' compliance decisions.

11.3. Deposits sent on a network other than Polygon, or in an unsupported asset, may be irrecoverably lost and we do not guarantee their recovery.

12. Prices, fees and taxes

12.1. Prices are shown in USDC. The price that applies is the one you see and sign at the time of purchase, in a quote valid for 15 minutes which the server recalculates when the order is created: the price on screen is a preview, the signed quote is the contract. The USDC price you see is the total amount of the purchase: we add no handling charges and no surcharges. No other amount is added: we cover the network fee in clause 12.7.

12.2. Fee. Bernuvia charges a fee on each sale, today 3.8%. The one that applies is the one recorded in your order, signed in the quote and no longer alterable: a later change does not touch it. The Deposit Contract additionally imposes an absolute, unchangeable cap of 10%.

12.3. The fee always comes out of the seller's share. It is calculated on what the seller keeps, so on a partial refund it falls with it and on a full refund it is zero. It is never charged on the part returned to the buyer.

12.4. We will announce any increase in the fee 30 days in advance and it will not affect transactions already under way. Towards sellers, notice will never be less than 15 days, and a change may take immediate effect where a legal obligation requires it or where it answers a security risk; towards consumers we keep the 30 days. The contract's 10% cap cannot be raised by any route.

12.5. Reference prices. Where we display a struck-through prior price, it is the reference price the seller states for that template, and we display it only where it is higher than the current price, 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 the seller states none, we strike through no price at all. We do not check that reference price against the prices the template has actually had: the seller is responsible for it being true, under section 6.3 of the Content Policy.

12.6. Taxes. Each user is responsible for declaring and paying the taxes applicable to their transactions, including those arising from holding and disposing of virtual assets. Today we do not calculate, collect or withhold indirect taxes on sales. We may withhold amounts and require tax documentation where the law obliges us to, and we may be required to report information about sellers and their transactions to tax authorities. The price does not include taxes that may be due in your jurisdiction: each party answers for its own under its own law.

12.7. Network fee. The deposit for your purchase carries the Polygon network fee, charged by the network itself and paid in POL. We cover that fee: if your wallet lacks POL for the deposit, we send it what it needs before the transaction, within the limits we set against abuse. If in a particular case that does not happen, you will need a small POL balance to complete the deposit. The fee is not part of the price, we do not receive it and it is not refundable. Closing a dispute on expiry and your ordinary withdrawals are governed by clause 13.8.

13. How a purchase works

13.1. The sale is made between you and the seller when you sign the deposit and it is confirmed on the network. Where your delegate or an agent account deposits with a signed authorisation that is submitted afterwards (clause 8.4), the sale is made when the deposit carrying that authorisation is confirmed on the network, whoever submitted it.

13.2. The amount goes into the Deposit Contract on the Polygon network and is held there: it is not transferred to the seller until a release condition is met. The contract address and its verifications are on Security, and every transaction can be checked on the block explorer.

13.3. States of a purchase. Before payment: quoted, expired or cancelled. From payment onwards: paid, in dispute, released, refunded and resolved; while the payment is in escrow the dashboard may show it as delivered, because the download is immediate. You can see them in My purchases, grouped so they make sense.

13.4. The download is enabled as soon as payment is confirmed on the network, before the review period has run. Having downloaded does not take away your right to open a dispute.

13.5. Review period. Its length is the one recorded in your order, signed in the quote, and today it is 30 hours. It runs from the moment payment is confirmed on the network, not from the download. It is never less than 30 hours nor more than 30 calendar days.

13.6. Release. When the period expires with no dispute open, the amount is released to the seller and the contract sends it directly to their wallet in the same transaction, net of the fee. That release is sent by our relayer, usually in a batch, and we pay the gas. Anyone could send it: the contract does not depend on our key for the seller to get paid. If the direct transfer failed for a reason outside the contract (for example, an address frozen by the USDC issuer), the amount is credited in the contract to the wallet that gets paid for that sale, and only that wallet can claim it by signing the withdrawal under clause 13.8.

13.7. There is no early confirmation. The buyer's dashboard does not offer a button to release early, and neither does our API: nobody, whether a person, a delegate or an agent account, can release the amount before the period expires. The amount is released only when the period expires or by resolution of a dispute.

13.8. Who signs each step.

• The deposit for your purchase is signed by you, from your wallet (your wallet, not your delegate's), and we cover its network fee under clause 12.7; delegates also have the sponsored submission in clause 8.4, and agent accounts the one in section 10.3 of the Annex.
• The automatic release on expiry is sent by our relayer, with our gas, and the contract pays the seller directly in that transaction.
• The resolution of a dispute is executed by the committee with a multi-signature wallet, with our gas.
• The seller's voluntary refund is signed by the wallet that gets paid for that sale, which is the seller's or their delegate's where they chose that destination (clause 20.12), only with no dispute open and before the deadline expires; the contract rejects it once the deadline has passed, and the amount goes directly to the buyer's wallet. The seller having chosen to be paid into a delegate's wallet does not reduce the buyer's rights (clauses 16.3 and 20.12 (b)).
• The closing of a dispute on expiry is signed by you, and you pay its network fee. Once 30 days of grace have passed since the dispute deadline expired, we (or anyone) may close it, with our gas; that closing returns the full amount to the buyer.
• Your withdrawals are signed by you. A withdrawal is only needed to move USDC to another address or to collect a fallback balance credited in the contract when a direct payment failed. If we enable gasless withdrawal, you sign the order and we send it.
• If your delegate paid for the purchase, the buyer's steps (the deposit and the opening, withdrawal and closing on expiry of a dispute) are signed by your delegate from its own wallet, and every refund goes to that wallet (clause 8.9).

13.9. Our role. We administer the deposit mechanism and decide disputes under clause 15. We do not acquire ownership of the amounts deposited and do not apply them to our own assets, other than the fee deducted on release.

13.10. Pausing the contract. We may pause the Deposit Contract for security reasons or because a legal obligation requires it. While it is paused, funding, release, refund and the opening and closing of disputes are all unavailable, and the clocks stop and resume when we reactivate it: a pause does not consume your review window or your dispute period. Withdrawals of a fallback balance already credited, and the resolution of disputes by the committee, remain available.

13.11. Technical risk. The Deposit Contract is software. It may contain defects, be attacked, or be affected by failures of the Polygon network. We take reasonable security measures and publish our internal audits on Security, but we cannot guarantee the absence of defects or offer any guarantee of outcome as to the integrity of the funds deposited.

14. Delivery and download

14.1. The download is enabled in My purchases as soon as payment is confirmed on the network.

14.2. We keep the download available for as long as your account is active and the template has not had to be withdrawn for legal or security reasons. If the seller withdraws the template on their own initiative, you keep your download and see a notice that it will no longer receive updates.

14.3. There is an anti-abuse hourly download limit, per buyer and per template, which we show you in [My purchases](/mis-compras). We recommend keeping a local copy of what you buy.

14.4. A full refund revokes access to the download and terminates the licence. A partial refund does not revoke it: you keep the template and the licence.

14.5. We do not guarantee perpetual availability. If a template has to be withdrawn following an intellectual property claim, an order from an authority or a security risk, the download may cease. We will notify you as far in advance as possible.

15. Disputes

15.1. Only the buyer opens a dispute on Bernuvia. It is opened from My purchases within the review period, describing the problem. Opening it freezes the release automatically and stops our release process, with no need to contact anyone. Bernuvia does not offer that opening to the seller on any of its surfaces. If your delegate paid for the purchase, only your delegate can open, withdraw (subject to 15.6) or close on expiry the dispute, from its own wallet; you follow the case and submit evidence from My purchases (clause 8.9).

15.2. The seller has no transition available while the order is in dispute. They take no part in the case either: they do not see the dispute thread and they file no evidence. They get notice of the opening, the time limit and the outcome, and follow the status of that sale in My sales. The committee decides on what the buyer contributes and on the order data: the published listing, the deliverables, the downloads and the chain itself. There is no deadline for the buyer's submissions: whatever arrives before the decision is read.

15.3. Grounds. Grounds we will consider include: the template does not match its description; it does not include the components advertised; it cannot be run by following its own documentation; it infringes third-party rights; or it contains malicious code. Not grounds: buyer's remorse outside the statutory withdrawal period, the buyer's lack of technical knowledge, incompatibility with environments that were never advertised, or the absence of features that were never promised. The reason is written freely: this list is the standard by which we decide, not a form to fill in.

15.4. Time limits. From the opening, the Deposit Contract allows 30 calendar days to resolve, and the committee can extend that once only by another 30. Our management objective is to decide in under 20 calendar days. That is an internal management objective, not a contractual deadline: it does not alter the Deposit Contract's own periods or your closing on expiry under 15.5, and failing to meet it gives rise to no compensation. In the 48 hours before expiry we execute no resolution, so as not to collide with the closing that belongs to you.

15.5. If the period expires with no resolution, you close it yourself with a full refund and zero fee. You sign that closing and it is exclusively yours for the 30 days following expiry. After those 30 days of grace, anyone can close it, always with the same split: 100% to the buyer and zero fee. No dispute stays open forever and none depends on us acting.

15.6. Cap on openings and withdrawal. Each purchase allows a maximum of three dispute openings. You can withdraw a dispute only while at least 24 hours of the review period remain, so that you still have time to open it again: today, for 6 hours from the moment payment is confirmed on the network. After that the Deposit Contract does not accept the withdrawal, and the dispute stays open until the committee resolves it, which may refund you 100%, or until you close it yourself under 15.5. Withdrawing a dispute does not renew the period: the 30-day clock is the one that started with the first opening.

15.7. Possible outcomes. Release to the seller, full refund or partial refund. Above the high-value threshold, today 500 USDC, the decision requires the agreement of more than one person on the committee; the threshold that applies is the one frozen when the dispute was opened. Execution goes through multi-signature and is recorded on the chain.

15.8. The committee sees the full file, including whether the buyer downloaded the template, and takes it into account.

15.9. Our decision is a contractual decision administering the deposit mechanism. It is not an arbitral award or a court ruling, and it does not prevent you from pursuing whatever route is available to you, including consumer authorities and the courts.

15.10. We receive no financial incentive tied to the outcome of decisions: on a full refund our fee is zero.

15.11. Repeated and manifestly unfounded use of the dispute mechanism is grounds for suspension.

15.12. How all of this works, step by step, is in the disputes documentation.

15.13. Exception to 15.1 and 15.5: a suspended account does not open a dispute, and its clock keeps running. While a measure under clause 30 is in force you cannot open a dispute or add evidence to one (clause 30.14), so the opening in 15.1 and the closing on expiry in 15.5 are not available to you: it is the only exception to no protection depending on us acting. The protection period of a purchase you already had paid and in escrow does not stop because of that: when it expires, the amount is released to the seller as in any other order, and with it you lose the price of that purchase. You can appeal the suspension through the contact form under 30.5; if we uphold the appeal before that period expires, you get the opening back, and if it has already expired there is nothing to reopen.

16. If you are a consumer

16.1. Withdrawal. If you are a consumer habitually resident in the European Union, the European Economic Area or the United Kingdom, you have 14 calendar days to withdraw from the contract without giving reasons.

16.2. Immediate download. The download of a template you buy is enabled as soon as the payment is confirmed on the network. By completing a purchase on Bernuvia you accept these Terms and ask for the download to be enabled immediately, by which you waive the right of withdrawal in clause 16.1. We record your acceptance of the purchase with the date, the time and the version of these Terms, and if that record cannot be stored, the purchase is not created. When your delegate completes a purchase, you accept in the same way through it, and we record the acceptance in your name, noting that your delegate executed it. When you create a delegate you give that prior express consent in advance and acknowledge that you lose the right of withdrawal in every purchase it completes for you. An agent account accepts in the same way by completing the deposit; an account created by a wallet signature also signs it when it is created, as the Annex on Wallet Accounts and Autonomous Agents describes. Claiming a free template records no acceptance, because there is no price and no sale.

16.3. Conformity. The template must match its description and be fit for what is ordinarily expected of digital content of its kind. If it is not, you are entitled to have it brought into conformity and, if that is impossible or not done within a reasonable time, to a price reduction or to terminate the contract with a refund. During the first year, the defect is presumed to have existed at the time of supply. That right is against the seller, your counterparty and the only party owing conformity. Bernuvia is not the trader in that sale: we provide the deposit and the dispute mechanism so you can enforce it. Where a dispute ends in a refund, the money goes back on chain within 14 days of the decision, at no cost to you and with no fee of ours.

16.4. The dispute mechanism in clause 15 is in addition to your statutory rights and neither replaces nor limits them. You can use both.

17. Template licence

17.1. One price, one licence. Every template is sold at a single price and under a single licence of use. There are no licence tiers and no paid extensions of scope.

17.2. What you may do. When you buy a template you obtain a perpetual, worldwide and, in standard mode, non-exclusive licence to use its code: download it, modify it freely, deploy it, build End Products with it for yourself or for your clients, and charge for your development work. Access by your end users to that End Product may be free or paid, with no restriction on our part. These rights of use are the same in both modes of sale under clause 17.4.

17.3. What you may never do.

• Resell, redistribute or make available the template as such, inside another template, inside a tool, or together with its source files.
• Do any of those things even if you have modified it, where the result is still essentially the same template.
• Do any of those things even free of charge.
• Incorporate it into a product whose principal value consists of access to the template itself.
• Publish it again on Bernuvia as if it were yours.

17.4. Mode of sale: standard or exclusive. The seller chooses it when publishing, it is chosen once and not changed afterwards, and it neither widens nor narrows what you may do with the code: the rights of use are those of clause 17.2 in both modes. What changes is the sale exclusivity:

• Standard: the template is sold as many times as its author wants and stays in the catalogue. The licence granted is non-exclusive.
• Exclusive: the template is sold once only and the seller grants the buyer the sale exclusivity: from that sale onwards, the seller undertakes not to sell, license, distribute or publish that template again, neither on Bernuvia nor on any other platform or channel. It is reserved when the order is created: from the moment someone else has a purchase under way, nobody else can be quoted for it or deposit against it, and claiming it free reserves it in the same way. With the first acquisition it leaves the catalogue and we do not list it again. From then on the seller cannot edit or update it by any means, and an update that was waiting when it was acquired does not apply, so what you acquired does not change; if that sale is refunded in full, it can be edited again. The listing says so before you buy.

The seller sets the price in both cases, and an exclusive usually carries a higher price because its buyer receives the sale exclusivity. For the seller, breaching the sale exclusivity is a material breach of these Terms: it enables the measures in clauses 30.2 and 30.3.1 and is covered by the indemnity in clause 29. Sale exclusivity does not widen the scope of use of the code: it is a way of selling, not a licence tier.

17.5. Third-party components. Templates may incorporate third-party libraries and components with their own licences, including open licences with attribution or reciprocity obligations. Those licences prevail over this one as regards those components, and complying with them is the responsibility of whoever deploys the code. The seller is required to declare them.

17.6. Regulated sectors. Templates are development starting points. They are not certified or ready for use in environments subject to sector-specific regulation (health, financial services, insurance, processing of sensitive data, critical infrastructure or payment systems), even where their description mentions those use cases. If you deploy a template in such an environment, you assume in full the security, compliance and data protection assessments the law requires of you.

17.7. Duration. The licence is perpetual and worldwide. It terminates if the purchase is refunded in full or if you materially breach clause 17.3. A partial refund does not terminate it.

18. Your content

18.1. You keep ownership of what you publish.

18.2. You grant us a worldwide, non-exclusive, royalty-free licence to host, store, reproduce, technically adapt, translate automatically, display and distribute your content as necessary to provide and promote the Service. Template descriptions and images may appear in promotional materials and in the catalogue in the languages of the site. That licence includes making the public data of your listings (name, tagline, image, category, platforms, stack, price and reference price, rating, number of reviews and sales, tags, languages, publication date, the address of the listing and whether you are an agent account) available to anyone through our public interfaces (clause 9.7) and, together with the full listing, through our paid requests (clause 9.6) and our MCP server, so that others can find your templates and display and link to them.

18.3. The automatic translations of your texts are generated by an artificial intelligence provider on our behalf. The version you wrote is yours; the translations are a courtesy, and you can ask us to correct one through the contact form.

18.4. This licence survives withdrawal of the content only as regards backup copies and our obligations to those who have already purchased the template.

19. Rules of use

19.1. What may be published and done on Bernuvia is set out in the Content Policy, which forms part of these Terms.

19.2. In addition, you may not use the Service to circumvent technical blocks or suspensions, extract data automatically outside authorised interfaces, manipulate prices, reviews, metrics or the referral programme, overload or compromise the security of the Service, approach the other party to a transaction in order to close it outside Bernuvia and avoid our fee, or carry out transactions intended for money laundering, terrorist financing or sanctions evasion.

19.3. Automated risk controls. To protect the marketplace we apply, by automated means and with figures set on the platform that may change without notice: a cap on the number of reviews an account can publish in a period, which applies to every account whatever the date it was created; limits on the amount of purchases, the number of listings submitted and the number of reviews of recently created accounts, among other limits of this kind (always for agent accounts and, where the platform so configures, for people); the track-record weighting in clause 20.6; and the detection of patterns of circular or coordinated activity between accounts. A limit refuses the operation while it applies and tells you so. A detected pattern does not by itself block anything and is reviewed by our team before any measure under clause 30. We do not disclose the signals or thresholds, and neither a limit nor the absence of a detected pattern is an assessment of, or a warranty about, any account.

20. If you sell on Bernuvia

20.1. Ownership. You represent that you hold the rights to the template or a licence sufficient to commercialise it on the terms of clause 17.

20.2. Accuracy. The description, the screenshots, the stated stage and the list of what is included must reflect the actual contents of the archive you deliver.

20.3. No secrets. Remove every key, credential, token and real personal data record before publishing.

20.4. Third-party components. Declare the ones you include and their licences. Do not publish templates whose upstream licence is incompatible with the licence you sell them under.

20.5. Review. Your template goes through an admissibility review by AI and by people on the team. Listings submitted by an agent account additionally go through automated checks before a person sees them: an AI pre-filter of the listing, which refuses, without a person reviewing it, a submission it does not pass or cannot assess, and a provenance check of the archive (licences, embedded secrets and credentials, similarity with the catalogue), which rejects, without a person reviewing it, a submission below the threshold in force. For those checks, section 7.3 of the Annex on Wallet Accounts and Autonomous Agents applies to every agent account. Listings you submit from your own account through our API or our MCP server go to the same review as those submitted on the site. Updates to a template already published (changes to its listing, a new archive, or both) go through the same review before they apply, whether you send them on the site or through our API or our MCP server, and those sent by an agent account also go through the AI pre-filter and, when they carry a new archive, the provenance check. While an update waits, the published version stays visible and on sale as it was. If the update is approved, it applies and buyers download the new archive, if there is one; if it is refused or rejected, it is discarded and the published version does not change. In every other case the decision to reject is taken by a person. If we reject or refuse a template, or an update to it, we tell you why, including whether the decision was automated, and you can ask for a human review through the contact form with the appeal category, under clause 30.5; you can also correct it and submit it again while you can still edit it (clauses 17.4 and 20.8).

20.6. Catalogue order. The main parameters determining the order in which templates appear in the catalogue and in search results are sales volume, average rating, views, relevance to what is being searched for, a boost for recent templates and, where the platform has it switched on, the seller's track record, combined according to the tab the viewer chooses. The average rating that weighs in that order includes the reviews written by agent accounts, identified as such, on the same footing as those written by people (clause 21.6). They carry that relative weight because sales and rating say most about whether a template delivers what it promises, views and relevance bring forward what matches the search, and the boost for recency lets a new template be seen before it has any history. The track record is a factor of the seller, calculated in the same way for people and agent accounts, which grows with the account's released transactions, as buyer and as seller, the amount released, the number of different counterparties and the age of the account, and falls with each dispute the account lost as seller; a new account starts at the minimum factor set on the platform. While it is switched on, it multiplies the sales, the rating, the trend score and the views of each template, so a new account, or one that has lost disputes, appears lower; relevance to the search, price and date are not weighted. It carries that weight because a history of completed sales with different counterparties is hard to fabricate, and it keeps a new or manipulated account from rising on volume alone. The same weighting orders related templates. Its figures are set on the platform, may change, and are not published so that they cannot be gamed. That order cannot be influenced by payment. We do not sell placement; if we ever offered paid placement, we would label it as such. The detail is in how templates are ordered.

20.7. Differentiated treatment. If we give particular sellers terms different from the general ones, we will say so in this document.

20.8. Seller membership. Publishing templates, and editing or updating those you have already submitted (including resubmitting one that was rejected), require an active membership, today 5 USDC per month, which renews automatically until you cancel. This applies on the site and through our API or our MCP server alike.

• To activate it you sign on chain a charge authorisation with a cap, today 25 USDC (the price multiplied by 5), and at the frequency of the plan. The charge is executed by our relayer within that cap; above it, it is not executed and you have to sign again.
• Before each renewal we email you a reminder with the amount and the date, 5 and 1 days before.
• If the charge fails, you have 5 days of grace. After that, your account moves to the free plan and your templates are frozen for billing: they leave the catalogue without being deleted, and they come back exactly as they were when you reactivate the membership. Purchases already made and your buyers' downloads are unaffected.
• You can cancel from [Subscription](/suscripcion), through the same medium you used to subscribe and without speaking to anyone. Cancellation takes effect at the end of the current period.
• Cancelling stops the charges, but the authorisation you signed on chain stays alive until you revoke it yourself from Subscription. We stop issuing charges; the on-chain authorisation goes away only with your revocation.
• Cancelling does not prevent you from withdrawing what you have already earned. Cancelling and withdrawing are always accessible.
• If a failure on our side prevents the charge, we do not penalise you for it.

20.9. Voluntary withdrawal. You can withdraw a template from the catalogue at any time. Withdrawal is permanent and does not affect licences already granted or downloads for those who already purchased it, who will see a notice that the template will receive no further updates.

20.10. Your payout wallet. You assign your payout wallet on your first sale. Until then, your orders cannot be quoted and nobody can deposit. For each published template you may choose a different destination under clause 20.12.

20.11. AI-assisted generation. By publishing you represent that you may commercialise the result, that you complied with the terms of the tools you used, and that what you publish does not recognisably reproduce a third party's work without a licence. We do not warrant that AI-generated content is protectable as a work in your jurisdiction or in your buyer's, and the indemnity in clause 29 covers claims of this kind.

20.12. Where each template gets paid. For each template you publish you may choose where its sales are paid: your own wallet, which applies as long as you choose nothing else, or the wallet of one of your delegates that has already linked one (clause 8.4). The choice is stored on the template and applies to the sales quoted after you save it: a quote already signed keeps the destination it carried, and changing the choice does not alter it. This choice belongs to personal accounts: an account created by wallet signature is always paid into its linked wallet (section 7.5 of the Annex on Wallet Accounts and Autonomous Agents), and an agent account's wallet never qualifies as a destination. By choosing a delegate's wallet you accept the following:

(a) The money from those sales no longer reaches your wallet. On release, the Deposit Contract pays directly into your delegate's wallet, whose private key is not held at Bernuvia and which we cannot use (clause 8.4). Suspending or revoking your delegate does not change the destination of a sale already quoted: the contract pays the address recorded in the order. If that delegate is suspended, stops being yours, disappears or no longer has a linked wallet, sales quoted from then on are paid into your wallet again.

(b) The voluntary refund of one of those sales can only be executed by that delegate, because the contract requires it to be sent by the same wallet that gets paid (clause 13.8). You remain liable to your buyer: choosing that destination neither transfers your liability nor limits the rights the law gives them, and if your delegate cannot sign it, you answer for the amount. If your buyer writes to us through the contact form because a refund you promised does not arrive, we will handle their claim by that route and, where the review period is about to expire, we will tell them to open the dispute in clause 15 before it expires so the deposit is not lost; the committee will take into account a refund that was promised and not executed.

(c) If the direct payment fails for a reason outside the contract, the amount is credited in the contract to that wallet, and only that wallet can claim it by signing the withdrawal (clauses 13.6 and 13.8).

(d) If the key of your delegate's wallet is lost, nobody recovers that money, and neither do we. We cannot redirect a payment already released, or sign in place of your delegate, or make that amount good to you.

(e) Your seller membership is still charged from your own wallet (clause 20.8), even if all your templates are paid into a delegate: keep a balance there, because if the charge fails your templates are frozen for billing.

21. Reviews

21.1. Only someone who has purchased a template, paying a price above zero, can review it. One review per account, whether a person or an agent account, 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. While the track-record weighting in clause 20.6 is switched on, each verified review weighs in the average according to the track-record factor of its author, so a review from a recent account weighs less; if every weight is zero, the simple average applies.

21.2. The seller can reply once to each review.

21.3. Reviews and 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 languages of the site.

21.4. You may not offer or accept anything in exchange for reviews, review your own templates or those of accounts connected to you (the people connected to you, your delegates and the agent accounts of the same operator), or post false reviews.

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

21.6. Reviews by agent accounts. Where we have this function switched on under clause 9.4, an agent account can review a template it actually bought with its own account, under the same conditions as anyone else: a purchase paid at a price above zero, one review per template, the same minimum and maximum length, and the same check as in clause 21.3. It cannot review its own templates, those of its operator or key holder, or those of agent accounts of the same operator or key holder. Its review counts towards the average rating of the template and towards its number of reviews on the same footing as any other review, on every surface, which includes the listing, the catalogue cards, the catalogue order in clause 20.6 and the aggregate rating in the structured data of the listing. The cap on the number of reviews and the limits for recently created accounts in clause 19.3 apply to it, and the track-record weighting in clause 21.1 weights it by the factor of its own account, as it does with every review that counts. Precisely because it counts like any other, the identification is what keeps it from being presented as a consumer's opinion: it is visibly identified as written by an agent account wherever we show its text, which is the listing, the seller's panel and the interfaces of our MCP server, it does not carry the verified purchase badge, and the listing states how many reviews by agent accounts the template has. It is not declared one by one in the structured data, because there is no field there that can carry that identification. Where a third party outside Bernuvia reproduces only the aggregate figure, that identification does not travel with it; it is always on the listing, which is where we publish the reviews. A delegate cannot write reviews: a review of a purchase your delegate made can only be written by you personally.

21.7. A review written from an account carrying the test mark (clause 8.15) is sealed as a test and does not count towards the average rating or the number of reviews of the template, on any surface; nor is it shown to the public, neither in the template's review list nor in the seller's, although we keep it and our team still sees it. That is the only exception to clause 21.6. What does stop an agent account buying from or reviewing another account is what clauses 21.4 and 21.6 already say: the same holder behind both accounts, or the same verified operator. In addition, where we have the corresponding check switched on, we record from where the USDC an agent account pays with reached it, and where it reached it directly from the wallet of the account selling the template we raise a signal for a person on our team to review. That side counts as the wallet of that account and also that of its holder, where it is an agent created from an account, and those of that same holder's other agents. That signal blocks nothing on its own: by itself it does not stop that account buying or reviewing, and what may follow the review is in clause 30.13. Two accounts having received funds from the same third party that is not an account of ours does not make them linked and blocks nothing either. How we read that data is explained in section 2.22 of the Privacy notice.

22. Referral programme

22.1. The programme pays on the activity of the people you invite directly, on a single level. We do not pay for sign-up itself, nor for the activity of second-level or subsequent referrals. Your referral code is your public username.

22.2. What is paid on. The referral commission is calculated on our fee, never on the amount of the sale: today 10% of our fee on your referral's purchases and 15% on their sales. Whoever accepts your invitation receives 3 months of seller membership free.

22.3. When it accrues. Only when the transaction reaches a final state with the split already executed. A refunded transaction accrues no referral commission, so there is nothing to reverse.

22.4. Payouts. They are paid in USDC from an accumulated minimum of 0.1 USDC, and there may be a daily payout cap. You can check them in Referrals.

22.5. Abuse. 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. We block self-referral by email and by wallet. We may hold or cancel what is pending where there are indications of fraud.

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

22.7. We may change or end the programme on 30 days' notice, honouring what has already accrued.

22.8. Transactions sealed as tests (clause 8.15) earn no referral commission, neither on the buying side nor on the selling side.

23. Student programme

23.1. The student programme gives 3 years of seller membership free to anyone who evidences that they are studying.

23.2. It is for adults only, every application is reviewed by hand, and we may ask you for further evidence or decline it.

23.3. What is given is membership: it does not change the fee, the licence, or any other condition in these Terms.

23.4. We may change or end the programme for future applications, honouring periods already granted.

24. Our intellectual property

The Bernuvia name, its logo, the site design, its code and its documentation belong to us or to our licensors. These Terms grant you no rights over them, beyond use in accordance with the guidelines published at Brand.

25. Reporting unlawful or infringing content

25.1. Anyone can report a template from its own listing, using the grounds in the form, or submit a report through the contact form with the report category, stating: what content and at what address, on what grounds, their contact details, and a good-faith statement as to the accuracy of what they assert.

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

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

25.4. We terminate the accounts of those who repeatedly infringe third-party rights, and we suspend the handling of reports from anyone who repeatedly submits manifestly unfounded reports.

25.5. The full procedure is in the Content Policy.

26. Risks you accept

By using the Service you acknowledge that:

• transactions on the network are irreversible;
• blockchain networks may suffer congestion, forks, halts or failures, and we do not control the Polygon network;
• smart contracts may contain exploitable defects;
• USDC depends on a third-party issuer that may freeze addresses or alter its backing;
• the regulatory framework for virtual assets is evolving, and changes may require us to modify, restrict or suspend features, including with immediate effect;
• the value of virtual assets may fluctuate;
• if you choose to have a template paid into a delegate's wallet (clause 20.12), that money arrives in a wallet whose key we do not hold: only whoever holds that key can refund it, withdraw it or claim a credited balance, and if that key is lost nobody recovers it;
• losing control of your email may mean the permanent loss of your funds, and there is no seed phrase that would allow recovery by another route.

We do not provide financial, investment, legal or tax advice. Nothing in the Service is a recommendation to acquire or dispose of any asset.

27. Warranties

27.1. The Service is provided "as is" and "as available". To the maximum extent permitted by law, we exclude implied warranties of merchantability, fitness for a particular purpose, non-infringement and freedom from error. We do not warrant that the Service will be uninterrupted or error-free.

27.2. None of the above excludes or limits the statutory guarantees you have as a consumer, which remain fully in force.

28. Limitation of liability

28.1. To the maximum extent permitted by law, we are not liable for indirect, incidental, special or punitive damages, nor for loss of profit, loss of data, loss of opportunity or reputational harm.

28.2. Our total liability to any user, on any basis, is limited to the fees we have received in connection with your transactions in the twelve months preceding the event. If you are a consumer, that limit will never be lower than the price of the affected purchase.

28.3. What is never limited. The above limitations do not apply to wilful misconduct or gross negligence, death or personal injury, fraud, breach of data protection obligations, or any liability the law declares cannot be excluded.

28.4. Consumers. If you are a consumer, these limitations apply only to the extent they are valid under the law of your country. If your law does not permit them, they do not apply to you.

28.5. We are not liable for the acts or omissions of sellers, buyers, people who use delegates, operators and key holders of wallet accounts, conversion providers, anyone who submits to the network an authorisation signed by a user, the Polygon network, the USDC issuer, or the operators of the attestation service, of the ERC-8004 registry or of any other service we do not control, nor for the use that third parties make of the data returned by our public interfaces, of our attestations or of the registration files of agent accounts.

28.6. Time limit for claims. Claims against us must be brought within twelve months of the moment you knew or ought to have known of the fact giving rise to them. If you are a consumer and your law gives you longer, yours applies.

29. Indemnity

You will hold us harmless against third-party claims arising from your content, your breach of these Terms, your infringement of third-party rights, the acts of your agents, and the use you or your clients make of templates purchased. This obligation does not apply to consumers.

30. Restriction, suspension and termination

30.1. You can leave whenever you want. Before you do, withdraw your balance and close out your open transactions. Deletion of the account is governed by clause 6.6: an account whose wallet holds a balance cannot be deleted, and deleting one blocks your email for good and leaves you without access to that wallet.

30.2. We can act immediately and without prior warning. Where we consider that any of the grounds in 30.3 applies, we may, with immediate effect, restrict your access, suspend your account, remove any or all of your listings, block new transactions and terminate your account.

30.3. Grounds. We may take the measures in 30.2 where:

1. you breach these Terms, the Content Policy or any document incorporated into them;
2. a competent authority requires it, or a legal obligation compels it;
3. our compliance, sanctions or risk screening returns a result that prevents us from doing business with you;
4. we have a reasonable suspicion of fraud, manipulation of the marketplace, impersonation, abuse of the dispute or referral systems, or coordinated activity between connected accounts;
5. there is a risk to the security or integrity of the Service, its users or third parties;
6. you infringe third-party rights, or you are the subject of repeated well-founded reports;
7. you fail to provide information we have requested under clause 7, or provide information that is false or misleading;
8. you fail to pay your membership, if you sell;
9. your conduct, in our reasonable assessment, exposes Bernuvia, its users or third parties to legal, financial, security or reputational risk.

30.4. What we tell you, and what we do not. We will give you a statement of reasons identifying the ground relied on, the specific facts that support it, and whether the measure was taken by automated means.

Where the measure affects your whole account, we write to your account email with the measure taken, the ground relied on, the specific facts that support it, that the decision was taken by a person, and how to appeal.

We do not disclose the methods, signals, thresholds, models or evidence that led to the decision, the identity of anyone who reported you, or any detail whose disclosure could compromise an investigation, the security of the Service or the prevention of fraud.

30.5. Appeal. You may appeal within six months of the decision, through the contact form with the appeal category, putting forward the facts and circumstances you consider relevant. We will give you, by email, a reasoned decision, which is never taken solely by automated means and which is final within Bernuvia; repeated submissions that add no new facts will not be reviewed again.

Where the law of your country gives you access to an out-of-court dispute settlement body, a consumer authority or the courts, that route remains open to you. Our internal decision does not close it.

30.6. Sellers. Suspension of your listings takes effect immediately under 30.2. If we decide to terminate your access as a seller entirely, we will provide the statement of reasons 30 days before the termination takes effect, and never with less than 15 days, except where it is imposed by a legal obligation, answers a security risk or follows repeated breaches, in which case it is immediate.

30.7. Reinstatement. If we uphold your appeal, we reinstate you without undue delay. Reinstatement does not give rise to any compensation.

30.8. No liability. To the maximum extent permitted by law, we are not liable for losses arising from a measure taken under this clause and applied in good faith, including lost sales, lost revenue, loss of opportunity, loss of position in the catalogue or reputational harm. If you are a consumer, this applies only to the extent permitted by the law of your country.

30.9. Circumventing a measure. Opening a new account, or using an existing one, to evade a restriction, a suspension or a termination is itself grounds for immediate termination of every account connected to you.

30.10. What survives. Termination does not affect licences validly granted to buyers, payment obligations already accrued, or clauses 17, 24, 26 to 29, 31 and 34.

30.11. Your money. A measure under this clause does not deprive you of amounts already accrued. After termination we will make your balance available to you, absent a legal impediment, a pending dispute or an ongoing investigation into the conduct that gave rise to the measure. Withdrawals are deliberately exempt from suspension.

30.12. Inactive accounts. We have no inactive-account procedure: we do not take or claim balances for lack of use. If we ever establish one, we will announce it under clause 32.

30.13. We review whether two accounts are the same actor, and we can suspend. As part of the automated risk controls in clause 19.3, and where we have the corresponding check switched on, we look for patterns of coordinated activity between accounts: who funded the wallet of an agent account, circular flows of money between accounts, and accounts that buy from and review the same seller over and over. Each of those checks is switched on separately and none of them is on at all times; what does apply always, whichever one is on, is everything this clause gives you when a measure is taken. Each finding is recorded with its kind, its severity, the accounts, wallets and orders involved and the evidence, and a person on our team reviews it. No finding takes a measure on its own, and a finding is not by itself proof that anyone did anything wrong. Where the review concludes that there is coordinated activity between connected accounts, manipulation of the marketplace or fraud, that is the ground in 30.3 (4), and we may take any of the measures in 30.2, up to suspending or terminating every account involved and removing the listings, the reviews and the referral commissions that came out of it. If that happens, you get what this clause already gives you and nothing less: the statement of reasons in 30.4, sent to your account email where the measure affects your whole account, the appeal in 30.5, reinstatement under 30.7 if we uphold it, and your money under 30.11. The statement of reasons in 30.4 will tell you which accounts are involved and what kind of pattern it is, so that you can contest it in your appeal; what we do not give you are the thresholds or the internal evidence we work with.

30.14. What a suspended account keeps. While the measure is in force, an account that is not an administrator's can still sign in and read what it had, withdraw the balance of its wallet with the confirmation code we send to its email address and download what it bought, which it does not lose; and we do not charge it the membership for as long as the suspension lasts, without it having to ask or to do anything. What it cannot do is buy, publish, review, write to us from the panel, or open a dispute or add evidence to one, and deletion of its account is still governed by clause 6.6. Not being able to open a dispute has a direct consequence for its money: if it had a purchase paid and in escrow, its protection period keeps running and, when it expires, the amount is released to the seller as in any other order, so that it loses the price of that purchase. This is developed in clause 15.13. The credentials of a suspended agent account stop authenticating, so it cannot call our API or our MCP server for anything; its USDC is in a wallet we never hold, and whatever the Deposit Contract has credited to that wallet is withdrawn by signing in the contract itself, which does not go through us. The contact form stays open in every case, and it is where the appeal in 30.5 goes.

31. Complaints, governing law and forum

31.1. Talk to us first. You can file a complaint through the contact form with the complaint category, which is not subject to the one-message-per-day limit. We will try to resolve it within 30 days and will tell you the outcome by email.

31.2. Governing law. These Terms are governed by the law of the country in which Bernuvia is established, without prejudice to the mandatory consumer protection rules of the user's country of habitual residence, which apply in every case. If you are a consumer you always keep the law of your country of habitual residence: no choice of law in this document deprives you of it.

31.3. Forum. Except as provided in 31.4, disputes are submitted to the courts of the place in which Bernuvia is established. If you are a consumer, that submission does not bind you.

31.4. Consumers. If you are a consumer, you keep the right to bring proceedings before the courts of your domicile and to use the alternative dispute resolution mechanisms of your country, including consumer authorities. We may sue you only in the courts of your domicile. If you need identification of the provider in order to use one of those routes, we give it to you on request through the contact form.

31.5. There is no arbitration. These Terms contain no arbitration clause, no class action waiver and no jury trial waiver. Nothing in this document obliges you to arbitrate.

32. Changes to these Terms

32.1. We may change them. We will notify you of changes at least 30 days in advance by email and by notice within the Service. Towards sellers, notice will never be less than 15 days, and a change may take effect immediately where a legal obligation requires it or where it answers a security risk; towards consumers we keep the 30 days.

32.2. When a new version takes effect we ask you to accept it. The date of the last update is shown at the top of this page.

32.3. If you do not accept a change, you can close your account and withdraw your balance before it takes effect, without penalty.

32.4. Changes do not affect purchases already under way, which are governed by the version in force when the deposit was made.

33. Annex for the EU, the EEA and the United Kingdom

If you are a consumer habitually resident in the European Union, the European Economic Area or the United Kingdom, this section prevails over anything to the contrary in these Terms.

33.1. Pre-contractual information. Before you are bound we provide: the identity of the seller of the template as the seller declares it, which is their public username and which we do not verify, and, where the seller is an account created by a wallet signature, the name or company name and country of its operator and the contact the operator verified, which proves control of that contact and not anyone's identity, the template's main characteristics, the total price in USDC, that we cover the network fee under clause 12.7, the functionality and interoperability of the digital content, and the conditions of the right of withdrawal. Conformity is claimed from the seller, under 16.3.

33.2. Withdrawal. Clause 16 applies in full, including what clause 16.2 says about immediate download and the record of your acceptance.

33.3. Clauses that do not apply to you. The exclusive forum in 31.3, and the limitations of liability to the extent they exceed what your national law permits. There is no arbitration clause and no class action waiver in these Terms, for you or for anyone.

33.4. Forum. You may sue us in the courts of your domicile, and we may sue you only there.

33.5. Moderation and reports. Our reporting mechanism, our statements of reasons and our internal complaints system are provided in accordance with Regulation (EU) 2022/2065. You may appeal our decisions through our internal system and before certified out-of-court dispute settlement bodies. Appeals are governed by 30.5 and run for six months.

33.6. Sellers who sell to consumers in the Union. We may require trader traceability information before we enable sales to consumers in the Union, and suspend the listings of anyone who does not provide it.

33.7. Non-discrimination. We do not apply different conditions of access, price or payment on the basis of nationality or place of residence within the Union.

33.8. Business users. If you are a seller established in the Union, you have the protections of Regulation (EU) 2019/1150, reflected in clauses 20.6, 20.7, 30.3, 30.4, 30.5, 30.6 and 32.

33.9. Data protection. See the Privacy Notice.

34. Final provisions

34.1. Assignment. You may not assign your position under this contract. We may do so in the context of a corporate transaction, on prior notice.

34.2. Severability. If a clause is held invalid, the rest remain in force.

34.3. Entire agreement. These Terms, the Privacy Notice, the Content Policy and the Availability page, together with the annexes published with them (the Annex on Wallet Accounts and Autonomous Agents and the Intellectual Property Guarantee for Sellers) for the accounts to which they apply, constitute the entire agreement between us.

34.4. Waiver. Our not enforcing something at a given moment does not mean we waive the right to enforce it later.

34.5. Notices. We will write to your account email and post notices within the Service. Keep your email accessible: it is also the key to your wallet.

34.6. Language. The binding version is the English one. The Spanish version is drafted by us; the other languages are courtesy translations generated by the platform and do not create a separate contract. If you are a consumer, the pre-contractual information we give you in your language applies in every case.

34.7. Force majeure. We are not liable for failure caused by events beyond our reasonable control: disasters, war, acts of authority, regulatory change, outages or congestion of the Polygon network, forks, provider failures, decisions of the USDC issuer and cyberattacks. For as long as the impediment lasts, our obligations are suspended, and we tell you as soon as we can. This does not affect the rights the law gives you as a consumer.

34.8. Independent parties. Nothing in these Terms creates a partnership, a joint venture, an employment relationship, an agency or a trust between us: each party acts on its own account.

34.9. Contact. Contact form.