Terms of Service

Terms of Service
(ToS)
for JDu Apps

Version dated: 12 August 2026


1. Provider and scope
1.1 Provider

The provider of the service is:

JDu Apps

Sole proprietor: Julian Dubbert

Eilenau 11

22087 Hamburg

Germany

Email: support@copy-for-trello.com

Website: copy-for-trello.com

1.2 Scope
These Terms of Service apply to all contracts between JDu Apps, sole proprietor
Julian Dubbert (hereinafter the “Provider”), and its customers (hereinafter the “Customer”)
concerning the use of the software and migration services provided by the Provider.

1.3 Incorporation and order of precedence
These Terms of Service are made available to the Customer in a reasonable manner before the contract is
concluded. The Customer may save or print the Terms of Service. By placing an order, the Customer agrees to
the applicability of these Terms of Service.

Individual agreements between the Provider and the Customer take precedence over these Terms of Service.
Deviating or conflicting terms of the Customer apply only if the Provider has expressly and in
writing consented to their applicability.

1.4 Consumers and entrepreneurs
The service is directed at both consumers and entrepreneurs.

Consumers within the meaning of these Terms of Service are natural persons who conclude a legal transaction
for purposes that are predominantly neither commercial nor related to their independent
professional activity (Section 13 of the German Civil Code – BGB).

Entrepreneurs are natural or legal persons or partnerships with legal capacity who, when
concluding the contract, act in the exercise of their commercial or independent professional
activity (Section 14 BGB).

Where provisions of these Terms of Service are addressed only to entrepreneurs or only to consumers, this is
expressly indicated. For consumers, the statutory consumer protection provisions apply without
limitation.


2. Subject matter and description of the service
2.1 Subject matter of the service
The Provider makes available an internet-based application with which customers can
automatically transfer data from supported project management and collaboration platforms into
other accounts, workspaces or supported target platforms.

The current focus of the service is the migration of Trello® boards.

Via the application, the Customer can connect a source account and a target account, select the
data to be transferred and start the migration.

The application reads the data released by the Customer from the source system and then
recreates them in the target system.

2.2 Explanation of migration
Migration means the technical transfer of data from an existing account or system into another
account or system.

For example, a customer may copy an existing Trello® board into another Trello® account or
another workspace.

The original board generally remains in place and is not deleted or moved by the migration.

2.3 Technical interfaces (API)
To perform a migration, the application uses the technical interface provided by the respective
platform, a so-called API (“Application Programming Interface”).

In simple terms, an API is a technical connection through which one program can read data from
another program or perform certain actions there.

For this purpose, the Customer grants the Provider the necessary permissions, for example via
OAuth or an API token.

Which data and functions are available via an API is determined by the respective platform. The
Provider has no influence over the functional scope of third-party platform APIs.

2.4 Data that may be transferred
Depending on the respective platform and its technical capabilities, the following data in
particular may be transferred:

  • Boards or projects
  • Lists or comparable structures
  • Cards or tasks
  • Card titles and descriptions
  • Labels
  • Checklists
  • Comments
  • Due dates
  • Status information
  • Attachments and files
  • Images
  • User assignments
  • User mentions and tags
  • Links and references
  • other data supported by the service

The data scope that can actually be transferred depends on the technical capabilities of the
respective platform, its API, the permissions granted and the concrete implementation of the
service.

2.5 Description of services: no guarantee of a complete 1:1 copy
The Provider owes performance of the migration in accordance with the functional scope of the
service available at the time of performance.

Complete technical identity between source and target system is not guaranteed.

In particular, data or functions may not be transferable if they:

  • are not provided by the platform’s API,
  • are available only with certain permissions,
  • originate from extensions or Power-Ups,
  • cannot be transferred due to technical limitations of the platform,
  • cannot be transferred due to API limits or other technical restrictions.

This may in particular affect custom fields, Power-Ups, certain activities, user assignments,
notifications or other platform-specific functions.

Before a migration starts, the Customer will be informed of any known limitations insofar as this
is technically possible and reasonable.

2.6 Unchanged source system
The application is generally designed to read the data of the source system and recreate them in
the target system.

The source board is generally not deleted, moved or archived by the migration.

2.7 Duration of the migration

