Terms of Service

Welcome to PixelPai. Our services and products are provided by PixelPai ApS, located at Applebys Plads 7, 2, 1411 Copenhagen K, Denmark. By using our website (www.pixelpai.com), platforms, or services, you are agreeing to these Terms of Service (“Terms”). Please read them carefully.

PixelPai ApS
Applebys Plads 7, 2
1411 Copenhagen K, Denmark
Company number: 44479397
Registered VASP with the Danish Financial Supervisory Authority

 

1. Definitions

1.1. “Services”: Refers to all services and products offered by PixelPai ApS, including but not limited to forensic analysis, Know Your Customer (KYC) verification, verification flow management, compliance cockpit, token lifecycle management including issuance, minting and burning and redemption, custody, issuance, swapping, or cross-chain management; identity services, verified credentials management, development of custom solutions tailored to specific client needs, and any related public or private distributed ledger technology (DLT) provision, as further detailed on PixelPai’s website or in a separate agreement.

These Services are designed to assist clients across various industries, including but not limited to gaming studios, digital asset platforms, and entrepreneurial ecosystems in meeting regulatory requirements, managing digital assets, and ensuring the integrity of their tokenized ecosystems.

 

1.2. “Platform”: Refers to PixelPai’s website, dashboards, portals, applications, APIs, and any user-facing or wallet-connected interfaces made available by PixelPai, including features that allow Users to connect a wallet, perform token burn actions, view balances, and request conversions.

 

1.3. “User”: Refers to any individual who accesses or uses the Platform, including users who connect a blockchain wallet and/or create a user profile using email and password.

 

1.4. “Client”: Refers to any entity or organization that utilizes PixelPai’s Services for a business purpose under the terms of this Agreement and/or under a separate order form, statement of work, or commercial agreement. Where a provision refers to “Client” specifically, that provision applies to business customers.

 

1.5. “Agreement”: Refers to these Terms and any applicable appendices, exhibits, schedules, amendments, and any supplemental agreements relating to the provision of Services. If a separate written agreement exists between PixelPai and a Client, that agreement will govern to the extent of any conflict.

 

1.6. “Deliverables”: Means any tangible or intangible outcomes or outputs generated in connection with the Services provided by PixelPai, as per separate order form and commercial terms as described in this Agreement and appendices.

 

1.7. “Documentation”: Refers to any technical or operational manuals, API documentation, user guides, implementation protocols, integration guidelines, and other supporting materials provided by PixelPai to assist Users or Clients in utilizing the Services.

 

1.8. “Rebirth Engine”: Refers to PixelPai’s platform feature enabling supported token burn flows and the issuance of internal credits, including subsequent conversion flows into supported utility tokens.

 

1.9. “Rebirth Credits”: Refers to internal, offchain platform credits recorded in a User’s Platform profile. Rebirth Credits are used within the Platform to request conversion into supported utility tokens. Rebirth Credits are not redeemable for fiat and are not transferable between users.

 

1.10. “RLY Token” or “RLY”: Refers to the Reality+ utility token issued as an ERC20 token on Arbitrum (or other networks as published by PixelPai). RLY is intended to function as a utility token within the ecosystem. RLY does not represent equity, ownership, profit share, or a claim against PixelPai.

 

1.11. “Conversion”: Refers to the process of converting Rebirth Credits into RLY or other supported project tokens, subject to eligibility checks, platform rules, and fees.

 

1.12. “Custodial Wallet”: Refers to a platform-linked wallet generated and maintained for a User profile to support compliant custody, settlement, and controlled withdrawals within the Platform.

 

2. Eligibility and User Responsibilities

2.1. Eligibility: By using the Platform, you represent that you are at least 18 years old (or the age of legal majority in your jurisdiction), and that you have the legal capacity to enter into these Terms.

 

2.2. User Account Security: Users are responsible for maintaining the confidentiality of their account credentials and any wallet authentication methods used to access the Platform. You must immediately notify PixelPai if you suspect unauthorized access or use of your account.

 

2.3. Accurate Information: Users and Clients guarantee that information provided to PixelPai is accurate and complete. PixelPai may restrict access, suspend, or terminate Services if information is false, misleading, or inconsistent with compliance requirements.

 

2.4. Prohibited Use: You may not use the Platform or Services for criminal, fraudulent, or unlawful activities, including money laundering, sanctions evasion, or the financing of terrorism.

 

2.5. Blockchain and Digital Asset Risks: You acknowledge that DLT, blockchain networks, and digital assets carry inherent risks, including regulatory uncertainty, volatility, irreversible transactions, and potential loss of assets. PixelPai does not provide financial advice and does not guarantee outcomes, values, or liquidity for any token.

 

3. Rebirth Engine, Credits, and Token Conversions

