PRIVACY INFORMATION

1. Controller and contact

SAMPLE — replace with confirmed organizer details before publication.

Organizer / controller

SAMPLE

Street and house number

SAMPLE

Postcode, city and country

SAMPLE

Privacy contact email

SAMPLE

The event organizer is intended to be responsible for event orders and attendee information. The event is presented on this website as 8586 Nepal. The fields above are placeholders, not valid contact details. Data protection officer contact details must be added if applicable.

2. Who is responsible for what?

This notice covers the public concert website and shop preview. Sixhead Studio / Aman Maharjan built the website and provides the platform. Under the intended arrangement, the organizer has access to event customer records, handles orders and receives customer payments directly. Sixhead Studio does not act as a payment intermediary and is not intended to have access to event customer records. NFC Stuttgart e.V is credited as a supporter; this does not grant access to customer data.

Before live use, confirm the actual access controls and whether platform hosting, maintenance or support involves processing personal data on the organizer’s behalf. The corresponding responsibilities and any required processing agreement must reflect that technical arrangement. Website hosting responsibilities must be documented separately from event-order responsibilities.

3. Visiting the site, hosting and security

Your browser requests pages, fonts and images from the server serving this site. These requests involve connection information such as an IP address, requested resource and browser headers. Fonts and artwork are served with the site; no external font service is embedded.

The supplied local preview server does not write access logs. Any public hosting provider may process connection or security logs separately.

Before publication: identify the host, processing locations, log fields, security purposes, legal basis and retention period. Public hosting has not been confirmed for this project.

4. Cookies and storage on your device

The current public preview does not set cookies or use localStorage, sessionStorage, advertising trackers or analytics. Selections and entered customer details are used in the open page only; the application does not persist them. Browser autofill or page restoration may retain information according to your browser settings.

Any future storage or third-party integrations must be assessed and described before activation, with consent controls where required.

5. Tickets, orders and customer details

The preview asks for full name and email; phone number is optional. It also handles ticket type, quantities, merchandise sizes, subtotal and payment-method choice. These values stay in the page: the current shop does not submit them to an organizer, create an order or send a ticket. Please use example details during testing.

For the planned live shop, name and email will support order handling and ticket delivery. An optional phone number is intended for order-related questions, not marketing. Order records, payment status and QR ticket or entry-check records will need their own confirmed handling arrangements.

Before sales: confirm the exact data, purposes, lawful bases, access permissions, email provider, ticket-checking process and merchandise fulfillment arrangements. A shipping address is not requested in this preview.

6. Payment

No payment provider is connected and no financial information is requested in this preview. PayPal and bank transfer are proposed options. Eventfrog has been discussed but is not integrated.

The planned PayPal flow would confirm an order after successful payment. The planned bank-transfer flow asks customers to send payment within one hour of placing an order; receipt would be verified manually. Neither a reservation nor a deadline is created here.

Before activation: identify the actual payment providers and account holder, information shared or received, provider privacy notices, lawful bases, retention and any international transfers. Do not send payment using this preview.

7. Accounts, announcements and other features

This public preview has no customer accounts, “keep me posted” subscriptions, customer cards, standing orders, referral or voucher system, reviews or sold-out waitlist.

There is no seller question system, AI helper, Ask bar, help bot, contact chat, contact form, microphone recording, automatic translation or AI processing of customer details. The checkout details form only supports the local walkthrough.

Google Analytics and other visit counters are not installed. The public site has no installable app, offline ticket storage or working ticket delivery. Any separate admin or scanner prototype is outside this public customer flow and must be assessed before use with real attendee data.

8. Photos, videos and information for organizers

Artist and merchandise images are displayed as website content. Visitors cannot upload photos or videos. This notice does not establish a policy for photographing or filming attendees at the concert; any such activity needs separate information from the responsible organizer.

There is no organizer or seller registration on the public site. Live administrative access and staff handling of customer data remain to be defined.

9. Recipients and transfers outside the EU/EEA

The preview does not transmit form entries to payment, email, analytics or AI services. The server serving the site receives the page requests described above.

For the live service, list the actual recipients or categories, their roles, processing countries and any applicable safeguards for transfers outside the EU/EEA. No provider list or international-transfer arrangement has been confirmed.

10. Storage periods

The public application does not store submitted orders or customer records because submission is not implemented. Entered details exist in the open page; browser-controlled autofill or restoration is separate. The local preview server does not keep access logs.

Before live use: specify retention periods or criteria for hosting logs, abandoned or unpaid orders, customer enquiries, paid orders, accounting records, payment references and ticket scans, including deletion and backup handling. No live retention schedule has been agreed.

11. Required information and automated decisions

A full name and a valid email format are required to open the payment preview. Phone is optional. The planned service would need an email address to deliver tickets. No customer details are needed just to browse the landing page.

The preview calculates prices and checks required fields. It does not profile visitors or make automated decisions with legal or similarly significant effects.

12. Your rights, objections and complaints

Where applicable, you may request access, correction, deletion, restriction and portability of your personal data. Consent can be withdrawn for the future. You may object on grounds relating to your situation to processing based on legitimate interests; you may object to direct marketing at any time.

You may complain to a supervisory authority, including where you live, work or believe an infringement occurred. See the Baden-Württemberg data protection authority’s complaint information. The controller’s contact details above must be completed so requests can be directed to the responsible organization.

Legal reference: GDPR, particularly Articles 12–22 and 77.

13. Changes to this policy

Draft updated: 2 October 2026. This notice must be reviewed when hosting, payments, ticket delivery or other data processing changes. Unconfirmed items must be completed before this is used as the privacy notice for a live ticketing service.