AslanStudios, Aslan Atelier, Aslanana and Aslax  Consolidated Terms and Conditions Document version: 1 September  2026  consolidated review edition Effective date for new agreements: 1 October 2026 ACTUAL PUBLICATION Service providers Studio Provider: Aslan Alabdali, trading as AslanStudios / Aslan Studios. Business address: 1111B S Governors Ave, Suite 52762, Dover, DE 19904 l Business registration  l DE , Dover

Studio, Atelier, legacy Aslanana and studio-assistant contact: aslan@aslanstudios.eu. Platform Provider: Aslax, LLC, a Delaware limited liability company, United States. Delaware file number: 10559309. Address: 1111B S Governors Ave, Suite 52762, Dover, DE 19904, United States. Representative: Aslan Al-Abdali. Support: support@aslax.eu. Legal and privacy: aslan@aslax.eu. Phone: +1 302 546 5151. Which terms apply Part A contains the shared contractual rules. Part B covers the Monthly Designer and Video Editor Subscription; Part C covers Aslan Atelier — Founding Brand Edition; Part D covers the Aslanana Photoshop AI Plugin; Part E covers the Aslax platform and its account-connected features; Part F covers the AslanStudios AI GPT and other expressly offered studio AI-assistant services. For studio services, Part A applies with any relevant Part B, C, D or F. For an Aslax platform contract, Part A applies with Part E; the specific platform provisions, including provider identity and governing law, prevail over inconsistent general provisions. A product schedule applies only to the product actually ordered or used under a contract incorporating it. Purchasing one service does not automatically include the others. The Studio Provider and Platform Provider are separate contracting persons. Shared branding, ownership, a link, an integration or the phrase “powered by Aslax” does not transfer a contract or create joint responsibility for another provider’s agreement. The offer must identify the actual provider before acceptance. Applicable merchant-of-record buyer terms govern the payment transaction where that role is clearly disclosed at checkout, without removing the service operator’s own obligations or mandatory customer rights. Important delivery and ownership information Unless expressly included in an agreement accepted by both parties, fees cover the agreed services, final deliverables and usage rights—not delivery or ownership of source code, development repositories, editable production files or the provider’s underlying technology. A functioning website, application or system is not, by itself, a source-code handover. Source-code delivery, source-file access, exclusive development rights, self-hosting packages and intellectual-property buyouts must be specifically agreed and priced. Client materials, user inputs and outputs, client data, third-party rights and mandatory legal rights remain protected. Sections 6–11 and the relevant product schedule explain the distinction. Portfolio notice Selected publicly released, commissioned business-project deliverables may be showcased under section 20.3, subject to confidentiality, agreed exclusions and protected rights. Private platform generations, plugin inputs, customer uploads and AI-assistant conversations are not covered by this permission merely because a user accepts these terms. Separate permission is required for their unrelated promotional use. Privacy and other notices The separate Privacy Notice, cookie information, applicable data-processing agreement and required consumer information remain separate documents. These terms do not replace them or establish that a consent-dependent data practice has been authorised. PART A — SHARED SERVICE AND DIGITAL-PRODUCT TERMS 1. Application and contracting parties 1.1 These terms govern services and digital products supplied by the relevant Studio Provider or Platform Provider identified above when incorporated into the relevant contract. “Provider”, “we”, “us” and “our” mean only the provider of that contract; “Client”, “user”, “you” and “your” mean its contracting customer. References to another provider do not bind that provider to the transaction. 1.2 Depending on the accepted order, services may include strategy, consulting, branding, graphic design, copywriting, photography, video, audio, animation, motion graphics, 3D work, AI-assisted production, social-media management, advertising, marketing, websites, e-commerce, applications, software, integrations, databases, automations, AI agents, plugins, extensions, digital resources, training, hosting, maintenance and technical support. Listing a service does not include it in every package or represent that a particular regulated service is offered. 1.3 The named schedules expressly cover the Monthly Designer and Video Editor Subscription, Aslan Atelier — Founding Brand Edition, Aslanana Photoshop AI Plugin, Aslax platform and AslanStudios AI GPT / studio assistant services when the applicable offer incorporates them. The contract identifies which provider supplies each item. A brand reference, internal tool, bundled link or later invoice cannot unilaterally substitute a different contracting party. 1.4 A consumer is a person contracting predominantly outside their trade, business or profession. Other customers may be business clients. Actual legal status, not merely a checkbox or invoice label, determines the protections that apply. Provisions expressly limited to business clients do not apply to consumers. 2. Contract formation, versions and priority 2.1 The contract consists of the accepted proposal, order or statement of work (“Order”), applicable service schedules, these terms as supplied before acceptance, and subsequent agreed changes. The Order identifies the deliverables, fees, delivery model and any material exclusions. An enquiry or application alone does not create a paid project. 2.2 Acceptance may be recorded by signature, electronic acceptance, email or another agreed communication method. Payment constitutes acceptance only where that acceptance mechanism was clearly communicated before payment and the relevant documents were made available. A link first added after a contract was formed does not itself amend that contract. 2.3 Mandatory law and binding individual agreements prevail. Subject to that rule, the accepted Order governs its project-specific scope, price and entitlements; the applicable named product schedule prevails over an inconsistent general provision of Part A; and a data-processing agreement prevails for processing it governs. Applicable merchant-of-record buyer terms govern the payment transaction where that role was disclosed. None of these standard documents overrides a legally binding individual promise. A later purchase order, website edit or communication does not unilaterally change an existing agreement. 2.4 We normally document changes in text form, including email or an approved messaging channel. A request is not an accepted change until agreement is reached. This documentation practice does not invalidate a binding individual agreement or require a stricter form than applicable law permits. 2.5 The version agreed for a project remains applicable to that project. Publishing revised terms does not retrospectively change completed work, remove previously granted rights or impose new charges. An existing project may be varied by a separately agreed addendum identifying the changes. 3. Scope, changes and project commencement 3.1 Only the services and deliverables described in the Order are included. A project description such as “complete website”, “custom application” or “full branding” must be read with the agreed specifications, delivery model and exclusions, not as an unlimited commitment to every possible feature or production asset. 3.2 Work begins after the agreed commencement conditions are satisfied, including any properly agreed advance payment, required materials, access and brief approval. Delivery estimates run from that point unless the Order states otherwise. 3.3 Changes to the approved brief, additional features, integrations, pages, languages, formats, environments, campaigns, user roles or deliverables require agreement on scope, price and scheduling before additional billable work proceeds. We will identify reasonably foreseeable consequences of a requested change. Undisclosed extras are not automatically chargeable. 3.4 Research, discovery, architecture, planning, design, development, configuration, testing and deployment count as project work where within the agreed scope. A marketing engagement does not automatically authorise replacing agreed marketing work with development; any such reallocation should be agreed. 3.5 Complimentary enhancements do not create an ongoing entitlement to free work. Their use and source-file treatment follow the applicable agreed terms, without changing rights already promised for the original project. 4. Client cooperation, access and approvals 4.1 The Client must provide reasonably necessary information, lawful materials, accurate requirements, authorised access and timely decisions. The parties should identify an authorised project contact. Instructions from other people require confirmation where authority is unclear. 4.2 The Client is responsible for the accuracy of supplied prices, product descriptions, factual claims, business information and legal instructions. The Client must identify relevant markets, accessibility needs, regulated activities, sensitive data and special operational requirements before approval of scope. We remain responsible for performing our own agreed work with reasonable professional care. 4.3 We use access only as authorised for the project. Both parties must protect credentials, use appropriate access controls and promptly report suspected compromise. Client-controlled accounts should use the Client’s recovery details. We may request delegated access rather than personal password sharing. 4.4 Client-caused delays may require a reasonable schedule adjustment. Any additional charge must reflect agreed rates or separately approved work, not an automatic undisclosed penalty. Failure to reply does not by itself mean acceptance, completion or forfeiture of all fees. 4.5 The Client should review deliverables before publication. Approval does not waive rights concerning concealed or legally actionable defects, and does not excuse our own breach. A later change of preference concerning an otherwise conforming approved design is ordinarily a new revision request. 5. Fees, payment and external expenditure 5.1 The Order specifies the currency, price, applicable taxes, payment dates and any advance or milestone payments. Advance payment is required only to the extent clearly agreed and legally permissible. Consumer-facing prices and additional charges will be disclosed as required before the order is placed. 5.2 Advertising spend, hosting, domains, cloud usage, model/API consumption, third-party licences, payment-provider charges and other external expenses are separate from service fees unless expressly included. We require approval of the expense or an agreed spending limit before incurring it on the Client’s behalf. 5.3 Prices accepted for a fixed project do not change merely because our public price list changes. Recurring prices may change only under an agreed lawful mechanism or a new agreement, with required notice and termination rights. Additional scope is priced separately. 5.4 We may claim statutory late-payment interest and legally recoverable collection costs. The Client retains lawful rights to dispute charges, withhold an appropriate amount or exercise set-off. Good-faith disputes should identify the contested item; undisputed sums remain payable when due. 5.5 A payment dispute or chargeback does not itself decide whether a contractual debt exists. We may provide accurate contract and delivery records to a payment provider when lawfully required. No automatic penalty or forfeiture arises merely because the Client uses a legitimate dispute process. 6. Definitions for delivery and intellectual property 6.1 “Final Deliverables” are the specific finished outputs identified for delivery in the Order: for example, exported graphics, approved copy, rendered video, reports, a configured website, a deployed application, an executable build or authorised access to a hosted service. Delivery format and operating rights depend on the Order. 6.2 “Client Materials” include materials, code, branding, documents and other assets supplied by or on behalf of the Client in which the Client or its licensors already hold rights. “Client Data” includes the Client’s content and business records processed through the services. These definitions do not treat personal data as property or diminish data-subject rights. 6.3 “Project Source” means human-readable development and editable production materials, including source code, repository contents and history, uncompiled application files, server-side code, build and deployment scripts, infrastructure configurations, proprietary database design files, development documentation, tests, editable design and motion files, raw footage, layered artwork, 3D scenes, prompts and internal workflow files. Material is excluded only to the extent it is not a Client Material, promised Final Deliverable or item required to be provided under applicable law or third-party licence. 6.4 “Provider Technology” means tools, libraries, components, frameworks, templates, methods, know-how, processes and technology developed or licensed by us, including reusable elements developed during a project. “Third-Party Materials” include open-source software, platform technology, models, fonts, stock media, music and other material controlled by third parties. 7. Source code and editable files are not included by default 7.1 Unless expressly included in an agreement accepted by both parties, the Client is purchasing the agreed services, Final Deliverables and usage rights—not delivery, disclosure or ownership of Project Source or Provider Technology. 7.2 This rule applies to websites, landing pages, online stores, applications, dashboards, portals, management systems, databases, integrations, plugins, extensions, AI agents, automations and other digital or creative work that we create, develop, build, configure, adapt, enhance, maintain or upgrade under the relevant agreement. 7.3 Bespoke development, payment of development fees, use of the Client’s branding, deployment to the Client’s domain or use of infrastructure paid for by the Client does not, on its own, include source-code delivery or an intellectual-property buyout. Terms such as “custom”, “built for you” or “your website” do not override an express source-code exclusion. Binding individual promises and mandatory law remain unaffected. 7.4 A Client requiring source code, an editable project, repository access, independent build capability, self-hosting rights, exclusive development rights or a buyout must raise that requirement before accepting the relevant scope. We must specifically agree to the requirement and its commercial terms. A request alone is not acceptance. The parties may also agree a separately priced handover later. 7.5 Where no source delivery has been agreed, we are not obliged to sell, disclose, license or transfer our retained Project Source merely because it is requested. We may decline an optional handover or offer a separate agreement, subject to rights the Client already holds and obligations imposed by law or third-party licences. 7.6 Administrative access, access to a content-management interface, a preview link, hosting access or the ability to operate a system is distinct from developer access or delivery of its underlying source. We must nevertheless provide the access expressly promised or reasonably necessary for the agreed delivery model. 7.7 Ordinary code and assets necessarily transmitted to an end-user’s browser are not represented as secret or technically inaccessible. Their necessary delivery is not a promise to provide a complete repository, private backend, development environment, source maps or production credentials. 7.8 This exclusion does not authorise withholding Client Materials, Client Data, client-owned accounts, expressly promised files or material that must be supplied under mandatory law or an applicable open-source licence. 8. Retained rights and permitted reuse 8.1 The Client and its licensors retain their rights in Client Materials. We and our licensors retain the copyrights, usage rights, know-how and other rights we respectively hold in Project Source and Provider Technology, except for rights expressly granted to the Client. We do not claim ownership of third-party material or of rights that do not exist under applicable law. 8.2 The Client grants us the limited rights in Client Materials reasonably necessary to perform the agreement, including approved use by authorised subcontractors and service providers. This does not authorise unrelated publication, sale or model training. 8.3 We may reuse general skills, techniques and Provider Technology, including non-confidential reusable components developed during the project. We must not disclose the Client’s confidential information, personal data, private business logic or restricted assets, or reproduce the Client’s distinctive commissioned branding as another client’s branding. 8.4 Exclusivity, a restriction on serving competitors, transfer of transferable intellectual-property rights or a grant of exclusive usage rights requires specific agreement identifying its subject matter, scope, duration and price. Source-file delivery alone does not create exclusivity or ownership of our entire technology stack. 8.5 We will obtain the permissions needed from people and suppliers we engage to grant the rights promised to the Client. We cannot transfer rights that belong to others; relevant restrictions must be identified where they materially affect the agreed use. 9. The Client’s licence and operating rights 9.1 Subject to payment of the fees properly due for the relevant deliverable, we grant the Client the rights expressly described in the Order. Unless a different scope is agreed, final exported creative deliverables carry a worldwide, non-exclusive, continuing right to reproduce, publish, display and make ordinary adaptations for the Client’s own business and brand purposes. This includes ordinary website, social-media, advertising, presentation and printed-marketing use, subject to disclosed third-party restrictions. 9.2 A final logo or brand asset expressly designated as exclusive in the Order receives the specified exclusive usage rights. No trademark registration, clearance opinion or exclusivity in stock elements, generic ideas or unprotectable material is promised unless expressly agreed and legally available. 9.3 For delivered software, the licence permits operation in the environment and for the business purpose identified in the Order. An agreed perpetual-use licence is distinct from a fixed-term subscription. For hosted services, access lasts for the agreed service period; paying a development fee alone does not include indefinite hosting. 9.4 The Client may allow employees and contractors to use Final Deliverables on its behalf within the licensed purpose. They may perform content administration and maintenance within the access and rights actually supplied, subject to appropriate confidentiality. This does not create a right to obtain undisclosed Project Source. Broader resale, white-labelling, sublicensing or product distribution must be agreed unless already permitted by the applicable licence or law. 9.5 A licence to fully paid Final Deliverables is not automatically revoked because a separate subscription ends or an unrelated invoice is disputed. Termination for a material licence breach requires a lawful basis and, where appropriate, an opportunity to remedy the breach. Mandatory rights and lawful rights relating to transfer or exhaustion remain unaffected. 9.6 Restrictions do not prohibit acts that mandatory law permits notwithstanding contract, including protected software backup, observation, testing, interoperability or decompilation rights. No general reverse-engineering restriction overrides those rights. 10. Separate source-code and source-file handovers 10.1 An optional handover requires an agreed source-code/source-file schedule or separate agreement. It should identify the exact project and version; the files and repositories included; excluded materials; permitted use and modifications; any exclusivity; payment; delivery timing; dependency and licensing information; and any agreed migration, documentation, training or support. 10.2 Source-code delivery, permission to modify source, permission to self-host, transfer of a repository, and an intellectual-property buyout are separate matters. One is not included merely because another is agreed. Any exclusivity or transfer must be stated expressly. 10.3 We may sanitise a handover to remove secrets, personal credentials, unrelated client material, internal administrative information and third-party material we cannot transfer. Sanitisation must not defeat the agreed build or operating capability. Necessary configuration instructions and replacement-credential requirements must be included where agreed for a usable handover. 10.4 Third-party subscriptions, API accounts, fonts, stock assets and licences transfer only where their terms allow. The Client must obtain replacement accounts or licences identified in the handover schedule. A source handover does not transfer our personal accounts, agency-wide subscriptions or other clients’ data. 10.5 Future updates, ongoing maintenance, history beyond the agreed version, new documentation, installation on a different infrastructure and developer training are included only as expressly agreed. Our statutory obligations and responsibility for conformity of the agreed handover remain unaffected. 10.6 Source-code escrow, continuity arrangements, release triggers and independent maintenance access can be separately agreed. No escrow obligation arises merely from providing hosting or support. 11. Existing systems, upgrades and inherited work 11.1 The Client must have authority to instruct work on an existing website, application, account or codebase. Existing Client Materials do not become our property merely because we access, host, repair or improve them. 11.2 Newly commissioned upgrades, extensions, redesigns, migrations, integrations and maintenance work are governed by the terms validly agreed for that work. They do not retrospectively change ownership, delivery obligations or licence rights relating to an earlier version. 11.3 Where our new retained components are incorporated into Client Materials, the Client receives the rights needed for the agreed combined operation. Source delivery depends on the agreed delivery model, applicable third-party licences and mandatory law. We will not introduce a new undisclosed dependency that materially prevents the Client from exercising existing agreed operating rights. 11.4 Responsibility for inherited defects, unsupported dependencies, compromised accounts or third-party modifications is limited to the assessment or remediation actually agreed. We remain responsible for our own work and must identify material discovered issues that affect the agreed delivery or safe implementation. 12. Third-party platforms and open-source software 12.1 Deliverables may depend on third-party platforms, software, hosting, payment systems, AI models or media. Material dependencies, recurring costs and licensing restrictions affecting the Client’s intended use should be identified in the Order or relevant schedule. 12.2 Third-party rights remain with their respective owners. Where an open-source licence requires attribution, notices, source availability or other conditions, those conditions govern the relevant components. These terms do not override them or impose incompatible restrictions. 12.3 We will not knowingly incorporate a dependency whose licence requires disclosure of otherwise proprietary Client Materials contrary to the agreed licensing model without prior disclosure and agreement, and subject to mandatory legal duties. 12.4 Third-party changes or outages may require technical changes or additional agreed work. They do not automatically excuse our own poor configuration, failure to perform agreed monitoring or other breach. Any allocation of external availability risk must preserve the service we actually promised. 13. Delivery, review and defect correction 13.1 The Order specifies deliverable formats, milestones, supported environments, relevant functionality and any acceptance criteria. Deadlines are estimates unless agreed as binding; we will promptly communicate a material anticipated delay and its expected effect. 13.2 Creative revisions are limited to the rounds or hours stated in the Order. A revision round means one consolidated set of feedback within the approved direction. New concepts, changed requirements or additional outputs are changes of scope. Correcting our failure to meet the agreed specification is not deducted from paid creative revision allowances. 13.3 For work requiring legal acceptance, we may request inspection and acceptance within a reasonable period after completion. Minor defects do not justify refusal where applicable law provides otherwise. Acceptance by failure to respond applies only where all statutory conditions are satisfied, including any required separate notice. Consumer digital-product rules apply instead where the law requires. 13.4 The Client should report defects with enough information to investigate, including the affected output, expected behaviour and available reproduction details. We will address a defect for which we are responsible under the applicable contract and statutory remedies. No two-day reporting deadline or ordinary review period extinguishes statutory defect rights. 13.5 Requests caused solely by a new preference, unsupported third-party change, unapproved modification or use outside agreed conditions may be chargeable after assessment and agreement. Responsibility is not excluded where our breach also contributed. 14. Websites, software, deployment and accounts 14.1 Each digital-development Order must identify whether delivery is a hosted service, deployment to Client-controlled infrastructure, an executable package, a platform configuration or a source-inclusive handover. The Order must also identify material hosting/API costs, access rights and relevant export or exit limitations before acceptance. 14.2 A production deployment means implementation of the agreed version in the agreed environment. It does not by itself include a complete repository, independent build environment, unlimited scalability, every device or browser, compliance certification or ongoing maintenance. 14.3 Where the Client owns a domain, social-media account, advertising account, payment account, hosting account or other platform account, it remains the Client’s account. We will not transfer it to ourselves or misrepresent ownership. Recovery details and permissions should reflect that ownership. 14.4 Our internal developer organisations, repositories, shared infrastructure and agency-wide accounts remain under our control, subject to agreed access, lawful audit, data-export and handover duties. A migration from shared infrastructure may require separately scoped technical work, but cannot override mandatory rights or already included migration services. 14.5 Launch approval should address content, essential workflows, payment handling and access responsibilities. The Client remains responsible for its own business operations and transaction decisions. We remain responsible for the implementation and safeguards actually included in our scope. 15. Hosting, maintenance, security and backups 15.1 Hosting, maintenance, monitoring, incident response, backups, disaster recovery, security updates and support are included only to the extent stated in the Order or required by law. A build fee is not a lifetime support or hosting fee. 15.2 A recurring service schedule should identify the service period, environments, included resources, support channels, response targets, backup arrangements, update responsibilities and any service-level commitments. Necessary consumer digital-product updates are not excluded merely because no maintenance package was purchased. 15.3 We will use reasonable professional care and the security measures required by our role and the agreement. No absolute guarantee of uninterrupted availability or immunity from every attack is given. This is not an exclusion of our responsibility for agreed security measures, negligent implementation or other actionable breach. 15.4 The party responsible for backups must be identified. The Client should retain copies of its original materials and use any available export functions. A Client backup obligation does not excuse failure to perform backup or restoration services we agreed to provide. 15.5 Security testing, penetration testing, incident response or compliance assessment requires a defined, authorised scope before it begins. Reports describe the agreed assessment, not a guarantee that every vulnerability has been identified. Destructive testing and access to third-party systems require specific lawful authorisation. 16. Marketing, advertising and social-media services 16.1 We provide the activities and outputs agreed, not a guarantee of sales, profit, lead quality, rankings, follower growth, virality, advertising approval or return on advertising spend, unless a specific result obligation is expressly accepted. 16.2 Campaign budgets, advertising accounts, target markets, creative approval and authority to publish must be agreed. We will not exceed an approved spending limit or materially change the campaign’s purpose without authority. The Client remains responsible for its offer, fulfilment, customer service and substantiation of claims it supplies. 16.3 Platform decisions, auctions, market conditions and audience behaviour may affect results. We remain responsible for the professional care and reporting actually promised. Estimates, examples and past performance are not contractual guarantees unless expressly adopted as such. 16.4 Influencer engagements, music rights, image releases, advertising disclosures and regulated claims require appropriate approvals. We will perform any compliance-related tasks expressly included in scope, while the Client must obtain specialist review where that review remains its responsibility. 17. AI-assisted services, agents and automation 17.1 Where disclosed in the Order or product description, we may use AI-assisted tools for generation, editing, development, research or automation. AI output may contain inaccuracies, unexpected elements or similarities to other output. Commercial permissions and intellectual-property protection depend on applicable law and the relevant licences; we do not promise rights that we cannot grant. 17.2 We will apply the human review and quality controls included in the service. The Client must provide accurate inputs and review business-specific facts and intended use. Neither Client approval nor the use of AI excuses our failure to perform agreed checks or comply with duties applicable to us. 17.3 The parties will comply with the AI disclosure, labelling, human-oversight and other requirements applicable to their respective roles and uses. Legally required provenance information, labels and notices must not be removed. We may refuse a request that requires unlawful or misleading publication. 17.4 AI agents and automations may take only actions within the permissions and scope authorised for them. Financial commitments, deletion, external publication or other material actions require the approval controls agreed for the project. The Client must not enable a use beyond the assessed scope without an appropriate review. 17.5 High-risk, safety-critical or regulated use, including consequential decisions about people, is excluded unless specifically assessed and accepted under a suitable agreement. We do not provide legal, medical or investment advice merely by supplying software or generated content. 17.6 Client-provided prompts, files, customer data and confidential material may be processed only under the agreed data arrangements. We will not use the Client’s confidential information or personal data to train our own general-purpose models without a separate lawful arrangement. Third-party processing must follow the disclosed provider arrangements and applicable data-protection duties. 18. Plugins, extensions, digital resources and training 18.1 A product schedule or listing must identify the product’s functionality, delivery or access period, licence scope, supported systems, material third-party dependencies, external fees and support/update commitments before purchase. These terms do not replace those product-specific disclosures. 18.2 A licence to use a plugin, extension, template, course or digital resource does not include its development source, editable authoring files or permission to resell or publicly redistribute it unless expressly stated. Rights necessary for the advertised use and any mandatory rights remain available. 18.3 Where a product uses the Client’s own API key or third-party account, the Client contracts with and pays that provider as disclosed. We must not use those credentials outside the authorised purpose. Consumption controls and limits are only those actually described for the product. 18.4 We may make changes necessary for security, legal compliance or compatibility with a materially changed third-party service. Further changes to ongoing consumer digital products require a valid contractual reason, no additional cost, appropriate information and any legally required cancellation or continued-access option. We will not use this clause to remove an essential paid feature without an appropriate remedy. 18.5 Download delivery does not automatically eliminate statutory withdrawal, conformity or update rights. Product-specific consumer information and valid early-performance consents must be supplied separately where required. 19. Subscriptions and reserved capacity 19.1 The Order identifies whether a service is one-off, fixed-term or recurring, together with the billing interval, initial duration, included capacity, renewal arrangement and cancellation method. No recurring charge is created solely by these general terms. 19.2 Unless another lawful arrangement is clearly agreed, recurring services run month to month and may be cancelled by either party with effect at the end of the current monthly service period. A cancellation received before renewal prevents renewal. Statutory rights to end a contract sooner remain unaffected. 19.3 “Unlimited requests” means requests may be submitted without a numerical submission cap; it does not mean unlimited simultaneous work, staff availability or completed deliverables. Any work-hour cap, task limit, concurrency limit, queue arrangement and non-rollover rule must be stated clearly in the purchased plan before acceptance. 19.4 Unused reserved capacity does not roll over only where that arrangement was expressly disclosed and we made the promised capacity available. Capacity we failed to provide is not treated as used. Extra work, expedited delivery or a plan upgrade requires agreement before additional charges. 19.5 Cancellation does not automatically create a refund for an unused part of a current service period where the agreed service remains available. Rights arising from withdrawal, non-performance, a material change, defects or another legal ground are unaffected. Consumer renewal and cancellation requirements take priority. 20. Confidentiality and publicity 20.1 Each party must protect the other’s non-public business, technical and personal information with appropriate care, use it only for the agreement and disclose it only to authorised people who need it and are subject to suitable confidentiality duties. 20.2 Confidentiality does not cover information demonstrably public without breach, already lawfully known, independently developed without misuse, or lawfully received without restriction. A required legal disclosure is permitted, with notice where lawful and reasonable steps to limit unnecessary disclosure. 20.3 Portfolio, Publicity and Self-Promotion 20.3.1 Portfolio Permission For projects commissioned for business or professional purposes, and subject to this section and any binding individual agreement, AslanStudios may showcase selected Final Deliverables and accurately describe the services performed for the Client. To the extent the Client controls the necessary rights, the Client grants us a non-exclusive, worldwide, royalty-free licence to reproduce, display, publish and communicate those selected materials solely to demonstrate and promote our work and services. We reserve corresponding limited portfolio rights in the work we create. No separate approval is required for each publication that falls within this permission. This permission does not extend to confidential information, protected personal data or materials whose publication would infringe third-party rights. 20.3.2 Services and Work Covered This permission covers work we create, design, produce, develop, build, configure, adapt, improve, maintain or upgrade under the relevant agreement, including branding, graphic design, copywriting, photography, video, animation, marketing materials, AI-assisted creative outputs, websites, online stores, applications, interfaces, dashboards, integrations, automations and other agreed deliverables. For software and technical projects, this permission covers permitted visual examples and descriptions of our contribution. It does not authorise unrestricted access to the underlying system, publication of private source code or disclosure of protected technical information. 20.3.3 Permitted Channels and Presentation Permitted uses include our websites, portfolios, social-media posts, stories, reels, showreels, case studies, proposals, presentations, professional directories, award submissions and digital or printed promotional materials. These uses may appear on AslanStudios’ accounts and on personal or professional accounts operated by the service provider identified in the agreement to showcase that provider’s work. We may create screenshots, excerpts, short recordings, mockups and reasonable presentation edits, including cropping, resizing, captions and compilation into showreels, provided these do not materially misrepresent the work, the Client or our contribution. 20.3.4 Publication Timing We may publish the relevant work only after the Client has lawfully released it to the public, authorised its public release, or expressly permitted earlier portfolio publication. Delivery, payment, internal approval, private deployment, a staging link or access to a restricted system does not, by itself, constitute public release. We will respect applicable launch embargoes and agreed publication dates. Public release of one part of a project does not authorise disclosure of its unreleased or confidential parts. 20.3.5 Client Identification and Accurate Attribution Within the scope of the rights granted under this section, we may use the Client’s business name, logo and public website link to identify the project and accurately describe our involvement. We will not imply that the Client endorses our business, that an ended relationship is ongoing, or that work created by another party was created by us. Client quotations, testimonials and non-public performance figures require express approval before publication. Paid advertisements featuring the Client’s identity or work also require separate approval. Applicable white-label, subcontracting and end-client identification restrictions remain unaffected. 20.3.6 Confidentiality, NDAs and Publication Restrictions Any applicable non-disclosure agreement, confidentiality undertaking, no-publicity provision, white-label restriction or individually agreed publication restriction takes priority over this portfolio permission to the extent of any conflict. The Client should identify requested confidentiality, anonymity, embargo or portfolio-exclusion requirements before accepting the relevant proposal or Order so that the parties can agree and record those requirements. Restrictions may also be agreed later. A separate signed NDA is not required for confidentiality obligations arising under these Terms, another binding agreement or applicable law. Failure to request or sign an NDA does not make confidential information publishable. 20.3.7 Protected Information, Personal Data and Third-Party Rights This permission does not authorise publication of confidential strategies, private correspondence, customer or employee records, non-public financial information, credentials, API keys, security findings, private source code, database contents or other protected information. Private dashboards and internal systems may be demonstrated only with specific permission and appropriate redaction, anonymisation or synthetic demonstration data. Removing a name alone is insufficient where the information remains identifiable or confidential. The Client grants only rights it is entitled to grant. Third-party licences and restrictions remain applicable, including those affecting photographs, footage, music, fonts, stock assets, software and brand materials. Identifiable individuals, their images, voices and other personal data may be featured only where we have the necessary lawful basis and any required permissions or releases covering that promotional use. Acceptance of these Terms is not a substitute for separate consent where such consent is required. 20.3.8 Relationship to Ownership, Source Files and Project Completion This portfolio permission is separate from the Client’s usage rights, any agreed source-code delivery, and any transfer or grant of intellectual-property rights. Unless a subsequent agreement expressly changes it, this permission continues after payment, delivery, project completion or termination, subject to the restrictions in this section and applicable law. It does not authorise selling the Client’s materials, licensing the Client’s brand for unrelated purposes, distributing the Client’s project as a reusable product, or disclosing source code or production materials otherwise excluded from publication. 20.3.9 Objections, Corrections and Removal The Client may contact us using the contact details in these Terms to raise a confidentiality, privacy, security, third-party-rights or accuracy concern, identifying the affected material and the reason for the concern. We will promptly assess the concern and, where justified or legally required, suspend publication, correct, anonymise or remove the affected material within an appropriate period, acting sooner where urgency or law requires. We will consider other reasonable removal requests in good faith. We cannot guarantee deletion of independent reposts, search-engine caches or copies outside our control. This does not limit any obligation to take reasonable removal steps or any liability for unlawful publication. Applicable withdrawal, objection, erasure and other statutory rights remain unaffected. 20.3.10 Consumer Projects and Earlier Agreements For projects commissioned by a consumer for purposes outside their business or profession, portfolio publication requires separate express permission. This section applies only where it forms part of the agreement between the parties. It does not retrospectively override earlier confidentiality promises, portfolio exclusions or other existing rights. Portfolio use of an earlier project remains subject to the agreement applicable to that project unless the parties agree otherwise. 20.3.11 Platform and assistant exclusions This commissioned-project permission does not apply merely because a person registers for Aslax, installs Aslanana, connects an account, uploads a file, generates content or uses an AI assistant. Those activities grant only the service and publication permissions specifically described in Parts D–F. No general licence to publicise private user material arises from these terms. 20.4 Confidentiality continues after termination for as long as the information remains confidential. Trade secrets and personal data receive the protection required by law. General skills may be reused only without misusing protected information. 21. Personal data and service providers 21.1 Each party is responsible for the data-protection obligations applicable to its actual role. Where we process personal data on the Client’s behalf, the parties must put an appropriate data-processing agreement in place before that processing, including the required instructions, security terms and subprocessor arrangements. 21.2 These terms are not a substitute for a privacy notice, a data-processing agreement, an international-transfer safeguard or consent where consent is legally necessary. The Client must not provide sensitive or regulated personal data for an unapproved purpose or environment. 21.3 We may use authorised suppliers for activities such as hosting, payment processing, file delivery, communications and AI processing in accordance with the relevant agreement and law. We remain responsible for obligations that apply to us when selecting or using them. 21.4 Data retention, deletion, subprocessors, locations and security claims must match the actual service. We make no general promise that all data bypasses us, is never shared with a processor or is always deleted within a fixed third-party retention period. The applicable privacy notice and processing agreement explain the verified arrangements. 21.5 Return, export and deletion of personal data follow the processing agreement and applicable law, including lawful record-retention requirements and data-subject rights. Source-code ownership is not a basis to disregard those duties. 22. Acceptable use and lawful instructions 22.1 The Client must not use the services for fraud, unlawful impersonation, harassment, infringement, unauthorised access, malicious code, non-consensual intimate content, deceptive manipulation or other unlawful activity. The Client must have the rights and authorisations required for supplied materials and instructions. 22.2 Requests involving a person’s likeness, voice, sensitive information or third-party branding must have an appropriate lawful basis and required permissions. We may reject work outside the agreed service boundaries or our disclosed content policies before acceptance, and may refuse unlawful instructions during a project. 22.3 A refusal or suspension does not automatically forfeit all advance payments. Fees and any refunds are assessed under the termination provisions and applicable law. We remain accountable for our own unlawful acts and cannot transfer that responsibility through Client approval. 23. Suspension, delay and termination 23.1 Either party may terminate for a material breach where permitted by law, ordinarily after written notice describing the breach and a reasonable opportunity to remedy it. Immediate suspension or termination may be appropriate for a serious security risk, unlawful activity or another legally sufficient urgent reason. 23.2 For overdue undisputed payment, we may suspend affected unpaid work or a recurring service after an appropriate reminder and notice, to the extent proportionate and lawful. We will consider the operational effect and reasonable measures to avoid unnecessary loss. Good-faith statutory withholding rights are preserved. 23.3 A client delay may justify pausing and rescheduling the project after notice. A prolonged failure to cooperate may lead to termination only on an applicable contractual or statutory basis. A project is not automatically completed or fully earned merely because the Client has not replied for a particular number of days. 23.4 We will not insert hidden disabling mechanisms, deliberately damage Client systems, delete Client Data as leverage or obstruct lawful recovery of Client-owned accounts. A lawful suspension of our hosted service is distinct from unauthorised interference with a Client-controlled system or a fully paid continuing software licence. 23.5 We will account for work performed, services made available and other amounts lawfully due. Unearned advance payments will be returned where required. Accrued payment rights, confidentiality, properly granted continuing licences and provisions intended to survive remain effective. 24. Cancellation and refunds 24.1 There is no general exclusion of refunds “regardless of circumstances”. Withdrawal, defects, non-performance, termination and other mandatory remedies remain available where their conditions are met. 24.2 For a project governed by German contract-for-work rules, the Client’s ordinary termination and our resulting remuneration are assessed under the applicable law, including section 648 BGB where applicable. Any remuneration for unperformed work must account for legally required deductions, including saved expenditure and relevant substitute earnings. We do not automatically retain the entire advance. 24.3 For services, subscriptions and digital products, cancellation and settlement depend on the applicable legal regime and the agreed service period. Properly incurred and approved non-cancellable third-party expenses may be included only where contractually and legally recoverable, without double recovery. 24.4 A change of preference or a failure to achieve an unpromised marketing outcome is not, by itself, a defect. This does not prevent a remedy where we failed to supply agreed work, misrepresented the service or otherwise breached the contract. 24.5 We will explain material deductions and refund amounts properly due within the legally required period. No administrative charge or processing fee is deducted from a statutory refund unless the law permits it. 25. Exit, export, migration and storage 25.1 On expiry or termination, the parties will identify what must be delivered, returned or exported under the Order, any processing agreement and applicable law. The Client remains entitled to its materials, relevant business data, client-owned account access and Final Deliverables for which the applicable delivery conditions have been met. 25.2 Unless a more protective arrangement applies, we will provide one standard export of Client Data in an available commonly used format upon timely request at the end of a hosted service, together with a reasonable retrieval opportunity. The service schedule must describe exportable data, relevant exclusions and the applicable retrieval period before acceptance. 25.3 Where mandatory switching or data-export rules apply, those rules control, including applicable assistance, notice, transition, retrieval and charging requirements. We will not condition a mandatory export on purchase of our source code or charge an unlawful exit fee. A separate compliant switching schedule will be supplied where required. 25.4 Data export does not automatically include our protected backend source, private development history, other clients’ material or non-transferable third-party assets. It must nevertheless contain the data and information we are contractually or legally required to provide. An export is not a promise that a different platform can reproduce every function without additional development. 25.5 Custom migration, data transformation, reconstruction on another platform and developer onboarding may be separately quoted where not already included or required without charge. The Client may appoint a replacement provider; necessary authorised cooperation must respect confidentiality and the rights of both parties. 25.6 Final download links remain available for at least 30 days after delivery unless a longer period is agreed or required. The Client should save its deliverables. We do not promise indefinite storage of drafts or working files, but will preserve material needed for unfulfilled delivery duties, agreed support, legal retention or a known dispute. Personal-data deletion follows section 21. 26. Professional standards and liability 26.1 We are responsible for performing the agreed services with the professional care and conformity required by the contract and applicable law. No provision excludes statutory remedies simply because work is digital, creative, AI-assisted or delivered through a third-party tool. 26.2 Our liability is unlimited for intent and gross negligence; death, personal injury or damage to health attributable to our fault; fraudulent concealment; an expressly assumed guarantee to the extent applicable; and liability that cannot lawfully be limited, including under mandatory product-liability or data-protection rules. 26.3 For ordinary negligence causing a breach of an essential contractual obligation, our liability is limited to the loss foreseeable at contract formation and typical for the agreement. An essential obligation is one whose performance makes proper contractual performance possible and on which the Client may ordinarily rely. 26.4 Subject to section 26.2 and mandatory law, liability for ordinary negligence in breach of other obligations is excluded. These limitations apply correspondingly to our representatives and people used to perform the agreement. They do not exclude non-damages remedies such as legally available correction, reduction, termination or repayment. 26.5 Each party must take reasonable steps to mitigate loss. Any contribution by the Client to the cause or extent of damage is assessed under applicable law. There is no blanket exclusion for all direct losses, lost data or third-party incidents, and no assumption that every claim is capped at the invoice amount. 27. Third-party claims — business clients only 27.1 A business Client is responsible for third-party claims to the extent caused by its culpable breach concerning the rights in Client Materials, unlawful instructions or unauthorised use. Subject to applicable law, it must reimburse reasonable damages and necessary defence costs attributable to that breach, not amounts caused by our own fault or an unauthorised settlement. 27.2 We will promptly inform the Client of a relevant claim, provide reasonable cooperation and allow a reasonable opportunity to participate in the defence. Neither party may impose an admission, non-monetary obligation or settlement on the other without its consent, which must not be unreasonably withheld where its interests are adequately protected. 27.3 This clause does not make the Client liable merely for approving work, and does not transfer our responsibility for rights in materials we independently supply. Consumer liability is governed by the applicable statutory rules rather than this indemnity. 28. Events outside reasonable control 28.1 A party affected by an event genuinely outside its reasonable control must notify the other promptly, explain the likely impact and take reasonable mitigation steps. Relief extends only to performance actually prevented or delayed and only for the relevant period. 28.2 Ordinary workload, avoidable resourcing problems and preventable failures are not automatically treated as such events. A supplier outage does not excuse a resilience or alternative-supply commitment expressly undertaken. 28.3 The parties will agree a reasonable revised plan where possible. If the agreed purpose can no longer be achieved or a delay becomes unreasonable, statutory adjustment, termination and refund rights remain available. Payment is not automatically earned for services never supplied. 29. Additional consumer protections 29.1 Consumers retain all mandatory protections, including required pre-contract information, statutory conformity and defect remedies, digital-product updates and any applicable withdrawal rights. A business-only label does not remove those rights from a person who is legally a consumer. 29.2 Where a withdrawal right applies, we will supply the applicable withdrawal instructions and model form separately. A request to start a service before the withdrawal period ends is distinct from consent to immediate supply of non-physical digital content. Any loss of withdrawal rights or obligation to pay for early performance arises only when the relevant legal conditions have been met. 29.3 The required early-performance consents and acknowledgements must be expressly obtained where applicable; they are not inferred merely from acceptance of these terms. We will provide the required contract confirmation on a durable medium. 29.4 Online withdrawal functionality and subscription cancellation functionality will be provided where legally required. Cancellation or withdrawal is not restricted to an unnecessarily burdensome channel. A consumer may use the statutory means of exercising their rights. 29.5 Changes to consumer digital products, subscription renewals and price changes are subject to the applicable consumer rules. These terms do not authorise a less favourable arrangement where the law prohibits one. 30. Governing law, disputes and notices 30.1 For Studio Provider contracts, the agreement is governed by the laws of the Federal Republic of Germany. This choice does not deprive a consumer of mandatory protection available under the law that would apply without the choice, and does not override other overriding mandatory rules. Aslax platform contracts have the separate governing-law provision in E.13. 30.2 For Studio Provider disputes, the competent courts are determined under applicable statutory jurisdiction rules unless a valid individual jurisdiction agreement states otherwise. These terms do not assert that the Studio Provider has a registered German place of business or compel a consumer to use a court contrary to mandatory law. E.13 governs permitted venue arrangements for the Platform Provider. 30.3 Studio complaints and contractual notices may be sent to aslan@aslanstudios.eu. Aslax notices use the platform contacts in E.13. The parties should attempt a practical resolution, but doing so is not a condition preventing timely court action, urgent relief, regulatory complaints or statutory rights. These general terms do not require mandatory arbitration. 30.4 Unless required by law or separately agreed, we do not undertake to participate in consumer conciliation proceedings. Any legally required dispute-resolution information will be supplied separately and accurately. 31. Changes and remaining provisions 31.1 Updated website terms apply to new agreements when properly incorporated. Changes to an existing agreement require an appropriate legal basis and the necessary agreement or procedure. Mere continued use does not automatically accept a change in source-code ownership, price or other essential rights. 31.2 An invalid or inapplicable standard term is dealt with under applicable law; it is not automatically rewritten into the most restrictive term that might have been valid. The remainder of the agreement continues only to the extent the law permits. 31.3 A delay in exercising a right is not automatically a waiver. No provision creates employment, a partnership, exclusivity or authority for either party to bind the other beyond the authority expressly granted. 31.4 Specific package quantities, prices, turnaround commitments and revisions are defined in the accepted Order and applicable Parts B–F. Historical offers included in a schedule apply only where expressly sold and accepted. This document does not revive expired promotions, increase an existing price or reduce an already promised deliverable. PART B — MONTHLY DESIGNER AND VIDEO EDITOR SUBSCRIPTION B.1 Scope and service period This schedule applies to the monthly design and video-editing service, including an expressly accepted offer based on the former Black Friday subscription. It covers graphic design for social posts, advertising and other agreed digital content; editing for promotional videos, advertisements, reels and other agreed multimedia; and revisions within the approved brief. A service month runs from the agreed subscription start date. The Order specifies whether the purchase is a single month or a recurring subscription, the fee and the billing date. Publication of these terms does not reactivate a historical Black Friday price or make an old promotion permanently available. An already agreed promotional entitlement remains governed by its accepted conditions. B.2 Capacity and request queue The historical capacity choices are up to 80 hours of active work per service month OR up to 20 design tasks and 10 video edits per service month, depending on the agreed complexity and scope. For a new Order, the purchased plan must identify which capacity model applies, what constitutes a task or edit, the supported complexity and any allocation between services. These alternatives are not automatically cumulative; we will not impose an undisclosed “whichever limit is reached first” rule or choose a less favourable basis retrospectively. Clients may submit unlimited requests to the queue, but one task is worked on at a time unless additional concurrency is expressly purchased. Unlimited requests do not mean unlimited completed work, unlimited revisions, guaranteed urgent capacity or a full-time employee. Complex deliverables and how they use the agreed allowance must be identified before work begins. We will not silently split a previously accepted task into additional chargeable tasks. Unused capacity rolls over only if the purchased plan expressly provides for it. An expressly disclosed non-rollover rule applies only to capacity we actually made available. Additional tasks, extra hours, a higher plan or expedited delivery require agreement before extra charges. Work deferred because we did not supply promised capacity remains subject to appropriate completion, credit or other remedies. B.3 Revisions and turnaround The subscription includes up to three revision rounds per project within the approved direction, unless the accepted Order expressly specifies a different package. Each round is one consolidated set of feedback. A new concept, substantially changed brief or additional output is separately scoped. Correction of our failure to meet the agreed specification does not consume the creative revision allowance. For ordinary subscription tasks, the target is 24–72 hours after the task reaches the active queue and all required inputs are available, subject to the complexity and availability disclosed in the Order. Any expressly promised 24–48-hour commitment remains applicable to the task for which it was agreed. Business-day treatment, priority arrangements and a binding deadline must be stated before acceptance; there is no general commitment to continuous weekend or overnight staffing. B.4 Payment, renewal and cancellation The agreed monthly fee is payable in advance to the extent lawful. A one-month purchase does not renew unless recurring billing was selected. A recurring monthly subscription may be cancelled before renewal with effect at the end of the current paid monthly period, using the agreed contact or cancellation facility. It does not require seven additional days’ notice under this new schedule. Mandatory cancellation and withdrawal rights remain unaffected. Unused time does not by itself give a discretionary refund where the promised capacity remained available. Non-performance, defects, lawful termination, statutory withdrawal and other mandatory refund rights remain protected under Part A. Approved external costs are separate unless included in the Order. B.5 Personal service, cooperation and misuse Where the subscription is sold as personally supplied by the Studio Provider, that personal-service commitment will be honoured; substitution of other production personnel requires agreement. Use of disclosed software and AI tools does not, by itself, change that commitment. The relationship is an independent service arrangement, not employment or entitlement to exclusive full-time staffing. The Client must provide a clear brief, lawful assets and timely consolidated feedback. Threats, harassment, unlawful requests, credential misuse or attempts to bypass agreed capacity may justify proportionate action under section 23. A large request queue, reasonable criticism or a genuine payment dispute does not automatically forfeit prepaid fees. Failure to cooperate may pause scheduling after notice, not automatically complete the work. B.6 Deliverables, rights and confidentiality The Client receives the final exports and usage rights in the Order and sections 6–11. This new schedule does not include raw footage, layered design files, editable project files, private prompts, templates or source code unless expressly agreed. An earlier binding ownership or delivery promise is not reduced retrospectively. Confidentiality and permitted studio portfolio use follow section 20. PART C — ASLAN ATELIER — FOUNDING BRAND EDITION C.1 Nature of the offer Aslan Atelier is the Studio Provider’s private visual-campaign production service. The Founding Brand Edition is a selected-brand launch offer, not a permanently available public subscription. An application is a request for assessment, not acceptance of a paid project. Before a contract is formed, we may decline an unsuitable brief, inadequate assets, an unrealistic timeline or a request outside our lawful service scope. After acceptance, cancellation and performance obligations follow the agreement. C.2 Founding Brand Edition package Where expressly offered and accepted as the Founding Brand Edition, the private launch price is €450, subject to the final tax-inclusive amount that must be disclosed to a consumer before purchase. The package includes: • 15 premium campaign visuals; • one cinematic 20-second brand film; • a 3D / motion product showcase; • AI model and location direction; • a creative campaign concept and brand style direction; • final exported files in one primary campaign format; • one refinement round; and • a delivery target of 5–7 business days after the commencement conditions below are satisfied. The Order records the creative treatment and how the 3D / motion showcase is delivered, including any separate output expressly promised. The phrase does not by itself include editable 3D scenes, meshes or production projects. The package quantities are not reduced merely because the campaign direction is customised. An additional or different deliverable requires an agreed scope change. This retained launch offer applies only where the Order expressly accepts it. It does not reopen a closed promotion, change an existing price or include an Aslax account, subscription or credit pack. The use of Aslax in production does not make Aslax, LLC the supplier of the Atelier engagement. C.3 Commencement and price information Production starts once the agreed advance payment has been received, the agreement accepted, required assets supplied and creative direction confirmed. Any taxes and permitted additional charges must be disclosed before purchase. Any small-business VAT treatment applies only where the Studio Provider actually qualifies; these terms do not assert a tax status. Processing fees are not automatically chargeable to the Client or deductible from statutory refunds. C.4 Exclusions Unless separately agreed, the package does not include physical shoots, models, studios or locations; paid advertising management, media buying or ad spend; a full brand identity or website; printing; full-website copywriting; unlimited revisions; extra format conversions; raw, editable or source files; prompts, workflows, templates, drafts or unused concepts; legal or regulatory clearance; third-party media, music or stock licence fees; or a guarantee of advertising or platform approval. Necessary licences for our own supplied material must nevertheless permit the usage rights we promised. C.5 Assets, accuracy and approval The Client provides relevant logos, product photographs, website and social links, colours, guidelines, product facts, campaign goals, references, required copy and intended usage. The Client must have the rights needed for those materials and instructions. The Client reviews product and brand accuracy, copy, prices, claims, cultural suitability and intended markets before publication. We remain responsible for our own agreed professional checks and actionable errors; approval is not a blanket release from liability. C.6 Timeline and refinements The 5–7-business-day period is a delivery target unless the Order makes it binding. Business days are Monday to Friday, excluding applicable public holidays at the Studio Provider’s disclosed place of business, unless the Order states another calendar. Missing materials, delayed feedback and accepted scope changes may reasonably adjust the schedule. We will communicate a material delay and its effect. The one refinement round covers reasonable adjustments within the approved direction, such as minor colour, visual, copy, crop or style changes. It does not include a new concept, product, campaign direction, script or storyline; additional images or films; multiple new formats; or major changes after final delivery. Separately requested work is quoted before it becomes chargeable. Defect correction remains separate from the refinement allowance. C.7 AI-assisted production and use rights The workflow may use Aslax and other disclosed creative tools for images, environments, fictional model scenes, backgrounds, motion concepts, visual effects, editing, upscaling and campaign visualisation. We curate and refine the outputs as included in the service. Similar AI elements may exist elsewhere; no universal uniqueness or legal-clearance guarantee is given. After payment properly due for the deliverables, the Client may use final exports for its brand’s website, social media, advertising, launches, e-commerce, presentations and promotion under section 9. Source materials and Provider Technology remain excluded under sections 6–11. Separate licences and mandatory rights remain applicable. C.8 Portfolio, prohibited work and third-party claims Section 20.3 governs portfolio use; an NDA or binding publication restriction takes priority. Unreleased materials, confidential information and protected personal data are not automatically publishable. Prohibited instructions are governed by section 22. The service does not include explicit adult content, deceptive impersonation, fraudulent endorsements or unlawful claims. Responsibility for third-party claims is allocated under section 27, not by an unlimited indemnity for everything a client approves. C.9 Cancellation, delivery and communications Cancellation and refunds follow sections 23–24, taking account of work performed, legally recoverable commitments and required deductions. Creative planning, generation and editing within scope are project work, but the entire fee is not automatically forfeited when production begins. Failure to achieve unpromised sales, engagement or platform approval is not by itself a defect. Delivery may be by email, a download link, cloud folder or agreed portal. Final download availability follows section 25.6. Clients should save their files; indefinite storage of working material is not included. Email, agreed messaging channels, forms and calls may be used for project communication. More than 14 days without a necessary response may lead to a notified pause and rescheduling; it does not automatically mean completion, acceptance or loss of all fees. PART D — ASLANANA PHOTOSHOP AI PLUGIN D.1 Product, provider and edition Aslanana is a software plugin integrating supported AI creative functions into Adobe Photoshop. The purchased edition’s listing must identify supported Photoshop and operating-system versions, functionality, licence period, seats or devices, required accounts, billing model, updates and support before purchase. This schedule does not promise that every edition supports video, every model or every operating system. The Studio Provider supplies the legacy direct-API edition unless a different provider is expressly identified before that purchase. Aslax-connected services supplied by Aslax, LLC are governed by Part E. A migration to an account-connected edition, new recurring fee or different contracting provider requires appropriate disclosure and agreement; an update does not silently change an existing contract. D.2 Legacy bring-your-own-key edition The legacy arrangement described in the original Aslanana terms connects supported requests to Replicate using the user’s own Replicate API key. The user must maintain a valid Replicate account, meet its applicable terms and model licences, and pay its charges. Plugin fees do not include Replicate compute or an Adobe subscription unless the Order expressly says so. Relevant prompts, selected images, uploaded files and instructions are transmitted for the requested processing. A direct provider connection does not establish that no technical metadata, local cache, support data or other data exists elsewhere. The edition-specific privacy information must accurately explain the actual route and retention. Replicate documents a default one-hour cleanup for specified prediction data created through its API, while web-created predictions follow a different retention rule. That external default is not a guarantee that all copies in Photoshop, on a user device, in support records or in another service are deleted within an hour. Save required outputs and consult the provider information disclosed for the edition. D.3 Aslax-account edition or mode Where an edition expressly offers Aslax-account connectivity, the applicable Aslax plan, permissions, usage limits and credit rules govern operations performed through that account. A user’s Replicate balance and Aslax credits are separate and are not interchangeable unless a specific integration expressly provides otherwise. The product must disclose which route and charging method will be used before a paid operation. This conditional provision does not represent that an account-connected edition or a user-key option is available in every release. We will not silently switch a paid job to an undisclosed chargeable route. D.4 Licence and source files During the purchased licence or service period, the user receives a non-exclusive right to install and use the plugin for its described purpose within the purchased seats or devices. Commercial use of lawful generated outputs is subject to applicable rights, model licences and the purchased plan, not a right to redistribute the plugin itself. The licence does not include the plugin’s source code, private repository, build environment, proprietary authoring files, resale rights or white-label rights unless separately agreed. Client-supplied inputs and generated outputs are not treated as our internal Project Source. Sections 6–11 preserve mandatory software backup, testing and interoperability rights. D.5 Inputs, outputs and authorisations The user retains its lawful rights in submitted content. Any rights in outputs remain subject to applicable law and third-party licences. No guarantee is given that AI output is accurate, exclusive, non-infringing or suitable for a regulated use. Users must review outputs and hold necessary copyright, privacy, likeness, voice and other permissions. Our own contractual and statutory obligations remain unaffected. Opening a file in Photoshop, owning a copy of a photograph or providing an API key is not authority to infringe another person’s rights. Users must not bypass safety controls, exceed purchased access or use the plugin for prohibited activity under section 22 or the applicable provider’s disclosed restrictions. D.6 Credentials and troubleshooting Users must protect and, when necessary, revoke their API keys. We may use credentials only for the authorised feature and must protect any credentials we actually handle. A user should not include live secrets, confidential documents or unnecessary personal data in screenshots or support reports. Necessary troubleshooting access must be authorised and proportionate. Charges made directly by a user’s provider account are governed by that provider relationship. A refund of a plugin licence does not automatically refund third-party compute. This distinction does not excuse our own unauthorised use, duplicate request handling or other actionable fault. D.7 Updates, support and discontinuation Subscribers receive the updates and priority support described in the purchased listing. Priority means the stated support arrangement, not a guarantee of immediate resolution or 24-hour staffing unless promised. Supported versions, service periods and compatibility limits must be disclosed before purchase. Necessary security, legal and compatibility changes may be made under section 18.4. Material loss of paid functionality is subject to required notice and remedies. Ending support or withdrawing an edition does not remove mandatory update, conformity, refund or already granted continuing-use rights. An “as is” description of an experimental feature does not replace section 26. D.8 Privacy and publicity The limited content permission is for delivering and securing the requested operation, not for unrelated promotion or training our own general-purpose model. We do not receive a portfolio licence to a user’s Photoshop files or private generations merely because the plugin is installed. A separately commissioned studio project may have its own section 20.3 permission. The applicable Privacy Notice and processing arrangements remain separate. PART E — ASLAX PLATFORM, ACCOUNTS, CREDITS AND CONNECTED FEATURES E.1 Platform operator and service scope Aslax, LLC is the Platform Provider. Aslax supplies access to its own hosted AI creative software, with supported tools for generation, editing and related image, video, audio, text, 3D, upscaling and workflow functions. Only the features included in the selected plan and actually offered are promised. It is not a marketplace for third-party sellers, a payment-facilitation service or a peer-to-peer payment system. Part A applies with this Part E when incorporated into an Aslax agreement. Studio package quantities and personal production commitments do not apply to self-service platform access. Using Aslax internally to fulfil a studio project does not create a separate Aslax subscription for the studio client. E.2 Eligibility, accounts and teams Users must be at least 18 and of legal age and capacity to enter the agreement in their jurisdiction. An authorised representative may accept for a business. Account and billing information must be accurate. Do not sell accounts, share credentials outside permitted team access, create false identities or circumvent restrictions by opening replacement accounts. Use supported team invitations where provided. Workspace owners and authorised administrators manage memberships and shared assets within their permissions. Organisation-controlled content may remain with the organisation when a member leaves; joining a workspace does not transfer unrelated personal content. Members must be told about applicable administrative access. Account responsibility does not exclude Aslax’s responsibility for its own security failures. E.3 Plans, purchases and recurring billing Before purchase, the order must show the selected plan or add-on, final payable price and tax information, billing interval, duration, included usage, important limits, renewal arrangement and any required subscription eligibility. A one-time credit-pack purchase does not itself authorise recurring charges. The checkout identifies the payment provider and any merchant-of-record or reseller role. Subscriptions renew on the disclosed billing cycle unless cancelled before renewal. Cancellation through account settings or support stops future renewals while the current paid period ordinarily continues. Mandatory earlier termination and withdrawal rights remain available. Plan changes normally apply with the effective date and proration shown in the billing flow before confirmation; no undisclosed extra charge is authorised. E.4 Credit allocation, consumption and expiry Credits are non-transferable contractual units for Aslax software usage, not currency, a withdrawable balance or an investment. A statement that credits have no cash value does not remove a statutory entitlement to repayment for an underlying purchase. Subscription allocations and reset rules are those shown for the accepted plan. Each add-on pack must disclose its expiry and eligibility before purchase. The accepted purchase conditions govern the pack; later catalogue edits do not shorten an already purchased expiry. No universal 45-day expiry is created by these terms. Promotional or founder allocations apply only where their eligibility, limits and validity were expressly offered. The user must be shown the applicable charging unit, credit amount or understandable usage calculation before submitting a paid request. Material factors may include model, duration, resolution, quality, batch size or compute usage. Any reservation, final settlement or further authorised charge must correspond to that disclosed basis. Future pricing changes do not retrospectively increase a completed operation’s charge. No automatic top-up, additional purchase or charge beyond the selected operation is authorised solely by these terms. A specific opt-in and disclosed limits are required for any offered automatic purchasing feature. Fraudulent grants and accounting errors may be corrected on a documented basis, without confiscating legitimately purchased credits or charging the same operation twice. E.5 Failed operations and billing reconciliation A confirmed paid technical failure with no usable output qualifies for restoration of the credits charged for the failed operation, including a confirmed upstream technical failure. The published service commitment is automatic restoration; support must correct a delayed or erroneous result. Pending jobs and uncertain provider outcomes may be reconciled before final settlement to avoid duplicate charges or restorations. For a partially successful batch, only the failed portion is restored; correctly delivered work remains chargeable. A result that differs from a user’s creative preference is not by itself a technical failure. A slow job is not automatically failed, but delay or a non-conforming result can still give contractual or statutory remedies. A request rejected before chargeable generation starts must not be billed as completed generation. Any separate chargeable check or actual compute already committed must have been disclosed and lawfully authorised. A cancelled or interrupted request is assessed against the work actually performed and the disclosed charging basis. Credit restoration does not remove a cash refund or other remedy required by law, and the same charge is not recovered twice. E.6 Discretionary refunds and statutory rights In addition to mandatory rights, the platform’s subscription refund thresholds are a request within seven days of a first subscription purchase with no more than 25 credits used in that billing period; or, for a renewal, a request within 48 hours with no post-renewal credits used. Any verification must be reasonable and must not delay a statutory remedy beyond its lawful deadline. These thresholds are not a substitute for statutory withdrawal, faulty-service remedies or more protective applicable merchant-of-record buyer terms. Unused subscription time and credits do not ordinarily receive an additional discretionary partial refund. Promotional, bonus and trial credits are not redeemable for cash; expiry rules do not cancel mandatory repayment rights. Duplicate, unauthorised or erroneous charges are investigated and refunded where appropriate. Approved refunds use the original payment method unless a different lawful arrangement is expressly agreed. Contact support@aslax.eu with the account email and relevant order or generation identifier; do not send full card numbers or live credentials. The published support targets are acknowledgement within 24 hours and review within five business days, subject to a necessary review and mandatory legal deadlines. A support review does not extend a statutory refund deadline. EU/EEA consumers normally have 14 days from a distance service contract’s conclusion to withdraw. Signing in, allocating credits, running a generation or downloading an output does not itself waive that right. Early-performance payment and any loss of withdrawal rights require the applicable statutory information, express requests, consents, acknowledgements and confirmation. The separate withdrawal information must be provided for the actual purchase, including any required online function. E.7 User content and platform intellectual property Users retain whatever lawful rights they hold in their inputs and outputs, subject to third-party rights and applicable law. Aslax receives a limited permission to host, copy, process, adapt technically and transmit submitted material as needed to provide, secure and support the authorised service. This is not a general licence to publish private work or use it in unrelated advertising. The platform, private source code, orchestration, interface components, account infrastructure, system instructions and reusable technology remain with their respective rights holders. A subscription or credit purchase does not include their source, model weights, proprietary prompts, repository access or self-hosting rights. The exclusion does not claim ownership of the user’s own prompts, uploads or outputs or override a relevant open-source licence. A user importing material from a URL must have the necessary rights for copying, storage, transformation and submission to the selected processing route. Public availability is not evidence of permission. Aslax may reject unsafe or unsupported formats or technically normalise supported files as disclosed, without authorising infringement. E.8 AI vendors, connected accounts and privacy Requests may use disclosed model, routing and infrastructure providers. The active feature information and separate privacy/provider disclosures identify material processing arrangements. A provider’s retention, training and safety settings may vary by model, route, account and plan. No blanket promise of zero retention or no third-party training is made without an expressly applicable verified arrangement. Where a feature supports the user’s own external account or key, its external billing and permissions must be identified before use. Platform access does not include ownership of third-party provider technology. Appropriate third-party terms are made available for the chosen feature. We remain responsible for our own contractual and data-protection obligations rather than referring every failure to a vendor. Where Vercel AI Gateway or another disclosed route is used, the user must follow the applicable feature, infrastructure and downstream-model restrictions made available before the relevant use. Model and provider names identify integrations, not sponsorship or endorsement. Changes must comply with section 18.4 and E.12; processing changes requiring consent or contract action are not authorised by a general reference to future providers. Business processing is governed by the applicable data-processing agreement. Independent account, billing and security processing is described in Aslax’s Privacy Policy. Using the service is not blanket consent to unrelated marketing, data sale or unrestricted model training. E.9 Safety, moderation and restricted uses Users must follow the disclosed Acceptable Use and AI policies. Prohibited uses include fraud, infringement, harassment, exploitation, unlawful impersonation, non-consensual intimate media, sexual content involving minors, identity misuse, fabricated endorsements, forged evidence, unauthorised tracking, malware, credential theft and circumvention of safeguards. The platform does not offer public face-swap, real-person voice-cloning, deceptive lip-sync or identity-replacement services. Requests involving a real person require the necessary documented rights and permissions; ownership of a photograph alone is insufficient. Consent does not authorise a feature otherwise prohibited by the service. Biometric identification, sensitive-trait inference and unsupervised high-risk decisions are outside standard platform scope. Users must not use the service for prohibited transactions, restricted businesses or conduct contrary to applicable sanctions or export controls. Restrictions apply according to actual law and the disclosed service policy, not nationality alone. Preserve required watermarks, provenance information and AI disclosures. The published Aslax disclosure policy applies when synthetic or materially AI-edited media is shared or used commercially as described in that policy. Requests, payments and public submissions may be subject to proportionate safety, rights or fraud checks. We may block or investigate abuse, give appropriate reasons where lawful and provide the available review route. Genuine complaints are not themselves misuse. E.10 Public community and portfolio use Where community features are offered, submitting content for public posting is a separate act from making a private generation. Posts submitted to the moderation queue are available to the submitter and authorised moderators until approval; approved posts may become public as described in the publishing interface. A public-post submission grants the limited rights necessary to review, host, display and distribute it on the disclosed community surfaces. It does not grant unrelated advertising rights to private files or every creation in the account. Withdrawal or removal is subject to legitimate moderation records, mandatory law and practical limits on independent copies. External promotional use of user content requires separate permission. Part A’s commissioned-project portfolio clause does not apply automatically to self-service platform activity. E.11 Agents, APIs, teams and scheduled work Only actions within the user’s instructions, granted permissions and the product’s approval controls are authorised. Review destinations, recipients, content and displayed charges before external publication, messages, purchases or other consequential actions. Do not give credentials or permission to connect an account you do not control or administer lawfully. Revocation stops future authorised use after processing, but does not recall a delivered message or reverse a completed third-party transaction. Aslax must process revocation appropriately. API and scheduled operations use the same permissions, billing units and plan limits. Cancellation, insufficient credits or revoked permissions can stop queued work, while authorised completed work remains chargeable. Unlimited access does not permit quota bypass, unsupported scraping or resale. E.12 Availability, changes, suspension and exit Model capacity, maintenance, regions and safety controls may affect availability. No continuous uptime or output-similarity guarantee is given beyond an express service commitment. A beta label does not remove the obligation to supply what was sold or the mandatory protections for paid digital products. Necessary changes follow Part A. Material adverse changes to paid functionality or future prices require the applicable advance notice, valid basis and termination or other remedies. Discontinuing an affected paid service must include any refund of prepaid unused service required by the agreement or law. A website edit does not change an accepted credit pack’s conditions. Suspension for non-payment, proven misuse or a serious legal or security risk must be proportionate and comply with section 23. A good-faith charge dispute is not automatically chargeback abuse. Termination does not automatically forfeit every purchased balance or excuse export duties. Account data and outputs must be handled under the disclosed retention/export arrangements, the applicable processing agreement and mandatory switching rules. Part A’s 30-day studio delivery-link promise is not a promise that every temporary provider output URL lasts 30 days. E.13 Liability, governing law and platform policies Part A, sections 26–27, governs professional responsibility, liability limits and business third-party claims, preserving all stated non-excludable liabilities and mandatory customer remedies. No general invoice-only or twelve-month-fees ceiling is created by this consolidated schedule. This is the liability allocation for newly accepted contracts incorporating this edition, not a retrospective change to an earlier contract. For contracts supplied by Aslax, LLC, Delaware law applies, excluding its conflict-of-laws rules, without depriving a consumer of mandatory protection available under the law that would otherwise apply. Delaware state or federal courts are the agreed forum only to the extent such an agreement is valid; mandatory local and consumer jurisdiction rules prevail. This paragraph replaces Part A, sections 30.1–30.2, only for the Aslax platform contract. The applicable versions of Aslax’s Refund / Cancellation, Acceptable Use, AI and Beta policies and any merchant-of-record buyer terms must be supplied or made available before acceptance where relevant. The separate Privacy Policy, subprocessor disclosures, complaint routes and business data-processing agreement remain in place. For this consolidated edition, E.5–E.6 control an inconsistent general platform refund summary, without reducing mandatory rights or a binding individual promise. Later online policy changes follow section 31.1, not automatic retroactive incorporation. Platform notices and complaints may be sent to support@aslax.eu or, for legal and privacy matters, aslan@aslax.eu. Intellectual-property and illegal-content reports may use the platform’s published reporting routes. Reports should identify the material and basis of the concern; a report alone does not establish infringement. Applicable notice, review and appeal duties remain unaffected. PART F — ASLANSTUDIOS AI GPT AND STUDIO AI-ASSISTANT SERVICES F.1 Scope and provider This schedule covers the Studio Provider’s expressly offered AI-assistant configuration and related creative-support, image/content-generation and e-commerce-support services, including the service previously described as Aslanstudios AI GPT. A GPT running within ChatGPT and an assistant built into another website are different delivery models. The listing or Order must identify which is supplied. These terms do not promise that a historical GPT, model or hosting feature remains available indefinitely. F.2 Access, third-party service and fees Use of a third-party-hosted assistant requires the host’s applicable account eligibility, terms and access conditions. A studio purchase does not include a ChatGPT, Adobe or other external subscription unless expressly stated. Availability may depend on host or workspace controls, while the Studio Provider remains responsible for its own paid commitments. No partnership or endorsement by the host is implied. F.3 Permitted instructions and reliance Users must have the necessary rights in prompts, uploaded images and other materials. The assistant is a support tool, not guaranteed professional advice, factual verification, legal clearance or authority to act outside the granted permissions. Review business facts, outputs and intended commercial use. It must not be relied upon for unsupervised safety-critical or regulated decisions. Sections 17 and 22 apply. F.4 Actions and connected services Where external actions or connectors are enabled, the feature must explain the destination, necessary data and permissions. Actions must stay within the authorised scope and approval controls. A general conversation does not authorise an undisclosed payment, publication, account change or deletion. Revoking a connection does not reverse work already lawfully completed. F.5 Content, configuration and portfolio Users retain their lawful rights in submitted materials and outputs. The provider receives only the permissions needed for the service and any separate permission expressly granted. A purchase does not include the provider’s private assistant instructions, reusable configuration, knowledge materials it owns, action implementation or source code unless agreed. A client-supplied knowledge file remains a Client Material. Mandatory rights and third-party licences remain protected. Private conversations, inputs and outputs are not studio portfolio content by default. Separately commissioned business deliverables may be showcased only under section 20.3 and its restrictions. A consumer project or unrelated promotion requires the applicable separate permission. F.6 Data handling and privacy notices For a GPT hosted in ChatGPT, OpenAI’s own privacy and account arrangements govern its processing. Being a GPT builder does not itself give the Studio Provider access to individual user conversations; external actions and direct support submissions may separately transmit information to the Studio Provider or another service. The actual enabled connections must be described accurately. A separately hosted or API-based assistant has a different data route that must be explained in its own privacy information. We do not promise that every prompt is invisible to us, that no third party processes data, that every copy is deleted immediately, or that all processing relies on consent. The relevant Privacy Notice must state the actual controller, purposes, legal bases, recipients, retention, transfer arrangements and user rights. These service terms do not substitute for that notice. F.7 Updates, discontinuation and remedies Host changes, model retirement, security needs or legal requirements may require adjustment. Required information, support, paid continuity commitments and statutory remedies remain applicable. Free or experimental access may be changed within applicable law; a paid service cannot be withdrawn without addressing unfulfilled obligations. Refunds, liability and complaints follow Part A and the Order. F.8 Contact and product relationship Studio assistant support and privacy queries may be sent to aslan@aslanstudios.eu. Questions about processing controlled by a third-party host must also be directed through that host’s appropriate privacy controls or support. Aslax account services remain subject to Part E; a reference to Aslax does not combine the users’ contracts or give the Studio Provider control of Aslax’s entire platform.