Privacy policy

1. Controller

[open: operator's name and address, email for privacy requests. Added before launch.]

This site is a preview with sample data. No real payments take place, sign-ups are closed.

2. In short

• No tracking, no analytics, no ad networks, no social plugins.
• Fonts, images, scripts and map tiles come from this server. Push notifications only if you switch them on.
• Without signing in we set no cookies.
• Your location and camera images never leave your device.

3. Server and logs

For every page our server processes technically necessary data: IP address, time, requested address, status code, browser identifier (user agent), to run the service securely and prevent abuse (Art. 6(1)(f) GDPR).

Logs rotate by size and older files are overwritten. Pages carrying confirmation or reset links are not logged. [open: fixed log retention]

[open: hosting provider, server location and data processing agreement]

To protect sign-in we count attempts per IP address (at most 10 in 15 minutes); the counter then expires.

4. Cookies and browser storage

We only access your device where strictly necessary for a service you asked for, or with your consent (§ 25 TDDDG).

• Session cookie “__Secure-nightigo.session_token” (HttpOnly, Secure): keeps you signed in, ends after 7 days or on sign-out.
• During a second-factor sign-in, a short-lived cookie for that step.
• “nightigo-theme” in localStorage: only when you press the light/dark switch.
• The service worker caches images, fonts and program files so the app loads faster. When you open your tickets while signed in, it keeps a copy of those pages on your device so the ticket shows at the door without signal. The copy is deleted when you sign out and at every new sign-in on the device, and is never shown after 7 days.

5. Your account

For an account we store email, display name, a hashed password, verification status, a second factor if set up, and per session the time, IP address and browser identifier (so you can recognise open sessions and we can prevent abuse) (Art. 6(1)(b) GDPR).

Optional: username, avatar, short bio, interests, saved events and clubs. Your profile is private by default; you decide whether friends or everyone can see it.

For features involving other people you confirm you are at least 18; we store when you confirmed.

Emails (verification, password reset) are not sent in this preview. [open: email provider at launch]

6. Friends, chats and reviews

When you use these features we store friend requests and friendships, whom you follow and block, your chats and messages, invitations and RSVPs.

Whether others see that you attended an event is your choice per event; off by default. Only people who were admitted themselves see other attendees.

Reviews require a real admission. Your username appears publicly only if your profile is public, otherwise “a guest”.

Blocking ends friendship, requests, follows and the direct chat; in groups you no longer see each other's messages. Reports are reviewed by an admin.

Points and badges are calculated from admissions, reviews and friendships and not stored separately. When you redeem a reward we store which one, when, and the voucher code. Recommendations use only your interests and saved clubs, never your location or chats.

7. Tickets and entry

We store orders, tickets and admission times to issue tickets and check them at the door. No money changes hands in this preview.

Organisers see short ticket references and admission status for their events. For guest lists, organisers enter names and plus-ones themselves.

The entry scanner uses the camera only after you allow it; the image is processed on the device and neither stored nor sent.

8. Organisers and uploads

For organisers we store organisation, role, venues, events and uploaded images. On upload we remove metadata such as camera and location data; images become public only when their event or venue is published.

Booked ads show one of the organiser's events with a short line, clearly labelled “Ad”. Nothing about visitors is stored or counted.

9. Maps, push and location

Maps: the maps show OpenStreetMap data. Our server fetches and caches the tiles itself; your browser does not connect to any map service, and OpenStreetMap learns neither your IP address nor what you look at. No consent is needed. The “Open in Google Maps” and “Route” (OpenStreetMap) links take you to those providers only when you click them.

Push notifications: only if you switch them on for a device. Your browser registers with its push service (Google, Mozilla, Microsoft or Apple depending on the browser); we store the delivery address and send encrypted notices with generic text, without names or event titles. Switching off under “Notifications” deletes the delivery address.

“Clubs near me”: your location is requested only after a tap, used only in the browser and neither sent nor stored.

10. Retention

• Sessions: 7 days. Confirmation and reset links: 24 hours or shorter.
• Account, profile and social data: until you delete the account.
• Orders and tickets: also after deletion where statutory retention applies; the account is then anonymised. [open: retention concept to be confirmed by a lawyer]

11. Your rights

You have the right of access, rectification, erasure, restriction, data portability and objection, and may withdraw consent at any time for the future.

Under “Profile → My data” you download everything stored about you and request deletion of your account. Deletion removes profile, favourites, sessions, push devices, friendships, chats, invitations and reviews; your chat messages are replaced by “–”.

You may lodge a complaint with a data protection supervisory authority. [open: competent authority depending on the operator's seat]