The duration of a migration depends in particular on the following factors:

  • number of boards
  • number of lists
  • number of cards
  • number and size of attachments
  • number of comments
  • volume of data to be transferred
  • API speed and API limits of the third-party platform
  • current load on the service

A migration may take from a few minutes to several hours. Stated or estimated processing times
are non-binding unless a binding deadline has been expressly agreed.


3. Scope of services and configuration
3.1 Selection of the migration
Within the application, the Customer may select the data to be migrated and the desired target
environment.

3.2 Migration options
Where offered, the Customer may configure additional options. These may in particular include:

  • selection of individual boards
  • selection of multiple boards
  • selection of certain data types
  • transfer of attachments
  • transfer of comments
  • transfer of user mentions
  • user mappings
  • repair of internal or cross-platform card references
  • other options offered by the service

3.3 User mapping
Where source and target system use different user accounts, the service may enable a mapping
between source and target users.

For example, a mapping may be made according to the following scheme:

[Source user] → [Target user]

A successful mapping requires that the target user exists in the target system and has the
necessary permissions.

Complete technical restoration of all user mentions, tags or notifications cannot be guaranteed.

3.4 Test migration
The Provider may offer a free test migration. Where a test migration is offered, the conditions
stated on the website apply.

The free test migration currently covers one board with a maximum of 25 cards.

The Provider may change the scope and conditions of the free test migration for future customers
or discontinue the test migration.


4. Conclusion of contract
4.1 Offer on the website
The presentation of services and prices on the website does not generally constitute a binding
offer to conclude a contract, unless expressly stated otherwise.

4.2 Selection and order
The Customer may select and configure a migration via the designated ordering process.

Before completing a paid order, the Customer receives an overview of the essential contract data,
in particular:

  • selected service
  • scope of the migration
  • price
  • any applicable taxes
  • essential terms of performance

4.3 Conclusion of contract and advance payment
The contract is concluded only when the Customer places a binding order for the paid migration
and payment has been successfully completed via the payment service provider offered in the
ordering process.

Upon successful payment, the Provider accepts the order. The migration is released and performed
only after successful receipt of payment.

If payment fails (e.g. due to aborting the payment process, insufficient funds, or rejection by
the payment service provider), no contract is concluded. In that case, the Customer has no
payment or other contractual obligations.

4.4 Exception for entrepreneurs
For entrepreneurs, a deviation from the advance-payment rule (e.g. payment on invoice within 14
days) may be agreed individually upon separate request. In that case, the contract is concluded
already upon confirmation of the order by the Provider.

4.5 Correction of entries
Before submitting an order, the Customer is given the opportunity to review and, where
necessary, correct their entries.

4.6 Contract language
The contract language is German.


5. Prices and payment
5.1 Prices and price information
The prices stated on the website at the time of conclusion of the contract apply. Towards
consumers, prices are stated as total prices including statutory value-added tax where VAT is
chargeable. All prices are in euros.

The price displayed in the ordering process comprises all costs charged by the Provider to the
Customer for the booked migration. For the contractually agreed performance of the migration,
the Customer incurs no additional charges for technical service providers or other third parties
engaged by the Provider.

Towards entrepreneurs, prices are shown as net or gross prices in accordance with statutory
requirements. Unless expressly stated otherwise, the price is a fixed price for the specifically
selected migration process.

5.2 Paid migration
For a paid migration, the price displayed in the ordering process applies.

5.3 Method of payment
Payment is made in the ordering process using the payment methods offered there (e.g. credit
card, PayPal, instant bank transfer). Payment processing is carried out via external payment
service providers.

5.4 Payment service providers
Stripe in particular may currently be used as a payment service provider.

Supplementary terms of the respective payment service provider may apply to payment processing.
The Customer will be informed of these terms before the payment process begins.

5.5 Invoices
Invoices are generally made available to the Customer electronically once payment has been
successfully processed and the contract has been concluded.


6. Customer obligations
6.1 Authorisation to transfer data
The Customer warrants that they are authorised to read, transfer and have stored or created in
the target system the data to be migrated.

In particular, the Customer ensures that the migration does not infringe any third-party rights.

6.2 Necessary access rights
The Customer provides the access rights required to perform the migration.

The Customer is responsible for ensuring that the accounts and permissions used enable
performance of the desired migration.

