Terms of Use

Last updated: July 16, 2026

These Terms of Use govern access to and use of AIIGLE, including the visual editor, workflow builder, AI blocks, data-processing functions, hosted services, free credits, documentation, and related software or services (collectively, the “Service”). By accessing or using the Service, you agree to be bound by these Terms, the EU AI Act and Responsible AI Use Statement, and any additional terms applicable to your account. If you do not agree, you must not use the Service.

1. Eligibility and account responsibility

You are responsible for all activity under your account and for ensuring that your use of the Service complies with applicable law, these Terms, the EU AI Act and Responsible AI Use Statement, and all technical or usage limits communicated by us. You must keep login credentials and API keys confidential and must not share, transfer, resell, or misuse access.

If you use the Service on behalf of an organisation, you represent that you have authority to bind that organisation and that the organisation has assigned competent persons to perform the privacy, AI-governance, security, and legal reviews required by these Terms.

2. Permitted use and intended purpose

The Service may be used to build visual pipelines, transform data, call AI or software components, connect external APIs, create interfaces, and turn experiments into reusable workflows. You may use the Service only for lawful purposes and only within the intended purpose, risk classification, data scope, deployment conditions, and approvals documented for the relevant workflow.

You must declare the intended purpose, affected persons, data categories, connected models and services, deployment context, and risk-sensitive sector information requested by AIIGLE. You must update that declaration before making a material change.

3. Closed prototypes and mandatory approval gates

You may design a closed prototype without deployment approval only where it is isolated, limited to authorised testers, uses synthetic, fictional, or effectively anonymised data, does not affect real individuals, does not trigger live operational actions, and is not published, marketed, sold, licensed, or exposed externally.

Before any commercial or non-commercial use outside those closed-prototype conditions, you must obtain and retain:

1. a written GDPR and privacy review from your data protection officer, where appointed, or from a suitably qualified privacy officer or adviser;
2. written approval from the controller, accountable management representative, or other person formally authorised to accept responsibility for GDPR compliance; and
3. written approval from your AI officer, responsible AI officer, AI governance officer, or equivalent authorised AI compliance officer.

A data protection officer's review is advisory and does not transfer management's or the controller's legal responsibility to that officer. If you do not have formal privacy or AI governance functions, you must obtain equivalent written review from suitably qualified independent privacy and AI advisers and accept the resulting compliance obligations.

You must not activate, publish, market, sell, license, externally deploy, expose through an API, connect to live operational systems, process personal data in production, or use a workflow on, for, or about real persons without AIIGLE's prior written compliance approval. This applies to commercial and non-commercial use, including education, research, open science, internal business use, public-sector use, pilot projects, and charitable use.

You must provide the approvals, assessments, documentation, testing evidence, and safeguards requested by AIIGLE. Approval is version-specific and must be renewed after a material change. AIIGLE approval is platform permission only and is not legal advice, certification, conformity assessment, CE marking, or regulatory authorisation.

4. Free, educational, open-science, and commercial use

Free access is intended for evaluation, learning, closed prototypes, open science, universities, high schools, and non-commercial academic or educational work, subject to fair-use limits. Non-commercial or educational status does not waive the approval, data-protection, safety, transparency, or AI Act requirements in these Terms.

Commercial use, including use by companies, professional service providers, commercial research teams, production systems, paid client projects, or revenue-generating products, requires a paid account or separate written agreement and all approvals required by Section 3.

5. Free credits, fair use, and high-intensity processing

Free credits have no cash value, are non-transferable, and may be changed, limited, suspended, or withdrawn. High-intensity processing, large-scale automation, repeated execution, heavy AI inference, high-volume data processing, production workloads, agentic tool use, or other resource-intensive activity may require paid services. We may apply rate limits, quotas, throttling, approval gates, temporary suspension, or other technical controls.

6. Prohibited uses

You must not use the Service to design, test with real data, configure, facilitate, publish, deploy, or operate any practice prohibited in the EU AI Act and Responsible AI Use Statement, including:

• harmful subliminal, manipulative, deceptive, or vulnerability-exploiting AI;
• social scoring, unlawful profiling, or discriminatory treatment;
• individual criminality prediction based solely on profiling or personality traits;
• untargeted scraping to create or expand facial-recognition databases;
• emotion inference in workplaces, recruitment, or educational institutions;
• biometric categorisation used to infer sensitive or protected characteristics;
• real-time remote biometric identification in publicly accessible spaces;
• unlawful automated decisions or decisions that deny rights without required safeguards;
• child sexual abuse material or sexualised depictions involving persons who are or appear to be minors;
• non-consensual intimate, nude, sexual, or sexually explicit depictions of identifiable persons;
• fraud, impersonation, stalking, doxxing, harassment, coercive surveillance, or unlawful location tracking;
• unlawful weapons, autonomous targeting, violent wrongdoing, biological harm, or serious physical harm;
• malware, credential theft, unauthorised access, attacks, or evasion of security controls;
• processing data or content without the required rights, licences, legal bases, notices, and safeguards;
• creating, offering, or operating services intended to generate, retrieve, reconstruct, reproduce, distribute, or make available copyright-protected lyrics, music, books, articles, films, images, software, databases, or other protected material without the required rights, licence, permission, or binding legal exception;
• bypassing paywalls, subscriptions, digital-rights-management controls, copy protection, or access restrictions, or removing copyright notices, credits, watermarks, provenance data, or rights-management information;
• training, fine-tuning, indexing, scraping, or using retrieval-augmented generation on protected works without the required rights or without respecting applicable reservations of text-and-data-mining rights;
• removing or bypassing safety controls, AI disclosures, provenance markings, human oversight, logging, quotas, or approval gates;
• overloading, scraping, reverse engineering, attacking, or impairing the Service; or
• any conduct that violates applicable law, third-party rights, or these Terms.

