Platform Usage Contract

A pdf can be downloaded here.

Table of Content

• Part I. SCOPE
  • Article 1: Definitions
  • Article 2: Platform Usage Contract
  • Article 3: Scope of application
  • Article 4: The PRISMA Platform: access and service prices

• Part II. ACCESS AND CONDUCT RULES
  • Article 5: Registration of the Customer on the PRISMA Capacity Platform
  • Article 6: Creation of an account on the PRISMA Capacity Platform
  • Article 7: Appointment of the User Administrator
  • Article 8: Appointment of the User(s)
  • Article 9: Approval of the System Operator
  • Article 10: Availability of access to the PRISMA Capacity Platform
  • Article 11: Access Key
  • Article 12: Conduct on the PRISMA Platform
  • Article 13: Functionality and suspension of the PRISMA Platform
  • Article 14: Protection of PRISMA’s system security 

• Part III. PROVISIONS REGARDING CONTRACT MODIFICATION, TERMINATION AND PLATFORM DEACTIVATION
  • Article 15: Changes to the GTCs
  • Article 16: Contract termination and deactivation of the Customer
  • Article 17: Deactivation of User Administrators
  • Article 18: Deactivation of Users

• Part IV. OTHER PROVISIONS
  • Article 19: Liability and warranty
  • Article 20: Force majeure
  • Article 21: Use of data
  • Article 22: Confidentiality
  • Article 23: Language and severability clause
  • Article 24: Place of jurisdiction and applicable law

PLATFORM USAGE CONTRACT (PUC) AS OF 15 DECEMBER 2025

Part I. Scope

Article 1: Definitions

 The capitalised words, expressions and abbreviations used in this PUC shall have the meaning as defined in the Glossary to the GTCs, in Regulation (EU) 2024/1789, Directive (EU) 2024/1788, Commission Regulation (EU) 2017/459 (“CAM NC”) or Regulation (EU) No 1227/2011 (“REMIT”). 

Article 2: Platform Usage Contract

1. The Platform Usage Contract (PUC) forms an integral part of the PRISMA General Terms and Conditions (PRISMA GTCs). It is concluded between the Customer and PRISMA European Capacity Platform GmbH (PRISMA) upon the Customer’s acceptance of the PRISMA GTCs by registering or using the Platform. 

Subject to the subscription of further services, additional terms and conditions for the specific service will be applied between the Customer and PRISMA as set out in PRISMA GTCs. 

2. The PUC is concluded for an indefinite period. Customers have the right to terminate the PUC at any time according to Art. 16, para. 2. PRISMA can also terminate the PUC according to Art. 16, para. 3 et seq. 

3. The PRISMA Platform serves as an IT infrastructure offering platform services to its Customers. PRISMA does not exercise own discretion in relation to any products offered on PRISMA Platform. PRISMA does not act as an agent for or on behalf of System Operators or System Users. PRISMA does not become a party to any transaction concluded on PRISMA Platform. The fulfilment, delivery, acceptance or any other settlement of the products offered via the PRISMA Platform takes place outside the PRISMA Platform. 

Article 3: Scope of application

1.       Customers, their User Administrators and their Users shall use the PRISMA Platform in compliance with all Applicable Regulations, in particular, but not 

limited to REMIT, Regulation (EU) 2024/1789, and Directive (EU) 2024/1788, and Commission Regulation (EU) No 2017/459. 

2.      The PUC includes provisions regarding:

2.1.   the contractual relationship established between the Customer and PRISMA related to the use of the PRISMA Platform;

2.2.   the conditions for the use of the PRISMA Platform by Customers, and their authorized User Administrators and Users. Customers ensure that their User Administrators and Users comply with all rights and obligations pursuant to the PUC;

3.      Any conflicting, deviating and/or supplementary provisions provided by the Customers regarding the scope of this PUC, including but not limited to the Customer’s special or general contractual terms and conditions, are hereby expressly rejected. 

Article 4: The PRISMA Platform: access and service prices

1.      PRISMA provides the electronic platform at: https://platform.prisma-capacity.eu, at which inter alia:

1.1.   primary and secondary market, entry and exit capacities of TSOs are marketed and traded;

1.2.   SSO services are published and Bids of respective Storage Users are collected;

