Terms of Use

Last updated: 22 October 2026

These Terms of Use ("Terms") are a contract between you and the operator of GenBlocks. They apply to the website, the assistant, the API, the MCP server, and every block, image, and task offered through them. By creating an account or using the service, you agree to these Terms. If you do not agree, do not use GenBlocks. The contract is formed when you successfully create an account. You can save or print these Terms for your records.

1. Who we are

GenBlocks is operated by:

Jonathan Eduardo Freire Espinoza
trading as Jonathan Freire
Mommsenstr. 31
10629 Berlin
Germany
Email: jonathan.freireespinoza@gmail.com

In these Terms, "GenBlocks", "we", "us", and "our" refer to that operator. "You" means the person using the service. The full provider information required by German law is in the Impressum.

2. The service

GenBlocks is a public registry of interface blocks and generated stock images. You can browse the registry without an account. With an account, you can ask the assistant to find an artifact, prepare a brief, generate a block, or generate an image. Generated artifacts pass automated checks and moderation before they can be published.

The service is currently free of charge. We may introduce paid features, change what is available for free, or set usage limits in the future. We will publish the price and the conditions of a paid feature before you can buy it, and we will not charge you without your express agreement. A change to the free service does not create a payment obligation for the past.

The free service does not create a distance contract for a price, so no statutory right of withdrawal applies to it. Before we offer a paid feature, we will provide the required pre-contractual information and withdrawal instructions, and we will ask for your express consent where a digital service begins immediately.

The assistant is an AI system. It is labelled as Ask AI in the interface, and it can be wrong. Do not treat its answers as legal, financial, security, or other professional advice.

The service is a registry, not a code audit, a legal review, or a guarantee that an artifact is fit for a particular purpose. Generated code is untrusted. Read it before you use it.

3. Eligibility and account

You must be at least 16 years old to create an account or use the generation features. If you are 16 or 17, you confirm that a parent or legal guardian consents to your use where the law requires it. If you are under 16, you may not use GenBlocks. Paid features may require additional age verification or parental consent.

You must give accurate account information, keep your credentials secure, and tell us promptly if you believe someone else has accessed your account. You are responsible for activity carried out through your account, unless the activity was caused by our breach of these Terms or by a circumstance outside your control.

You may sign in with email and password or with Google. If you use Google, Google's terms and privacy policy apply to your Google account. Google shares your name, email address, and account identifier with our authentication provider.

You may connect an AI agent through the MCP server. The agent acts with the access and scopes you approve. You are responsible for the instructions you give it and for the tasks it creates in your name. You can revoke a connected app from your profile.

We may refuse an account, suspend it, or close it when you breach these Terms, when the law requires it, or when this is necessary to protect the service or other users.

4. Your content and public publication

You keep whatever rights you have in the briefs and prompts you write. You grant us a non-exclusive, worldwide, royalty-free licence to store, reproduce, publish, display, distribute, modify for technical reasons, create embeddings, indexes, and other derived representations, and make available your submissions and the artifacts generated from them. This licence includes the right to let others use published artifacts under the public licence described in section 5. It survives account deletion for artifacts that remain public.

Published blocks and images are public. Their briefs, prompts, code, images, scores, model names, creation dates, and your display name can be read by anyone and may be indexed by search engines. The same applies to a brief that contains personal data or confidential information. Do not submit personal data, secrets, API keys, passwords, private addresses, or confidential business information.

You confirm that you have the rights needed to submit your content and that your content does not infringe the rights of another person. We may redact personal data, remove content, or refuse a submission when this is necessary to comply with the law or these Terms.

Your account email is not shown in the public catalogue. Your display name can be shown beside a published artifact. If you delete your account, we remove the author link and your display name from the item, but the artifact and its brief can remain public. Section 8 explains how to ask for removal.

5. Licence to use published blocks and images

Unless an item page says otherwise, blocks published in GenBlocks are made available under the MIT licence. You may use, copy, modify, merge, publish, distribute, sublicense, and sell copies of a block, provided you keep the copyright and permission notice that belongs to it. Third-party packages used by a block keep their own licences. Check them before you redistribute the project.

