Privacy policy

1. Controller

The controller for the CrowdFlow Live website, user accounts and plans, and our own administrative functions is:

2. Responsibility at events

The event organiser is responsible for the event’s song requests, guest messages and feedback. They determine why the information is collected, how it is moderated and where it is displayed. CrowdFlow Live processes this information on the organiser’s behalf.

The name shown on the guest page identifies who receives the request or message. The organiser must also provide guests with a way to contact them and the privacy information applicable to the event, for example at the venue or in the event documents. For questions about a specific submission, contact the organiser first. Questions about CrowdFlow Live can be sent to info@crowdflow.live.

3. Availability and security

When you visit the website, we process necessary access data such as your IP address, time, requested page, browser and device information, and request status. We need this information to provide CrowdFlow Live, detect errors and prevent misuse.

Website access and error logs remain available for up to five weeks. Other operational logs are retained to a limited extent until new entries replace older ones.

For troubleshooting, we also store the error type, time, affected site section, and browser and device group. Errors during logged-in use may be linked to your account. Form contents, card details and access keys are not recorded in this error store. Entries are deleted during regular cleanup after 30 days without recurrence. Short-lived identifiers are used for up to ten minutes to prevent misuse and are then deleted regularly.

For temporary protection measures in guest forms, an identifier that changes daily may be generated from the IP address. The IP address is not stored permanently alongside the song request or message.

The legal basis is Article 6(1)(f) GDPR. Our legitimate interest is secure, uninterrupted operation. The connection to CrowdFlow Live is encrypted.

4. User account, plan and billing details

During registration and account use, we process your username, display name, email address, login credentials, plan status, settings and any contact or billing details you choose to provide. These may include company, first and last name, street, postcode, town, country and billing email. Passwords are not stored in plain text.

We need these details to provide your account and subscribed plans (Article 6(1)(b) GDPR). Security measures also rely on our legitimate interest under Article 6(1)(f) GDPR. We process legally required billing data under Article 6(1)(c) GDPR.

If you change your email address, we may send confirmation and security notices to both the old and new addresses. Temporary confirmation data is deleted after the relevant link expires.

4a. Public profiles

You decide whether to publish your profile. Your name, introduction, profile photo, logo and any contact details you make available are then public and may appear in search engines. We process this information to provide your profile under Article 6(1)(b) GDPR, until you remove it or your account is deleted. Search engines may retain their own copies for longer.

4b. Enquiries through profiles

When you send an enquiry, the provider receives your name, email address or telephone number, event date and location, and any other details you enter. These may include the occasion, number of guests, equipment requirements and answers to the provider’s own questions. This information is used to respond to your enquiry and prepare for a possible booking (Article 6(1)(b) GDPR). The enquiry is not public.

The enquiry remains in the provider’s account until they delete it or their account. Providers should delete completed enquiries once they are no longer needed and no retention obligation applies. To request access or deletion, contact the provider or info@crowdflow.live. This also applies if you provided only a telephone number; in that case, we will use an appropriate method to verify which enquiry is yours.

5. Payments with Stripe and PayPal

You can use Stripe or PayPal for paid plans. Your chosen payment provider processes the account, payment and transaction data needed for payment, security and fraud prevention. Full card details are not stored in CrowdFlow Live.

When an organiser enables requests with an extra contribution, Stripe processes the payment directly to the organiser’s connected merchant account. CrowdFlow Live stores only the transaction and amount data needed for matching, status, refunds and records; it does not receive card or wallet details. A payment does not guarantee that a song will be played and does not add an extra vote.

Tipping is voluntary and does not require a song request. Your payment is charged as soon as you confirm it, without approval from the DJ. The recipient is the provider shown.

Processing serves contract performance and payment handling under Article 6(1)(b) GDPR and legal obligations under Article 6(1)(c) GDPR. Stripe and PayPal act as independent controllers for substantial parts of their payment processing.

• Stripe: Stripe privacy policy
• PayPal: PayPal privacy policy

6. Song requests, voting and events

For a song request, we process the entered name or pseudonym, artist, title, optional comment, time and handling status. The request is assigned to the relevant organiser and, where applicable, an event or archive folder. Music search information may add an album, genre, release year and cover image.

When voting is enabled, a guest can rate a visible song once and finally within an event context, positively or, if the organiser allows it, negatively. CrowdFlow Live processes a pseudonymous guest association, the song reference, vote and time. This ensures one vote per song and a limit of five accepted votes in five minutes and 30 votes per context. Votes cannot be changed or withdrawn; only the combined net score is shown publicly, without guest names.

The information is available to the organiser for preparing and running the event. The organiser determines the applicable legal basis according to their use. Please do not include confidential details or unnecessary information about others in comments.

A shared browser identifier links guest song requests, votes and messages during a session. For standard forms it lasts 16 hours. Separately created song-request events use their own identifier, valid for 90 days. Both periods start when the identifier is issued and are not extended by further use. Event link validity is independent. The organiser may move requests to the live list or archive and retain them there until deletion. Aggregated vote scores may remain saved with an archive; the short-lived guest association is not needed for this.

The DJ can send short messages about a song request. Explicitly public DJ messages appear in the request list; private DJ messages and guest replies are visible only to that guest and authorised account managers. We store the message, time, request reference, visibility and read status. In My song requests, guests can view their requests and messages while their identifier remains valid (16 hours for standard forms, 90 days for separate events), even after archiving. Archived conversations cannot continue. Messages remain linked to the saved request and are deleted with it or the associated account.

6a. Private event briefing

A private briefing link allows customers to submit song requests, songs to avoid, the first dance, items on the schedule and other notes for an event. The account holder and anyone with the link can access it, so share it only with authorised people. The briefing is used for event planning and is stored until the event or account is deleted. The provider concerned is responsible for the purpose and legal basis of this processing.

7. Chatwall, guest photos and public display

For Chatwall, we process the message, time, moderation status, account association and a pseudonymous visitor identifier. This identifier helps prevent duplicate submissions, supports moderation and enables temporary blocks in cases of misuse.

If the organiser enables guest photos, we also process the selected images (up to six per post), one shared optional caption, moderation status and technical file information. CrowdFlow Live initially stores uploads privately, removes embedded metadata and prepares images for display. The organiser chooses whether posts appear automatically after upload or only after manual approval. Photos submitted together are displayed and moderated as one group. The organiser may reject posts or temporarily block the sender. Image content is not assessed automatically, and photos are not sent to external image-review services. CrowdFlow Live does not use guest photos for facial recognition, advertising or model training.

Approved messages and photos may appear on the event display. They are visible to people present and anyone given access to the display address. Share only content that may be shown at the event, without confidential or sensitive information. For photos, you must hold the necessary rights and have the consent of recognisable people pictured.

Guest messages and related blocking information are automatically deleted after 16 hours by default. Rejected photos are deleted immediately; all other guest photos and versions created from them become inaccessible 16 hours after upload and are then automatically deleted. The legal basis depends on the event; legitimate interests may include running the event, moderation and preventing misuse (Article 6(1)(f) GDPR).

7a. Chatwall polls

For a Chatwall poll, we store the question, answer options, selected answers, time and a pseudonymous guest identifier to prevent repeat participation. The display shows aggregated results, not voters’ names. Questions, answer options and aggregated results remain stored until the account holder deletes them or the account is deleted. Guest identifiers used to prevent repeat participation are removed during regular clean-up once the poll is 90 days old; the results remain. Drafts also remain stored until deleted. The organiser’s responsibility described in section 2 also applies to the use of polls.

8. Feedback and analytics

Guests can submit star ratings or their mood. Until an analysis period closes, we store the rating, time, account association and visitor identifier. These may then be used to produce aggregated values such as counts and averages. The organiser can rename or delete saved periods.

For the account overview, CrowdFlow Live counts song requests and guest messages by account and period. These counts contain no request or message texts.

8a. Profile recommendations

A recommendation is counted only after you confirm it by email. We need your email address to send the message; the mail providers involved process it for delivery. In the recommendations database, we instead store a protected verification value, the relevant profile and the confirmation status. This lets us identify repeated recommendations from the same address for a given profile. Only the total count is public. The verification value is pseudonymous, not anonymous.