3.1. Rebirth Engine Functionality: The Platform may allow Users to interact with supported token burn processes. Where supported, Users may voluntarily burn certain assets and receive Rebirth Credits recorded within their Platform account.

 

3.2. Rebirth Credits: Rebirth Credits are internal platform credits. They:

• are recorded offchain within the Platform,
• are non-transferable between Users,
• may be subject to platform rules, limits, and eligibility checks,
• can be used to request a Conversion into supported tokens where available.

3.3. Conversions to RLY or Partner Tokens: Users may request Conversion of Rebirth Credits into:

• RLY, and/or
• other supported utility tokens offered through the Platform in the future.

 

3.4. No Guarantee of Availability: PixelPai may modify, suspend, or discontinue any token support, conversion route, or feature at any time, including due to legal, regulatory, technical, or risk-related reasons.

 

3.5. No Investment Representation: RLY and any other supported utility tokens are intended for utility within the ecosystem. PixelPai does not make any representation that any token will increase in value, be listed on exchanges, or have liquidity available.

 

4. Fees, Stablecoin Payments, and Network Costs

4.1. Conversion Fee: PixelPai charges a fee for Conversions of Rebirth Credits into RLY or other supported tokens.

 

4.2. Tiered Fees: Fees may vary based on the quantity of Rebirth Credits being converted and may be structured as fixed tier amounts. The applicable fee will be displayed to the User prior to confirmation of a Conversion.

 

4.3. Payment Method: Conversion fees must be paid in supported stablecoins (e.g. USD-denominated stablecoins such as USDC and USDT, as specified in the Platform). PixelPai may update supported stablecoins and networks from time to time.

 

4.4. Network Fees: Users are responsible for blockchain network fees (gas) related to onchain transactions, including wallet interactions, burn transactions, or withdrawals.

 

4.5. No Refunds: Fees paid for completed Conversions are non-refundable unless required by applicable law.

 

5. Wallet Screening, Custody, and Withdrawals

5.1. Wallet Sanctions Screening and Risk Checks: When a User connects a wallet or uses token-related Platform features, PixelPai may perform automated screening and risk checks, including sanctions screening and transaction monitoring, to comply with AML, KYC, FATF, MiCA, and other applicable legal requirements.

 

5.2. Custodial Wallet Creation: PixelPai may generate a Custodial Wallet linked to a User profile. The Custodial Wallet may be used to temporarily hold assets, RLY tokens, and/or balances associated with the Platform experience.

 

5.3. KYC and Withdrawal Eligibility: Withdrawals to external non-custodial wallets may require identity verification (KYC) depending on jurisdiction, transaction thresholds, user risk profile, and applicable regulation. PixelPai may restrict or delay withdrawals where required to comply with legal obligations.

 

5.4. Third-Party Infrastructure Providers: PixelPai may use specialized third-party providers to support custody, wallet generation, and settlement operations. PixelPai remains responsible for selecting providers that meet appropriate security and compliance standards. PixelPai may provide information about key sub-processors upon request.

 

5.5. Freezing and Legal Holds: PixelPai may freeze, restrict, or delay asset movements where required by law, regulatory direction, court order, or where PixelPai has reasonable grounds to suspect illicit activity.

 

6. Client Responsibilities (Business-to-Business)

6.1. Client Account Security: The Client agrees to take full responsibility for maintaining the confidentiality of account credentials, including but not limited to usernames, passwords, and API keys, used to access PixelPai’s Services. The Client shall not share these credentials with unauthorized third parties and must immediately notify PixelPai if it suspects unauthorized access or usage.

The Client is solely responsible for any activity that occurs under their account, authorized or unauthorized. PixelPai reserves the right to suspend or terminate the account in cases of suspected misuse or failure to comply with these obligations.

 

6.2. Regulatory Compliance Obligations: The Client agrees to comply with all applicable laws, regulations, and rules, including but not limited to digital assets, AML/CFT, and privacy regulations.

 

6.3. Appointment of Compliance Liaison: The Client must appoint a designated individual responsible for compliance with the above-mentioned regulations. This person will act as the primary liaison between the Client and PixelPai, ensuring that all compliance-related obligations are met.

 

6.4. System Requirements: The Client must ensure that all system access, compatibility, and software required for integration with PixelPai’s services are maintained at their own expense.

 

6.5. API Integration and Testing: The Client will provide access to testing environments, API documentation, and other necessary resources to facilitate seamless integration with PixelPai’s platform.

 

7. Payment Terms (Business-to-Business)

7.1. Pricing: Fees for B2B Services shall be as stated on PixelPai’s website or as outlined in a separate agreement with the Client. PixelPai reserves the right to adjust fees upon thirty (30) days’ notice.

 

7.2. Payments: Invoices shall be issued monthly and payable within seven (7) days from the invoice date, unless otherwise agreed in writing.

 