To the extent we hold the necessary rights, we grant you the permissions in this section. We will not assert rights we hold against use that the applicable public licence permits. A licence already granted for a copy is irrevocable as to that copy.

Generated images are made available for use in your own projects on a non-exclusive, worldwide, royalty-free basis. You may reproduce, modify, display, and distribute them, including for commercial projects. Attribution is not required. We do not grant exclusive rights, and we do not guarantee that copyright or other rights subsist in an AI-generated image or that it is free of third-party rights.

You may not use a published image or block to suggest that we endorse you, your product, or your use of the artifact. You may not use an artifact in a way that is unlawful, deceptive, or infringes the rights of another person.

6. AI-generated output

Blocks and images are generated by AI models. They can be wrong, incomplete, similar to material generated for someone else, or unsuitable for your purpose. We do not guarantee that an output is unique, accurate, secure, or free of third-party rights.

Generated code is untrusted. The sandbox checks are a safety net, not a security audit. You are responsible for reviewing code, dependencies, and assets before you use them in a product. Keep your own copy of anything you rely on.

Generated images are synthetic. Do not present them as a real photograph of a real person or a real event. If you publish AI-generated material, disclose that fact where the law or the platform you use requires it. We provide provenance information in the registry where available. Do not remove or alter a provenance notice that accompanies an artifact.

We do not use your content to train our own models. Third-party providers process content under their own terms and our agreements with them. Section 4 of the Privacy Notice lists the providers used in the current production setup.

Nothing in this section limits mandatory statutory rights in digital products under sections 327 et seq. of the German Civil Code (BGB).

7. Acceptable use

You may use GenBlocks only for lawful purposes and in line with these Terms and the Content Policy in section 8. You must not:

• use the service to create or distribute content that is illegal, harmful, or prohibited by section 8;
• attempt to bypass moderation, the no-people rule, quotas, access controls, or other safety measures;
• create multiple accounts or use automated means to evade a limit;
• scrape, overload, or interfere with the service, its providers, or another person's use;
• reverse engineer, decompile, or attempt to extract source code or credentials, except where the law expressly permits it;
• upload malware, phishing pages, credential-stealing code, or code that contacts an attacker-controlled service;
• submit personal data, secrets, or confidential information about yourself or another person;
• impersonate another person, a company, or an official body;
• use the service to build a deceptive interface or a fake login;
• resell access to the service as if it were your own product.

We may investigate suspected breaches, restrict access, and report conduct to the competent authorities where the law requires or permits it.

8. Content Policy

This Content Policy is part of these Terms. It explains what GenBlocks will generate, publish, and keep.

8.1 Scope

GenBlocks accepts interface sections and components such as heroes, pricing tables, forms, dashboards, menus, cards, charts, and empty states. It also accepts generated stock-image scenes, including photographs, illustrations, and abstract scenes.

GenBlocks does not accept essays, poems, articles, scripts, standalone websites, games, malware, phishing pages, political campaigns, or any request whose purpose is not a UI block or a stock image.

8.2 Prohibited content

The following is never accepted, even when it is legal in some jurisdiction:

• people in generated images, in any form, including a person, face, head, body, hands, arms, legs, skin, silhouette, crowd, humanoid character, realistic mannequin, or statue of a person;
• sexual content and nudity, including suggestive or fetish content;
• sexual content involving a minor, and any generated image that depicts a minor;
• child sexual abuse material, which is handled under section 9.4;
• violence and gore, including animal cruelty, torture, mutilation, and instructions for causing harm;
• hate and extremism, including slurs, supremacist symbols, dehumanisation, and content that promotes or glorifies violence against a group;
• harassment, threats, bullying, targeted abuse, and doxxing;
• self-harm and suicide, including promotion, instruction, or graphic imagery;
• illegal activity, including drug manufacture, weapons, fraud, evasion, trafficking, and instructions for wrongdoing;
• malware, phishing, credential theft, and evasion, including code that steals data, impersonates a login, evades a detector, or contacts an attacker-controlled service;
• privacy violations, including personal data, private addresses, private images, or content that identifies a person without consent;
• real people and deceptive likeness, including recognisable people, celebrities, politicians, private individuals, deepfakes, and voice or persona impersonation;
• brands and third-party rights, including real logos, trademarks, copyrighted characters, and a style request that names a living artist;
• deceptive interfaces, including a block that pretends to be another company's product, collects credentials, hides its purpose, or presents a fake system dialog;
• political, religious, or ideological persuasion, gambling, alcohol, tobacco, and weapons. These are restricted by product choice, not by law.

