Legal
AI & Generated Content Policy
On this page1. Overview
Effective date: 14 July 2026
1. Overview
This AI & Generated Content Policy (“Policy”) explains how artificial intelligence is used within BrelexCode and sets out the rules, limitations, rights, and responsibilities applicable to:
- prompts and other AI inputs;
- AI-generated source code;
- AI-generated text;
- AI-generated images;
- generated files and project components;
- AI-assisted modifications;
- recommendations and explanations;
- other content produced through AI-powered features; and
- the use, export, publication, deployment, and distribution of such content.
BrelexCode is operated by:
BERELEX TRADE OÜ Registry code: 17535099 Registered address: Maakri tn 19/1, Kesklinna linnaosa, 10145 Tallinn, Harju maakond, Estonia Email: info@brelexcode.com Phone: +372 669 2281
This Policy forms part of our Terms of Service and should be read together with our:
- Terms of Service;
- Privacy Policy;
- Acceptable Use Policy;
- Payment, Tokens & Billing Policy;
- Refund & Cancellation Policy; and
- Cookie Policy.
Nothing in this Policy limits any mandatory rights that cannot lawfully be excluded.
2. Purpose of BrelexCode
BrelexCode is an AI-powered development platform designed to assist users in creating, modifying, testing, previewing, and exporting software projects and related digital content.
Depending on the features available, users may be able to:
- describe an application or feature using natural language;
- generate source code;
- modify existing project files;
- create user interfaces;
- generate text or images;
- request technical changes;
- receive explanations or suggestions;
- iterate on existing projects;
- preview generated applications;
- create or restore project checkpoints;
- export project files; and
- connect projects with supported third-party services.
BrelexCode is intended to assist development.
It does not replace:
- professional software engineering;
- independent security review;
- testing;
- legal review;
- regulatory assessment;
- accessibility review;
- intellectual property clearance; or
- other specialist review appropriate to the intended use of a project.
3. Definitions
For the purposes of this Policy:
3.1 “Input”
“Input” means any information or material that you provide to an AI-powered feature, including:
- prompts;
- instructions;
- questions;
- source code;
- project files;
- text;
- images;
- specifications;
- design requirements;
- previous Output;
- conversation context; and
- other information submitted or made available for processing.
3.2 “Output”
“Output” means material generated or modified through an AI-powered feature, including:
- source code;
- files;
- components;
- text;
- images;
- designs;
- suggestions;
- explanations;
- configurations;
- modifications; and
- other generated content.
3.3 “Generated Content”
“Generated Content” means Output and other material created or materially modified through AI-powered features.
3.4 “Project”
“Project” means the collection of files, code, content, configurations, Generated Content, and other materials associated with a project created, imported, modified, or maintained through BrelexCode.
4. How AI Is Used
BrelexCode may use artificial intelligence to:
- interpret user instructions;
- analyse relevant project context;
- generate source code;
- modify existing code;
- create files and components;
- generate text;
- generate images;
- suggest solutions;
- identify possible technical approaches;
- assist with debugging;
- explain code or technical concepts;
- support project iteration; and
- provide other AI-assisted functionality.
AI-generated results are produced based on:
- your Input;
- available project context;
- relevant system instructions;
- the selected AI model;
- model capabilities;
- technical configuration; and
- other factors affecting the generation process.
AI systems are probabilistic.
The same Input may produce different Output at different times or when processed by different models.
5. Third-Party AI Providers
BrelexCode may use AI models, APIs, infrastructure, or other technology provided by third parties.
Depending on the feature or model selected, these providers may include:
- OpenAI;
- Anthropic;
- Google; and
- other AI or technology providers introduced in the future.
The providers and models available through BrelexCode may change over time.
BrelexCode does not guarantee the permanent availability of:
- a particular provider;
- a particular model;
- a particular model version;
- a particular context window;
- a particular generation capability; or
- identical model behaviour over time.
A model may be:
- added;
- updated;
- replaced;
- renamed;
- restricted;
- deprecated;
- temporarily unavailable; or
- permanently removed.
6. Selection of AI Models
Where BrelexCode allows you to select an AI model, different models may vary in:
- capability;
- speed;
- cost;
- Token consumption;
- context capacity;
- reasoning behaviour;
- coding performance;
- image capabilities;
- safety restrictions;
- availability; and
- Output quality.
The availability of a particular model does not mean that BrelexCode recommends it as suitable for every purpose.
You are responsible for selecting an appropriate model for your intended use where model selection is available.
7. Processing of Project Context
To respond to a request, BrelexCode may provide an AI system with relevant information from your Project.
Depending on the operation, this may include:
- your current prompt;
- previous relevant instructions;
- relevant source files;
- project structure;
- existing code;
- previous Output;
- selected images or attachments;
- configuration information; and
- other context reasonably necessary to perform the requested operation.
BrelexCode may use technical methods to select or limit the amount of context sent for processing.
This means that an AI model may not always receive or consider every file or every previous interaction in a Project.
You should not assume that an AI system has complete knowledge of:
- the entire Project;
- every previous prompt;
- external systems;
- unpublished requirements; or
- information that has not been included in the relevant context.
8. Your Rights in Input
As between you and BrelexCode, you retain your rights in your Input.
You are responsible for ensuring that you have the rights, permissions, and lawful authority necessary to submit and use Input through the Service.
You must not submit Input where doing so would unlawfully:
- infringe intellectual property rights;
- disclose confidential information;
- disclose trade secrets;
- violate privacy rights;
- breach a contract;
- violate employment obligations;
- violate applicable law; or
- breach another person’s rights.
The fact that BrelexCode technically accepts particular Input does not mean that you have the legal right to submit or use it.
9. Licence Necessary to Process Input
You grant BrelexCode a limited, non-exclusive, worldwide right to process Input only to the extent reasonably necessary to:
- provide the Service;
- process your request;
- generate Output;
- maintain your Project;
- provide previews and checkpoints;
- enable exports and integrations;
- provide support;
- maintain security;
- investigate technical problems or misuse;
- comply with applicable law; and
- exercise our rights and obligations under our Terms and policies.
This does not transfer ownership of your Input to BrelexCode.
Further information about the processing of personal data is provided in our Privacy Policy.
10. Rights in Generated Output
As between you and BrelexCode, and to the extent permitted by applicable law:
- you retain your rights in your Input; and
- BrelexCode does not claim ownership of Output generated specifically for you merely because you used the Service.
To the extent that BrelexCode itself obtains transferable intellectual property rights in Output generated specifically for you through the Service, BrelexCode assigns those rights to you upon generation, subject to:
- applicable law;
- third-party rights;
- open-source licences;
- third-party software licences;
- pre-existing materials;
- underlying platform rights;
- rights in AI models and technology; and
- other restrictions described in our Terms and this Policy.
This assignment does not transfer ownership of:
- the BrelexCode platform;
- underlying AI models;
- third-party services;
- proprietary BrelexCode technology;
- third-party libraries;
- existing software;
- open-source components; or
- other materials not owned by BrelexCode.
11. No Guarantee That Intellectual Property Rights Exist
Not every AI-generated result is necessarily protected by copyright or another intellectual property right.
Whether legal protection exists may depend on:
- applicable law;
- the nature of the Output;
- the level of human contribution;
- originality requirements;
- the jurisdiction involved; and
- other relevant circumstances.
BrelexCode does not guarantee that:
- copyright exists in particular Output;
- Output qualifies for patent protection;
- Output is eligible for registration;
- you will obtain exclusive rights;
- another person cannot lawfully create similar material; or
- a court or authority will recognise a particular intellectual property claim.
You are responsible for obtaining legal advice where intellectual property ownership or exclusivity is commercially important.
12. Output May Not Be Unique
AI-generated Output may not be unique.
Because AI models may respond to similar instructions in similar ways:
- another user may receive identical or similar code;
- another user may receive a similar design;
- common programming patterns may appear across multiple projects;
- standard solutions may be generated repeatedly;
- similar text or images may be produced for different users; and
- the same user may receive different Output from the same prompt.
BrelexCode does not guarantee exclusivity in Generated Content.
Output generated for another user is not considered your Output merely because it is similar to material generated for you.
13. Third-Party Rights
BrelexCode does not guarantee that Generated Content is free from all third-party rights.
Depending on the Output and its intended use, relevant rights may include:
- copyright;
- trademarks;
- patents;
- design rights;
- database rights;
- personality or publicity rights;
- privacy rights;
- contractual rights;
- trade secrets; and
- other proprietary rights.
Before commercially using, distributing, publishing, registering, or deploying Generated Content, you should conduct a level of review appropriate to the circumstances.
This may include:
- code review;
- dependency review;
- licence review;
- trademark searches;
- intellectual property clearance;
- image-rights review; or
- professional legal advice.
14. Open-Source Software
AI-generated projects may include or recommend:
- open-source libraries;
- frameworks;
- packages;
- templates;
- code snippets;
- dependencies; or
- other third-party software.
Such materials remain subject to their applicable licences.
Your rights in the overall Project do not override the licence terms applicable to third-party components.
You are responsible for checking:
- which dependencies are included;
- their applicable licences;
- attribution requirements;
- notice requirements;
- source-disclosure obligations;
- copyleft requirements;
- commercial-use restrictions;
- version-specific conditions; and
- other applicable obligations.
BrelexCode does not guarantee that every dependency selected or suggested by AI is appropriate for your intended licensing model.
15. Third-Party APIs and Services
Generated code may:
- integrate with external APIs;
- reference third-party services;
- use third-party SDKs;
- rely on external databases;
- use hosting providers;
- use authentication systems; or
- depend on other external technology.
You are responsible for:
- obtaining necessary accounts;
- obtaining API access;
- complying with third-party terms;
- paying applicable third-party fees;
- configuring integrations correctly;
- securing credentials;
- complying with rate limits; and
- ensuring that your use is lawful.
BrelexCode does not grant you rights to use a third-party service merely because Generated Content references or integrates with it.
16. Generated Code
AI-generated code may contain:
- bugs;
- syntax errors;
- logical errors;
- incomplete implementations;
- outdated methods;
- deprecated dependencies;
- security vulnerabilities;
- insecure defaults;
- incorrect assumptions;
- compatibility problems;
- inefficient code;
- missing error handling;
- inaccessible interfaces; or
- other defects.
You must not assume that code is correct merely because it:
- was generated by an advanced AI model;
- appears technically sophisticated;
- compiles;
- runs in a preview;
- produces the expected visual result; or
- works in a limited test.
Generated code should be reviewed and tested before production use.
17. Security of Generated Code
BrelexCode does not guarantee that Generated Content is secure.
Before deploying a Project, you should consider appropriate measures such as:
- code review;
- dependency scanning;
- vulnerability testing;
- authentication review;
- authorisation testing;
- secret management;
- input validation;
- output encoding;
- access-control testing;
- database security;
- API security;
- rate limiting;
- logging;
- monitoring;
- penetration testing; and
- other appropriate security measures.
The level of review should be proportionate to:
- the nature of the application;
- the sensitivity of the data;
- the number of users;
- the systems connected;
- the potential impact of failure; and
- applicable legal or industry requirements.
18. Secrets, Credentials and Production Data
You should not unnecessarily include sensitive credentials in:
- prompts;
- source code;
- project files;
- screenshots;
- generated configuration files; or
- public repositories.
This includes:
- passwords;
- private keys;
- API secrets;
- authentication tokens;
- database credentials;
- signing keys; and
- other confidential access information.
You are responsible for:
- using appropriate secret-management practices;
- reviewing Generated Content for accidentally exposed secrets;
- rotating compromised credentials;
- separating development and production environments; and
- protecting access to connected services.
19. Preview Environments
A successful preview does not mean that a Project is:
- production-ready;
- secure;
- scalable;
- legally compliant;
- accessible;
- free of defects; or
- compatible with every deployment environment.
A preview may operate differently from:
- a production hosting environment;
- a user’s browser or device;
- a third-party platform;
- a configured backend;
- a production database; or
- an external API.
You remain responsible for appropriate production testing.
20. Checkpoints and AI Modifications
BrelexCode may allow you to create or restore project checkpoints or previous states.
AI-generated modifications may affect:
- existing code;
- files;
- dependencies;
- configurations;
- styles;
- behaviour; and
- project structure.
You should review significant changes before relying on them.
Checkpoints and project history are convenience features and should not be treated as a substitute for independent backup or professional version-control practices.
21. Generated Images
BrelexCode may provide AI-powered image-generation features.
Generated images may:
- resemble existing styles;
- contain visual inaccuracies;
- contain distorted text;
- contain anatomical or technical errors;
- resemble existing works;
- unintentionally resemble real persons;
- depict fictional persons who appear realistic; or
- contain other artefacts common to generative AI.
Before using a generated image, you are responsible for considering:
- intellectual property rights;
- personality and publicity rights;
- privacy;
- trademark use;
- misleading presentation;
- advertising requirements;
- disclosure requirements; and
- other applicable laws.
22. Images of Real Persons
You must not use BrelexCode to unlawfully create, modify, or distribute Generated Content that violates another person’s rights.
Where Generated Content depicts or resembles a real person, you are responsible for considering whether your intended use requires:
- consent;
- authorisation;
- disclosure;
- labelling;
- removal of misleading context; or
- other legal safeguards.
You must comply with our Acceptable Use Policy concerning:
- impersonation;
- fraud;
- privacy violations;
- non-consensual harmful content; and
- other prohibited activity.
23. Generated Text and Factual Statements
AI-generated text may contain:
- factual errors;
- outdated information;
- fabricated information;
- incorrect citations;
- incorrect names;
- inaccurate technical details;
- misleading assumptions; or
- unsupported statements.
You should independently verify important factual claims before relying on or publishing them.
BrelexCode does not guarantee that Generated Content reflects the most current information.
24. No Professional Advice
Generated Content does not constitute professional advice merely because it concerns a professional subject.
You should not rely solely on AI-generated Output as a substitute for qualified:
- legal advice;
- medical advice;
- financial advice;
- tax advice;
- accounting advice;
- cybersecurity advice;
- engineering advice; or
- other regulated professional advice.
Where a Project concerns a regulated or high-risk activity, appropriate specialist review should be obtained.
25. Human Review
You are responsible for determining the level of human review appropriate to your use case.
Human review is particularly important where Generated Content may materially affect:
- personal safety;
- financial interests;
- legal rights;
- employment;
- healthcare;
- education;
- access to essential services;
- personal data;
- cybersecurity;
- critical infrastructure; or
- other high-impact matters.
AI-generated Output should not be treated as inherently correct merely because it was generated automatically.
26. High-Risk and Safety-Critical Uses
Unless expressly agreed by BrelexCode in writing, the Service is not designed or warranted as a safety-critical system.
You must not rely on BrelexCode as the sole development, validation, or decision-making mechanism for systems where failure could reasonably result in:
- death;
- serious physical injury;
- major environmental harm;
- significant infrastructure disruption; or
- other severe consequences.
Examples may include:
- life-support systems;
- emergency control systems;
- autonomous weapons;
- critical industrial control;
- transportation safety systems;
- medical devices;
- safety-critical infrastructure; and
- other comparable applications.
Where such uses are lawful, you remain responsible for all required:
- testing;
- professional oversight;
- certification;
- regulatory approval;
- risk management;
- documentation; and
- human control.
27. Regulated Uses
Generated Content may be subject to legal or regulatory requirements depending on how it is used.
This may apply to areas such as:
- financial services;
- healthcare;
- employment;
- education;
- insurance;
- credit;
- consumer protection;
- data protection;
- accessibility;
- cybersecurity;
- advertising; and
- artificial intelligence regulation.
BrelexCode does not determine whether your Project is regulated.
You are responsible for identifying and complying with laws and standards applicable to your Project and its users.
28. AI Transparency and Disclosure
Depending on how Generated Content is used, applicable law may require users to be informed that:
- they are interacting with an AI system;
- particular content was artificially generated or manipulated;
- a particular automated process is being used; or
- human oversight is available.
You are responsible for determining whether your application or use of Generated Content requires:
- AI disclosure;
- synthetic-content labelling;
- notices to users;
- machine-readable marking;
- provenance information;
- human-review mechanisms; or
- other transparency measures.
BrelexCode may introduce technical tools intended to assist with transparency or provenance, but the availability of such tools does not transfer legal responsibility for your independent use or deployment of a Project.
29. Metadata, Provenance and AI Labelling
Where Generated Content contains:
- provenance information;
- watermarks;
- content credentials;
- machine-readable AI indicators; or
- other legally or technically required markers,
you must not remove or manipulate those elements where doing so would violate applicable law or third-party terms.
BrelexCode may add, preserve, or support such technologies where appropriate.
The absence of a visible AI label does not mean that content was not AI-generated.
30. Responsibility for Applications You Build
You are responsible for applications, websites, systems, and services that you create or operate using BrelexCode.
This includes responsibility for:
- functionality;
- security;
- data collection;
- privacy;
- user communications;
- terms and policies;
- accessibility;
- third-party integrations;
- payment functionality;
- content;
- legal compliance;
- regulatory approvals; and
- ongoing maintenance.
BrelexCode does not become:
- the operator of your application;
- the publisher of your application;
- your legal adviser;
- your security auditor; or
- the controller of all data processed by your application
merely because BrelexCode was used during development.
31. Modifying and Exporting Output
Subject to applicable law and third-party rights, you may generally:
- review;
- copy;
- modify;
- export;
- combine;
- deploy;
- distribute;
- commercially use; and
- further develop
Generated Content produced for you through the Service.
Your use remains subject to:
- third-party rights;
- open-source licences;
- third-party service terms;
- applicable law;
- our Terms; and
- this Policy.
Once Output has been exported and independently modified or deployed, BrelexCode is not responsible for changes made outside the Service.
32. Attribution
BrelexCode does not generally require you to publicly attribute your Project to BrelexCode merely because you used the Service to create it, unless a specific feature or separate agreement expressly states otherwise.
However, attribution may still be required by:
- open-source licences;
- third-party content licences;
- external APIs;
- external data sources;
- applicable law; or
- other third-party terms.
You are responsible for complying with such requirements.
33. Use of Third-Party AI Output
Different AI providers may impose their own terms, restrictions, or technical requirements on services used to generate Output.
BrelexCode may implement provider-specific requirements where necessary to:
- comply with provider terms;
- maintain access to models;
- protect users;
- prevent abuse;
- comply with law; or
- maintain technical functionality.
You must not use BrelexCode to intentionally circumvent restrictions imposed on an underlying AI service.
34. Safety Systems and Refusals
AI models and BrelexCode may use safeguards designed to:
- prevent harmful activity;
- comply with law;
- prevent abuse;
- protect third-party rights;
- prevent security threats; or
- comply with provider requirements.
As a result, a request may:
- be refused;
- be partially completed;
- produce a limited response;
- require modification;
- be blocked; or
- be subject to account review.
The fact that a particular model refuses a request does not guarantee that another model will behave identically.
You must not repeatedly attempt to circumvent safeguards for a purpose prohibited by our Acceptable Use Policy.
35. Acceptable Use
All use of AI-powered features must comply with our Acceptable Use Policy.
You must not knowingly use Generated Content to facilitate prohibited activities including:
- malicious cyber activity;
- phishing;
- credential theft;
- fraud;
- unlawful surveillance;
- exploitation;
- serious unlawful violence;
- infringement of third-party rights; or
- other prohibited conduct.
You remain responsible for how Generated Content is used after generation.
36. AI Provider Data Processing
To provide AI-powered functionality, relevant Input and project context may be transmitted to an applicable AI provider.
The information processed may depend on:
- the model selected;
- the feature used;
- the project context required;
- technical configuration; and
- applicable provider arrangements.
Further information concerning:
- the categories of information processed;
- purposes of processing;
- service providers;
- international transfers;
- retention; and
- personal data rights
is provided in our Privacy Policy.
37. Model Training and Service Improvement
The way Input and Output are handled for model improvement may depend on:
- the AI provider used;
- whether BrelexCode uses a paid or commercial API;
- applicable contractual arrangements;
- provider configuration;
- technical settings;
- legally required retention; and
- changes to the underlying service.
BrelexCode does not make an absolute promise in this Policy that no information will ever be retained or processed by any technical provider for purposes such as:
- service delivery;
- security;
- abuse prevention;
- debugging;
- legal compliance; or
- other purposes permitted under the applicable arrangement.
BrelexCode does not intend to provide User Content to third-party AI providers for unrelated advertising purposes.
Where third-party providers process personal data on behalf of BrelexCode, appropriate contractual and data protection measures will be used where required by law.
For the current and more detailed description of data handling, please review our Privacy Policy.
38. Confidential and Sensitive Information
You should carefully consider what information you submit to AI-powered features.
Unless a specific feature is expressly designed and appropriately configured for such information, you should not unnecessarily submit:
- passwords;
- private keys;
- production secrets;
- complete payment card data;
- highly sensitive personal data;
- confidential client data;
- regulated medical information;
- trade secrets; or
- information that you are not authorised to disclose.
You are responsible for complying with your own:
- confidentiality obligations;
- employment obligations;
- client agreements;
- data protection obligations; and
- information-security requirements.
39. Personal Data in Input
If you submit personal data concerning another person, you are responsible for ensuring that you have an appropriate legal basis or other lawful authority to do so.
You should minimise unnecessary personal data in:
- prompts;
- project files;
- test data;
- screenshots;
- databases; and
- generated applications.
Where possible, consider using:
- synthetic data;
- anonymised data;
- pseudonymised data; or
- non-production test data
during development.
40. No Guarantee of Model Continuity
AI models change over time.
A provider may:
- update a model;
- change behaviour;
- change pricing;
- change availability;
- retire a model;
- change context limits;
- change safety systems; or
- discontinue access.
As a result:
- the same prompt may produce different results in the future;
- a Project may behave differently when further modified;
- Token consumption may change;
- previous workflows may need adjustment; and
- a model may no longer be available.
BrelexCode may substitute, replace, or remove models where reasonably necessary.
41. Beta, Preview and Experimental AI Features
BrelexCode may make certain:
- beta;
- preview;
- experimental;
- early-access; or
- newly released
AI features available.
Such features may:
- be less reliable;
- change more frequently;
- produce unexpected results;
- have additional limitations;
- be withdrawn;
- have different usage costs; or
- not be suitable for production use.
Where a feature is identified as experimental or preview functionality, you should use additional caution before relying on it.
42. Generated Content and Refunds
Dissatisfaction with Generated Content does not automatically mean that a generation has technically failed.
AI systems may produce Output that:
- requires revision;
- requires debugging;
- does not match subjective preferences;
- interprets ambiguous instructions differently;
- requires additional prompts; or
- needs further development.
Token restorations and monetary refunds are governed by our:
- Payment, Tokens & Billing Policy; and
- Refund & Cancellation Policy.
A qualifying technical failure may be treated differently from a generation that successfully produced usable but imperfect Output.
43. Intellectual Property Complaints
If you believe that material generated, stored, or made available through BrelexCode infringes your intellectual property rights, you may contact:
Please provide, where reasonably available:
- identification of the protected work or right;
- identification of the allegedly infringing material;
- your contact information;
- the basis of your claim;
- evidence of your rights or authority to act; and
- any other information reasonably necessary to assess the complaint.
We may:
- request additional information;
- restrict access to relevant material;
- preserve relevant information where legally necessary;
- take action under our Terms; or
- respond in another manner required by applicable law.
44. Reporting Harmful or Problematic Output
If you encounter Generated Content that you believe:
- creates a serious safety risk;
- exposes private information;
- facilitates prohibited activity;
- appears to infringe rights;
- reveals a significant security issue; or
- otherwise requires urgent review,
you may contact:
Please provide sufficient information to help us identify and investigate the relevant issue.
Do not send unnecessary sensitive information.
45. Evaluation and Improvement of the Service
BrelexCode may analyse technical and usage information to:
- identify failures;
- improve reliability;
- detect abuse;
- evaluate system performance;
- understand usage patterns; and
- improve the Service.
Where User Content or personal data is processed for these purposes, such processing will be handled in accordance with our Privacy Policy and applicable law.
Where possible and appropriate, aggregated or de-identified information may be used for analytics and product improvement.
46. BrelexCode Does Not Endorse Generated Content
Generated Content does not represent the views, opinions, recommendations, or endorsement of:
- BrelexCode;
- BERELEX TRADE OÜ;
- our employees;
- our service providers; or
- the underlying AI provider
merely because it was generated through the Service.
AI models may generate content that is:
- inaccurate;
- incomplete;
- unexpected;
- objectionable;
- inconsistent; or
- unsuitable for a particular use.
You are responsible for deciding whether and how to use it.
47. No Guarantee of Particular Results
BrelexCode does not guarantee that AI-powered features will:
- generate a complete application from a single prompt;
- eliminate the need for developers;
- produce production-ready software;
- generate a specific design;
- solve every technical problem;
- use the lowest possible number of Tokens;
- produce the same result as another AI service;
- create legally protectable Output;
- avoid all third-party rights;
- create secure code; or
- achieve a particular business or commercial outcome.
Marketing examples, demonstrations, sample projects, or generated previews are illustrative unless expressly stated otherwise.
48. Your Final Responsibility
You are responsible for the final decision to:
- use;
- modify;
- publish;
- export;
- deploy;
- distribute;
- sell;
- license; or
- otherwise rely on
Generated Content.
Before doing so, you should apply the level of review reasonably appropriate to:
- the intended use;
- the risk involved;
- the audience;
- the data processed;
- the systems connected;
- the jurisdiction; and
- applicable professional or regulatory requirements.
AI assistance does not transfer your responsibility for the application you ultimately create and operate.
49. Enforcement
BrelexCode may restrict AI-powered functionality or take action under its Terms where use of the Service:
- violates this Policy;
- violates the Acceptable Use Policy;
- violates applicable law;
- creates a serious security risk;
- infringes third-party rights;
- abuses AI providers; or
- threatens the availability or integrity of the Service.
Depending on the circumstances, action may include:
- blocking a request;
- limiting a feature;
- restricting a particular model;
- issuing a warning;
- suspending an account;
- terminating an account; or
- taking another proportionate measure.
Urgent action may be taken without advance notice where reasonably necessary to prevent serious harm, fraud, unlawful activity, or a significant security risk.
50. Consumer Rights
Nothing in this Policy excludes or limits mandatory rights that consumers may have under applicable law.
Where an AI-powered digital service fails to conform to applicable contractual or statutory requirements, consumers may have remedies under applicable law.
The limitations and warnings in this Policy concerning the inherent characteristics of AI do not remove obligations that BrelexCode cannot lawfully exclude.
51. Changes to This Policy
We may update this Policy to reflect:
- changes to AI technology;
- new models;
- new providers;
- new features;
- changes to Generated Content functionality;
- legal or regulatory developments;
- security requirements;
- changes to industry practices; or
- improvements in how we explain AI-related risks and responsibilities.
The updated Policy will display a revised effective date.
Where a change materially affects an ongoing contractual relationship, we will provide any notice or other protections required by applicable law.
52. Relationship with Other Policies
This Policy should be read together with our:
- Terms of Service;
- Privacy Policy;
- Acceptable Use Policy;
- Payment, Tokens & Billing Policy;
- Refund & Cancellation Policy; and
- Cookie Policy.
Where this Policy addresses an AI-specific issue in greater detail, its more specific provisions apply to that issue, subject to mandatory law.
53. Contact
BrelexCode is operated by:
BERELEX TRADE OÜ Registry code: 17535099 Registered address: Maakri tn 19/1, Kesklinna linnaosa, 10145 Tallinn, Harju maakond, Estonia
Email: info@brelexcode.com Phone: +372 669 2281
For questions concerning:
- AI-generated content;
- intellectual property;
- Generated Content;
- AI safety;
- problematic Output; or
- this Policy,
please contact: