Catalog EULA and Cloud Services Terms

Operator and Developer: Roberto Bourgonjen, a private individual in the Netherlands, operating under operator code fndr
Address: Lange Leidsedwarsstraat 96, 1017 NM Amsterdam, the Netherlands
Applies to: Catalog desktop applications for Windows, macOS, Linux (the “Software”) and the Catalog cloud services operated by the Operator (the “Cloud Services”).
Last updated: 2026-10-15

Key notice: permanent retention (Cloud Services). The Cloud Services are designed for permanent archiving. Content uploaded to the Cloud Services may be retained indefinitely (including version history and edit trails) and may not be deletable. If you are not comfortable with permanent storage, do not use the Cloud Services. Use the Software in standalone/local mode only.

1) Parties and scope

  1. Roberto Bourgonjen (“Developer”) develops and owns the Software and related intellectual property, including the Bitcash trademark and the Catalog.org suite.
  2. Roberto Bourgonjen also distributes the Software and operates the Cloud Services himself, as a private individual (“Operator”), under operator code fndr.
  3. This EULA governs:
    • your use of the Software (standalone/local use and use connected to the Operator's Cloud Services); and
    • your access to and use of the Operator's Cloud Services.
  4. Identity and membership layer. If you use the identity/membership network at catalog.id, your participation is governed by the separate Catalog.ID Membership Agreement. This EULA does not replace or modify that agreement.

Contact: [email protected]

2) Acceptance

By downloading, installing, accessing, or using the Software or Cloud Services, you agree to this EULA. If you do not agree, do not use them.

3) Definitions

  • Cloud Services: the Catalog.org cloud services operated by the Operator, accessed through the Software or official APIs.
  • BIT / BIT tokens ("BIT"): the prepaid service credit issued by the Operator through the Bitcash payment system and used to pay for Cloud Services. See Bitcash Whitepaper.
  • User Content: files, media, recordings, metadata, tags, comments, and other content you create, import, record, or upload. Where you are also a Member of catalog.id, User Content you share with other Members via the Network may also constitute "Member Shared Data" as defined in the Catalog.ID Membership Agreement.
  • Standalone/Local mode: using the Software without connecting to any Catalog servers.

4) Software license (desktop applications)

  1. License grant. Subject to this EULA and your compliance, the Operator grants you a limited, non-exclusive, non-transferable, revocable license to install and use the Software on your devices.
  2. Two permitted modes of use. You may use the Software:
    • (A) Standalone/Local mode; or
    • (B) Connected to the Operator's Cloud Services through the Software’s supported features and official APIs.
  3. Reservation of rights. All rights not expressly granted are reserved by the Developer.
  4. Additional terms for specific applications. Certain applications within the Catalog.org suite (e.g., the Bitcash wallet) may be subject to additional terms, such as financial or regulatory disclosures. You will be presented with any such additional terms before first use of the relevant application. Additional terms supplement this EULA. If additional terms conflict with this EULA, the additional terms control only for the relevant application or feature.

5) Cloud Services access, accounts, and eligibility

  1. Account may be required. Certain Cloud Services features may require an account with the Operator (including via catalog.id). Account creation and membership rules are governed by the Catalog.ID Membership Agreement. For Cloud Services operation (billing, security, compliance), the Operator may require validated contact details; where these are held as end-to-end encrypted Attributes under the Catalog.ID Membership Agreement, they are validated through the Validator Black Box and shared with the Operator only through that agreement's key-sharing mechanisms.
  2. Eligibility. This EULA imposes no separate age requirement for using the Software. Where features require a catalog.id account, the eligibility rules of the Catalog.ID Membership Agreement apply, including its requirement that Members be at least 18 years old.
  3. Jurisdiction limits. The Operator may restrict service availability to certain jurisdictions or user categories to comply with law or manage risk.
  4. Account security. You are responsible for safeguarding your credentials, devices, and keys. Notify the Operator promptly of suspected unauthorized access.

6) Privacy and security (Cloud Services)

  1. Encryption and key sharing. The Catalog.org ecosystem supports encryption and key-based sharing mechanisms. Details of identity-layer encryption, attribute sharing, and revocation are governed by the Catalog.ID Membership Agreement.
  2. Service metadata. To operate and secure the Cloud Services and comply with law, the Operator may process necessary technical and operational data (e.g., timestamps, file sizes, service usage, security logs, and network information), even where some content fields are encrypted.
  3. Data protection and your rights. The Operator processes personal data in accordance with the General Data Protection Regulation (GDPR) and applicable Dutch data protection law. Your rights (including access, rectification, portability, erasure, restriction, and objection) are described in the Privacy Policy. Where this EULA permits permanent retention or restricts deletion (e.g., the archival policy in Section 11), the Operator explains the applicable legal basis in the Privacy Policy.

7) Payments, BIT tokens, and Bitcash

