# Event Platform for Agencies: Separate Client Data

> Run events for several clients on one platform: separate data per event, client admins scoped to one event, own domains and a GDPR chain that holds.

- Canonical: https://www.amphi.cc/en/blog/event-platform-for-agencies
- Language: en
- All pages: https://www.amphi.cc/llms.txt

---

# Event Platform for Agencies: How to Keep Every Client Separate

An event agency can run several clients on one platform when four things are in place: data separated per client or per event, client administrators limited to their own event, a custom domain per client, and a GDPR contract chain covering client, agency and platform. If the platform cannot separate data and access, use one account per client.

Jakub Miřejovský, Founder of Amphi · Published 18 July 2026 · Updated 21 October 2026 · 10 min read

## Key points

- EventMobi recommends a separate organisation for each customer; InEvent and Swapcard can limit administrators to specific events inside one account.
- Under GDPR, every controller-processor link needs a written contract under Article 28, and a processor needs the controller's prior written authorisation before engaging a sub-processor.
- A custom domain is a DNS change made by the client's IT team; Eventee says it can take up to 72 hours to take effect.
- With Amphi, the annual Premium Conference plan costs EUR 4,150 excl. VAT for up to 50 conferences, cheaper than EUR 1,050 single licences from the 4th conference (calculated).
- On Amphi, a custom-built public site is Enterprise custom development; Free and Premium plans use predefined layouts.

## What does an agency need from a platform to run several clients at once?

An agency running events for several clients needs six things from one platform: separated data, scoped client access, per-client branding, per-client domains, a data processing contract that covers its own role, and a billing model that works across many events.

| Requirement | Question for the vendor |
| --- | --- |
| Data separation | Is data separated per client account, per event, or both? |
| Scoped client access | Can an administrator be limited to one event? |
| Per-client branding | Are logo and colours set per event or per account? |
| Per-client domain | Which DNS record, who issues the TLS certificate, how long does it take? |
| Contract chain | Does the DPA cover an agency acting as processor for its client? |
| Billing model | Is there an annual plan, and what are its limits? |