1.3.   LSO services are published and Bids of respective LSO Users are collected;

2.      The use of the PRISMA Platform for the services mentioned in para 1 above is free of charge for the System User. Within the scope of the Applicable Regulations, PRISMA is entitled to introduce fees and charges for the use of the PRISMA Platform. Any changes must be introduced in line with the rules laid down in Art. 15 and are subject to the approval of National Regulatory Authorities if required by Applicable Regulations. 

3.      Other services such as REMIT Reporting or API (Application Programming Interface) are priced separately and are subject to Service Specific Terms. 

4.      In the event that any regulatory or administrative charges are introduced or imposed by an entitled authority – including, but not limited to ACER or any National Regulatory Authority (NRA) on PRISMA in its capacity as Registered Reporting Mechanism (RRM) or Organized Marketplace (OMP), PRISMA shall be entitled to pass on and invoice those charges to the individual Customer. 

Part II. ACCESS AND CONDUCT RULES

Article 5:  Registration of the Customer on the PRISMA Capacity Platform

Registration for the PRISMA Platform is a two-step process that involves:

1.      The creation of an account on the PRISMA Platform.

2.      The designation and validation of the initial User Administrator.

Article 6: Creation of an account on the PRISMA Capacity Platform

Customer’s account is created at the PRISMA Capacity Platform in two steps:

1.      Entering the following information, not limited to:

1.1.  Customer’s information: name, address, billing information, the valid EIC as published by ENTSOE and/or ENTSOG and as specified in the Centralized European Registry of Energy Market Participants (CEREMP); and,

1.2.   Initial User Administrator’s information: name, email address, phone number and a Power of Attorney (PoA).

2. Depending on the type of transaction intended to be entered into, applicable valid EIC as published by ENTSOE and/or ENTSOG and as specified in the Centralized European Registry of Energy Market Participants (CEREMP), DVGW Code or additional information may be required. 

3. Requesting a Token Device for the Customer to access the PRISMA Platform. The User Administrator must choose between a hardware or software solution. If selected, the delivery of the hardware solution could take 2 to 10 business days. In the meantime, a preliminary Customer account will be created on the PRISMA Platform.

Article 7: Appointment of the User Administrator

1. A User Administrator is a natural person who is granted by the Customer, via PoA, the legal capacity to make binding declarations and action on behalf of 

the Customer and to perform especially but not limited to the following functions and obligations: 

1.1. regarding the Customer to: 

a. Register the Customer on the PRISMA Platform. 

b. Accept the PRISMA GTCs and/ or any other applicable terms and conditions on behalf of the Customer. 

c. Receive and accept the results of the consultation and new versions of this PUC and/ or PRISMA GTCs in case of modification, update or amendment. 

d. Activate and deactivate features and to subscribe to and unsubscribe from functionalities and services provided by PRISMA; 

e. Submit, compile and maintain the Customer’s information, documentation and data; 

f. Manage rights and assignments of the Customer’s Users; 

g. Participate in transactions on PRISMA Platform; 

h. Terminate the PUC. 

1.2. regarding Users: 

a. to register and administer further Users on the PRISMA Platform, including the management of their respective rights, assignments, and authorization for their participation in transactions on the PRISMA Platform; 

b. Manage Users in the Prisma Platform, which includes: 

• registering new Users; 

• sending the PUC to the Users for their individual acceptance, 

• uploading Users’ information at registration, 

• deactivating assignments, 

• deactivating Users 

• adding User Administrators, thereby entitling them to the same rights as mentioned for the Initial User Administrator. 

1.3. regarding the PRISMA Platform: 

a. Provide PRISMA with additional information as required by the System Operators. 

b. Keep the Customer’s registration information up to date upon successful registration of individual Users. Fulfilment of this obligation does not relieve the Customer from any corresponding or additional notification obligation to the System Operators pursuant to the TTCs or GTCs of the respective System Operators. 

2. To validate a User Administrator, it is necessary to : 

2.1. upload the Power of Attorney Form (PoA) provided by PRISMA, duly completed and signed, which legally authorizes the Initial User Administrator to act on the PRISMA Platform. The PoA must clearly identify the authorising representative(s) and be executed by means of the Qualified Electronic Signature. 

