---
title: "GDPR and EU data residency"
description: "What every AgendaForge customer gets under the GDPR (a DPA on request, sub-processors with locations, subject requests within a month, breach notice within 72 hours), where data is stored by default, and the paid EU data residency option."
canonical: "https://agendaforge.app/gdpr"
last-updated: 2026-09-20
---
# GDPR and EU data residency
> What every AgendaForge customer gets under the GDPR (a DPA on request, sub-processors with locations, subject requests within a month, breach notice within 72 hours), where data is stored by default, and the paid EU data residency option.
Canonical page: https://agendaforge.app/gdpr
Last reviewed or updated: 2026-09-20
Content type: page

Title: Is AgendaForge GDPR Compliant? DPA, Sub-processors, EU Hosting
Breadcrumb: Home > GDPR
Last reviewed: September 20, 2026. Locations checked 2026-09-20.

## Is AgendaForge GDPR compliant?

Yes. GDPR compliance is a set of obligations, and AgendaForge meets them for every customer on every plan: a data processing agreement on request, a published sub-processor list with locations, data subject requests answered within one month, breach notice to the customer within 72 hours, and transfers that rest on standard contractual clauses. By default data is stored in the United States. Organizations that need it kept in the EU can buy EU data residency.

## What AgendaForge does for every customer under the GDPR

- A data processing agreement, on request: email hello@agendaforge.app with "GDPR" in the subject and receive the DPA with the standard contractual clauses attached. It names every sub-processor below. A customer's own DPA is reviewed on request.
- Sub-processors listed, with locations: the table below says which provider holds which data and in which country. If a provider or a location changes, the table changes first and DPA customers are told before it does.
- Data subject requests within one month: access, correction, export, and deletion. When an event organizer is the controller of a speaker's or attendee's data, AgendaForge forwards the request to the organizer and helps them answer it.
- Breach notice within 72 hours of AgendaForge becoming aware of a personal data breach affecting the organization's data.
- Transfers out of the EU, the UK, or Switzerland rest on standard contractual clauses or, where the provider holds it, the EU-US Data Privacy Framework certification.
- No training on customer data and no selling it: the AI provider does not use API inputs to train its models, a person approves what the AI produces, and the marketing site runs no advertising trackers.

## Sub-processors: standard location, and location with EU data residency

| Data | Provider | Standard location | With EU data residency |
|---|---|---|---|
| Event records (speakers, contacts, submissions, sessions, the agenda) | Convex | United States | EU West (Ireland) |
| Uploaded files (headshots, logos, sponsor assets, portal uploads) | Cloudflare R2 | Cloudflare data centres, location chosen by Cloudflare | EU jurisdiction storage, pinned to EU data centres |
| Sign-in, sessions and single sign-on | WorkOS | United States | United States (team sign-in only; EU option on request) |
| The app and website pages (no event data stored) | Vercel | Global edge network | Unchanged (holds no event data) |
| Email to speakers, reviewers and attendees | Amazon Web Services (SES) | Singapore | An EU region |
| Payments (card numbers never reach AgendaForge) | Stripe | Global; Stripe is its own controller | Unchanged |
| AI features (drafting, pipeline analysis, search, Event Coordinator) | OpenAI API | United States | EU data residency project, processed and stored in Europe |
| Speaker research (name, company, job title, location and LinkedIn link, as web searches) | Exa | United States | United States (no EU option) |
| Visits to the marketing website (analytics) | PostHog | European Union | Unchanged |
| Visits from our ads, and signups from them as a hashed email (advertising measurement) | OpenAI | United States | Unchanged |

Each provider's own security statement is linked at https://agendaforge.app/security.

## EU data residency

For organizations whose rules say personal data stays inside the EU, AgendaForge runs a second, separate stack: the database in Ireland, uploaded files in storage pinned to EU data centres, email sent from an EU region, and AI requests processed and stored in Europe through the AI provider's EU residency programme.

- Provisioned per organization, not per event, because contacts, the team and speaker portals are shared across every event an organization runs. Set up by AgendaForge within a week of agreement, usually in three to four days, before the first event; it stays in place for every event after.
- Two things stay where they are: the organizing team signs in through the identity provider in the United States under standard contractual clauses (speakers and attendees never create an identity there; an EU alternative for team sign-in is scoped on request before provisioning), and payments stay with Stripe.
- An organization is either on the standard stack or the EU stack, never half on each. It is not a switch in the product.
- Pricing: $1,000 per event, or $3,000 per organization per year for unlimited events. Moving an existing organization from the standard stack to the EU stack is a one-off $500 (a scheduled export and import with a short freeze). Available on Pro. Ask at signup or email hello@agendaforge.app with "EU data residency" in the subject.

## Good to know

- The organizing team signs in through the identity provider in the United States on every stack today; an EU alternative is scoped on request, not self-serve.
- EU data residency is provisioned by AgendaForge within a week of agreement; it is not self-serve.
- This page is a plain description of what AgendaForge does, not legal advice.

## FAQ

### Will AgendaForge sign a data processing agreement?

Yes. Email hello@agendaforge.app with "GDPR" in the subject for the DPA with the standard contractual clauses attached. A customer's own DPA is reviewed on request.

### Where is data stored by default?

Event records, sign-in data, and AI processing are in the United States. Uploaded files are in Cloudflare data centres of Cloudflare's choosing. Email is sent through Amazon Web Services in Singapore. Speaker research searches run through Exa in the United States. Website analytics are in the European Union.

### Can event data stay in the EU?

Yes, as a paid option on Pro ($1,000 per event or $3,000 per organization per year): database in Ireland, EU-pinned file storage, email from an EU region, AI processed in Europe. The organizing team signs in through the identity provider in the United States (an EU alternative is scoped on request); payments stay with Stripe. Once agreed, provisioning takes three to four days, a week at most, and it has to be in place before the first event.

### How does a speaker or attendee exercise their rights?

The event organizer is the controller of speaker and attendee data, so the request goes to them; most of it can be answered inside the product (profile edits, exports, deletion). A request that reaches AgendaForge directly is forwarded to the organizer with help to answer within one month. Organizers exercise their own rights by emailing hello@agendaforge.app.

### Does the AI learn from event data?

No. AI features send only the text the feature needs to the AI provider through its API, which does not use API inputs to train models. On the EU stack the request is processed and stored in Europe. A person accepts every draft before it becomes event content.

Contact for DPA, sub-processor notices, and data subject requests: hello@agendaforge.app with "GDPR" in the subject. Related: https://agendaforge.app/privacy-policy and https://agendaforge.app/security.

---

AgendaForge is an AI-native event-management platform. Public machine-readable index: https://agendaforge.app/api/ai