Ask these questions in writing and keep the answers with the client contract. For general selection criteria, see [How to Choose a Conference Platform](https://www.amphi.cc/en/blog/how-to-choose-conference-platform).

## How do event platforms keep client data separate?

Event platforms usually separate client data in one of two ways: a separate top-level account for each client, or one agency account where every event is a separate container and administrators are scoped to individual events. The first gives harder walls; the second is easier to manage when you run many events.

| Platform | Separation model | Client administrator scope | Source |
| --- | --- | --- | --- |
| EventMobi | Separate organisation per customer, recommended to prevent accidental transfer of sensitive information between events | Users get access only to the organisations relevant to their role | [10] |
| InEvent | Events are created at company level; company tools affect all events. Tier I partners can create a new company per client, starting as a 7-day free trial | Event admins have event-specific access | [12] , [13] , [14] |
| Swapcard | Events sit inside an organisation in Swapcard Studio; the Owner has full control over all events and settings | Event Manager can be limited to chosen events; default is all events | [16] , [17] |
| Amphi | Each event's data is kept separate; a licence always belongs to one specific event | See the next section | [1] , [3] |

Defaults matter: on Swapcard, a new Event Manager gets rights to all the organisation's events unless restricted [\[16\]](#source-16). In the one-account model, also check whether exports and integrations are set per event or account-wide, because account-wide settings are where clients mix.

## How do you give client staff access without exposing other clients?

Give each client's staff an administrator role scoped to their own event, and keep account-wide roles for agency staff only. Then test it: log in as the client administrator and confirm that no other client's event, attendee list or invoice is visible.

Agency lead

**Needs access to**
All client events, billing, account settings

**Must not see**
n/a

**InEvent role**
Company admin with full admin access [\[12\]](#source-12)

**Swapcard role**
Owner or Admin [\[17\]](#source-17)

Agency event manager

**Needs access to**
The events they deliver

**Must not see**
Events of clients they do not work on

**InEvent role**
Event admin [\[12\]](#source-12)

**Swapcard role**
Event Manager scoped to chosen events [\[16\]](#source-16)

Client administrator

**Needs access to**
Their own event, its agenda, speakers and attendees

**Must not see**
Other clients' events and attendees, agency billing

**InEvent role**
Event admin [\[12\]](#source-12)

**Swapcard role**
Event Manager scoped to chosen events [\[16\]](#source-16)

Amphi has four built-in roles: attendee, speaker, organiser and admin [\[1\]](#source-1), [\[5\]](#source-5). Amphi's FAQ states that an agency can invite its clients' own administrators and give them rights to their own event only [\[1\]](#source-1).

## Who is responsible for attendee data under GDPR?

In the usual agency setup, the client is the data controller, the agency is a processor acting on the client's instructions, and the event platform is a sub-processor. The roles follow what each party actually does, not what the contract calls it [\[8\]](#source-8).

A data controller is the body that, alone or jointly with others, determines the purposes and means of processing personal data; a processor is a separate entity that processes it on the controller's behalf [\[8\]](#source-8).

| Party | Usual GDPR role | Main obligations |
| --- | --- | --- |
| Client | Controller | Decides why data is collected; signs a written processing contract with the agency; chooses return or deletion at the end [8] , [9] |
| Agency | Processor | Follows the client's instructions; needs the client's prior written authorisation to engage the platform; stays liable to the client for the platform's compliance [8] |
| Event platform | Sub-processor | Bound by contract to the same data protection obligations as the agency [8] |

Two exceptions: an agency that uses attendee data for its own purposes becomes a controller for that processing, and companies that co-organise a co-branded event can be joint controllers [\[8\]](#source-8).

Amphi's documentation treats the organiser as controller and Amphi as processor, with the DPA as an integral annex to the contract formed when an event is created [\[3\]](#source-3), [\[6\]](#source-6). Data is physically stored in data centres within the European Union [\[7\]](#source-7). Under the general sub-processor authorisation, you have 15 days to object to a new sub-processor [\[6\]](#source-6), so build that window into the notice period you agree with your client. Amphi's DPA also covers an agency acting as processor for its own client, with Amphi as sub-processor, so the contract chain above works without a separate agreement. The full split of duties is in the [GDPR section of the Amphi guides](https://www.amphi.cc/en/features/guides#gdpr).

## How do you set up a new client event, step by step?

Set up each client event in the same order: contract, event, branding, domain, access, attendee limits, offboarding. Amphi specifics are noted where Amphi has published them.

1. **Sign the contract chain.** Client to agency, agency to platform; name the platform as a sub-processor.
2. **Create one event per client project.** On Amphi, a licence always belongs to one specific event [\[3\]](#source-3).
3. **Apply the client's branding.** Upload the logo and set the colours before you invite anyone.
4. **Request the custom domain from the client's IT team.** A CNAME record is a DNS entry that points one domain name to another. InEvent recommends a CNAME and generates the SSL certificate automatically [\[15\]](#source-15); Eventee says changes can take up to 72 hours [\[18\]](#source-18); Canapii requires domain validation before it generates the certificate [\[19\]](#source-19). On Amphi's paid plans, the client's IT team points a subdomain such as events.your-org.com at Amphi; Free uses an address like your-event.amphi.cc [\[1\]](#source-1). Amphi issues the TLS certificate, and its guides say the setup is simple and that Amphi helps with it [\[3\]](#source-3).
5. **Invite client administrators with event-only access and test it with their login.**
6. **Watch the attendee count.** On Amphi, every registered user who is not blocked counts toward the limit, whether or not they attend a talk; admins and speakers do not count [\[3\]](#source-3).
7. **Offboard.** Export what the client needs, then archive or delete. On Amphi, archive is irreversible; on Premium plans the event space is kept for 2 years from the start of archive and then physically deleted [\[3\]](#source-3), and the client can instruct earlier deletion [\[6\]](#source-6).

## How much branding can each client get without custom development?

Without custom development, per-client branding usually means a logo, colours and a custom domain on top of the vendor's page layouts. A white-label platform is one where the vendor's brand is removed so attendees see only the client's name, logo and domain. Check where each setting lives: InEvent lists branding at company level and sets the custom domain per event [\[13\]](#source-13), [\[15\]](#source-15).

On Amphi, branding covers the logo (on the event's public site and available in email templates), primary and secondary colours, and a custom domain on paid plans [\[3\]](#source-3). On the annual Premium Conference plan, every conference has its own branding and domain, so one plan can carry several clients side by side. The pricing table lists predefined layouts for Free, Premium Webinar and Premium Conference, and custom development only on Enterprise [\[2\]](#source-2). More detail is in the [branding section of the Amphi guides](https://www.amphi.cc/en/features/guides#branding).

What Premium does not include, according to the published plans [\[2\]](#source-2):

- a custom-built public site (Enterprise)
- API and custom integrations (Enterprise); the MCP connector for AI event setup is on every plan, including Free
- individually agreed data retention (Enterprise)

## What does a multi-client setup cost per event?

With Amphi, the annual Premium Conference plan costs EUR 4,150 excl. VAT for up to 50 conferences, against EUR 1,050 for a single conference licence [\[2\]](#source-2). The annual plan is cheaper from the 4th conference in a licence year: four single licences cost EUR 4,200 (calculated).

| Conferences per licence year | Annual plan total (EUR) | Annual plan per conference (EUR, calculated) | Single licences total (EUR, calculated) |
| --- | --- | --- | --- |
| 3 | 4,150 | 1,383 | 3,150 |
| 4 | 4,150 | 1,038 | 4,200 |
| 10 | 4,150 | 415 | 10,500 |
| 25 | 4,150 | 166 | 26,250 |
| 50 | 4,150 | 83 | 52,500 |

Prices excl. VAT and extra attendees, from the Amphi pricing page, checked 13 October 2026. Per-conference values rounded to whole euros.

Conditions: one payment covers a 365-day licence year; at most 30 calendar days may pass between a conference's first and last talk day, and a talk outside that window is another conference; the annual plan cannot be bought as a top-up to an existing single-conference licence [\[4\]](#source-4). Each conference in the annual plan has the same limits as a standalone conference: 1,000 attendees included, extra attendees EUR 0.10 each, billed in arrears for the previous calendar month on a separate invoice [\[2\]](#source-2), [\[3\]](#source-3), [\[4\]](#source-4). Billing rules are in the [billing section of the Amphi guides](https://www.amphi.cc/en/features/guides#billing) and current prices on [Amphi pricing](https://www.amphi.cc/en/pricing).

EventMobi publishes starting prices of $3,000 per event and $8,900 per year with unlimited events [\[11\]](#source-11) (checked 13 October 2026). Limits and features differ, so compare totals for your own event count.

## Frequently asked questions

### Can an event agency use one platform for several clients?

Yes, if the platform separates data per client or per event and can limit client administrators to their own event. EventMobi recommends a separate organisation per customer; InEvent and Swapcard can limit administrators to specific events inside one account.

### How do I keep client data separate on an event platform?

Use a separate account per client, or one account where each event is a separate container. Give client staff event-scoped roles only, check that exports and integrations are per event, and test access with a client administrator's login.

### Can each client's event have its own domain?

Often yes. The client's IT team adds a DNS record, typically a CNAME, pointing a subdomain such as events.client.com at the platform. Eventee says changes can take up to 72 hours. On Amphi, a custom domain needs a paid plan.

### Is an event agency a data controller or a processor?

Usually a processor: the client decides why attendee data is collected, and the agency acts on its instructions. If the agency uses the data for its own purposes, it becomes a controller for that processing.

### How much does an event platform for agencies cost?

Published prices vary. Amphi's annual Premium Conference plan costs EUR 4,150 excl. VAT for up to 50 conferences; EventMobi starts at $8,900 per year. Checked 13 October 2026.

## Your next event can run on Amphi.

One place for the whole event.

Build the programme, manage speakers and attendees, communicate with participants, and keep live content and recordings together, before, during and after the event.

- Event agencies running four or more client conferences a year

    Try the setup on a Free event first, then ask us how the annual Premium Conference plan fits your client list.

    [Start for free](https://www.amphi.cc/en/begin)

## Sources

1. Amphi, llms.txt (FAQ "Can I run events for several different clients in Amphi?", "Can my event live on my own domain?", Access and roles module): [amphi.cc/llms.txt](https://www.amphi.cc/llms.txt)
2. Amphi, Pricing: [amphi.cc/en/pricing](https://www.amphi.cc/en/pricing)
3. Amphi, Guides (Licensing model, Branding, Billing, Recurring billing, GDPR, Archive mode): [amphi.cc/en/features/guides](https://www.amphi.cc/en/features/guides)
4. Amphi, Guides full text (Billing scheme, Premium Conference up to 50 conferences): [amphi.cc/llms-full.txt](https://www.amphi.cc/llms-full.txt)
5. Amphi, Context (Access and roles): [amphi.cc/context](https://www.amphi.cc/context)
6. Amphi, Terms of Service incl. Data Processing Agreement (Art. 1.3, DPA 2/12, 2/13, 2/14), effective from 24 September 2026: [amphi.cc/en/tos](https://www.amphi.cc/en/tos)
7. Amphi, Privacy Policy, Section 1.2, effective from 30 September 2026: [amphi.cc/en/privacy](https://www.amphi.cc/en/privacy)
8. European Data Protection Board, Guidelines 07/2020 on the concepts of controller and processor in the GDPR, Version 2.1 (paras 12, 15, 40, 76, 81, 128, 129 and example "Marketing operation"): [edpb.europa.eu/system/files/documents/2023-10/EDPB\_guidelines\_202007\_controllerprocessor\_final\_en.pdf](https://www.edpb.europa.eu/system/files/documents/2023-10/EDPB_guidelines_202007_controllerprocessor_final_en.pdf)
9. EUR-Lex, Regulation (EU) 2016/679 (GDPR), Recital 81: [eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679)
10. EventMobi Help, How do I organize multiple events for various customers?: [help.eventmobi.com/en/knowledge/how-do-i-organize-multiple-events-for-various-customers](https://help.eventmobi.com/en/knowledge/how-do-i-organize-multiple-events-for-various-customers)
11. EventMobi, Pricing: [eventmobi.com/pricing](https://www.eventmobi.com/pricing/)
12. InEvent FAQ, Users: Global admins and customized access admins: [faq.inevent.com/l/en/in-event-start/admin-global](https://faq.inevent.com/l/en/in-event-start/admin-global)
13. InEvent FAQ, Company and event levels: [faq.inevent.com/l/en/article/tnbqhfyw7y](https://faq.inevent.com/l/en/article/tnbqhfyw7y)
14. InEvent FAQ, Partner: How to create a new company?: [faq.inevent.com/l/en/partners/partner-how-to-create-a-new-company](https://faq.inevent.com/l/en/partners/partner-how-to-create-a-new-company)
15. InEvent Developers, Custom domain: [developers.inevent.com/event-api/custom-domain](https://developers.inevent.com/event-api/custom-domain)
16. Swapcard Product Updates, New roles in the administration team: [release.swapcard.com/new-roles-in-the-administration-team-Wy2L6](https://release.swapcard.com/new-roles-in-the-administration-team-Wy2L6)
17. Swapcard Help, Managing members and ownership in your organization: [help.swapcard.com/en/articles/8158917-managing-members-and-ownership-in-your-organization](https://help.swapcard.com/en/articles/8158917-managing-members-and-ownership-in-your-organization)
18. Eventee Help, Customize the event website domain: [help.eventee.com/en/articles/143-customize-the-event-website-domain](https://help.eventee.com/en/articles/143-customize-the-event-website-domain)
19. Canapii Knowledge Base, How to get a custom web domain for an event: [knowledge-base.canapii.com/how-to-get-a-custom-web-domain-for-an-event](https://knowledge-base.canapii.com/how-to-get-a-custom-web-domain-for-an-event)