2.2. the commercial registry extract (and/or any other legally valid document proving company’s incorporation, legal existence and representation), issued no later than three months before uploading, to prove the legitimacy of the submitted PoA. 

3. PRISMA will review the documents uploaded by the User Administrator and, based on such review, determine whether to recognize their legal capacity. PRISMA shall inform the User Administrator of its decision without undue delay. PRISMA reserves the right to request the originals of the submitted documents. 

Article 8: Appointment of the User(s)

1. The Users are natural persons granted authority by a User Administrator(s) to participate in transactions on the PRISMA Platform. 

2. The User(s) receive their Token Devices and temporary passwords to access the PRISMA Platform only after prior acceptance of this PUC. 

Article 9: Approval of the System Operator 

1. To use primary and/or secondary functionalities of the PRISMA Platform, the User Administrator shall initiate the System Operator assignment on behalf of the Customer by submitting an application to the selected System Operators. The 

application and approval process are based on the requirements set out in the GTCs or the TTCs of the respective System Operator. 

2. In accordance with Applicable Regulations, the Customer may need the approval of the respective System Operator for the use of primary and/or secondary functionalities. The approval for the use of primary and/or secondary functionalities may be granted or denied independently of each other in accordance with Applicable Regulations. 

3. The respective System Operator preserves the right to request from the User Administrator(s) any supplementary documents required for the approval process as well as the originals of the submitted documents. 

4. PRISMA is not responsible for the approval process undertaken by System Operators. The same applies mutatis mutandis to the suspension or withdrawal of an approval. 

5. System Operators can call for a verification of credentials or a credit assessment. 

6. The User Administrator will receive a notification from PRISMA informing them about the results of the System Operator’s approval process. 

Article 10: Availability of access to the PRISMA Capacity Platform 

PRISMA will use the professional care of a reasonable and prudent operator to perform all services under this contract, grant access and make available the PRISMA Platform in a safe, secure, and properly functioning way, according to the applicable industrial standard. The Customers’ right to use the PRISMA Platform and the services are subject to the current state of technology.

The parties agree, that due to the state of technology it is not possible to warrant the uninterrupted and steady functioning of data processing devices and device combinations under all application conditions imaginable and to exclude errors in the data processing programs and that a continuous operation of or access to the Platform and the services shall not be guaranteed. 

Article 11: Access Key 

1. Booking primary and secondary market, entry and exit capacities of the TSOs and other products of the System Operators at the PRISMA Capacity Platform is only possible with a non-transferable Access Key that is provided by PRISMA to each Customer upon successful approval according to Art. 9 by the System Operator. 

2. This Access Key is a technical necessity for the Customer’s access to the PRISMA Capacity Platform. 

3. Upon first registration, the Customer may choose between the hardware token or the software solution. 

4. The hardware token will be sent by registered letter and remains the property of PRISMA. PRISMA reserves the right to request the return of the hardware upon deactivation of the Customer’s account. In case of malfunctioning of the hardware token, the User Administrator may request its replacement to PRISMA who will provide a replacement to the Customer without undue delay. 

Part III. PROVISIONS REGARDING CONTRACT MODIFICATION, TERMINATION AND PLATFORM DEACTIVATION

Article 12: Conduct on the PRISMA Platform 

1. The Customer and the respective User Administrators and Users shall behave in a prudent and reasonable manner, which means to fulfil, in particular, the following obligations: 

1.1. to keep the information of the Customer, User Administrator and Users up to date; 

1.2. to refrain from any action which is illegal or may directly and/or indirectly infringe any market behaviour rules or regulations, including but not limited to REMIT; and, 

1.3. to refrain from any actions that lead or could lead to the damaging or reduction in effectiveness of the PRISMA Platform, that can be linked to an attack on the information system such as, but not limited to, spam, virus, brute forcing, Trojan horse attack, denial of service attack, ping of death attack, sniffing and spoofing and dictionary attack. 

2. Customers, their User Administrators and their Users shall not manipulate the course of a transaction or an auction, in particular through ghost-bidding (e.g. by using sniper tools), shill bidding, or assuming multiple roles in a single auction. However, in accordance with Applicable Regulations System Operators may assume multiple roles in auctions (e.g. as a TSO or Network User). 

