Dance Events
Version: 1 November 2026 (revision 4)
View current agreementThis is a historical version, shown for reference only.
In short: for attendee data of your events, you are the controller and DanceMeetup processes the data on your behalf. Organizers accept this agreement separately when creating an organizer account.
This Data Processing Agreement ("DPA") is concluded between:
The person accepting this DPA confirms that they are authorised to bind the Organizer. The Organizer accepts this DPA through the designated acceptance action in the Platform. The acceptance record identifies the accepting account, the DPA version and the time of acceptance and is associated with the Organizer's organization profile.
The DPA supplements the Terms & Conditions for Organizers ("Terms") and any license or service order. It applies whenever DanceMeetup processes personal data on the Organizer's behalf in providing an agreed Platform service, whether paid or free. Annex A describes that processing; a separate paid service order is not required for this DPA to apply.
DanceMeetup also processes personal data as an independent controller for separately identified purposes, including Platform accounts, authentication, security, its own communications and the attendee archive described in its Privacy Policy. That processing is not covered by this DPA. A provider's role, including payment providers, depends on the specific service, contract, account holder and purpose.
DanceMeetup processes the personal data only on the Organizer's documented instructions, including with regard to transfers outside the EEA, unless EU or Member State law requires otherwise. In that case DanceMeetup informs the Organizer before processing, unless that law prohibits it on important grounds of public interest.
The Terms, any applicable service order, this DPA and the settings the Organizer's authorised users make on the Platform are the Organizer's documented instructions. Other instructions must be sent to info@dancemeetup.com; instructions outside the agreed services may require a separate agreement. If DanceMeetup reasonably considers an instruction unlawful, it promptly informs the Organizer and seeks clarification. DanceMeetup may suspend the affected instruction while the issue is resolved and will not carry out processing it knows would breach applicable law. Any suspension is limited to what is reasonably necessary, and the parties will cooperate to identify a lawful alternative. This does not make assistance required by data protection law conditional on buying an additional service.
The Organizer determines the purposes of its processing, ensures a lawful basis, informs data subjects and is responsible for the lawfulness of its instructions and of the data it collects. The Organizer must not collect data it does not need, must not collect special-category data without an applicable condition under Article 9 GDPR, and must not collect copies of identity documents through the Platform.
DanceMeetup ensures that persons authorised to process the personal data are bound by confidentiality and have access only to the extent their role requires. DanceMeetup implements the technical and organisational measures described in Annex B, taking into account the nature, scope, context, purposes and risks of the processing. Measures may change over time, provided the level of protection is not reduced.
The Organizer gives DanceMeetup general written authorisation to engage the sub-processors listed in Annex C.
DanceMeetup gives the Organizer at least 30 calendar days' advance notice by email to the administrator contact address registered for the Organizer, and updates Annex C, before an intended addition or replacement starts processing the Organizer's personal data. The notice identifies the provider, the service and data involved, and any known processing location or transfer information. The Organizer may object on reasonable data protection grounds by writing to info@dancemeetup.com before the proposed start date. DanceMeetup will not start the new processing for that Organizer while a timely objection remains unresolved. The parties will seek a reasonable solution; if none is found, the Organizer may stop using the affected feature or terminate the affected services.
DanceMeetup imposes on each sub-processor data protection obligations equivalent in substance to those in this DPA and remains liable to the Organizer for the sub-processor's performance of those obligations.
Taking into account the nature of the processing, DanceMeetup assists the Organizer with appropriate technical and organisational measures, insofar as possible, in responding to requests from data subjects exercising their rights. DanceMeetup forwards to the Organizer without undue delay any such request it receives that concerns processing on the Organizer's behalf, unless prohibited by law.
DanceMeetup assists the Organizer, taking into account the information available to it, in meeting its obligations under Articles 32 to 36 GDPR, including security, breach notification, data protection impact assessments and prior consultation.
DanceMeetup notifies the Organizer of a personal data breach affecting the Organizer's data without undue delay after becoming aware of it. The initial notification describes, to the extent then available, the nature of the breach, affected data and data-subject categories, approximate numbers of affected individuals and records, likely consequences, measures taken or proposed, and a contact for follow-up. Incomplete information does not delay the initial notification; further information is provided without undue delay as it becomes available. DanceMeetup takes reasonable steps to contain and mitigate the breach and preserve relevant evidence.
DanceMeetup transfers personal data outside the EEA only on the Organizer's documented instructions, including this DPA and Annex C, or where required by law, and only where Chapter V GDPR is complied with.
DanceMeetup makes available to the Organizer the information necessary to demonstrate compliance with Article 28 GDPR and allows for and contributes to audits, including inspections, conducted by the Organizer or an auditor it mandates. The parties agree reasonable notice, scope, confidentiality and security arrangements in advance.
During the term of the Organizer's account, Organizer-controlled event data may remain stored after an event ends so that the Organizer can administer past events, its CRM records and related claims. The Organizer determines the purpose and appropriate retention period for its CRM data and must not retain data it no longer needs. Sensitive or optional fields are not retained merely because other event-history records remain available. The Organizer may delete data it no longer needs using the Platform or by request.
When the Organizer's account or the relevant services end, DanceMeetup, at the Organizer's choice, returns the Organizer-controlled personal data in a commonly used electronic format available on the Platform or agreed between the parties, or deletes it, and deletes existing copies without undue delay, unless EU or Member State law requires storage. Backups are handled as described in Annex D.
The attendee's separate DanceMeetup archive (including event history, old pass records and links to memories where available) is a distinct Platform purpose described in the Privacy Policy. It is not retained as Organizer CRM data under this DPA. An Organizer's deletion instructions do not delete data held by another Organizer or data DanceMeetup processes as an independent controller. An attendee may request erasure of their Platform archive; records retained under a separate legal obligation are handled separately.
This DPA applies for as long as DanceMeetup processes personal data on the Organizer's behalf. For the processing it covers, the DPA prevails over the Terms and any license or order. Liability between the parties is governed by the Terms, subject to mandatory law. Nothing in this DPA limits data subjects' rights or the powers of supervisory authorities under applicable data protection law. DanceMeetup may update this DPA; material changes are notified in the same way as changes to the Terms.
| Item | Description |
|---|---|
| Subject matter | Event registrations, bookings, passes, payment status, check-in, attendee communication and related event services provided to the Organizer through the Platform. |
| Duration | For the term of the Organizer's account and services, followed by return or deletion under section 7. |
| Nature | Collection, recording, organisation, storage, consultation, use, disclosure to the Organizer's authorised users and to recipients chosen by the Organizer, return and deletion. |
| Purposes | Administration of the Organizer's events and of the services and communications the Organizer requests. |
| Data subjects | Applicants, attendees, waiting-list members, performers and other persons whose data the Organizer handles for its events. |
| Data categories | Names and contact details; account and registration identifiers; applications, waiting lists, bookings, passes, payment status and attendance/check-in data; transaction and payment references (not full payment-card details); responses to Organizer-enabled forms, including dietary, travel or accommodation information; Organizer-entered notes; and communication content and delivery metadata, including email, WhatsApp or push data where the relevant service is enabled. Copies of identity documents are not collected. |
| Special categories | Health or other special-category information only where an attendee provides it in an Organizer-enabled field, such as allergy information. The Organizer is responsible for identifying and documenting an applicable Article 9 condition and limiting access and retention. Optional entry alone does not establish that condition. |
| Event profile photo (optional) | Where enabled: the photo selected by the attendee, event artwork and image-creation instructions, which may include the attendee's first name and/or chosen nickname, event date, style and other event details, and the generated images. Automatic attendee fields available to the template are limited to the first name and any chosen nickname; the Organizer must not include unnecessary personal data in free-text instructions or artwork. The selected photo is sent to the AI image-processing sub-processor in Annex C only after recorded consent for each generation. Event-specific source uploads and generated files are deleted from active event storage automatically one year after the event ends. This deletion does not delete a separate account profile photo reused as the input; that photo is governed by the attendee-account retention rules in the Privacy Policy. Any copies in separate file backups, if applicable, follow the relevant backup lifecycle. |
| Flight information (optional) | Flight number and date entered by the attendee. Only the flight number and date are sent to an external flight-data provider; no attendee identifier is sent, and the link between a flight and an attendee stays on the Platform. |
This Annex identifies the service providers used in delivering the Platform, the services they provide and the categories of personal data involved.
DanceMeetup shall ensure that providers acting as sub-processors are bound by the data protection obligations required under Article 28 GDPR. Any transfers of personal data outside the EEA shall comply with section 5 of this DPA.
Information necessary to demonstrate compliance, including applicable provider roles, contracting entities, processing locations, retention arrangements and transfer safeguards, shall be made available to the Organizer under section 6, subject to appropriate confidentiality safeguards.
| Provider | Service | Personal data and other information |
|---|---|---|
| OpenAI API (OpenAI Ireland Ltd. under the published EEA/Swiss DPA) | Editing event profile photos where enabled by the Organizer | The selected attendee photo, event artwork and optional logo, and the prompt and instructions, which may include the attendee's first name and/or nickname and event details. The generated image is returned to the Platform. |
| Web4U s.r.o. | Delivery of Organizer-requested emails to attendees | Recipient email addresses, message content and delivery metadata. |
| WhatsApp Business Platform / Cloud API (WhatsApp Ireland Limited in the published EEA terms) | Organizer-requested WhatsApp messages | Recipient phone numbers, message or template content and parameters, and delivery metadata. |
| Apple Push Notification service (APNs) (Apple Inc. in the published developer program agreement) | Delivery of Organizer-requested push notifications to Apple devices | Device push tokens, notification content and associated payload. |
| Google Firebase Cloud Messaging (FCM) (contracting entity depends on the applicable terms) | Delivery of Organizer-requested push notifications to Android devices | Device push tokens and data payload, including notification content and delivery/tracking information. |
| Item | Detail |
|---|---|
| Backups | Encrypted database backups are stored in the Czech Republic and retained for up to one year. They are used only to restore the Platform and are not used for ordinary processing. Where selective deletion is not technically practicable, affected data remain protected until the backup expires. If a backup is restored, applicable deletion instructions are reapplied before restored data are made available for ordinary processing. |
| Event profile photos | Event-specific source uploads and generated files are deleted from active event storage automatically one year after the event ends. A separate attendee account profile photo reused as an input is not deleted by this event-file purge. Any copies in separate file backups, if applicable, follow the relevant backup lifecycle. |
| Requests, instructions and breach notifications | info@dancemeetup.com |
See also the Terms for Organizers and our Privacy Policy.
info@dancemeetup.com© 2026 Dance Meetup · XWare, s.r.o.