Louco Event Media GmbH, Berliner Straße 300b, 63065 Offenbach am Main
Last updated: 22 October 2026
This English version is a convenience translation. Only the German version is legally binding.
(1) The "Louco" platform (the website www.louco.app including subdomains, the mobile apps for iOS and Android and the associated interfaces, together the "Platform") is operated by Louco Event Media GmbH, Berliner Straße 300b, 63065 Offenbach am Main, registered in the commercial register of the Local Court (Amtsgericht) of Frankfurt am Main under HRB 130691, represented by its managing directors Evin Acar and Erhan Tilki ("Louco", "we").
(2) These Terms and Conditions apply to all contracts between Louco and the Users of the Platform. Users' deviating terms do not apply, even if Louco does not expressly object to them.
(3) Part B applies additionally to the purchase of tickets. Part C applies additionally to Creators. In the event of conflict, the rules in Part B or Part C take precedence over this Part A.
(4) Services of third parties that are linked to or integrated into the Platform (e.g. payment service providers, app stores, ticket providers) are additionally subject to those third parties' terms. We point this out at the relevant place.
(1) User means any person who accesses or uses the Platform, with or without an account.
(2) Private User means a User with an account who discovers Events, follows Creators, saves and shares Events and acquires tickets.
(3) Creator means a business with a Creator account who publishes Events on the Platform and, where applicable, sells tickets for them (e.g. organisers, clubs, DJs, artists, agencies). A Creator account is managed by one person.
(4) Door Staff means a person deployed by the Creator for a specific Event who scans tickets and manages the guest list using the separate Louco entry app ("Door Staff App"). Door Staff do not need a Louco account.
(5) Event means an event that a Creator publishes on the Platform (Creator Event) or that Louco automatically takes over from partners' offerings and displays (Partner Event, see Part B § B9).
(6) Consumer means any natural person who enters into a legal transaction for purposes that are predominantly outside their trade, business or profession (Section 13 German Civil Code (BGB)). Business (trader, Section 14 German Civil Code (BGB)) means any natural or legal person or partnership with legal capacity that, when entering into a legal transaction, acts in the exercise of its trade, business or profession (Section 14 BGB).
(1) Louco provides an online platform through which Users can discover Events, follow Creators, receive notifications and acquire tickets, and through which Creators can publish and promote Events and sell tickets.
(2) Louco is not the organiser of the Events offered on the Platform and not the seller of tickets for Creator Events. The organiser and the ticket Buyer's contractual partner is solely the relevant Creator. In this respect, Louco only provides the ticket shop to the Creator (ticket shop provider) and acts as an intermediary in the name and on behalf of the Creator. Part B sets out the details.
(3) For Partner Events, Louco does not broker a contract but merely redirects Users to the website of the relevant ticket provider (Part B § B9).
(4) Use of the Platform as a Private User is free of charge. Only services expressly marked as subject to a charge are chargeable (tickets; for Creators: subscriptions, event packs and Ticket Fees under Part C).
(4a) Louco reviews a Creator's first Event before publication, as well as changes to the date, time or venue of Events already running with tickets sold. This review serves the quality and safety of the Platform; it is no guarantee that the information is correct or that the Event will take place.
(5) Louco continually develops the Platform. Louco may change, add or discontinue functions, provided this is reasonable for the User and the core of the contractually owed service is preserved, in particular in the case of technical developments, changed legal requirements or for security reasons. Part C § C13 applies additionally to paid services.
(6) Louco does not owe uninterrupted availability. Where possible, we carry out maintenance at times of low usage. Claims relating to paid services remain unaffected.
(1) An account is required for many functions. Registration takes place by email address or telephone number with a verification code (one-time code by email or SMS) and password, or via a third-party login ("Sign in with Apple", "Sign in with Google"). On registration, the User chooses their role (Private User or Creator). An email address or telephone number can only be used for one account and only for one role; a Creator account cannot buy tickets.
(2) Anyone aged at least 16 may create a Private User account; users confirm this on registration by ticking a mandatory checkbox. If there are indications that a user is under 16, Louco may suspend or delete the account. A Creator account may only be created by a person who acts as a business (Section 14 BGB), is of full age and has unrestricted legal capacity, or who acts as an authorised representative of a company. Ticket purchases by minors require the consent of their legal guardians; age and entry restrictions for individual Events are set by the Creator (Part B § B7).
(2a) A Private User account is required to buy tickets for Creator Events. No Louco account is needed for Partner Events (Part B § B9), as the purchase is made from the partner.
(3) The information provided on registration and in the account must be true and complete and must be kept up to date. Each person may hold only one Private User account. Accounts are not transferable. An account must always have at least one sign-in method.
(4) Access data must be kept secret and protected against access by third parties. If there is a suspicion that third parties have gained access, Louco must be informed without undue delay (info@louco.app).
(5) On completion of registration, a free-of-charge user agreement for an indefinite period is concluded between the User and Louco. There is no entitlement to registration.
(1) Users, in particular Creators, can publish content on the Platform, e.g. Event descriptions, images, videos, logos, profile information and texts ("User Content"). The User remains the owner of their rights.
(2) The User grants Louco a non-exclusive, free-of-charge, territorially unlimited right in their User Content, limited to the duration of publication on the Platform plus reasonable run-off periods (in particular for technical backup copies and promotional materials already produced), to store, reproduce, technically adapt (e.g. formatting, cropping, compression, translation) and make the content publicly available, and to use it to promote the relevant Event and the Platform, including in newsletters, push notifications, on Louco's social media channels and in search engines. Louco may sublicense these rights to technical service providers to the extent necessary for operating the Platform.
(3) The User warrants that they hold all necessary rights in their User Content (in particular copyright, trade mark rights, personality rights and image rights of persons depicted, as well as rights of artists, photographers and collecting societies) and that the content does not violate any laws or these Terms and Conditions.
(4) The User indemnifies Louco against all third-party claims based on a culpable breach of paragraph 3, including the reasonable costs of legal defence. Louco informs the User without undue delay of any claims asserted and gives them the opportunity to comment.
(1) Users are prohibited from
(2) Part C sets out further obligations for Creators.
(1) Reporting: Any person – even without an account – can report Events and content they consider unlawful or in breach of these T&Cs via our report function ("Report event") or via our contact form (louco.freshdesk.com/support/tickets/new, category "Report content"). The report should contain the location (link), a statement of reasons and – except for certain criminal offences – the name and email address of the reporting person. We confirm receipt and inform the reporting person of our decision if they have provided contact details. We do not pass the identity of the reporting person on to the Creator unless this is strictly necessary for the review (e.g. in cases of copyright infringement) or required by law.
(1a) Each User can submit one report per Event; to prevent misuse, the number of reports per User per day is limited.
(2) Review and measures: Louco reviews reports promptly, diligently and objectively. Louco may remove or block content that is unlawful or violates these Terms and Conditions, refuse to publish an Event, take an Event offline (in particular in the case of legal or policy violations, safety risks, false or misleading information, frequent complaints or chargebacks, the Creator being unreachable, technical errors or suspected misuse), hide Partner Events, suspend ticket sales, restrict functions or block accounts temporarily or permanently. When choosing the measure, Louco takes into account the severity of the violation, whether it is a repeated violation and the legitimate interests of all parties involved (proportionality).
(3) Statement of reasons: If a User's content is removed or restricted or an account is blocked, Louco informs the affected User, at the latest at the time of the measure, of the measure, the reasons, the facts on which it is based, whether automated means were used, and the available remedies.
(4) Appeal: The affected User and the reporting User can lodge an appeal by email to info@louco.app within six months of the decision. Louco decides under the supervision of a qualified person and not solely by automated means. In addition, a certified out-of-court dispute settlement body under Art. 21 DSA and recourse to the courts are available.
(5) Point of contact: The single point of contact for authorities, the EU Commission and Users under Art. 11, 12 DSA is: info@louco.app. Communication is possible in German and English.
(6) Misuse: Louco may, after prior warning, block for a reasonable period Users who frequently provide manifestly unlawful content or persons who frequently submit manifestly unfounded reports.
(7) Automated moderation: Louco uses automated tools only in a supporting role (e.g. to detect duplicates and spam); decisions on content are made by a human.
(1) The User may terminate the user agreement at any time without notice by deleting their account in the app or on the website under "Settings > Delete account". Part C § C7 applies to Creators' paid subscriptions.
(2) Louco may terminate the free-of-charge user agreement with 30 days' notice. The right to extraordinary termination for good cause remains unaffected. Good cause exists in particular in the case of serious violations of these Terms and Conditions or violations repeated despite a warning, fraud, misuse of means of payment or an order by a public authority.
(3) Instead of terminating, Louco may temporarily block the account in the event of violations (§ 7 (2)). In doing so, Louco takes into account the legitimate interests of the User, in particular tickets already acquired and, for Creators, tickets already sold for upcoming Events.
(4) When the account is deleted, the account is deactivated immediately and the profile becomes invisible. Personal data is deleted or anonymised within 30 days in accordance with the privacy policy, unless statutory retention obligations apply. Tickets already acquired remain valid via the ticket link where technically possible; we recommend saving tickets before deletion (e.g. in the wallet).
(1) Louco is liable without limitation for intent and gross negligence, for injury to life, body or health, under the German Product Liability Act (ProdHaftG) and to the extent of any guarantee given.
(2) In the event of a slightly negligent breach of a material contractual obligation, Louco's liability is limited to the damage typical for the contract and foreseeable at the time the contract was concluded. Material contractual obligations are those whose fulfilment makes the proper performance of the contract possible in the first place and on whose observance the contractual partner may regularly rely.
(3) Otherwise, Louco's liability for slight negligence is excluded.
(4) Louco is not liable for the holding, cancellation, postponement, quality or safety of Events, for information provided by Creators or for services of partner ticket providers; the relevant Creator or provider is solely responsible for these. Louco's liability for its own breaches of duty under paragraphs 1 to 3 remains unaffected.
(5) The above limitations also apply in favour of Louco's legal representatives, employees and vicarious agents.
(6) In relation to businesses, liability under paragraph 2 is limited per claim to the amount of fees paid to Louco in the twelve months before the event giving rise to the damage, but to at least € 5,000; paragraph 1 remains unaffected.
Information on the processing of personal data is contained in our privacy policy at www.louco.app/de/privacy-policy. Part C § C11 applies to the use of Buyer data by Creators.
(1) Louco may amend these Terms and Conditions with effect for the future if there is a valid reason, in particular in the event of changes in the law or case law, when introducing new functions or changing existing ones, or to close regulatory gaps. Essential contractual terms, in particular the type and scope of the agreed services, prices and terms, are not changed in this way.
(2) Louco notifies changes in text form (e.g. by email or in-app message) at least six weeks (for Creators who are businesses: at least 15 days) before they take effect. The User may object to the changes until they take effect or terminate the contract without notice. For consumers, the changes only take effect if the User expressly agrees to them (e.g. by clicking at the next login); if they do not agree, the previous Terms and Conditions continue to apply and Louco may terminate the contract with 30 days' notice.
(3) For businesses, silence in response to the notification is deemed consent if Louco specifically pointed out this consequence, the objection period and the right of termination in the notification.
(1) Louco is neither willing nor obliged to participate in dispute resolution proceedings before a consumer arbitration board (Section 36 German Consumer Dispute Resolution Act (VSBG)).
(2) The law of the Federal Republic of Germany applies, excluding the UN Convention on Contracts for the International Sale of Goods (CISG). In relation to consumers, this choice of law applies only to the extent that it does not deprive them of the protection afforded by mandatory provisions of the law of the state in which the consumer has their habitual residence.
(3) If the User is a merchant, a legal entity under public law or a special fund under public law, the exclusive place of jurisdiction for all disputes is Offenbach am Main. Louco is also entitled to bring an action at the User's general place of jurisdiction.
(4) The language of the contract is German. Translations are for information only; in the event of discrepancies, the German version prevails.
(5) Louco does not store the contract text (these Terms and Conditions in the version valid at the time the contract was concluded) individually for each User. The current version is available at any time at www.louco.app (link "AGB"); we will provide earlier versions on request. For purchases, the User also receives the Terms and Conditions by link in the confirmation email.
(6) Should individual provisions be invalid, the validity of the remaining provisions remains unaffected. The invalid provision is replaced by the statutory provision.
(1) A Creator account may only be created by businesses (traders) within the meaning of Section 14 German Civil Code (BGB). By registering, the Creator confirms that it is acting in the exercise of its commercial or independent professional activity. A Creator account is managed by a natural person; where that person acts for a company, they warrant that they are authorised to do so.
(1a) Creator accounts are currently only available to businesses with their registered office or an establishment in Germany; Events can only be published for venues in Germany (or as online Events).
(2) When registering, the Creator provides its full name, email address, telephone number, the name of the Creator or company and its business address. In the settings, it also enters its company name, legal form, billing address and, where available, its VAT identification number, commercial register number and tax number. The information must be true and complete and must be kept up to date.
(3) During onboarding, Louco may ask for information on the scope of the business (e.g. Event categories, annual ticket volume, frequency of Events) in order to tailor its offering and support.
(4) The Creator profile only becomes publicly visible and searchable once the Creator's first Event has been approved by Louco.
(5) Louco may request further proof of identity and of the business in order to comply with legal obligations (e.g. under the Digital Services Act or the German Platform Tax Transparency Act (PStTG)). Until such proof is provided, Louco may suspend ticket sales.
(6) If a consumer poses as a business, they shall indemnify Louco against all resulting disadvantages; in this case, Louco may terminate the contract for cause.
(1) The Creator first creates Events as drafts. Clicking "Publish" or "Submit for review" uses or reserves a credit (§ C4).
(2) Review before the first Event: Before a Creator's first Event is published, Louco reviews the Event and the Creator, in particular that the Creator operates a business or is self-employed and is not a consumer. For this purpose, Louco may request proof, e.g. a trade registration, an extract from the commercial register, a VAT identification number or other proof of self-employment. The review usually takes up to 24 hours after complete submission; the first Event must therefore start at least 24 hours after the expected publication. Louco approves the Event or rejects it, giving reasons; the Creator may then revise it and resubmit it. If the Creator cannot prove its status as a business, Louco may refuse approval and terminate the Creator account. There is no entitlement to approval.
(3) Further Events are published immediately once the first Event has been approved. Louco may review them subsequently and take them offline under § 7 Part A.
(4) Changes: The title, description, media, ticket types, discount codes, category and other details can be changed at any time. Changes to the date, time or venue of a published Event for which tickets have already been sold are reviewed by Louco before they take effect; until approval, the previous version remains visible. All ticket holders are automatically informed of changes to the date, time and venue. The type of Event (public/private) cannot be changed after publication.
(5) Duplicates: Louco compares new Events with existing ones. If an Event matches an Event already published by another Creator, it cannot be created. If it matches a partner Event (Part B § B9), the Creator Event is displayed and the partners' purchase options are additionally offered on the Creator's Event page. The Creator agrees to this.
(6) Cancellation: The Creator may request the cancellation of a published Event via "Request cancellation", stating a reason. Louco reviews the request and either carries out the cancellation or rejects it, giving reasons. Louco may also cancel Events without a request if legal, safety-related or policy-related reasons so require. Upon cancellation, all paid tickets are refunded in accordance with Part B § B8. The Creator's obligation towards Buyers to refund cancelled Events remains unaffected; the Creator must not let an Event for which tickets have been sold fail to take place without cancelling it via Louco.
(6a) Refund policy: For Events with paid tickets, the Creator must set a refund policy before publication (template "Flexible: 100 % up to 7 days before the Event", up to three custom tiers, or "no refunds"). It is bound by the published policy and processes refund requests from Buyers promptly, usually within 48 hours. A subsequent change to the detriment of Buyers does not apply to tickets already sold.
(7) Deletion: The Creator may delete drafts; they are permanently removed after 6 months. Published, past, cancelled or offline Events are only hidden when deleted; order, ticket and admission data are retained (archive).
(1) The Creator is the organiser of its Events and is solely responsible for holding them. In particular, it is obliged
(2) Taxes: The Creator sets the tax rate and tax designation for its tickets itself. Louco does not check tax accuracy and does not pay any taxes. The Creator is solely responsible for the correct tax treatment of its ticket sales.
(3) Discount and access codes are set by the Creator on its own responsibility. It ensures that codes are not advertised in a misleading way.
(4) The Creator shall indemnify Louco against all claims by third parties (including Buyers, authorities, collecting societies and rights holders) arising from a culpable breach of these obligations or from the holding or non-holding of its Events, including the reasonable costs of legal defence.
(1) To publish each Event, the Creator needs one credit – regardless of whether the Event has paid tickets, free tickets or no tickets at all. For the first Event, the credit is reserved on submission, used on approval and released again on rejection; resubmitting a rejected Event does not use an additional credit. For all further Events, the credit is used on publication. Drafts do not use credits.
(2) Used credits are not refunded, including where an Event is cancelled, taken offline or deleted.
(3) The Creator receives credits through a subscription, an event pack or the free trial month. All prices are final prices including statutory VAT (19 %).
(4) Release of subscription events in weekly tranches: The Events of a subscription are not released all at once, but in four tranches per billing month (at the start of the billing month and then after 7, 14 and 21 days): Basic 1 Event, Plus 2 Events, Pro 3 Events per tranche. Unused Events of a tranche remain usable until the end of the billing month. All subscription events expire at the end of the billing month; they are not carried over to the next month, paid out or refunded. Anyone who needs more Events at short notice can buy event packs at any time; these are available immediately.
(3a) Only one subscription at a time: A Creator can only have one subscription (Basic, Plus or Pro) at any one time. Event packs can be bought in addition to a subscription or without a subscription.
(4a) Event pack credits are valid for 12 months from purchase and remain usable without a subscription; on expiry, they lapse without replacement. Subscription events are always used first, followed by event pack credits; event pack credits are used in order of their expiry date (those expiring first are used first).
(5) Without available credits, the Creator can create and edit drafts, but cannot publish or submit Events.
(6) The current plans and prices can be viewed at any time in the Creator area under subscription management.
(1) The Creator selects a subscription or event pack in the Creator area and completes the order on the Louco website via Stripe (button e.g. "Buy now · € 249.90" or "Start free trial month"). The contract with Louco is concluded on completion of payment or – for the free trial month – on completion of the order. Event pack credits are credited immediately.
(2) Subscription fees and event pack prices are payable in advance and are collected via the stored payment method. The Creator manages payment methods and invoices in the Creator area. Louco issues invoices electronically to the stored billing address; the Creator agrees to electronic invoicing.
(3) In-app purchase (once available): If subscriptions are purchased in the iOS or Android app, purchase, payment, renewal, trial period, cancellation and refund are handled exclusively by Apple (App Store) or Google (Google Play) in accordance with their terms; prices there may differ. A subscription cannot exist via the website and an app store at the same time.
(1) When taking out a subscription for the first time, the Creator receives a free trial period of 30 days ("free trial month") with the Events of the selected plan (Basic 4, Plus 8, Pro 12 Events, released in weekly tranches as in § C4 (4)). The free trial month is available to each Creator (for companies: to each company) only once, regardless of the plan selected. Anyone who has already had a subscription does not receive a free trial month.
(2) If the subscription is not cancelled by the end of the free trial month, it automatically converts into the selected paid plan. The date of conversion and the price then payable are displayed before the order is completed. Nothing is charged on the day of the order; the first subscription fee becomes due at the end of the free trial month. The first billing month starts on that day (§ C7 (1)).
(3) Upgrade during the free trial month: If the Creator selects a higher plan during the free trial month, it starts at the end of the free trial month. If the Creator has already used all Events of the free trial month, the free trial month ends immediately; the full price of the higher plan is charged on that day, and the first billing month begins.
(4) Downgrade during the free trial month: If the Creator selects a lower plan during the free trial month, it applies from the end of the free trial month; the first charge is then made at the price of the lower plan.
(5) Unused Events from the free trial month expire at its end.
(6) Louco reminds the Creator by email no later than 3 days before the free trial month ends that it will convert into the paid subscription.
(1) Term and billing month: The billing month starts on the day of booking or – after a free trial month – on the day the free trial month ends. The subscription automatically renews for a further month on the same calendar day of the following month unless it is cancelled before expiry; if that day does not exist in the following month (e.g. the 31st), it renews on the last day of that month. Example: start on 15 October → billing on the 15th of each month.
(2) Upgrade (switch to a higher plan): An Upgrade is scheduled and starts automatically as soon as all Events of the current billing month have been used or the billing month ends – whichever occurs first. On that day, the full price of the new plan is charged and a new billing month begins; the billing date moves to that day. There is no pro rata offsetting, credit or refund of the previous plan. Unused subscription events of the previous plan expire on the switch. The switch only takes place if payment is successful; otherwise, the previous plan remains unchanged. The Creator may withdraw a scheduled Upgrade until the switch. The timing and price are displayed before confirmation.
(3) Downgrade (switch to a lower plan): A Downgrade takes effect at the end of the current billing month and can be reversed until then. Until then, the plan and available Events remain unchanged. There is no pro rata refund or credit. A scheduled Upgrade cancels a scheduled Downgrade; while an Upgrade is scheduled, no Downgrade can be scheduled.
(4) Cancellation by the Creator: Subscriptions can be cancelled at any time with effect from the end of the current billing month (or of the free trial month), in the Creator area under subscription management or in text form to info@louco.app. Louco confirms the cancellation with the end date. The Creator may reverse the cancellation until the end of the billing period. Invoices remain accessible.
(5) No refund: Subscription fees already paid are not refunded pro rata, either on cancellation or on Downgrade. Event pack prices are not refunded. Statutory rights (e.g. termination for cause, warranty) remain unaffected.
(6) Consequences of the end of the subscription: When the subscription ends, unused subscription events expire. Event pack credits are retained. Events already published remain online, and ticket sales continue until the Event date; the Ticket Fees under § C8 remain payable. Events submitted for review before the end of the subscription retain the subscription event reserved for them. To publish further Events afterwards, the Creator needs event pack credits or a new subscription.
(7) Failed payment: If a subscription fee cannot be collected, Louco informs the Creator by email of each failed attempt and retries collection via Stripe several times within 14 days. The Creator may update its payment method during this period. New subscription events are only credited after successful payment; event pack credits remain usable. This does not apply to the Events of the free trial month (§ C6), which are provided without payment. If the last attempt also fails, the subscription ends automatically; Events already published remain online and ticket sales continue. The outstanding subscription fee remains payable; Louco may claim default interest and the lump sum under Section 288 (5) German Civil Code (BGB) and may pass the claim to a debt collection service provider.
(8) Termination by Louco: Louco may terminate a subscription with 30 days' notice with effect from the end of a billing period and will state the reasons (Art. 4 EU Platform-to-Business Regulation (P2B Regulation)). The right to terminate for cause (e.g. serious breaches of these Terms, fraud, repeated payment default) remains unaffected. If Louco terminates without fault on the part of the Creator, Louco refunds the purchase price of unused event pack credits pro rata.
(1) For each paid ticket sold via the platform for a Creator Event, a Ticket Fee of 1.9 % of the ticket price plus € 0.30 per ticket, in each case plus statutory VAT, is charged. The basis of assessment is the ticket price after deduction of discounts including the tax set by the Creator (gross ticket price). Louco's VAT is charged only on the Ticket Fee, not on the ticket price.
(2) Passing on to Buyers: The Ticket Fee is owed by the Creator. For each ticket type, it can decide whether to bear the fee itself or to pass it on to the Buyer in full or in part as a "service fee" (Part B § B3). If it passes it on, the service fee charged to the Buyer must not exceed Louco's Ticket Fee including VAT; the Creator must not add a surcharge to it. The service fee must be included in the total price displayed. This does not change the amount of the Ticket Fee owed to Louco.
(3) No Ticket Fee is charged for free tickets. No Ticket Fee is charged for partner Events.
(4) Fees of payment service providers: In addition, the Creator bears the fees of Stripe or PayPal for payment processing. Their amount depends on the payment method (e.g. card, Apple Pay, Google Pay, PayPal) and is governed by the Creator's contract with the respective payment service provider. That provider deducts them directly from the Creator's account; they are not charged by Louco and do not reduce the Ticket Fee.
(5) Collection: The Ticket Fee is automatically retained with each payment – with Stripe as an "application fee", with PayPal as a platform fee ("partner fee") – and credited to Louco. Louco provides the Creator with a monthly invoice or collective invoice for the Ticket Fees in the Creator area.
(6) Refunds – the Ticket Fee is always earned: Louco's Ticket Fee is not refunded under any circumstances, including where a ticket is cancelled and refunded in full or in part – whether under the Creator's refund policy, at the Buyer's request, voluntarily by the Creator or upon cancellation of the Event. Refunds to Buyers are made exclusively from the Creator's balance. How much the Buyer receives back depends on the Creator's refund policy; whether a service fee paid by the Buyer is also refunded is decided by the Creator when issuing the refund (§ B8 (3a)). Upon cancellation of an Event, the Creator is legally obliged to refund the Buyer the full price including any service fee paid, regardless of its refund policy; this refund is borne solely by the Creator, and Louco's Ticket Fee remains earned. Stripe payment fees are likewise not repaid on refunds; these costs are borne by the Creator.
(1) A prerequisite for selling paid tickets is a connected Stripe Standard account of the Creator with the status "connected". By setting it up, the Creator enters into its own contract with Stripe (Stripe Services Agreement, available at stripe.com/legal). Stripe carries out identity and anti-money laundering checks itself. Events with free tickets only can be published without a Stripe account.
(2) The Creator is the merchant ("Merchant of Record") towards Stripe and the Buyers. Ticket revenue goes directly to its Stripe account and is paid out according to its payout schedule at Stripe. Louco does not receive ticket revenue and has no influence on payouts, blocks or reviews by Stripe.
(3) The Creator handles chargebacks and payment disputes itself via its Stripe dashboard. Louco informs the Creator of incoming disputes and displays their status.
(4) Restricted Stripe account: If Stripe restricts the Creator's account, the Creator cannot publish Events with paid tickets, and its published Events with paid tickets are automatically taken offline; sales are stopped, and tickets already issued remain valid. Once the issue has been resolved, the Creator may request reinstatement via support.
(5) PayPal: If Louco offers PayPal as a payment method and the Creator uses it, the following applies: the Creator connects its own PayPal business account for this purpose and enters into its own contract with PayPal (Europe) S.à r.l. et Cie, S.C.A., Luxembourg. Payments via PayPal go directly to the Creator's PayPal account; the Creator is the merchant towards PayPal. The Ticket Fee under § C8 is retained directly in favour of Louco as a platform fee on each PayPal payment. The Creator handles and bears refunds, chargebacks and buyer protection cases with PayPal; the platform fee is not refunded in such cases (§ C8 (6)). Paragraph 4 applies accordingly to a restricted PayPal account.
(6) If Louco incurs costs or damage because the Creator fails to meet its refund or payment obligations, the Creator shall reimburse them.
(1) The Creator instructs and authorises Louco to issue invoices for tickets sold to Buyers, at their request, in the name and for the account of the Creator and to send them by email (Section 14 (2) sentence 4 German VAT Act (UStG)). They are based on the information stored by the Creator (company name, address, VAT identification number or tax number, tax rate and tax designation).
(2) The Creator ensures that this information is complete and correct, checks the invoices on a spot-check basis and reports errors without undue delay. The Creator remains solely responsible for the tax treatment of its sales.
(2a) Missing tax information: Providing a VAT identification number or tax number is voluntary; the Creator is solely responsible for ensuring that its invoices are correct for tax purposes. If the Creator has not stored a tax number or VAT identification number, Louco only issues invoices as small-amount invoices (total amount up to € 250) or as payment confirmations without the function of a VAT invoice; if a Buyer needs a full invoice, the Creator issues it itself. Louco is not liable for disadvantages resulting from missing or incorrect tax information; the Creator shall indemnify Louco against claims by third parties and the tax authorities.
(3) The Creator may object to invoicing by Louco in text form; it must then issue invoices itself.
(1) Louco provides the Creator with the data required to hold its Event, in particular name, email address, order and ticket data, discount codes used, check-in status and, where voluntarily provided by the Buyer, telephone number and billing address. For followers, the Creator only sees the number, not their identity; for watchlists and shared links, only totals.
(2) The Creator processes this data as an independent controller within the meaning of the GDPR. It may use the data exclusively to hold the Event (e.g. admission, guest list, information about changes and cancellations, refunds, invoicing, compliance with legal obligations). Any other use, in particular for advertising, newsletters or disclosure to third parties, is only permitted if the Creator has its own legal basis for it (e.g. demonstrable consent).
(3) Invitations: If the Creator invites persons by email address or CSV upload, it warrants that it has collected the contact details lawfully and that each invited person has agreed to receive an invitation to its Events. Louco sends the invitation on behalf of the Creator with the Creator's name as sender. Invitations may only refer to the specific Event and must not contain any further advertising. The Creator shall indemnify Louco against all claims arising from unwanted invitations (in particular for unlawful email advertising). Louco may restrict the invitation function in the event of complaints.
(4) Guest list: If the Creator or its door staff enter persons in the guest list (name, optionally email, notes), the Creator is responsible for the lawfulness of this. Notes must not contain sensitive information (e.g. health, ethnic origin) or derogatory content.
(5) Door staff: The Creator sets up door staff for the Louco check-in app and itself determines the access period, the Events, the visibility of personal guest data and the permissions (e.g. managing the guest list, on-site sales); it may revoke access at any time. In doing so, it only selects the rights and data required for admission and restricts access to the period of the Event. It is responsible for the selection and conduct of the staff, including where they add, edit, delete or invite guests; paragraph 3 applies accordingly. It obliges the staff to maintain confidentiality, shares the invitation link only with these persons and ensures that the ticket and guest list data stored on their devices for offline operation is not used further after the Event. Access ends automatically after the Event.
(6) The Creator provides Buyers and guests with the information under Art. 13, 14 GDPR about its own data processing (e.g. a link to its privacy policy in the Creator profile), deletes data as soon as it is no longer required, takes appropriate security measures and informs Louco without undue delay of personal data breaches affecting data from the platform.
(7) The Creator shall indemnify Louco against all claims and fines arising from an unlawful use of this data for which it is responsible.
(8) Processing on behalf for guest lists and invitation lists: Insofar as Louco processes data that the Creator itself enters or uploads (guest list, invitation and CSV lists, notes), Louco acts as the Creator's processor under Art. 28 GDPR. The Data Processing Agreement in Annex 1 to Part C applies; it is agreed upon acceptance of these terms.
(1) Louco decides on the display and ranking of Events according to the main parameters in Part B § B10. There is no entitlement to a particular placement, reach, number of views or ticket sales.
(2) Statistics in the Creator area (e.g. revenue, views, check-ins, watchlists, shared links) are for information purposes; Louco does not guarantee that they are complete or in real time. The data from Stripe is authoritative for payments.
(3) Complaints: Creators may contact info@louco.app with complaints about rejections, Events being taken offline, blocks or the ranking. Louco reviews complaints promptly and communicates the outcome.
(1) Louco may change the prices of a subscription and the Ticket Fee for the future. Louco gives notice of the change in text form at least 30 days before it takes effect. The change is deemed approved if the Creator does not cancel before it takes effect; Louco points out this consequence and the right to cancel in the notice.
(2) Event pack credits already purchased and tickets already sold are not affected by price changes.
(1) Louco endeavours to ensure high availability of the platform, excluding scheduled maintenance and disruptions beyond Louco's control (e.g. outages of payment service providers, app stores, partners). The admission app also works offline with the data loaded in advance.
(2) The statutory warranty rights apply, subject to the proviso that Louco is first given the opportunity to remedy the defect within a reasonable period.
The Creator account exists independently of a subscription until it is terminated under § 8 Part A. If a Creator requests deletion, its account is deactivated immediately. As long as the Creator has upcoming Events with tickets sold, the account is only deactivated; no new tickets are sold for these Events, and deletion takes place only after the last Event and after all refunds have been processed. Tickets already issued remain valid, and the Creator's obligations towards Buyers (in particular holding or cancelling and refunding future Events) continue. Unused credits expire upon deletion.
Agreement under Art. 28 (3) GDPR between the Creator ("controller") and Louco Event Media GmbH, Berliner Straße 300b, 63065 Offenbach am Main ("Louco" or "processor")
(1) Louco processes, on behalf of the Creator, personal data that the Creator or door staff deployed by it enter or upload into the platform in order to (a) keep guest lists for Events and check them at admission, (b) send and manage invitations and waitlist notifications by email, push and in-app message in the name of the Creator, and (c) record guest check-ins.
(2) Nature of processing: collection (by entry/upload), storage, display (Creator area, check-in app, including offline on door staff devices), sending, matching, alteration, erasure.
(3) This Agreement applies as long as Louco processes such data for the Creator and ends with the termination of the Creator account or the erasure of the data under § 9.
(1) Categories of data: first and last name, email address, Louco username, number of accompanying persons, ticket type name, "invited by", notes for staff, personal invitation message, invitation and waitlist status, check-in status and time, person carrying out the check-in.
(2) Data subjects: the Creator's guests and invitees (including persons without a Louco account), accompanying persons, door staff.
(3) Special categories of personal data (Art. 9 GDPR) must not be entered (e.g. health, ethnic origin, religion in notes).
(1) Louco processes the data only on documented instructions from the Creator. The instructions are set out exhaustively in this Agreement and in the functions of the platform (e.g. add guest, send invitation, delete guest). The Creator gives further instructions in text form to info@louco.app; Louco may reject instructions that go beyond the scope of functions.
(2) Louco informs the Creator without undue delay if, in Louco's opinion, an instruction infringes data protection law.
(3) Louco does not process the data for its own purposes. This does not apply to storing an email address on a block list if the data subject states that they no longer wish to receive invitations via Louco; to that extent, Louco is an independent controller.
(1) The Creator is responsible for the lawfulness of the processing, in particular for having collected the data lawfully, for there being a legal basis for the guest list and invitations, and for the invited persons having agreed to receive invitations (Part C § C11 (3)).
(2) The Creator informs the data subjects in accordance with Art. 13, 14 GDPR and handles their requests; Louco supports it in this in accordance with § 7.
Louco only uses persons who have been bound to confidentiality and familiarised with the data protection provisions. Only persons who need access for their tasks (e.g. support, operations) have access.
(1) Louco takes appropriate technical and organisational measures under Art. 32 GDPR, in particular encryption of transmission (TLS) and of stored data, a role and permissions concept, two-factor authentication for administrators, logging, data backup and regular review.
(2) Louco may further develop the measures, provided that the level of protection is not reduced.
Louco supports the Creator with appropriate measures in fulfilling the rights of data subjects (Art. 15–22 GDPR), in particular through the functions for editing, exporting and deleting guests and invitations and the "Delete personal data" function for orders. If a data subject contacts Louco directly, Louco forwards the request to the Creator without undue delay. Louco also supports the Creator with data protection impact assessments and consultations with the supervisory authority, insofar as these concern the processing under this Agreement.
Louco notifies the Creator of personal data breaches affecting the Creator's data without undue delay, where possible within 48 hours of becoming aware of them, with the information under Art. 33 (3) GDPR, insofar as available. Notification to the supervisory authority and to data subjects is the responsibility of the Creator; Louco supports it in this.
(1) Louco erases guest lists, guest check-in data and invitations and waitlist entries that have not been accepted on the Creator's instructions, at the latest at the end of the Creator account (paragraph 2); the Creator may delete them itself at any time. Uploaded CSV lists are not stored for other purposes after the invitations have been sent.
(2) At the end of the Creator account, Louco erases all data under this Agreement, unless there is a statutory retention obligation. Before erasure, the Creator may download the guest lists via the export function. Copies in backups are erased as part of the regular backup rotation.
(1) The Creator approves the use of the sub-processors listed in the current list at www.louco.app/de/unterauftragsverarbeiter (currently in particular Amazon Web Services EMEA SARL and Hetzner Online GmbH for hosting, Microsoft Ireland Operations Ltd. (Microsoft Graph) for sending emails, Google Ireland Limited (Firebase) and Apple for push notifications).
(2) Louco informs the Creator at least 30 days in advance of the engagement or replacement of sub-processors (e.g. by email or by updating the list with a notification function). The Creator may object for an important reason under data protection law; if no agreement is reached, it may stop using the affected functions or terminate the Creator account.
(3) Louco contractually binds sub-processors to a level of protection that corresponds to this Agreement.
Processing outside the EU or the EEA only takes place if the requirements of Art. 44 et seq. GDPR are met, in particular in the case of sub-processors that are certified under the EU-U.S. Data Privacy Framework or have concluded EU Standard Contractual Clauses.
(1) On request, Louco provides the Creator with the information required to demonstrate compliance with this Agreement, in particular a current description of the technical and organisational measures and any existing certificates or audit reports.
(2) On-site audits are possible with at least 30 days' notice, during normal business hours, without disrupting operations and no more than once a year, provided that the information under paragraph 1 is not sufficient. The costs are borne by the Creator, unless the audit reveals a material breach by Louco.
(1) Liability is governed by Art. 82 GDPR. Otherwise, the liability rules of the Terms (Part A § 9) apply.
(2) In the event of conflicts between this Agreement and the other terms, this Agreement takes precedence with regard to data protection.