3. Customers, their User Administrators and the respective Users are not allowed to execute through PRISMA any transaction in Financial Instruments. If nevertheless PRISMA finds that a Customer, their User Administrator(s) and/or the respective User(s) try to execute a transaction in Financial Instruments, their respective 

transactions shall be rejected and the Customer, User Administrators and its User(s) may be deactivated from the Secondary Market functionalities on the PRISMA Platform. 

4. In case of infringements of the preceding paragraphs, Art. 16, Art. 17 and Art. 18 apply. 

Article 13: Functionality and suspension of the PRISMA Platform 

1. PRISMA may restrict or suspend its services temporarily if this is necessary to guarantee the security and integrity of PRISMA Platform or for maintenance. The same applies to cases of unforeseen technical difficulties or disruptions such as and especially in the case of the interruption of the power supply or a hardware or software error which causes the breakdown and/or failure of the PRISMA Platform or other System Operators’ connected systems. The provision of Art. 16 remains unaffected. 

2. PRISMA shall notify the affected Customers in due time of maintenance measures carried out on the PRISMA Platform. A schedule for planned maintenance will be published on the Platform regularly. Information about unplanned maintenance will be published as an Urgent Market Message on our website and as RSS feed and made available to the Customers without undue delay on the Platform and via established electronically means. 

3. If PRISMA is unable to resolve situations within the meaning of para. 1 within a reasonable time or at reasonably justifiable expenses, PRISMA shall use reasonable efforts to propose an alternative or interim solution to the Customers in order to meet their needs. 

4. In the case of a limitation of the availability and/or functionality of the PRISMA Platform as described in para. 1, any procedures currently in progress may be interrupted and continued later. 

5. The above paragraph 4 is not applicable for: 

5.1. affected auctions for short-term capacity products; and, 

5.2. any Trade Proposals and auctions that expired before PRISMA Capacity Platform is available again. 

These procedures will be cancelled. In case a procedure is continued, the Customers shall be notified of the continuation in a timely manner. In addition, Art. 14, para. 5 and 6 of the General Allocation Rules apply accordingly. 

6. The proper functioning of telecommunications services the Customer needs to access the PRISMA Platform is not within PRISMA’s sphere of influence. Therefore, each and any liability and/or warranty of PRISMA with regard to said services is herewith excluded. 

Article 14: Protection of PRISMA’s system security 

1. The Customer shall guarantee the careful handling of access information and Access Keys needed for the use of the PRISMA Platform. A careful handling includes, in particular to: 

1.1. safeguard and ensure the exclusive use of the Token Device by the User Administrator and Access Keys (Tokens) by the User to whom they were assigned; 

1.2. not forward or make available information about the Access Key to third parties; and, 

1.3. safeguard the working place after successfully logging on to PRISMA Platform. 

2. The Customer shall notify PRISMA immediately when: 

2.1. an Access Key has been lost or corrupted; or, 

2.2. a well-founded suspicion exists that access information has become available to an unauthorised third party. 

Part III. PROVISIONS REGARDING CONTRACT MODIFICATION, TERMINATION AND PLATFORM DEACTIVATION 

Article 15: Changes to the GTCs 

1. PRISMA reserves the right to change or expand the scope and the content of the provisions of the GTCs, in particular when this is necessary to meet the requirements of applicable laws and regulations and/or legally binding rulings from national or international courts or agencies (e.g. decisions made by the respective regulatory authority) and to conform with, or as a result of, technical adjustments. 

2. If required by Applicable Regulations changes to the GTCs are subject to a timely and public consultation with: 

2.1. national competent agencies or authorities; and, 

2.2. stakeholders. 

3. Changes can be considered minor even if they require changes to the Customers’ back-end systems. 

4. After the consultation, User Administrators shall be notified in a timely manner of any consolidated changes or amendments in Text Form. In case of disagreement with the introduced changes or amendments, the Customer can terminate the PUC in accordance with Art. 16. 

Article 16: Contract termination and deactivation of the Customer 

1. The immediate consequence of the termination of the PUC is the deactivation of the Customer from the PRISMA Platform. This means that the Customer will no longer have access to the Platform and will not be able to use its functionalities. 