7.3. Late Payments: PixelPai may charge interest at 2% per month on overdue amounts and may suspend access until the account is brought current.

 

7.4. EDD / SAR / Time & Materials: Where Enhanced Due Diligence or Suspicious Activity Reporting services are required, PixelPai may charge on a time-and-materials basis and will notify the Client of costs where practicable.

 

8. Compliance with Laws

8.1. PixelPai’s Compliance: PixelPai shall comply with laws applicable to the conduct of its business.

 

8.2. User and Client Compliance: Users and Clients are responsible for ensuring that their use of the Platform and Services complies with applicable laws and regulations.

 

8.3. Cooperation with Authorities: Both parties agree to cooperate with lawful requests by competent authorities, subject to legal restrictions.

 

9. Data Privacy and Security

9.1. Security Measures: PixelPai implements technical and organizational measures to safeguard personal data in compliance with GDPR and applicable regulations.

 

9.2. Data Breach Response: PixelPai will respond to personal data breaches in line with GDPR requirements, including notification obligations where applicable.

 

9.3. Sub-processors: PixelPai may engage sub-processors for hosting, analytics, identity verification, custody, monitoring, and related services. Clients may request an up-to-date list of sub-processors at any time.

 

10. Intellectual Property Rights

10.1. Ownership: All intellectual property rights associated with the Services and underlying software remain the exclusive property of PixelPai.

 

10.2. License Grant: PixelPai grants a limited, non-exclusive, non-transferable, revocable license to use the Services in accordance with these Terms.

 

10.3. Prohibited Activities: You may not reverse engineer, decompile, scrape, or misuse the Services, exceed rate limits, compromise security, or infringe IP rights.

 

10.4. Feedback: Feedback provided to PixelPai may be used by PixelPai without restriction.

 

11. Confidentiality

11.1. Each party shall treat confidential information disclosed by the other as confidential and protect it using reasonable measures.

 

11.2. Confidentiality obligations survive for five (5) years following termination.

 

12. Term and Termination

12.1. These Terms apply from the date you start using the Platform or Services.

 

12.2. PixelPai may modify or discontinue Services or these Terms with notice where practicable, or immediately where required by law.

 

12.3. PixelPai may suspend or terminate access to the Platform or Services to comply with legal obligations or due to risk-based decisions.

 

12.4. Upon termination, PixelPai will delete User or Client data unless retention is required by law.

13. Termination Due to Breach

PixelPai may terminate these Terms for the reasons described below, including negative publicity, sanctions, misrepresentation, regulatory orders, or suspected criminal activity, and may restrict access without notice where required to manage risk or comply with law.

(Your existing termination grounds and asset-handling logic are retained in effect, and apply to Clients and to custody situations where PixelPai holds assets, subject to regulatory requirements.)

 

14. Limitation of Liability

14.1. Cap on Liability: PixelPai’s liability is limited to the total fees paid by the Client in the twelve (12) months preceding the event giving rise to the claim, except where mandatory law requires otherwise.

 

14.2. Third-Party Dependencies: PixelPai is not liable for failures of third-party services, networks, APIs, or blockchain infrastructure.

 

14.3. Exclusion of Indirect Damages: PixelPai is not liable for indirect, incidental, or consequential damages.

 

14.4. Beta Services: Beta features are provided “as is” and used at your own risk.

 

14.5. No Token Value Guarantee: PixelPai does not guarantee token value, exchange availability, or liquidity for RLY or any other supported token.

 

14.6. Exceptions: Liability limits do not apply to gross negligence or willful misconduct, confidentiality breaches, IP infringement, or mandatory GDPR-related liabilities.

 

15. Custody and Administration of Crypto-Assets

PixelPai may provide custodial services for crypto-assets and funds to Clients and, where applicable, to Users through platform-linked Custodial Wallets. Assets are safeguarded through security measures, segregation practices, and third-party oversight where applicable.

 

15.1. Asset Segregation: Client funds and relevant custody balances are segregated from PixelPai operational funds.

 

15.2. Security Measures: PixelPai applies encryption, access controls, operational resilience measures, and secure key management practices (including MPC where relevant).

 

15.3. Third-Party Custodians: PixelPai conducts due diligence on third-party custody providers.

 

15.4. Regulatory Compliance: PixelPai follows applicable prudential safeguards and ICT risk management expectations (including DORA-aligned resilience principles where applicable).

 

Further custody details may be disclosed upon request.

 

16. Governing Law and Jurisdiction

These Terms shall be governed by Danish law. The Courts of Copenhagen shall have exclusive jurisdiction.

 

17. Miscellaneous

17.1. Severability: If any provision is invalid, the remainder remains in effect.

 

17.2. Non-Waiver: Failure to enforce a provision is not a waiver.

 

17.3. Force Majeure: PixelPai is not liable for events beyond reasonable control.