MOIMio

The Allocation Engine.

The Allocation Engine is the heart of Moimio. It assigns participants to rooms, groups and teams by the rules you define. What used to take a weekend is done in minutes.

01

Rules you set

What absolutely needs to stay fixed, you decide. How many people fit in a room. Which units are gender-separated. Which groups should stay together. The engine holds to that wherever it can.

02

Who with whom

The Park family want to stay in one room. A youth group should remain connected across multiple rooms. Eight friends arrive with the same group code. Moimio keeps them linked during allocation.

03

When something changes

Registrations keep coming in. Someone cancels on Wednesday, a family signs up late on Thursday. One more click. Allocation runs again. Existing assignments stay in place where possible.

When preferences conflict, the more important one takes priority. The engine shows you every decision and why it came out the way it did. A group code takes precedence over a "stay-together" mark, for example.

The full workflow

  1. Registration

    The public registration form: multilingual, with group codes for people signing up together and your own fields for your event. The form interface appears in each participant's language and in yours. Free-text answers come through as written.

    A registration form everyone can use.

    Completed registration form

  2. Allocation

    Where the rules, preferences and group codes from above come together. The engine produces a proposed allocation you can review and commit when ready, or roll back if something needs adjusting.

    A reviewable plan, before anything is committed.

    The Allocation Engine in action

  3. Event-day check-in

    Open the dashboard on event day: who's here, who's missing, who registered at the desk. Tick off names. Everything in one view, no switching between menus.

    One view instead of ten tabs.

    Event-day check-in dashboard

  4. Reports

    Printable room and small group lists. Can be saved as a PDF file or exported as CSV for accounting and your own records.

    Lists and exports for your specific purposes.

    PDF preview of a room list

Built deliberately

Traceable. Every change to an allocation is saved. Who changed what, and when. When someone asks why they ended up in a particular room, you can show them.

EU-hosted, no third-party tracking. Your participants' data stays where it should. No advertising cookies, no tracking pixels, no profiling.

Open source. Every line of code is readable. If you prefer, you can self-host the same software free of charge from our side.

Designed for mobile, too

The full admin interface works on a phone. Run allocations, check participants in, review groups. No matter which device you use.

Allocation board on mobile
Check-in dashboard on mobile

Six languages

Registration forms, the user interface and PDF exports are currently available in:

Deutsch · English · 한국어 · Español · Português (Brasil) · Français

Participants fill out the form in their language. You see the form in yours. Free-text answers come through as written.

That's the whole workflow.

Legal Notice

Pistio
Sole trader registered in the United Kingdom
Proprietor: Johannes Kim
66 Paul Street
London EC2A 4NA
United Kingdom
Contact: [email protected]

Refund Policy

Last updated: 4 June 2026

This policy explains when a payment for Moimio can be refunded, and how to request a refund. Moimio is operated by Pistio, a sole trader registered in the United Kingdom, of 66 Paul Street, London EC2A 4NA. Payments are handled by Paddle as Merchant of Record, which means Paddle is your contracting party for the purchase and processes any refund.

1. How Moimio is paid for

Moimio Hosted costs €150 for each event, plus any applicable tax, for an event of up to 300 participants. Each €150 payment is an event credit: it lets you run one event. Your first payment creates your account and gives you one event credit; any further payment adds another, and you may hold a small number in advance. Creating an event uses one credit.

2. Your first payment is covered by a 30-day guarantee

Your first payment, the one that creates your account, carries a 30-day money-back guarantee. Within 30 days of that payment you may request a full refund, even if you have already created and run your event. Because this payment is what brought your account into being, refunding it closes your account and erases its data straight away: there is no export period and no reactivation window in this case. You therefore keep either the refund or the data, not both.

3. Later event credits are refundable while unused

Any event credit you buy after the first is refundable in full within 30 days of purchase, for as long as it remains unused. Once you create an event using a credit, that credit is spent and is no longer refundable. You always confirm before a credit is used, so a credit is never spent by accident. Unused credits do not otherwise expire.

4. After 30 days

Once 30 days have passed since a payment, that payment is final and is not refundable, except where applicable law provides otherwise.

5. How to request a refund

Refunds are handled by Paddle, our Merchant of Record. To request one, use the link in your Paddle receipt, or go to paddle.net. You do not request a refund by deleting your account inside Moimio: deleting your account is a separate action with its own data-retention process, described in section 7.

6. Your statutory rights and Paddle’s terms

This policy applies alongside your statutory rights as a consumer, where those apply to you, and alongside Paddle’s Buyer Terms and Conditions and Refund Policy. Where any of these gives you a stronger right, the stronger right applies. Nothing in this policy affects your rights in respect of a product that is faulty, not as described, or not fit for purpose.

7. Refunds and closing your account

A refund of your first payment erases your account immediately, as described in section 2. Closing your account without a refund works differently: nothing is deleted at once. Your account is paused; for 30 days you can download a complete copy of your data through a private link, with no sign-in needed; for 44 days you can reopen the account in one click, with no payment; and only after that is your data erased, backups included. This lifecycle is also summarised on the pricing page and set out in the Data Processing Agreement.

8. Refund abuse

A refund may be declined where there is evidence of fraud, refund abuse, or other manipulative behaviour. This does not affect your rights in respect of a product that is faulty, not as described, or not fit for purpose.

Questions about this policy? Write to [email protected].

Data Processing Agreement

Last updated: 28 May 2026