6.3 Backup
The Customer is responsible for creating a suitable backup of the source data before a migration
begins.

In particular, the Provider recommends using the export or backup functions offered by the
respective platform before the migration.

The migration does not replace a backup.

6.4 Changes during the migration
The Customer should not make changes to the affected source data during an ongoing migration.

This concerns in particular:

  • creating or deleting cards
  • changes to cards
  • changes to lists
  • adding or deleting attachments
  • changes to comments
  • changes to user assignments

Changes during the migration may cause data not to be transferred, or not to be transferred in
full.

6.5 Access credentials
The Customer is obliged to treat access credentials, API tokens and other authentication means
carefully and to use them only for authorised purposes.


7. OAuth and API tokens
7.1 OAuth
Where the Provider supports OAuth, authorisation generally takes place via the OAuth mechanism
provided by the respective platform.

In that case, the Provider generally does not obtain knowledge of the Customer’s password for
the respective platform.

7.2 API tokens
Where API tokens are required, they are used solely to perform the services commissioned by the
Customer.

7.3 Revocation of permissions
The Customer may revoke granted permissions where this is provided for by the respective
platform.

The Customer remains responsible for revoking permissions that are no longer required after
completion of a migration, unless they are automatically withdrawn by the service.


8. Performance of the migration
8.1 Start
The migration starts after successful completion of the ordering and authorisation process and
once the technical requirements for performance are met.

8.2 Queue
The number of migrations that can run concurrently may be technically limited. In the event of
high load, migrations may be placed in a queue.

8.3 API limits
The third-party platform used may impose technical restrictions, in particular so-called rate
limits. Rate limits restrict the number of technical requests that may be made within a given
period.

If such limits are reached, the migration may be delayed or interrupted.


9. Errors and partially successful migrations
9.1 Technical errors
A migration may fail or be completed only in part for technical reasons. This may in particular
be caused by:

  • errors or outages of the third-party platform
  • API limits
  • missing permissions
  • changes to data structures
  • invalid or no longer available data
  • network problems
  • damaged files
  • technical errors within the service

9.2 Partially successful migration
A migration may be partially successful. In that case, some data were transferred successfully
while other data could not be transferred, or not transferred in full.

Where technically possible, the Provider informs the Customer of the status of the migration and
of identified errors.

9.3 Repetition of a migration and goodwill arrangement
In the event of a failed or substantially incomplete migration, the Provider offers to perform
the migration again, provided the migration error is not based on a circumstance for which the
Customer is responsible (e.g. defective source data, insufficient permissions, changes to the
source data during the migration).

Where the Provider offers a renewed performance as a goodwill gesture, no additional costs
arise. If the second performance also fails for reasons for which the Provider is responsible,
the Customer is entitled to a refund of the remuneration paid.

The Customer’s statutory rights in the event of defective performance remain unaffected.


10. Dependence on third-party platforms
Performance of a migration may depend on the availability and functioning of external platforms.
This concerns in particular their:

  • APIs
  • authentication procedures
  • permission models
  • data structures
  • rate limits
  • servers and infrastructure

The Provider has no influence over changes to or outages of such third-party platforms.

Changes to a third-party platform may cause individual functions of the service to be
restricted or no longer available.


11. Availability and maintenance
The Provider endeavours to achieve the highest possible availability of the service. A specific
minimum availability or a service level agreement (SLA) is not owed unless expressly agreed
otherwise.

The service may in particular be temporarily unavailable or only available to a limited extent
due to maintenance work, security updates, technical disruptions, overload, third-party
outages, network problems or force majeure.

Maintenance work may, for technical, security-related or operational reasons, also be carried
out at short notice or without prior announcement. The Provider endeavours to keep the impact of
maintenance work on the availability of the service as low as possible.

Where circumstances permit, planned maintenance work will be announced in advance.


12. Customer data and Customer rights
The data transferred by the Customer generally remain with the Customer or the respective rights
holder.

By performing a migration, the Provider does not acquire ownership or any other rights in the
customer data.

The Customer grants the Provider only the rights of use and processing required to perform the
agreed services. These rights exist only for the purpose of performing the contract and the
associated statutory obligations.


13. Third-party rights and lawful use
The Customer is responsible for ensuring that the data they transfer do not infringe third-party
rights. This concerns in particular:

  • copyrights
  • trade mark rights
  • personality rights
  • data protection rights
  • trade secrets
  • other protective rights

