What is data residency?

Data residency asks where your attendee data physically sits. For many organizations it is a binding requirement rather than a preference, driven by regulation, by an internal policy, or by a customer’s contract.

In practice at an event

An attendee list is personal data: names and email addresses tied to identified people, plus whatever behaviour the app records. That is true whether or not your industry thinks of a conference as a data-processing activity.

The question to ask a vendor is short: name the country or region where attendee data is stored, and where backups are stored. “The cloud” and “securely” are not answers. A vendor that cannot name it cannot help you pass a review.

Backups are the part people forget. Data stored in one region and backed up to another has not met a residency requirement.

What to look for

Ask in the written round, not in the demo. Residency is a filter, and applying it early saves weeks.

Ask about sub-processors too, since a vendor’s own region tells you nothing about where their email provider or analytics provider sits.

Where event67 stands

event67 does not publish a data residency guarantee or a region-selection option on this site, and we will not imply one. If residency is a requirement for your review, ask us directly and you will get a specific answer about where data is held rather than a general reassurance.

That is deliberately a pointer to a conversation rather than a claim. A residency commitment is a contractual matter and it should be in your contract, not inferred from a marketing page.