Terms of use

PaperPlane Terms of Service

Version: 1.0 · Effective: 27 October 2026

1. Scope and parties

1.1 These Terms govern the use of PaperPlane (the "Service"), a web service for managing paper submissions, reviews and decisions for conferences, workshops and similar events. The Service is provided by META Frame Technologies Softwaredesign & Consulting GmbH, Hedwigstraße 50, 44149 Dortmund, Germany (Amtsgericht Dortmund, HRB 12709, VAT ID DE188479310; further provider details in the Impressum at the Service's /imprint page) ("we", "us").

1.2 These Terms apply to:

1.3 The Service is offered only to businesses, public bodies, universities, research institutions and persons acting in a professional capacity, not to consumers within the meaning of § 13 BGB. When registering, users state the company, institution or organization they act for, and thereby confirm that they act in that capacity and not as consumers. Participants, who do not register, take part in connection with a conference, workshop or similar professional or academic event and likewise act in a professional or academic capacity, not as consumers; they confirm this when they accept these Terms (section 2.4).

1.4 Conflicting or supplementary terms of a Customer apply only if we agree to them in writing. We may conclude an individual agreement with a Customer in text form, for example on fees and limits for a project (section 8.5). In the points it regulates, the individual agreement prevails over these Terms; in all other respects these Terms apply.

1.5 The Service always asks authors, on each submission, to declare third-party content and competing interests, and always asks reviewers to declare a conflict of interest with the submission before they respond to an invite. An organizer may also ask participants to accept additional conference-specific terms, for example a publisher's copyright terms. Those additional terms are agreements between the participant and the organizer or publisher, not with us, and the organizer is responsible for their content.

1.6 A project is the space in the Service that a Customer sets up for one edition of a conference, workshop, seminar or similar event.

2. Accounts

2.1 You must provide accurate registration information and keep it up to date.

2.2 You must keep your sign-in credentials confidential and tell us promptly if you suspect unauthorized use. You are responsible for activity under your account unless you are not at fault.

2.3 If you register on behalf of an organization, you confirm that you are authorized to bind it to these Terms.

2.4 Participants without an account. Authors and reviewers do not create an account; they access the Service through a personal link provided by the organizer. They may submit or review only after they have accepted these Terms and confirmed that they have read the Privacy Policy.

3. The Service

3.1 The functions of the Service are described in the product and on our website at the time of ordering. We may further develop the Service, provided that, outside the Pilot (section 8), its essential functions during ongoing paid use are not materially reduced.

3.2 We provide the Service with commercially reasonable care. We aim for high availability but do not guarantee uninterrupted availability unless separately agreed. Planned maintenance is announced in advance where reasonably possible.

3.3 Features marked as beta are provided for evaluation, may change or be removed, and are excluded from any availability or support commitments.

3.4 While the Service is offered in the Pilot (section 8), section 3.3 applies to the Service as a whole, features may be changed, limited or withdrawn, and we owe no availability commitments beyond section 3.2.

3.5 AI features. Parts of the Service use artificial intelligence to generate or suggest content (“AI features”). AI features are marked as such in the Service. Their results are generated automatically and may be inaccurate or incomplete; the user remains responsible for checking and using them. Canvas generate, transcription, and title generation can be used by any signed-in PaperPlane user. Programme generate can be used by a project organizer or an admin. Authors and reviewers on a personal link cannot use AI features. AI features cannot be switched off. To provide an AI feature, that user’s inputs and the project content needed for that feature may be sent to our AI provider as described in the Privacy Policy.

4. Content and rights

4.1 Your content stays yours. Papers, abstracts, reviews, messages, and other material uploaded by users ("Content") remain the property of their authors or rights holders. We do not claim ownership and do not require any transfer of copyright.

4.2 Licence to operate the Service. You grant us a non-exclusive, royalty-free, worldwide licence, limited to the duration of storage, to store, copy, convert (for example to generate previews or anonymized versions), transmit and display Content, solely to provide the Service to the Customer and its participants. This includes backups, technical operations, and processing by AI features when a user who can access that feature uses them. We do not use Content for advertising or to train machine-learning models.

4.3 Visibility within a project. Content is visible to other users of a project according to the organizer's configuration, for example to assigned reviewers or the program committee. Organizers may publish submission metadata (titles, authors, affiliations, abstracts, session information) of accepted papers in connection with the event.

4.4 Submitter warranties. When you submit Content you confirm that:

4.5 Confidentiality of reviewing. Participants may only use submissions, reviews and discussions they can access for the review process they were invited to. They must not disclose, copy or otherwise exploit them, including by uploading them to third-party tools that do not keep them confidential, unless the organizer or the rights holder permits it.

4.6 Rights of co-authors and other rights holders. Co-authors and other rights holders who do not use the Service themselves and do not accept these Terms are not bound by section 4.2. The submitting author (section 4.4) and the Customer are responsible for obtaining from them the rights and consents needed for us to use Content as set out in section 4.2, for example through the call for papers and the submission form.

5. Acceptable use

You must not:

6. Suspension and removal

6.1 We may block Content or suspend accounts, temporarily or permanently, where there are concrete indications of a serious breach of these Terms or of law, taking the legitimate interests of the affected users into account. Where reasonable, we notify the affected user or Customer in advance and give them an opportunity to respond.

6.2 We are not obliged to monitor Content, but will act on notices of unlawful content. We do not verify the origin or authorship of Content, including whether it was created or assisted by AI tools. Rules on the use of AI tools in submissions and reviews are set by the Customer for its events; we give no warranty that Content complies with such rules.

6.3 Notices. Anyone may notify us of content they consider unlawful by email to support@paperplane.services; this address is also shown in the Service. The notice should explain why the content is unlawful, give its exact location (for example URL), state the notifier's name and email address, and confirm that the notice is submitted in good faith. We confirm receipt, decide in a timely, diligent and objective manner (usually within five to seven working days), and inform the notifier of our decision and the available redress options.

6.4 Statement of reasons. If we remove or block Content, or suspend or terminate an account because the Content is unlawful or conflicts with these Terms, we inform the affected user at the latest when the measure takes effect, with a clear statement of the facts and grounds, whether automated means were used, the legal or contractual basis, and the options for redress, unless a legal obligation prevents this.

6.5 Points of contact. Users, authorities and the European Commission can contact us about matters under the Digital Services Act at support@paperplane.services. We communicate in German and English.

6.6 Content moderation. We do not monitor Content proactively. Notices are reviewed by our staff; we do not use automated tools to detect or decide on Content. We may remove a reported paper so other users of that project no longer see it. Section 6.4 applies.

7. Data protection

7.1 Our processing of personal data as controller is described in our Privacy Policy.

7.2 For personal data in a Customer's projects, the Customer is the controller and we act as processor under the Data Processing Agreement, which forms part of these Terms for every Customer. If these Terms and the Data Processing Agreement conflict on the processing of personal data, the Data Processing Agreement prevails. This does not apply to liability between the parties, which is governed by section 12 of these Terms and section 12 of the Data Processing Agreement.

7.3 The Customer is responsible for the lawfulness of the data it collects through the Service (including custom form fields) and for informing its participants about its own processing of their personal data. The Service is not designed for special categories of personal data (Art. 9 GDPR); Customers should not collect them unless strictly necessary.

8. Pilot program and fees (Customers)

8.1 Pilot program. The Service is currently offered in a pilot program (the "Pilot"). The Pilot starts when these Terms take effect and lasts until we announce its end under section 8.7. During the Pilot, fees are determined by this section 8 only. There are no charges for Participants.

8.2 Pay what you want. The Customer decides what it pays for the use of the Service in each project during the Pilot (the "Pilot Fee"). The Pilot Fee is a net USD amount for the project. Amounts below USD 5 cannot be stated, because below this amount payment and administrative costs exceed the fee. The amount may not be zero. The Customer can state the Pilot Fee at any time. In addition, we invite the Customer by email and by notice in the Service to state the Pilot Fee for a project, at times we choose; there is no fixed due date. If the Customer pays, we start a Paddle transaction for that net USD amount for the project (section 8.6). If the Customer does not pay, we create no invoice. The Pilot Fee is the consideration for the use of the Service. A Customer that has not paid any Pilot Fee is a "free account"; its use of the Service is free of charge, and sections 11.1 and 12.3 apply to it.

8.3 Counting papers. For the limit in section 8.4, papers are counted per project. A paper counts exactly once, when it is first successfully submitted. Abstract and full-paper submissions of the same paper count as one paper. Later events, including revision, review, acceptance, rejection, and desk rejection, do not change the count. Drafts, failed uploads and technical retries are not counted. Any removal from the project, including withdrawal, drops that paper from the count.

8.4 Soft lock past the threshold. Once the configured number of papers have been submitted in a project—the default is 60—we continue to accept further submissions; submissions are never stopped. For every paper beyond that threshold, organizers and other users see the title and the author names but cannot review, comment, assign, or download it. The soft lock applies whether or not a Pilot Fee has been paid. It is lifted only by an individual agreement: the Customer contacts us by email at support@paperplane.services (section 8.5).

8.5 Individual agreements. For projects with more papers, or for other conditions, we may conclude an individual agreement with the Customer in text form, for example on fees and limits. That agreement is the text exchanged with the Customer. The Service does not store an agreement date or reference. The Customer's use of the Service remains subject to these Terms; the individual agreement prevails in the points it regulates (section 1.4).

8.6 Invoicing and payment through Paddle. When the Customer pays a Pilot Fee, we start a Paddle transaction for the net USD amount stated for the project. Pilot Fees are paid through Paddle.com Market Ltd. ("Paddle"), which acts as merchant of record. We issue each invoice as a custom invoice through Paddle. The purchase contract for the Pilot Fee, payment, invoicing and sales tax are governed by Paddle's checkout buyer terms (https://www.paddle.com/legal/checkout-buyer-terms), which are shown at checkout. The use of the Service itself is governed by these Terms. Paddle adds sales tax or applies the reverse-charge procedure where applicable. Refunds of Pilot Fees are possible only under the terms of Paddle and mandatory law; we do not grant refunds of our own.

8.7 End of the Pilot and standard prices. Either party may end the Pilot at any time with effect from the end of a calendar month by notice in text form. We will announce the end of the Pilot and the standard prices that apply afterwards in text form at least six (6) weeks in advance. The standard prices apply only to papers first submitted after the end of the Pilot; papers first submitted during the Pilot are not charged at the standard price afterwards. If the Customer does not agree to the standard prices, it may terminate with effect from the end of the Pilot.

8.8 No minimum term. There is no minimum term and no automatic renewal. Existing projects remain accessible under the retention rules in section 10. This section does not limit the Customer's switching right under section 10.

9. Term and termination

9.1 The agreement between you and us under these Terms runs for an indefinite period. Users may close their account at any time. Amounts invoiced under section 8 remain payable.

9.2 We may terminate free accounts with 12 weeks' notice, stating a reason such as inactivity. Either party may terminate for good cause without notice.

9.3 If an account is involved in an ongoing review process, closing it may be postponed until the organizer can reassign the affected tasks, as far as this is necessary for the process.

10. Data export and deletion

10.1 Customers can export their project data in the formats offered by the Service while their account is active.

10.2 Right to switch. The Customer may at any time switch to a data processing service of another provider, or port its exportable data and digital assets to its own ICT infrastructure, or instead have them deleted. To initiate this, the Customer gives us notice in text form (the "Switching Notice") with a notice period of no more than two (2) months. The Switching Notice may cover all or part of the Service and the Customer's data.

10.3 Transition period. The transition period is thirty (30) calendar days and begins when the notice period ends. The contract remains applicable during the transition period. During this period we provide reasonable assistance, act with due care to maintain business continuity, and maintain a high level of security.

10.4 Technical infeasibility. If we determine that switching cannot be completed within thirty (30) days for technical reasons, we will inform the Customer within fourteen (14) working days after receiving the Switching Notice, explain why, and propose an alternative transition period of no more than seven (7) months. The Customer may extend the transition period once by a period it considers appropriate.

10.5 Exportable data and digital assets. An export is one ZIP. The caller can omit metadata, participants, files, or review reports. Quota-locked papers are omitted. When reviewer identity is hidden, reviewer names and emails are omitted. When metadata is included, the ZIP contains JSON for a subset of project settings. Review blind mode is not included. There is no form definition or form schema. For each unlocked paper it contains the id, serial, title, track, submission count, the current decision (accept, reject, or revise), and whether the author was notified. It does not contain the submission snapshot or the decision note. When participants are included, the ZIP contains JSON for authors who have an email: name, email, role, and paper ids. Affiliation is not included. Authors without an email are omitted. When reviewer identity is visible, it also contains the reviewer name, email, and assignment ids. When files are included, the ZIP contains the latest stored file, unchanged, of these types for each unlocked paper: paper document, source archive, supplementary file, licence acceptance, signed licence, and interest statement. Older versions and other file types are not included. Unreadable files are skipped. A structured conflict-of-interest record is not included. When review reports are included, the ZIP contains each submitted review for an unlocked paper whose reviewer signals are visible: recommendation, confidence, scores, comments to authors, comments to the chair, submitted time, and a reviewer-uploaded PDF when one exists. Reviewer name and email are included only when participants are also included and reviewer identity is visible. A review that was never submitted is not included. The ZIP does not contain bids or discussion or comment threads. Structured data is JSON. There is no CSV.

10.6 Retrieval period and deletion. After the transition period ends, the Customer may retrieve its exportable data for at least thirty (30) calendar days. After that period we delete the Customer's data within 30 days, subject to statutory retention obligations. Copies in shared backups are not deleted for one customer. Postgres backups are kept for 7 days. Deleted blob versions are kept for 43 days. Those copies age out only when that shared retention expires.

10.7 End of contract. The contract ends when the switching process is successfully completed. Amounts invoiced under section 8 for the period until then remain payable. We do not request Pilot Fees in advance.

10.8 Fees. We do not charge switching charges. Amounts invoiced under section 8 remain payable until the contract ends.

10.9 Information before signing. The Customer can store and reproduce these Terms before concluding the contract.

10.10 If the agreement ends without a Switching Notice, project data remains stored for 24 months and can be viewed and exported. We remind the Customer before deletion. Closing an account does not start deletion of project data. When the agreement ends without a Switching Notice, project data is deleted within 30 days only after that 24-month hold. Account and profile data are deleted or anonymized within 30 days of account closure, subject to statutory retention obligations. Copies in shared backups are not deleted for one customer. Postgres backups are kept for 7 days. Deleted blob versions are kept for 43 days. Those copies age out only when that shared retention expires.

11. Warranty

11.1 For free accounts, we are liable for defects only if we fraudulently concealed them.

11.2 For paid use, statutory warranty law for rental-type contracts applies, with the exception that strict liability for defects existing at the start of the contract (§ 536a(1), first alternative, BGB) is excluded.

12. Liability

12.1 We are liable without limitation for intent and gross negligence, for injury to life, body or health, under the German Product Liability Act, and to the extent we have given a guarantee.

12.2 In cases of slight negligence, we are liable only for breach of an essential contractual obligation (an obligation whose fulfilment makes proper performance of the contract possible in the first place and on whose fulfilment the other party may regularly rely). In that case our liability is limited to the typical, foreseeable damage and to the higher of (a) the fees paid by the Customer in the 12 months before the damaging event and (b) EUR 2,000.

12.3 For free accounts, our liability for slight negligence is excluded, except in the cases listed in 12.1.

12.4 We are liable for loss of data only to the extent the loss would have occurred even if the Customer had exported its data regularly and appropriately.

12.5 These limitations also apply to our employees, representatives and agents.

13. Indemnity

The Customer indemnifies us against third-party claims arising from Content uploaded by it, or from its breach of these Terms, including reasonable legal defence costs, unless it is not responsible for the breach.

14. Changes to these Terms

14.1 We may change these Terms for valid reasons (for example changes in law, case law or regulatory requirements, or new features). We will notify users of changes in text form at least 6 weeks before they take effect.

14.2 Non-material changes. If a change (a) is required by law or an authority, (b) only clarifies wording or corrects errors without changing rights or obligations, or (c) adds new functions or services without changing existing functions, fees or liability, it takes effect on the date stated in the notice unless the user objects in text form before that date. Our notice will point out this effect of silence and the right to object.

14.3 Material changes. Changes affecting essential functions of the Service, the relationship between performance and consideration, fees or liability require the user's express consent. Without consent, the existing Terms continue to apply. We may then terminate the agreement with effect from the end of the current billing period.

14.4 Fees. Price changes are governed exclusively by section 8.7.

14.5 If a user objects to a change under section 14.2, either party may terminate the agreement with effect from the date the change would have taken effect. Section 10 applies.

15. Final provisions

15.1 German law applies, excluding the UN Convention on Contracts for the International Sale of Goods (CISG).

15.2 If the Customer is a merchant, a legal entity under public law or a special fund under public law, the exclusive place of jurisdiction is Dortmund, Germany.

15.3 Should any provision be invalid, the remaining provisions remain unaffected.

See also Privacy and Imprint.