Canada and the European Union, hosted on AWS.
Set when your organization is created, never revisited.
From registrations and payments to backups and AI processing.
For clients who need a country beyond Canada or the EU.
The region is picked on the Data residency step of the event wizard, right before Review: the moment your organization is actually created, on your very first event. Neither Canada nor the EU is preselected, and a confirmation dialog asks you to be sure before anything is saved. There's no tool to move an organization from one region to the other afterward, so that pause is doing real work: an organizer who genuinely needs a presence in both runs two organizations, not one with a switch.
Once your organization exists, its region shows up as a read-only Data location card on Organization → Profile, next to your logo, company information and brand colours (pictured above). A "What this means" statement expands into a paragraph you can lift straight into a privacy notice or a procurement questionnaire, with no rewriting needed.
It's a longer list than you'd guess. Your organization's settings and team roster; every event you run and everything inside it; registrations, profile answers and form responses; orders, tickets and payment records; sessions, speakers, sponsor and exhibitor companies, contacts; meetings, messages and the notes attached to them; uploaded files and images; badges, check-ins and attendance logs; the emails your organization sends; your analytics. Search indexes, system logs and backups too; none of it is carved out as an exception.
AI stays in the region too. For an EU organization, Ask Moostoo, AI matchmaking, profile-writing help and floor-plan import all run on models hosted in the EU, and the assistant will say so if you ask it directly. If a feature has no EU-hosted model yet, nothing gets quietly routed to a US server — Moostoo switches that feature off for the organization until it does.
A person's sign-in, their email addresses and their password or SSO provider, lives in whichever region they first created their account in, not wherever they're currently attending an event. That's how one account can reach a Canadian organization's event and an EU organization's event without creating two logins. To route each sign-in correctly, Moostoo keeps a small index in Canada: account IDs, which region each one lives in, and a keyed fingerprint of each email address. No names, no physical addresses, no passwords.
Day to day, this is invisible. The admin app, the attendee app and your event website all live at the same addresses regardless of region, and someone who attends a Canadian organization's event and an EU organization's event sees both in one list. Screens that gather events across several organizations at once (an attendee's full event list, their cross-event agenda) ask each region directly; if one happens to be unreachable, the rest still load, with a note that a region couldn't be reached rather than a broken page.
The two standing regions cover most of our organizers, and once an organization is created, its data doesn't move; that part is fixed by design and it's not something we'll make an exception on. What we can do is set up a different one from the start. If your organization needs to host in the United States, mainland China or another country Amazon Web Services operates in, Moostoo can provision that region as part of your onboarding, before your organization and its first event exist. It isn't a dropdown next to Canada and the EU yet, so talk to sales about your specific country and compliance requirements and we'll scope what's involved.
Data residency isn't a paid add-on held back for one tier. Every organization, whether it's on Moostoo Tickets or the full event app, chooses its region once at signup and gets the exact same guarantee for everything it stores.
You don't have to write this from scratch. The Data location card on your organization profile carries a ready-made "What this means" statement, worded for pasting into a privacy notice or a procurement questionnaire, so the answer in your paperwork matches the answer in the product.
Five steps from signing up to a permanent, documented answer.
Create your account with your work or personal email. You land straight on the event wizard for your first event.
Name your event, pick dates and timezone, choose the event type and format.
This step appears only on your first event, because it's the moment your organization is created.
Neither is preselected. Check the organization name shown underneath before you continue.
A confirmation dialog names your organization and its region. Once you confirm, it's permanent.
No. The region is set when your organization is created and there's no tool to change it afterward. If you need a presence in both, you run two separate organizations.
Yes. Ask Moostoo, AI matchmaking and other AI features run on models hosted in your organization's region. Where no model is hosted there yet, that feature is turned off for your organization instead of being processed elsewhere.
Canada and the EU (Frankfurt, Germany) are the two regions available by default. A client that needs the US, China or another AWS region can have one provisioned as part of onboarding, arranged with sales before your organization is created rather than a setting you change later.
Canada is hosted in Montréal; the EU region is hosted in Frankfurt, Germany. Both run on Amazon Web Services infrastructure.
No. The admin app, attendee app and event website look and work the same in either region. The only visible difference is on screens that pull events from multiple organizations at once, which query each region separately.
All of them. Moostoo Tickets, Event App, Corporate and Association & Portfolio all give every organization the same one-time choice of Canada or the EU, with no residency features held back for a higher tier.
Last updated October 2026. Product details are taken from the Moostoo Admin Guide.