7. High-risk and regulated uses

High-risk or otherwise regulated use cases may not leave a closed prototype unless AIIGLE has expressly approved them under a specific written agreement. This includes systems involving biometrics, critical infrastructure, regulated products, education, employment, essential public or private services, credit, insurance, healthcare, emergency response, law enforcement, migration, asylum, border control, justice, democratic processes, medical functions, or decisions producing legal or similarly significant effects.

Where permitted, you are responsible for completing every required classification, conformity assessment, registration, quality-management measure, technical document, risk-management process, data-governance control, log-retention measure, fundamental-rights assessment, data protection impact assessment, human-oversight measure, transparency notice, incident report, and post-market monitoring obligation.

8. User data, GDPR, and data-governance responsibility

You remain responsible for the data, prompts, files, models, workflows, outputs, and content you upload, retrieve, generate, process, or deploy. You must establish and document all required legal bases, Article 9 GDPR conditions, notices, permissions, licences, data subject rights procedures, processor agreements, joint-controller arrangements, transfer safeguards, retention rules, and deletion procedures.

You must complete a data protection impact assessment whenever processing is likely to result in a high risk to individuals. You must not send personal, confidential, or protected data to an LLM, model provider, API, connector, or other recipient without assessing that recipient and implementing required contracts, settings, security controls, and transfer safeguards.

We do not certify your workflow's GDPR, AI Act, sectoral, safety, accuracy, fairness, or legal compliance unless a specific written agreement expressly states otherwise.

9. External models, APIs, connectors, and credentials

You are responsible for all external models, APIs, data sources, connectors, plug-ins, agents, services, and destinations that you select. You must comply with their terms, licences, documentation, usage restrictions, copyright rules, rights reservations, security requirements, and geographic limits. You must not place secret keys or credentials in public client-side code or expose credentials to unauthorised persons.

10. AI outputs, human oversight, and consequential actions

AI-generated outputs, predictions, transformations, visualisations, logs, and workflow results may be inaccurate, incomplete, biased, unsafe, delayed, or unsuitable. You are responsible for testing and validating them before reliance or deployment.

You must provide competent and authorised human oversight for externally used workflows. No AI output may be the sole basis for a legal or similarly significant decision unless that use is lawful and all required safeguards, information, human intervention, contestation, and review rights are implemented.

Agentic or automated workflows capable of taking consequential external actions must use least-privilege permissions, explicit action boundaries, confirmation for high-impact actions, transaction limits, audit logs, and effective interruption or rollback mechanisms.

11. Transparency and generated content

You must clearly inform people when they are interacting with AI where required. You must preserve legally required machine-readable markings and disclose deepfakes and other AI-generated or manipulated content where required. You must not remove, conceal, or misrepresent provenance, labels, disclosures, warnings, or identity information.

12. Documentation, monitoring, and incidents

You must retain the workflow versions, approvals, assessments, test evidence, model and API identifiers, configuration history, deployment records, and logs reasonably necessary to investigate incidents and demonstrate compliance.

You must monitor deployed workflows and suspend them immediately where you reasonably suspect illegality, serious risk, discriminatory effects, loss of control, or security compromise. You must report serious incidents, personal-data breaches, prohibited use, material model failures, and regulatory investigations relating to the Service to AIIGLE without undue delay and cooperate with investigations and legally competent authorities.

13. AI literacy and competent personnel

You must ensure that persons who design, approve, operate, supervise, or use AI systems on your behalf have sufficient AI literacy, training, competence, authority, and support for their role and the relevant risks. You must retain evidence of training and authorisation where required by law or requested as part of an approval process.

14. AIIGLE review, technical controls, suspension, and termination

We may request identity verification, organisation verification, risk declarations, approvals, DPIAs, fundamental-rights assessments, technical documentation, model information, licences, contracts, test results, or other evidence.

We may restrict or disable models, connectors, data types, features, sharing, publication, deployment, execution, or external access. Where reasonably necessary and legally permitted, we may review relevant workflow metadata, content, or logs to investigate security threats, abuse, incidents, or suspected non-compliance.