2. The Customers may terminate the PUC either by deactivating all of their Users’ and User Administrators’ accounts on the PRISMA Platform or by submitting to PRISMA the corresponding PRISMA template in the Written Form. With the deactivation of the last User Administrator of the Customer, the account of that Customer will be deactivated. 

3. PRISMA may also terminate the PUC in case of discontinuing operations of the PRISMA Platform at any time with a notice period of at least 3 months to the end of the month. The Customers are to be notified of the reasons in Text Form. PRISMA will notify the Customers of the precise point in time of the discontinuation of the operation of the PRISMA Platform in a timely manner. 

4. Subject to applicable regulations, PRISMA is also entitled to terminate the PUC and deactivate the Customer in the following cases: 

4.1. in the event of bankruptcy, liquidation or dissolution of the Customer; or, 

4.2. following the receipt by PRISMA of a decision of a competent authority stating that the Customer has committed an abusive or fraudulent act and requesting the exclusion of the Customer from the PRISMA Platform; or, 

4.3. in case of definitive withdrawal of all business relations of the Customer concerned with System Operators; or, 

4.4. based on evidence or grounds to believe that a Customer (a) jeopardizes the proper functioning of the PRISMA Platform; (b) contravenes any reasonable action, measure, or instruction of PRISMA under this PUC; and/or (c) persistently and/or intentionally breaches the PUC. 

In these cases, PRISMA will terminate the PUC and deactivate the Customer according to the following process: 

a. PRISMA shall notify the Customer in Text Form about the reasons for termination of the PUC and deactivation of the Customer; the date and time of the deactivation; the consequences of the deactivation and of the obligation to remedy any breach or non-compliance of its contractual obligations. The concerned System Operators receive a copy of the notification. The notification shall contain the following information: 

• the alleged breach of, or non-compliance with the PUC, 

• the necessary action(s) that should be taken by the Customer to remedy the breach and/or non-compliance, 

• a deadline of minimum 14 calendar days, starting from the date of receipt of the notification, within which these action(s) should be taken, and 

• the possibility for the Customer, upon its request in Text Form to answer to this notification. 

b. If the Customer does not take the requested action(s) to remedy the breach within the above-mentioned deadline, the Customer may be deactivated by PRISMA. This decision of deactivation shall be taken within minimum 7, and maximum 14 calendar days starting at the end of the abovementioned deadline. PRISMA notifies the deactivation decision in Text Form. This notification will include the date and time when the termination of the PUC and consequent deactivation from the Platform takes effect and the reasons for termination and deactivation. 

5. If the Customer demonstrates that the conditions to place transactions have been met again and/or there is a ground for belief that the Customer will comply with the PUC, the Customer will be allowed to start a new registration process on the Platform. 

6. Deactivation of a Customer will automatically result in the deactivation of all respective User(s) of said Customer. If the Customer is active on other sections of 

the PRISMA Platform or is subscribed to other services or functionalities, the deactivation affects the registration of all sections and access to all functionalities. 

7. All transactions performed before the termination of the PUC remain unaffected by the termination. 

8. Upon termination of the PUC, PRISMA reserves the right to request the return of all hardware tokens and the software tokens must be deactivated without undue delay, but in any case, no later than 14 calendar days after termination. 

9. If a hardware token is not returned after PRISMA’s request, PRISMA is entitled to bill the Customer for the costs of the hardware token. In that case, the Customer is obliged to pay the costs of the hardware token. 

Article 17: Deactivation of User Administrators 

The Platform accounts of User Administrators will be deactivated upon withdrawal of the respective PoA. User Administrators appointed by such User Administrator shall remain valid unless the PoA of each of them is individually withdrawn. If the User Administrator that is about to be deactivated is the last one active on the Platform, and there are still Users or assignments under their responsibility, the Customer must appoint a replacement immediately. 

Article 18: Deactivation of Users 

1. User Administrators can deactivate the accounts of their Users. 

2. PRISMA can also deactivate accounts of Users if there exists evidence or ground for belief that a User: 

2.1. has infringed or contravenes the PUC; or, 

2.2. contravenes any reasonable action, measure or instruction of PRISMA under the PUC. 

Before deactivation, PRISMA shall consider the interests of the affected User, the Customer concerned, as well as all System Operators and System Users engaged with the Customer. 