Where the Operator sells BIT, the purchase is governed by the sales terms the Operator publishes for it. Holding and spending BIT through the Bitcash Wallet Manager is additionally governed by its Additional Terms (Section 4.4). For a full description of the Bitcash prepaid micropayment system, see the Bitcash Whitepaper.

  1. Pay-as-you-go. Cloud Services are billed on a usage basis against a prepaid wallet using BIT tokens.
  2. Obtaining BIT tokens. BIT tokens may be obtained by:
    • purchasing them from the Operator, where the Operator sells BIT;
    • receiving them from the Operator free of charge (for example with an invitation); and/or
    • receiving them from another holder, as a transfer, a gift voucher, or a tip.
  3. No guaranteed value, no redemption. BIT tokens are a prepaid usage mechanism for Cloud Services and do not represent investment value or a promise of profit. Nobody redeems BIT for money, the Operator included.
  4. Expiry. A wallet's balance expires when the wallet has been idle for its term, ten years for BIT sold or given by the Operator, and then returns as described in the Bitcash Whitepaper §8. Any transaction the wallet takes part in restarts the term.
  5. Refunds. BIT is delivered digitally and can be spent immediately. By consenting to immediate delivery at checkout, you acknowledge that your right of withdrawal is lost once BIT is delivered to your wallet. Unless mandatory consumer law requires otherwise, BIT purchases are non-refundable once delivered. The Operator's sales terms describe the digital delivery acknowledgement and the refund process.
  6. BIT on termination. BIT is held in bearer wallets, not in an account. Termination of your access under Section 17 does not by itself cancel BIT in wallets you hold, and BIT is not refunded on termination unless mandatory consumer law requires it. Where termination results from your breach of this EULA, the Operator may freeze the wallets concerned to the extent permitted by applicable law. Any freeze will be proportionate to the Operator's actual losses, costs, or legal obligations arising from the breach, and will not affect mandatory consumer rights.
  7. Bitcash trademark. "Bitcash" is a trademark owned by the Developer.

8) Acceptable use

You must not use the Software or Cloud Services to:

  • violate any law or third-party rights;
  • upload unlawful, infringing, abusive, or harmful content;
  • distribute malware or attempt unauthorized access;
  • interfere with service integrity, including by abuse, automated scraping, or denial-of-service activity;
  • violate applicable export control or sanctions laws.

The Operator may suspend or terminate access for violations, security reasons, legal compliance, or non-payment.

9) Restrictions (important)

You must not, and must not attempt to:

  1. Connect to third-party APIs. Modify, patch, proxy, or otherwise alter the Software so that it connects to third-party APIs or non-Catalog server endpoints.
    • The Software may be used standalone, or connected only to the Operator's Cloud Services where such connection is explicitly supported by the Software.
  2. Reverse engineer. Reverse engineer, decompile, or disassemble the Software, except where such restriction is prohibited by applicable law.
  3. Bypass controls. Bypass authentication, wallet debiting, rate limits, licensing checks, encryption, or security controls.

10) User Content, copyright, and provenance

  1. Your responsibility. You are responsible for your User Content and for ensuring you have the rights to create, record, upload, and share it.
  2. No false claims. You must not make false authorship or copyright claims.
  3. Provenance and process recording. The platform may record and archive the creative process (e.g., task recordings, edit history, logs) to support provenance. Creativity is often collaborative; authorship disputes can be complex. A permanent record can help support legitimate claims and enable courts to challenge claims where appropriate.

11) Permanent archiving and “never delete” policy (Cloud Services)

  1. Archiving by design. The Cloud Services are designed to preserve file histories, versions, edits, and related records. Deletion may be technically impossible or restricted.
  2. Do not upload if you require deletion. If you require the ability to delete cloud-stored content, do not upload it to the Cloud Services. Use the Software in Standalone/Local mode.
  3. Non-encrypted uploads: archival license. If you upload or create User Content on the Cloud Services in non-encrypted form, you grant the Operator a perpetual, irrevocable, worldwide, royalty-free license to:
    • store, copy, and preserve the content for archival purposes (at any time); and
    • make the content publicly available once copyright, database rights, and other applicable legal protections on that content have expired, where lawful.
      For the avoidance of doubt, this license does not authorize the Operator to publish your content while it remains protected by copyright or other IP or related rights, unless you separately consent or unless publication is otherwise lawful (for example, under a license you have applied to the content, or an applicable legal exception). Nothing in this paragraph obligates the Operator to publish any content.
  4. Encrypted uploads. If content is encrypted such that the Operator cannot access plaintext, the Operator’s use of that content is limited to what is technically required to provide storage/transport and to comply with law.
  5. GDPR and mandatory rights. Nothing in this EULA limits mandatory rights you may have under applicable law. However, the archival design and legal retention obligations may mean that certain deletion/erasure requests cannot be fulfilled for content already uploaded, while the Operator may still be able to restrict access, limit publication, or apply other safeguards depending on the circumstances and the service’s technical design.

12) Public availability vs. retention

Retention (keeping an archival copy) is not the same as publication. Where the Cloud Services provide publication or sharing features, access controls may be available. You are responsible for the sharing settings you choose and for any decryption keys you distribute.