The Provider is generally not obliged to fully examine the content transferred by the Customer
for legal infringements before performing a migration.

Where there are concrete indications of unlawful use, the Provider is entitled to refuse or
interrupt a migration or temporarily restrict access to the service, insofar as this is
necessary to prevent the infringement or misuse.


14. Data protection and commissioned processing
The Provider processes personal data in connection with the provision and performance of the
service in accordance with the applicable General Data Protection Regulation (GDPR) and the
German Federal Data Protection Act (BDSG).

Further details are set out in the Provider’s privacy policy, which is made available to the
Customer before conclusion of the contract.

Where the Provider processes personal data on behalf of the Customer, a separate data processing
agreement is concluded. That agreement governs in particular:

  • the nature and scope of the data processing
  • the technical and organisational measures
  • the rights and obligations of the controller
  • sub-processing
  • the deletion and return of data

The Provider may engage further processors within the meaning of Article 28 GDPR to provide its
services. The Provider informs the Customer of the processors engaged in a suitable manner, in
particular by means of an up-to-date list of processors engaged. Engagement and replacement of
processors take place within the framework of the statutory and data-protection requirements.

This may in particular include providers for:

  • hosting
  • cloud infrastructure
  • payment processing
  • email delivery
  • databases
  • monitoring
  • technical security


15. Storage and deletion of migration data
15.1 Temporary storage
For the performance of a migration, customer data may temporarily be stored on the Provider’s
systems. This may in particular be required for:

  • processing of source data
  • interim storage of attachments
  • technical processing
  • error handling
  • retry of failed migrations
  • logging

15.2 Deletion
After completion or cancellation of a migration, temporarily stored data are generally deleted
within 14 days, unless statutory retention obligations or other legitimate reasons prevent this.

15.3 Backups
Data may be contained in technical backups for a limited period. Deletion from backups takes
place as part of the regular technical deletion cycles.


16. Liability
16.1 Unlimited liability
The Provider is liable without limitation for damage based on intent or gross negligence. This
also applies in the event of slightly negligent injury to life, body or health.

The Provider is also liable without limitation for damage arising from injury to life, body or
health caused by a negligent breach of duty by the Provider or by an intentional or negligent
breach of duty by a statutory representative or vicarious agent of the Provider.

16.2 Liability under mandatory law
Statutory liability provisions that may not be excluded or limited by agreement remain
unaffected. This concerns in particular:

  • liability under the German Product Liability Act
  • liability for fraudulently concealed defects
  • liability for the absence of guaranteed characteristics

16.3 Material contractual obligations
Material contractual obligations are those obligations whose fulfilment makes proper
performance of the contract possible in the first place and on whose compliance the Customer may
regularly rely. Within this contract, the following obligations in particular are material
contractual obligations:

  • the technically proper provision of the migration application
  • performance of the migration in accordance with the agreed scope of services
  • compliance with the agreed security standards for the processed data
  • observance of data-protection provisions

16.4 Limitation of liability for slight negligence
Where legally permissible, the Provider’s liability for damage caused by slight negligence is
limited to three times the remuneration paid for the migration, but in any event to a maximum of
EUR 5,000 per damage event. Typically foreseeable contractual damage means damage whose
occurrence must typically be expected in a contract of this kind, in particular:

  • the costs of repeating a failed migration
  • the costs of restoring data from a backup, provided the Customer has complied with their
    backup obligation

This limitation of liability does not apply in the event of a breach of a material contractual
obligation. In the event of a slightly negligent breach of a material contractual obligation,
liability is limited to the typically foreseeable contractual damage, unless the requirements of
Section 16.1 are met.

16.5 Towards entrepreneurs
Towards entrepreneurs, liability for damage caused by slight negligence is additionally limited
to the amount paid by the Customer for the relevant migration, where legally permissible and
where no material contractual obligation is affected.

16.6 Consequential damage
Where legally permissible, the Provider is not liable towards entrepreneurs for indirect damage,
loss of profit, business interruption or other consequential damage that is not a direct
consequence of a breach of duty by the Provider and was not caused by the breach of a material
contractual obligation.

Towards consumers, the statutory provisions apply.