The confirmation link is valid for 24 hours. Unconfirmed entries are removed during regular clean-up once 48 hours have passed since the last request for a confirmation link. Confirmed recommendations remain until you withdraw them or the profile or account is deleted; withdrawn entries are removed after 30 days. You can withdraw a recommendation using your link or by contacting us. The legal bases are your consent under Article 6(1)(a) GDPR and our legitimate interest in preventing repeated recommendations under Article 6(1)(f).

9. Music data from Spotify, Apple, Deezer and Last.fm

To search for a song or add album, genre, release year or cover information, artist and title details and the associated song or album identifiers may be sent to Spotify, Apple (iTunes), Deezer and Last.fm. Guest names and comments are not part of these requests. Searches and additions run through CrowdFlow Live; the guest’s IP address is not sent directly from their browser to these providers.

Music data and covers found may be saved for later searches and analyses. The providers’ privacy notices apply to their processing:

• Spotify
• Apple
• Deezer
• Last.fm

The legal basis is Article 6(1)(f) GDPR. Our legitimate interest is convenient song searches and meaningful analytics for the account holder.

10. Browser notifications

Account holders can enable browser notifications for new song requests. We store the data needed for delivery, along with status and error information. Depending on the device, notifications are delivered through the browser or operating system provider’s push service, such as Apple, Google or Mozilla.

The legal basis is your consent under Article 6(1)(a) GDPR. You can withdraw permission in your browser and in CrowdFlow Live. Successfully processed delivery events are deleted after seven days; undelivered events after 30 days.

11. Protecting login and registration

Cloudflare Turnstile protects registration, login and password recovery against automated abuse. The check loads only when you use one of these forms. The provider is Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA. It processes your IP address and technical browser, device and connection signals. According to Cloudflare, form contents are not collected.

Account protection is based on Article 6(1)(f) GDPR. Our legitimate interest is to prevent automated registrations and attacks on user accounts. Where this requires storing or accessing strictly necessary information on your device, the legal basis is section 25(2)(2) of the German Telecommunications Digital Services Data Protection Act (TDDDG). No additional clearance cookie (Pre-Clearance) is enabled.

Cloudflare processes the data as our processor to protect our website and also as an independent controller to improve its bot detection. The Turnstile Privacy Addendum does not specify a single fixed retention period. For transfers to the USA, Cloudflare relies on the EU-US Data Privacy Framework; its contractual terms also provide for standard contractual clauses for relevant international transfers.

Turnstile privacy notice · Data processing terms

Google reCAPTCHA may still protect the contact form. It processes IP addresses, interactions and browser, device and connection information. The legal basis is Article 6(1)(f) GDPR; our interest is preventing automated submissions. Google processes this data as our processor. Retention depends on the type of data and security purpose; Google does not specify a single fixed period. Google reCAPTCHA.

Contact signup at events

After posting to the Chatwall, you can choose to leave your contact details with the organiser. Photos and messages work without signing up. The organiser is responsible for the contact list; CrowdFlow Live processes it on their behalf.

We store your name, email address and/or phone number, plus your website and message if provided. We also store the event, language, time and wording of your consent (Article 6(1)(a) GDPR). Email contacts are only shared after confirmation. Phone numbers are not verified.

Contacts are deleted after 12 months; unconfirmed email signups after 24 hours. The organiser can delete or export them earlier; their privacy notice applies to exported copies. The data does not appear on the Chatwall.

You can withdraw your consent at any time using the link in the confirmation email or by contacting the organiser. To apply the unsubscription to lists already exported, only the necessary matching information, particularly your email address and unsubscription date, remains visible for up to 30 days. This limited processing serves the legitimate interest of preventing further unwanted messages (Article 6(1)(f) GDPR).

A local browser identifier remembers that you have already seen the invitation until the next event changeover. Short-lived, hashed identifiers limit abusive signup attempts for up to one hour.

11a. Contact form

When you use the contact form, we process your name, email address, subject, message and receipt and delivery status. We need these details to process and answer your enquiry and track its receipt. Depending on the enquiry, the legal basis is Article 6(1)(b) GDPR for pre-contractual or contractual matters, or Article 6(1)(f) GDPR for general enquiries. Our legitimate interest is reliable communication.