3. In case of severe breaches, and after informing the concerned engaged System Operators, PRISMA is entitled to immediately deactivate the respective User. Severe 

breaches are constituted inter alia by attacking the Platform or manipulating transactions, or by executing any transaction in Financial Instruments. 

4. PRISMA shall accept a new registration of a deactivated User if the Customer proves the establishment of internal procedures to ensure compliance of this User with the PUC. 

5. If one User of a Customer is repeatedly deactivated, PRISMA has the right to exclude this User permanently. 

6. After the deactivation of a User account, Art. 16, para. 8 and 9 apply accordingly. 

Part IV. OTHER PROVISIONS 

Article 19: Liability and warranty 

1. PRISMA makes the PRISMA Platform available as described in this PUC. PRISMA does not, in doing so, take any responsibility for, or make any guarantee concerning the contracts concluded between Customers, in particular, for the actions, capabilities and performance of the contractual parties involved. 

2. Each party to the PUC shall be liable without limitations: 

a. for damages arising from culpable injury to life, limb or health, caused by an intentional or negligent breach of duty; 

b. for any other damages caused by an intentional or grossly negligent breach of duty. 

3. The liability for damages in case of breach of material contractual obligations through simple negligence, i.e. non-gross negligence, is limited to the contract-typical, foreseeable damage. 

4. All other liability not mentioned in this article is excluded. 

5. Material contractual obligations are obligations, the performance of which are fundamental to the proper performance of the PUC, and the performance of which the parties to such a contract normally rely on and may at all times expect. For the avoidance of doubt, the duties stipulated in Art. 12 and Art. 14 shall also be deemed to be material contractual obligations. 

6. Contract-typical and foreseeable damages are those which the contractual partner foresaw as a possible result of breach of contract at the time of contract conclusion, or those which, under consideration of the circumstances which were or should have 

been known to them, should have been foreseen had due diligence been applied. Contract-typical, foreseeable damages are deemed not to exceed 250.000 € for an event of damage. 

7. Claims resulting from the expressed assumption of guarantee and from absolute liability, in particular product liability, remain unaffected by the above-mentioned liability exclusions and limitations. 

8. The aforementioned liability provisions also apply to legal representatives, employees as well as sub-contractors or vicarious agents of parties to the PUC. 

Article 20: Force majeure 

1. Force majeure is an event which occurs due to occurrences outside one’s own control and not because one’s fault, is not foreseeable, may not be avoided (or avoided in a timely fashion) by use of due diligence and technologically or economically reasonable means and which makes it impossible to fulfil temporarily or definitively ones’ contractual obligations. 

2. Such occurrences include, in particular, natural catastrophes, terrorist attacks, interruption of the power supply or communications technology, legally occurring strikes as well as legal provisions or actions ordered by governmental institutions, agencies or the courts (independent of their legality). For the avoidance of doubt, the exit of the United Kingdom (or another European Union Member Country) from the European Union shall not be considered force majeure. 

3. In case of force majeure, the contractual party invoking force majeure shall be freed of the obligations affected by force majeure for the duration of the event of force majeure. The other contractual party shall be freed of his own contractual obligations in such cases for as long as it is impossible to the contractual party affected by force majeure to fulfil contractual obligations. 

4. The contractual party affected is obligated to immediately inform the other contractual party of the reason for, and expected duration of the event of force majeure. The contractual party affected is obligated to make an effort, using all technological and economically reasonable means, to ensure that they are able to fulfil their contractual obligations again as soon as possible. 

5. If the contractual party uses a third party to execute the obligations under the PUC, and the third party experiences an occurrence which satisfies the conditions of force 

majeure or other condition in the sense of para. 1, this occurrence shall be considered as force majeure affecting the contractual party as well. 

Article 21: Use of data 

1. The parties commit to comply with data protection laws and regulations. 

2. PRISMA may store, use and process data of its Customers, User Administrator(s) and Users. PRISMA may also store, use and process data generated via the PRISMA Platform: 

2.1. for the execution and/or documentation of the PUC; or, 

2.2. to comply with legal or contractual requirements. 

3. In the context of Data Protection Regulation, PRISMA processes personal data to fulfil the PUC, whereas the Customers are responsible for the personal information they upload in the Platform. How PRISMA complies with the current data protection regulation is specified in PRISMA’s Privacy Policy available at PRISMA’s corporate website, which may change from time to time. 