We may reject or revoke approval, suspend workflows, remove content, preserve relevant evidence, restrict accounts, terminate access, revoke credits, or report matters to competent authorities where we reasonably suspect prohibited, unlawful, unsafe, non-compliant, or harmful use.

15. Intellectual property, copyright, and rights-holder complaints

The Service, including its software, interface, design, documentation, templates, icons, infrastructure, and underlying technology, is owned by us or our licensors and is protected by intellectual-property law. You retain rights you already hold in lawful inputs and content, subject to the rights necessary for us and our service providers to operate, secure, provide, and support the Service.

You represent and warrant that you have all rights, licences, permissions, and other legal bases required to upload, copy, scrape, index, transform, adapt, train on, fine-tune on, retrieve from, generate from, publish, distribute, communicate, sell, license, or otherwise use every work, dataset, recording, image, text, item of software, and other material used in or produced by your workflow.

You must not use AIIGLE to create or operate a service whose purpose or reasonably foreseeable use is to supply unauthorised copies or substantial portions of protected song lyrics, musical works, sheet music, sound recordings, books, articles, scripts, films, photographs, artwork, software, databases, or other protected material. This includes services that reconstruct protected works from fragments, embeddings, retrieval systems, prompts, screenshots, recordings, or uploaded reference copies.

You must not bypass technological protection measures, paywalls, subscriptions, copy controls, or access restrictions, and must not remove or falsify copyright notices, authorship or performer credits, watermarks, provenance information, rights-management information, or licence terms.

Where you rely on ownership, a licence, the public domain, an open licence, or a statutory exception or limitation, you must keep sufficient evidence and provide it to AIIGLE on request. You must also respect applicable machine-readable or otherwise valid reservations of text-and-data-mining rights.

AIIGLE may block generation, restrict a workflow, disable public access, remove or preserve disputed material, request evidence of rights, suspend repeat or serious infringers, and terminate accounts where it reasonably believes that intellectual-property rights are being infringed. Rights holders may submit a sufficiently precise and substantiated notice using the legal contact details published on the AIIGLE website. Where legally required, AIIGLE will provide affected users with information about restrictions and available review or complaint mechanisms.

16. Restrictions on copying, crawling, reverse engineering, and reuse

You must not copy, reproduce, mirror, scrape, crawl, frame, republish, extract, index, monitor, reverse engineer, decompile, disassemble, benchmark, automate access to, or attempt to derive the source code, structure, workflows, architecture, design, interaction logic, or implementation of the Service, except where mandatory law prohibits that restriction.

You may not use the Service or its interface, workflows, functionality, or implementation to clone the Service, train a competing system, build a derivative editor or workflow builder, perform unauthorised competitive analysis, or commercially redistribute extracted material without our prior written consent.

17. Paid services and separate regulated-use agreements

Paid accounts, subscriptions, enterprise plans, support, hosting, dedicated processing, and regulated-use functionality may be subject to additional terms, pricing, limits, security requirements, data-processing terms, service descriptions, and role-allocation agreements. In case of conflict, the specific written terms govern the relevant paid service, but no agreement permits conduct prohibited by mandatory law.

18. Service provided “as is”

Except where expressly agreed otherwise, the Service is provided on an “as is” and “as available” basis. AIIGLE does not guarantee that workflows, models, APIs, outputs, or integrations are accurate, uninterrupted, secure, legally compliant, suitable for production, or appropriate for a particular purpose. Mandatory statutory rights remain unaffected.

19. Liability

Nothing in these Terms excludes or limits liability that cannot lawfully be excluded, including liability for intent, gross negligence, injury to life, body, or health, or mandatory product-liability obligations. Subject to those exceptions, liability for slight negligence is limited to breaches of essential contractual duties and to foreseeable damage typical for the contract. Additional limitations may apply under a written business agreement.

20. Business-user indemnity

To the extent permitted by law, a user acting for business, professional, public-sector, or organisational purposes shall indemnify AIIGLE against third-party claims, regulatory costs, and reasonable defence expenses arising from the user's unlawful data, workflows, deployments, omissions, representations, or breach of these Terms, except to the extent caused by AIIGLE.

21. Changes to the Service and Terms

We may modify, suspend, discontinue, or replace parts of the Service, including free features, credits, limits, integrations, AI blocks, approval processes, and availability. We may update these Terms to reflect legal, security, safety, or operational developments. Where legally required, we will give advance notice or request renewed acceptance.

22. Governing law and venue

These Terms are governed by German law, excluding its conflict-of-law rules and the UN Convention on Contracts for the International Sale of Goods. Mandatory consumer protections remain unaffected. For merchants, legal entities under public law, and public-law special funds, the exclusive venue is Berlin, Germany, to the extent legally permitted.

23. Contact

Questions about these Terms, approval requests, paid commercial use, regulated deployments, educational access, or data-protection arrangements should be directed to the contact details provided on the AIIGLE website.