The answers before you ask

Data stays in India on infrastructure we control, purpose is limited to the event, and retention is set in the contract rather than left open. We sign a data processing agreement, list sub-processors on /security, and purge event-scoped data on schedule.

You do. We are the processor, not the controller. You get a full export in a documented format, and our copy is purged on the agreed retention date.

Six to eight weeks is comfortable for a conference under 3,000 delegates. Badge stock and hardware have real lead times, and the venue network survey has to happen before we can commit to sizing. We have delivered on three weeks; it costs more and removes options.

We run events across Indian cities as standard. Outside India we work as the technology partner alongside a local operations vendor, because show-day operations need people who know the venue and the local suppliers.

Because the honest answer varies by more than an order of magnitude. A 300-delegate single-hall event and a 6,000-delegate four-hall congress share almost nothing. We quote an indicative range within three working days of getting the date, city and headcount.

In order: delegate count, number of halls needing access control, show days, and whether we supply hardware or use yours. Language count is the main driver on translation work.

Common, and planned for. We bring our own segmented network for registration and access control, and treat the venue link as an uplink rather than as infrastructure. Everything delegate-critical is designed to survive losing it.

Usually. We have imported from most of the common platforms and can work from a CSV where there is no API. Tell us what you have and we will say plainly whether it is a clean integration or a nightly sync.