The enquiry is sent to info@crowdflow.live and also stored in CrowdFlow Live’s protected administration area. Contact enquiries are automatically deleted after 365 days. You may request earlier deletion unless legal obligations or overriding grounds prevent it.

Google reCAPTCHA may also be used on the contact page to protect against automated enquiries. It evaluates connection and usage data. The information about Google reCAPTCHA in section 11 applies accordingly.

12. Media uploads

Account holders can upload their own images for Chatwall backgrounds and overlays. Upload only material for which you have sufficient usage rights, and avoid unnecessary personal data. These operator files remain stored until removed or replaced.

Guest photos are instead subject to the short retention period, initially private storage and organiser-selected approval described in section 7. Guest photos are available only when the organiser has an eligible plan and enables them in Chatwall settings.

13. Cookies and browser storage

To suggest a currency for subscription prices, we use your IP address to estimate your country. This lookup takes place on our server; your IP address is not sent to another provider or stored additionally for this purpose. You can change the currency yourself. The suggestion is based on our legitimate interest in presenting understandable prices (Article 6(1)(f) GDPR).

We store the currency preference for up to 180 days in the cf_currency cookie and, for signed-in users, in their account until it is changed or the account is deleted. This supports the pricing and booking display you use (section 25(2)(2) TDDDG; Article 6(1)(b) GDPR). Existing subscriptions keep their currency.

Necessary cookies and local storage support login, security, spam prevention, moderation, voting, one-time notices and saved interaction or display preferences. They rely on section 25(2) no. 2 TDDDG and, where personal data is processed, Article 6(1)(b) or (f) GDPR.

We remember your language choice in a functional cookie for up to twelve months. To suggest a language, we read your browser’s preferred languages without requesting your location. Your confirmed choice also applies in this browser the next time you visit or scan a QR code.

When you register, we save the language of the page you use in your account. You can change it in settings. It is also the default language for your guest pages; a guest’s own language choice takes priority.

On your first login, we use your browser’s time zone for the daily renewal at 08:00 local time. You can change it in settings. We do not request your location.

Unsent text is kept in the current tab for recovery for up to 15 minutes; photos are not stored for this purpose. The draft is removed after successful submission or on the next visit after it expires. If delivery is uncertain, a submission identifier is retained until confirmation, for no longer than the 16-hour guest session. This lets us check delivery without automatically sending again.

A necessary cookie is stored for a shared moderation access link until its expiry, for no more than 16 hours. Access applies only to the associated event and can be revoked at any time. We store the association, an optional helper name and the validity period; these access records are regularly deleted after expiry.

You can delete or block cookies and local storage in your browser. This may limit necessary features.

13a. Shared DJ access

An account holder can give other signed-in users time-limited access to selected areas and floors. For this, we store the accounts involved, permissions, validity period, acceptance and revocation status, and protected access credentials. Access ends at the specified time or when revoked. Expired and revoked entries are removed during regular clean-up after 90 days. This processing enables the requested shared use of the account and helps keep it secure (Article 6(1)(b) and (f) GDPR).

14. Campaign attribution and demo

If you arrive at CrowdFlow Live through a tagged campaign or partner link and then create an account, the campaign, partner, first page visited and time may be assigned to your new account. We use this to evaluate our own information campaigns and agreed partnerships. Without registration, no account-related campaign entry is created. We do not use an additional analytics or advertising cookie for this attribution.

The public song request demo displays the name, artist, song and optional comment in the demo list. Please do not enter private or confidential details. Demo entries become invisible after 24 hours and are then automatically deleted. Time-limited identifiers and quantity limits protect the demo from misuse. The IP address used for this is not stored with the demo request.

A separate demo count may record only the date, type and number of demo visits. If you register afterwards, your path through the demo may be assigned to your account. Campaign attributions and aggregated demo counts are deleted after twelve months.

The legal basis is Article 6(1)(f) GDPR. Our legitimate interests are a secure demo, preventing misuse and evaluating our own campaigns and partnerships. On grounds relating to your particular situation, you may contact info@crowdflow.live to exercise your right to object.