16.7 Description of services: migration result
The Provider does not guarantee that a migration will be performed completely, free of errors or
in a manner that is technically fully identical to the initial state. This limitation describes
the scope of services owed and does not constitute a warranty.

The technical limitations of the migration described in these Terms of Service form part of the agreed
service.

16.8 Customer responsibility for backups
The Customer is responsible for creating a suitable backup of their source data before a
migration begins. The Provider assumes no liability for data loss arising because the Customer
failed to comply with their backup obligation.

16.9 Third parties
The Provider is not liable for disruptions, outages or changes of third-party platforms, APIs or
other external services, unless the Provider is responsible for those circumstances.

16.10 Warranty
If the migration is defective, the Customer may first demand subsequent performance. Subsequent
performance consists of repeating the migration or remedying the defect. If subsequent
performance fails, the Customer may, at their choice, demand a reduction of the remuneration or
withdraw from the contract.

Towards entrepreneurs, warranty claims must be asserted within a period of 12 months from
delivery of the service, unless a longer period is provided by law.

Towards consumers, the statutory warranty periods apply.


17. Indemnification
The Customer indemnifies the Provider against third-party claims based on the Customer having
transferred data without sufficient authorisation or on third-party rights having been infringed
through the use of the service initiated by the Customer.

The indemnification also covers reasonable costs of legal defence, insofar as the Customer is
responsible for the infringement.


18. Right of withdrawal for consumers
18.1 Statutory right of withdrawal
In distance contracts, consumers generally have a statutory right of withdrawal, unless a
statutory exclusion applies.

Details are set out in the separate withdrawal information notice.

18.2 Immediate start of the migration and expiry of the right of withdrawal
The Customer may expressly request that performance of the migration begin before expiry of the
withdrawal period. For this purpose, the Customer is informed separately in the ordering process
and must give their express consent by ticking a corresponding checkbox.

By consenting to early commencement of performance, the Customer simultaneously agrees that, if
they exercise the right of withdrawal, they owe the Provider a reasonable amount for the
services already provided. That amount corresponds to the pro-rata price for the services
already provided.

Where the service has been fully performed, the consumer’s right of withdrawal expires if the
Provider began performance only after the consumer gave express consent and at the same time
confirmed that they lose their right of withdrawal upon full performance of the contract by the
Provider.

18.3 Withdrawal during an ongoing migration
If a consumer exercises their right of withdrawal after expressly requesting that performance
begin before expiry of the withdrawal period, the statutory rules on the legal consequences of
withdrawal apply.

18.4 Full performance
Where the service has been fully performed, the right of withdrawal may expire early under the
statutory conditions.

The declarations and information required for this purpose are provided in the ordering process
and in the withdrawal information notice.

18.5 Withdrawal information notice
Where legally required, the consumer receives a separate withdrawal information notice including
a model withdrawal form.


19. Electronic communication
The Customer agrees that contract-related communication may generally take place electronically.
This may in particular include:

  • order confirmations
  • payment information
  • invoices
  • status messages
  • notifications of completed migrations
  • error messages
  • security-related information
  • information about the service

Marketing communications take place only where the statutory requirements are met.


20. Support
The Provider provides support via the following channels:

support@copy-for-trello.com

Unless expressly agreed otherwise, there is no entitlement to a specific response time.


21. Misuse of the service
The Customer may not use the service for purposes that violate applicable law or third-party
rights. In particular, it is prohibited to:

  • migrate data without corresponding authorisation
  • use third-party accounts without consent
  • use third-party access credentials without authorisation
  • circumvent security measures
  • burden the service with excessive or abusive requests
  • introduce malware or manipulated files
  • use the service for unlawful purposes

Where there is a justified suspicion of misuse, the Provider is entitled to take appropriate
measures to protect the service and third parties.


22. User account and termination
22.1 Deletion by the Customer
The Customer may delete their user account at any time, provided no outstanding contractual
obligations prevent this.

Deletion of the user account does not affect payment or other claims that have already arisen.

22.2 Termination by the Provider
The Provider may terminate a continuing obligation for good cause. Good cause may in particular
exist in the event of:

  • material breaches of these Terms of Service
  • misuse
  • unlawful use
  • unauthorised access to third-party data
  • default in payment
  • material endangerment of the security of the service

Statutory termination rights remain unaffected.