13) Third-party components

The Software and Cloud Services may include third-party components (including open-source). Those components may be governed by their own licenses, which apply to the extent required.

14) Updates and service changes

  1. Software updates. The Software may update automatically or manually. Updates may add, change, or remove features.
  2. Cloud Services changes. The Operator may modify, suspend, or discontinue parts of the Cloud Services, including for security, maintenance, or legal compliance.
  3. Changes to this EULA. The Operator may update this EULA. For material changes the Operator gives at least 30 days' advance notice in the notification area of the Catalog Dashboard and on catalog.org, stating the effective date. If you do not accept a material change, you may stop using the Software and Cloud Services before the effective date; continued use after the effective date constitutes acceptance. Changes required by law, court order, or urgent security needs may take effect immediately, with notice as soon as practicable.
  4. Transfer of the role of Operator. The Operator may transfer the distribution of the Software and the operation of the Cloud Services, together with the Operator's rights and obligations under this EULA, to a company or other organisation that takes over the role of Operator. You consent in advance to such a transfer. The Operator announces a transfer at least 30 days before it takes effect, in the same way as a material change, naming the successor. Your User Content and your BIT are not affected by the transfer.

15) Disclaimers

The Operator will provide the Cloud Services with reasonable skill and care, but does not guarantee uninterrupted availability unless agreed in writing.

If you are a consumer in the EU/EEA, the Software and Cloud Services must conform to this EULA and to mandatory conformity requirements for digital content and digital services (Directive (EU) 2019/770 as implemented in Dutch law), and your statutory remedies for non-conformity remain unaffected.

Subject to the foregoing, and to the maximum extent permitted by law, the Software and Cloud Services are otherwise provided “as is” and “as available”, without warranties of any kind, whether express, implied, or statutory, including implied warranties of merchantability, fitness for a particular purpose, and non-infringement.

Some jurisdictions do not allow certain disclaimers, so some of the above may not apply to you.

16) Limitation of liability

To the maximum extent permitted by law:

  1. Neither the Operator nor the Developer shall be liable for indirect, incidental, consequential, special, or punitive damages, or loss of profits, revenue, data, goodwill, or business interruption.
  2. The total liability of the Operator and the Developer for claims relating to the Software or Cloud Services shall not exceed the amount you paid to the Operator for the Cloud Services and/or Software in the 12 months before the event giving rise to the claim (or €50 if you paid nothing), unless mandatory law requires otherwise.

17) Termination and suspension

  1. You may stop using the Software and Cloud Services at any time.
  2. The Operator may suspend or terminate your access for breach, security reasons, legal compliance, or non-payment.
  3. Retention survives. Termination does not delete or remove content already uploaded to the Cloud Services, especially where the archival model applies.

18) Force majeure

Neither the Operator nor the Developer shall be liable for delays or failures in performance of the Software or Cloud Services resulting from events beyond reasonable control, including natural disasters, war, terrorism, cyberattacks, pandemic, government action, or internet/infrastructure failures.

19) Severability

If any provision of this EULA is held invalid, illegal, or unenforceable, the remaining provisions continue in full force. The invalid provision shall be modified to the minimum extent necessary to make it enforceable while preserving its intent.

20) Waiver

Failure or delay by the Operator or the Developer in enforcing a provision of this EULA does not constitute a waiver of that provision or of the right to enforce it later.

21) Governing law and disputes

21.1 Governing law

This EULA is governed by the laws of the Netherlands, excluding conflict-of-law rules, unless mandatory consumer law requires otherwise.

21.2 Disputes between you and the Operator

This section applies to disputes between you and the Operator arising from or relating to this EULA, the Software, or the Cloud Services.

Step 1 — Informal resolution (mandatory). Before initiating formal proceedings, you must contact the Operator at [email protected] describing your dispute. The Operator will attempt to resolve the matter within 30 days. You agree to engage in this step in good faith.

Step 2 — Mediation (mandatory). If Step 1 does not resolve the dispute, either party may refer the matter to mediation administered by a qualified mediator in the Netherlands, agreed upon by the parties or, failing agreement, appointed by the competent court. Each party bears its own mediation costs; the mediator's fees are shared equally, except that where you are a consumer, the Operator bears the mediator's fees. Mediation shall conclude within 60 days of referral unless the parties agree to extend. Mediation is without prejudice to a consumer's right to bring the dispute before the competent court at any time.

Step 3 — Court (last resort). If the dispute is not resolved through Steps 1–2, either party may bring the dispute before the competent court in the Netherlands for the district in which the Operator is domiciled or established, unless mandatory consumer law requires a different court.

Urgent relief. Nothing in this section prevents either party from seeking interim or injunctive relief from a competent court where necessary to prevent irreparable harm.

22) Contact

Roberto Bourgonjen, operator of the Catalog Cloud Services
Address: Lange Leidsedwarsstraat 96, 1017 NM Amsterdam, the Netherlands
Website: catalog.org
Email: [email protected]