This Data Processing Agreement (the “DPA”) governs how Pistio processes personal data on behalf of organisations using Moimio. It mirrors the processor clauses agreed at checkout as part of the Moimio Terms; the two are kept consistent. For most customers the version agreed at checkout is sufficient. A countersigned copy is available to organisations whose own compliance requires a separate signed agreement.

This DPA forms part of the agreement between:

(1) The Customer — the organisation that holds a Moimio account (“Controller”); and

(2) Pistio, a sole trader registered in the United Kingdom, of 66 Paul Street, London EC2A 4NA (“Processor”),

and governs the Processor’s processing of personal data on the Controller’s behalf in connection with the Moimio service.

1. Definitions

Terms such as “personal data”, “processing”, “controller”, “processor”, “data subject”, and “personal data breach” have the meanings given in the UK GDPR and EU GDPR as applicable. “Applicable Data Protection Law” means the UK GDPR, the EU GDPR, and any other data-protection laws applicable to the processing.

2. Subject matter, nature, and purpose

The Processor processes personal data on the Controller’s behalf solely to provide the Moimio service: the registration of event participants and their assignment to rooms, groups, and teams according to the Controller’s configuration. Processing continues for the duration of the Controller’s Moimio account.

3. Categories of data and data subjects

See Annex 1.

4. Controller instructions

4.1 The Processor processes the personal data only on the Controller’s documented instructions, including as set out in this DPA, the Moimio Terms, and the Controller’s configuration and use of the software.

4.2 The Processor informs the Controller if, in its opinion, an instruction infringes Applicable Data Protection Law.

4.3 The Processor does not use the personal data for its own purposes.

5. Processor obligations

The Processor shall:

  1. ensure that persons authorised to process the personal data are bound by an obligation of confidentiality;
  2. implement the technical and organisational security measures set out in Annex 2;
  3. respect the conditions in clause 6 for engaging subprocessors;
  4. taking into account the nature of the processing, assist the Controller by appropriate measures, so far as possible, in fulfilling the Controller’s obligation to respond to requests by data subjects exercising their rights;
  5. assist the Controller in ensuring compliance with its obligations relating to security, breach notification, data protection impact assessments, and prior consultation, taking into account the nature of processing and the information available to the Processor;
  6. at the Controller’s choice, delete or return the personal data at the end of the provision of services, and delete existing copies, as described in clause 8;
  7. make available to the Controller information necessary to demonstrate compliance with this DPA, and allow for and contribute to audits as set out in clause 9.

6. Subprocessors

6.1 The Controller grants general authorisation to the Processor to engage the subprocessors listed in Annex 3.

6.2 The Processor imposes data-protection obligations on each subprocessor equivalent to those in this DPA, and remains fully liable to the Controller for the performance of each subprocessor.

6.3 The Processor informs the Controller of any intended addition or replacement of a subprocessor, giving the Controller a reasonable opportunity to object.

7. Personal data breach

The Processor notifies the Controller without undue delay after becoming aware of a personal data breach affecting the Controller’s personal data, and provides the Controller with the information reasonably necessary for the Controller to meet its own breach notification obligations.

8. Deletion and return

On closure of the Controller’s account, participant personal data is made available to the Controller for export for 30 days, then erased in line with the Moimio retention schedule. The workspace and its data, including routine backups, are permanently erased within 44 days of account closure, save that copies present in routine backups age out of the backup retention schedule within a maximum of six months for individually deleted events.

9. Audit

The Processor makes available to the Controller information necessary to demonstrate compliance with this DPA and contributes to reasonable audits, including inspections, conducted by the Controller or an auditor mandated by the Controller, on reasonable notice and subject to confidentiality.

10. International transfers

Personal data is hosted and processed within the European Union (Germany). The Processor, Pistio, is established in the United Kingdom and accesses the personal data from there to operate and support the service. Personal data therefore moves between the United Kingdom and the European Economic Area; those flows are covered by the European Commission’s adequacy decision for the United Kingdom and by the United Kingdom’s recognition of the EEA, so no additional transfer safeguards are required. The Processor does not transfer the personal data to any country outside the United Kingdom or the EEA except under safeguards permitted by Applicable Data Protection Law.

11. EU and UK representatives

For any data-protection matter in connection with this agreement, including the role of an EU representative under Article 27 EU GDPR where one is required, contact [email protected].

12. Liability and governing law

12.1 Each party’s liability under this DPA is subject to the limitations and exclusions of liability set out in the Moimio Terms.

12.2 This DPA is governed by the laws of England and Wales.

Annex 1 — Categories of data and data subjects

Data subjects: participants in events organised by the Controller (for example, attendees of retreats, conferences, or camps).

Categories of personal data: names; contact details (such as email address); dietary, allergy, or accessibility requirements where entered by the Controller; group, room, and team assignments; and any other information the Controller chooses to enter about participants.

Dietary, allergy, or accessibility information may constitute special-category (health) data. The Controller is responsible for ensuring it has a lawful basis for entering such data.

Annex 2 — Security measures

  • Hosting within the EU (Germany).
  • Per-tenant isolation: each Controller’s workspace runs in its own isolated container with its own database.
  • Access controls limiting access to authorised persons.
  • Encryption of data in transit (HTTPS/TLS).
  • Regular encrypted backups, with defined retention and erasure.
  • Logical separation of each Controller’s data from every other Controller’s data.

Annex 3 — Subprocessors

Subprocessor Role Location
Hetzner Hosting and infrastructure Germany (EU)
Paddle Payment processing (Merchant of Record) EU / global
Mailjet Transactional email delivery EU
Cloudflare DNS, content delivery, website hosting Global

A countersigned PDF copy of this agreement is available to customers on request. Write to [email protected].