4. The User Administrator(s) is responsible for erasing registration information of other User Administrators and Users upon PUC termination. Nevertheless, PRISMA will retain personal information if necessary to comply with the General Data Protection Regulation (GDPR) and other EU and national laws. 

5. PRISMA may erase information of the Customer and personal information of the User Administrators and Users, upon PUC termination, and according to PRISMA’s erasure policy, if it has been impossible to contact the Customer and/or one of their User Administrators. 

6. PRISMA shall share company and personal data of the Customer, their User Administrators and their Users with the respective System Operators being contractual parties to the Customer. PRISMA will also share company and personal data (subject to Applicable Regulations) with competent authorities. 

7. While maintaining anonymity, PRISMA may disclose data concerning its Customers, User Administrators(s) and their User(s) on the PRISMA Platform if that data is required for the description of the capacity right. Such disclosed data may include the price of the transaction to transfer the capacity right, any special conditions that have been included in the offer or request as well as required data about the concerned TSO and network point. 

8. After a successfully concluded CFO or FCFS transaction on PRISMA Capacity Platform, PRISMA may disclose to the offering and to the requesting Customer both the name and the address of each other. Such disclosure shall only be intended for the fulfilment of the contract. 

Article 22: Confidentiality 

1. In addition to this article, Art. 40 Directive (EU) 2024/1788 and its national transposition measures apply. 

2. Without prejudice to Art. 40, Directive (EU) 2024/1788, the parties of the PUC agree to treat, subject to the provisions in Art.22, para. 4, as confidential all information which they receive in connection with the PUC and the conclusion of contracts on the PRISMA Platform (hereafter named "Confidential Information") and agree not to disclose this information to any third party unless the affected parties of the PUC have previously authorised such action in Written Form. It is understood that information already known by the parties of the PUC receiving the information at the time of receipt and which was legally acquired is not Confidential Information. 

3. The parties of the PUC are obliged to use the Confidential Information exclusively for the purpose of fulfilling the aims of this agreement. 

4. The parties of the PUC have, in the following situations, the right to disclose Confidential Information received from the other contractual party without their prior written authorisation: 

4.1. to Affiliated Companies, provided that such disclosure is required for the proper execution of the obligations contained in the PUC by the disclosing party. In such case, the disclosing parties of the PUC shall ensure that their Affiliated Company shall treat the information received as confidential; 

4.2. to their representatives, advisors, banks and insurance agencies in the case that the disclosure is necessary for the proper execution of contractual agreements and as long as these persons, companies or agencies have committed themselves to treating the information confidentially or are legally obligated to maintain secrecy as a result of their profession; 

4.3. to any third party to the extent that this Confidential Information: 

a. is already publicly available or has been made available to the public in a way that is not influenced by the actions of the receiving parties of the PUC; or, 

b. must be disclosed because of a legal requirement or binding decision from a public authority or court. In such cases the parties of the PUC disclosing the information are obliged to inform the affected parties of the PUC immediately of the disclosure. 

4.4. and/or if the respective data are aggregated and anonymous. 

5. The obligation to confidentiality ends 5 years after the termination of the PUC. 

Article 23: Language and severability clause 

1. Only and exclusively the English version of this PUC is legally binding. Any other versions of the PUC created in a language other than English are for convenience and only meant to serve as a source of information. If there is any contradiction between versions of the PUC, the English language version shall take precedence. 

2. Should individual provisions of the PUC or its amendments be or become ineffective or unenforceable, all other parts of the PUC and its amendments remain unaffected. If any provision is declared to be legally invalid or unenforceable, then the invalid or unenforceable provision shall be replaced by a valid, enforceable provision that most closely matches the economic purpose of the original provision. The same shall apply if the conditions are found to contain omissions. 

Article 24: Place of jurisdiction and applicable law 

1. The PUC shall be governed exclusively by German laws excluding the referring rules of private international law. The UN Convention on Contracts for the International Sale of Goods is expressly excluded and shall in no case apply. 

2. The exclusive place of jurisdiction for all legal disputes arising from or in connection with the PUC shall be Leipzig, Germany.