Picture someone on a destination marketing organization's partnerships team, three vendors into a shortlist review for a new training program. They pause on one line and ask a question that used to feel like a formality: "Where is this actually built? Who's on the team? What happens to our data once we sign?"

That's not an unusual question anymore. It's just good due diligence — and destination organizations of every kind, from a provincial tourism board to a regional chamber to a big-city CVB, are asking it more carefully than they used to, especially when a vendor sits across a border.

Fair enough. It's a good question. It's just usually the wrong question to answer with a slogan.

"Global" should be a checklist, not a claim

Plenty of vendors will tell you they're a "global partner" the same way they'll tell you their platform is "innovative" — as a marketing word, not a fact you could verify. But global-readiness is actually checkable. It comes down to a handful of concrete things:

Where does the engineering and technology development actually happen? Who is genuinely on the team, and where do they work from? What formal commitments exist around data — not a line in a privacy policy nobody reads, but an actual agreement? And when a partner says they support multiple languages, is that real, human-built localization, or a browser plugin doing its best?

We'd rather show you how we answer those questions than just assert that we do.

How this shows up inside Learn Tourism

The engineering and technology development behind our learning platform is based in Vancouver, British Columbia. That's not a footnote — it's who actually builds and maintains the system your learners use every day.

Our team itself isn't headquartered in one place either. Our Operations Manager works from East Africa, handling much of the day-to-day support our partners rely on. Specialized technology development and data work run through contractor teams based in Pakistan and Nepal. Between our Florida home base, our engineering partners in Canada, and teammates and contractors across East Africa and South Asia, "our team" genuinely spans multiple countries and three continents — not because it looks good on a slide, but because that's where the right people happened to be.

On data: we sign data processing agreements (DPAs) directly with our partners, and we align our practices with GDPR requirements. That's true whether a partner is based in Boise or Brussels. Good data hygiene shouldn't depend on which side of a border a client sits on.

And on language: as of July 2026, our courses can be delivered in 45 languages —

Afrikaans, Armenian, Azerbaijani, Bulgarian, Catalan, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, Georgian, German, Greek, Hindi, Hungarian, Icelandic, Indonesian, Italian, Japanese, Korean, Lao, Latvian, Lithuanian, Mandarin (Simplified), Mandarin (Traditional), Norwegian, Polish, Portuguese (Brazil), Portuguese (Portugal), Romanian, Russian, Serbian (Cyrillic), Serbian (Latin), Slovak, Slovenian, Spanish (Mexico), Spanish (Spain), Swedish, Thai, Turkish, Ukrainian, and Vietnamese.

That's a genuinely useful thing to know if you're building a frontline training program for a multilingual destination workforce, a resident engagement campaign in a border region, or an ambassador program that needs to reach visitors and staff in more than one language.

Four questions worth asking any training partner

None of this is really about us. It's a reasonable standard for evaluating any education or technology partner, domestic or international. Before you sign with anyone:

Where is the engineering actually built and maintained? A vendor should be able to answer this in one sentence, not a paragraph of deflection.

Who's on the team, and where do they work from? "Global" should mean actual people in actual places, not a mailing address.

What data agreements do they sign, and do their practices reflect recognized privacy standards? Ask for the DPA. If they don't have one ready, that tells you something.

What languages can they genuinely deliver in — and is it real localization or a translation plugin? There's a real difference between a course built in French and a course run through an auto-translate widget.

Before your next vendor conversation

Take whichever partner you're currently evaluating — for training, for technology, for anything — and run them through those four questions this week. You might be surprised how many can't answer all four cleanly. We can, and we're glad to walk through the specifics for your program if it's useful.

If you'd like to see how this looks for your organization specifically — which languages matter for your workforce, what a DPA with us actually says, or how our team would support your program day-to-day — reach out and let's talk about what that could look like for your destination.