Ordinary product marketing is allowed. A pricing page, a SaaS hero, a checkout form, or a generic "Acme" dashboard is the product working as intended.

8.3 Technical rules for blocks

A block is presentational. It must not:

• load a script, stylesheet, font, image, or media from a host outside the registry's asset library;
• contain a <script>, <iframe>, <object>, <embed>, <base>, or a form with an action;
• navigate the page, open a window, use window, document, navigator, browser storage, eval, new Function, document.write, dangerouslySetInnerHTML, or a javascript: URL;
• use a dynamic import, require, process, or a package outside the published shelf;
• embed secrets, credentials, tracking pixels, or hidden data collection.

These rules are checked statically, at build time, and at render time. The checks are a safety net, not a security audit. Generated code is untrusted, and a person who copies it is responsible for reviewing it.

8.4 Images

Images can be generated for a block or requested on their own. Every image is public stock once it passes the gates. Pictures made for a block and pictures made independently live in the same library.

You may describe the picture you want. That direction is checked before the task is queued. A picture with people is refused. If the person is incidental, the product may offer a no-person rewrite and proceeds only if you accept it. If the person is the subject, the request is refused. If a component brief says nothing about images, the builder chooses the pictures.

An image prompt may describe a scene, a subject, light, and composition. It may not ask for a person, a real person, a brand, a copyrighted character, text that looks like an interface, or any prohibited content in section 8.2. The bytes that come back are checked for people before the generic classifier sees them. An image with a human is not stored. Rendered screenshots pass the same gate.

Pictures are decoded, bounded by bytes and pixels, re-encoded without EXIF or other camera metadata, and only then moderated or stored. Each generated artifact has a provenance record in the registry naming the model and the IPTC/C2PA digital source type trainedAlgorithmicMedia. The registry record is the source of that information; do not rely on metadata inside a downloaded file.

9. Moderation, reports, and enforcement

9.1 Moderation

Text is moderated before a task is queued and again after the block is written. Standalone image prompts pass a policy preflight, and the prompt is checked again before generation. Image bytes and rendered screenshots are checked by the no-people detector before they can reach a public asset host, and then by the generic safety classifier.

Production fails closed when moderation or the no-people detector is not configured. A missing provider is an outage, not permission to publish. Every moderation decision is recorded with the reason and the policy version.

Generated artifacts are published after automated moderation and can be removed by an operator. The operator receives one notification per generated block and per generated image, after publication. The notification is not an approval gate. A generated image containing a person is refused, not edited silently. The operator receives a metadata-only notice with the brief, the user, the reason, and an image hash. The image itself is not attached or stored with that notice.

9.2 Reports

Anyone can report a published block or image through the report control when it is available, or through the contact address in section 17. Reports are reviewed by a human. We are not required to monitor every item before publication, but we act on reports. We may remove content, restrict access, or take no action after review.

When we remove content, we tell the author the facts we relied on, the rule that was applied, whether the decision was taken automatically, and how to appeal, unless the law or a safety investigation prevents us from doing so. A repeated or serious violation can lead to suspension. A suspended account can no longer sign in and is limited to what an anonymous visitor can see.

We preserve only what is needed for the review, a legal obligation, or an active investigation. We may disclose content and records to competent authorities when the law requires or permits it.

9.3 Appeals

You can appeal a moderation decision by writing to jonathan.freireespinoza@gmail.com. Include the item or task, the decision, and the reason you believe it was wrong. A person will review the appeal. We may keep the original decision record while the appeal is open.