15. Emails and advertising

Necessary account, security, billing and contract messages are not marketing emails. They are sent only when required for your account, a contract, payment or security. The legal basis is Article 6(1)(b), (c) or (f) GDPR.

We treat all optional offers, promotions, surveys, newsletters, product news and site updates as advertising. We send these emails only if you explicitly consent in your account. The legal basis is Article 6(1)(a) GDPR together with section 7(2) no. 2 UWG.

You can withdraw consent at any time in your account or through the unsubscribe link in any marketing email, with effect for the future. For sending and record-keeping, we process the email address, content, delivery status, times and details of consent and withdrawal. Email addresses may be pseudonymised in records. After withdrawal, we retain proof for up to four years.

15a. Email send log

To investigate errors and keep a record of email handling, we store the recipient address, subject, a sanitised text excerpt, attachment names, time and sending status in a protected send log. Credentials and security links are hidden. A sending status does not confirm that an email was read or actually delivered. Entries are removed during regular clean-up after 90 days and are also covered by requests for access or deletion. The legal basis is our legitimate interest in reliable communication (Article 6(1)(f) GDPR). Invoices and legally required contractual records are kept separately for the periods described in section 17.

16. Recipients and transfers outside the EEA

Only parties needing data for the stated purposes receive it. These may include hosting and infrastructure providers, email, payment, music data and browser push providers, IT maintenance, support, advisers and legally authorised authorities.

Some providers may process data outside the European Economic Area. Transfers take place only under the conditions of Articles 44 et seq. GDPR, for example on the basis of an adequacy decision, the EU-US Data Privacy Framework or standard contractual clauses.

17. Retention periods and deletion

We retain data for the following periods:

• Guest messages and blocks: 16 hours.
• Guest photos: deleted immediately if rejected; otherwise inaccessible from 16 hours after upload, then automatically deleted along with all generated image versions.
• Guest browser identifier: 16 hours for standard forms; a separate identifier for individually created song-request events: 90 days. Both from issue, without rolling extension. Event link validity is separate.
• Aggregated vote scores in an imported song request archive: until the archive or account is deleted.
• Public song request demo: invisible after 24 hours, then automatically deleted.
• Error store: cleanup after 30 days without recurrence. Protection identifiers are used for no more than ten minutes and deleted during subsequent cleanup. Section 3 applies to other access and operational logs.
• Contact enquiries: 365 days.
• Browser notification events: seven days after successful delivery, otherwise 30 days.
• Account campaign attributions and aggregated demo counts: twelve months.
• Completed bulk email delivery logs: 90 days.
• Proof of withdrawn marketing consent: up to four years.
• Song request archives, including related conversations, feedback histories, settings and operator uploads: until deleted by the account holder or until the account is deleted. A plan change or cancellation does not automatically delete this data.
• Invoices and accounting vouchers: eight years from the end of the calendar year in which the document was created. Other documents required by tax or commercial law may be retained for six or ten years depending on their type. Necessary payment, refund and dispute data for requests with an extra contribution is retained only as long as required for processing, legal records or defending claims.

To request deletion of your account, email info@crowdflow.live. Documents subject to legal retention requirements remain stored with restricted access until the relevant period ends.

18. Required information and automated decisions

Information required for registration, contracts and payments must be provided. Without it, an account or plan cannot be set up. Comments, push notifications and marketing emails are optional.

CrowdFlow Live does not make solely automated decisions with legal or similarly significant effects within the meaning of Article 22 GDPR. Payment providers may carry out their own automated fraud and risk checks; their privacy notices apply.

19. Your rights

Subject to legal requirements, you have rights including access, rectification, erasure, restriction, data portability and objection. You can withdraw consent at any time with effect for the future. Withdrawal does not affect the lawfulness of processing before withdrawal.

To exercise your rights, email info@crowdflow.live. You can also complain to a data protection supervisory authority. The authority responsible for our registered location is:

20. Changes to this policy

We update this privacy policy when features, providers or the law change. The current version is always available through the footer.

Last updated: 23.10.2026