22.3 Suspension
Where there are concrete indications of misuse or a threat to security, the Provider may
temporarily suspend access insofar as this is necessary to avert the threat.


23. Intellectual property in the service
All rights in the software, website, user interface, documentation, technical concepts and other
components of the service developed by the Provider remain with the Provider or the respective
rights holders.

The Customer receives only the rights of use required for contractual use of the service. Source
code is not provided.

In particular, the Customer may not:

  • copy
  • resell
  • rent
  • sublicense
  • use in an automated manner outside the intended scope
  • technically modify

the service, where legally permissible. Mandatory statutory rights of the Customer remain
unaffected.


24. Changes and further development of the service
The Provider continuously develops the service further. Functions may be added, changed or
discontinued. This applies in particular to functions that depend on the technical capabilities
of external platforms.

For contracts with consumers, the statutory provisions on changes to digital products apply.

For continuing obligations, material changes will, where legally required, be announced in good
time.


25. Changes to these Terms of Service
The Provider may amend these Terms of Service where this is necessary due to changes in law, changes in case
law, technical developments or changes to the business model.

For existing continuing obligations, changes will be communicated to the Customer in a suitable
manner. Statutory rights of the Customer remain unaffected.


26. Set-off and right of retention
The Customer may set off counterclaims only insofar as they are undisputed, finally adjudicated
or ready for decision.

A right of retention may be exercised only insofar as the statutory requirements are met.

Towards consumers, the statutory provisions apply.


27. Assignment
An assignment of the Customer’s claims arising from the contractual relationship is permissible
where legally allowed. The statutory rules on the assignability of claims remain unaffected.


28. Force majeure
The Provider is not liable for events outside its reasonable sphere of influence, insofar as they
materially impair performance. These may in particular include:

  • natural disasters
  • war
  • official measures
  • large-scale outages of internet or telecommunications networks
  • outages of material infrastructure or cloud providers
  • cyber attacks despite appropriate protective measures
  • prolonged outages of third-party platforms

Mandatory statutory liability provisions remain unaffected.


29. Contract text and contract data
The Provider stores the contract and order data required for performance of the contract within
the framework of statutory requirements.

The Customer receives the legally required contract information and contractual documents on a
durable medium, in particular by email.


30. Limitation
The statutory limitation periods apply.

Towards entrepreneurs, claims for damages due to a defect become time-barred two years after
delivery of the service, unless a longer period is provided by law.

Towards consumers, the statutory limitation periods apply.


31. Consumer dispute resolution
The Provider informs consumers of the information required by law regarding participation or
non-participation in a dispute resolution procedure before a consumer arbitration body.

[Provider information]


32. Governing law
The law of the Federal Republic of Germany applies.

Towards consumers, this choice of law applies only insofar as it does not deprive the consumer
of the protection afforded by mandatory provisions of the state in which the consumer has their
habitual residence.

The UN Convention on Contracts for the International Sale of Goods (CISG) does not apply, where
legally permissible.


33. Place of jurisdiction
Towards consumers, the statutory places of jurisdiction apply.

If the Customer is a merchant, a legal entity under public law or a special fund under public
law, the Provider’s registered seat may — where legally permissible — be agreed as the place of
jurisdiction.


34. Severability
Should any provision of these Terms of Service be or become wholly or partly invalid, the remaining provisions
remain valid.

The parties undertake to agree, in place of the invalid provision, a valid provision that most
closely approximates the commercial purpose of the invalid provision. The same applies if a gap
in these Terms of Service becomes apparent.


35. Supplementary documents
Supplementary contractual and information documents may in particular include:

1. Privacy Policy
2. Data Processing Agreement
3. Withdrawal information notice
4. Model withdrawal form
5. Price list
6. Service overview
7. where applicable, special support or service terms

The statutory requirements regarding incorporation and order of precedence of these documents
remain unaffected.


36. Trade marks and third-party notices
Trello® and other product, company and trade mark designations mentioned in connection with the
service are trade marks or distinctive signs of their respective owners.

The Provider is an independent third-party provider.

Unless expressly stated otherwise, there is no partnership, corporate affiliation, endorsement,
certification or other official connection between the Provider and the respective platform
providers.

The use of names and trade marks of supported platforms serves solely to describe the
compatibility and intended use of the service.