9.4 Child sexual abuse material and illegal content

GenBlocks does not generate people. Every generated image is checked for a human before it is stored, and a picture with a person is refused. Suspected child sexual abuse material is never published intentionally. If it appears through a report or another path, we restrict access immediately, preserve the minimum evidence needed for an investigation, and report to the competent authority or a specialist reporting service where the law requires or permits it.

We cooperate with law enforcement and may preserve the minimum information needed for an investigation. We may also restrict access while a report is reviewed.

10. Intellectual property

The GenBlocks name, logo, interface, and the text we write are protected by intellectual property law. These Terms do not grant you a licence to use our name or logo except to refer factually to GenBlocks or as the law allows.

If you believe content on GenBlocks infringes your copyright, trademark, or another right, write to jonathan.freireespinoza@gmail.com with the item address, the right you rely on, and enough information for us to review the claim. We may remove or restrict the item while we investigate. We may close the accounts of repeat infringers.

11. Availability and changes

The free service is provided as available. We do not promise uninterrupted availability, a particular response time, or that a feature will remain free. We may perform maintenance, change features, introduce limits, or discontinue a part of the service for technical, security, or legal reasons. Where a change materially affects your use, we will give reasonable advance notice.

You are responsible for keeping your own copy of code or images you rely on. Public registry entries can change or disappear when an item is deleted or removed.

12. Termination

You may stop using GenBlocks at any time and delete your account from your profile. Section 8 of the Privacy Notice explains what deletion removes and what can remain public.

We may suspend or terminate your access if you breach these Terms, if the law requires it, or if this is necessary to protect the service, other users, or a third party. Where possible, we will tell you why and give you a chance to respond. A serious breach, a security risk, or illegal content can lead to immediate suspension.

Sections 4, 5, 6, 8, 9, 10, 13, 14, and 16 survive termination.

13. Liability

We are liable without limitation for intent, gross negligence, and injury to life, body, or health. We are also liable for breach of an essential contractual obligation caused by slight negligence, limited to the foreseeable damage typical for this type of contract. In all other cases, liability for slight negligence is excluded.

Liability under the German Product Liability Act, a guarantee, or mandatory law remains unaffected. We do not exclude liability where the law does not allow it.

The service is currently free. You use generated code and images at your own risk, and you are responsible for checking that they fit your purpose and do not infringe the rights of another person. Mandatory statutory rights remain unaffected.

14. Governing law and jurisdiction

German law applies to these Terms, excluding the United Nations Convention on Contracts for the International Sale of Goods. If you are a consumer, this choice does not deprive you of the mandatory consumer protections of your country of residence.

If you are a merchant, a legal entity under public law, or a special fund under public law, the courts at our registered place of business in Germany have exclusive jurisdiction. Otherwise, the statutory rules on jurisdiction apply.

We are not obliged and not willing to participate in dispute resolution proceedings before a consumer arbitration board.

15. Changes to these Terms

We may update these Terms when the service, the law, or our providers change. The date at the top shows the current version. If a change is material, we will notify account holders by email or in the interface before it takes effect, where the law requires notice. If you do not agree to a change, you may stop using the service and delete your account. Where the law requires your express consent, we will ask for it.

16. General

If a provision of these Terms is invalid or unenforceable, the remaining provisions stay in force. The invalid provision is replaced by a valid provision that comes closest to its purpose, to the extent the law allows.

You may not transfer your rights or obligations under these Terms without our consent, except monetary claims. We may transfer our rights and obligations to a successor operator or in connection with a restructuring, provided this does not reduce your statutory rights and you may object where the law allows.

If we do not enforce a provision immediately, this does not waive our right to enforce it later.

These Terms, the Content Policy in section 8, and the Privacy Notice are the entire agreement about the service. They replace earlier understandings about the same subject. Your statutory rights remain unaffected.

17. Contact

Questions about these Terms, reports, appeals, or copyright complaints can be sent to jonathan.freireespinoza@gmail.com.