Privacy
Last updated: [date]
Draft
Draft – review before publishing, not legal advice. Details in [square brackets] are placeholders.
This is a translation of the German draft. The German version is authoritative.
In short: Dropcrew only processes what the app needs. No trackers, no analytics, no ads. Fonts are served from our own server.
1. Controller
[First and last name or company][Street and number], [Postcode and city]
Email: [Email address]
You can reach us at this address with any privacy question.
2. Hosting and server
The start page (dropcrew.live) and the app (app.dropcrew.live) run on our own server at [hosting provider] in [server location]. A data processing agreement with the provider is in place [check].
When you visit, the web server processes technically necessary data: IP address, time, requested address and browser identifier. Server logs are deleted after [server log retention period]. To prevent abuse (too many sign-in attempts) the server counts requests per IP address – only as a salted hash and only in memory.
Legal basis: legitimate interest in a secure, working service (Art. 6(1)(f) GDPR).
3. Your account
For an account we store your email address, your name (how others in your crew see you), whether your email address is confirmed, and your password – only as a hash, never in plain text. If you use passkeys, we store each passkey’s public key, a counter, the device name and timestamps. Your private key never leaves your device.
Legal basis: performance of the user agreement (Art. 6(1)(b) GDPR). You can delete your account in the app at any time; this deletes your account, passkeys, sessions and memberships. In the app you can also download a copy of your account data.
4. Sign-in cookie
After you sign in, the app sets exactly one cookie: __Host-dc_session. It contains a random session ID, cannot be read by scripts (httpOnly), is only sent over encrypted connections (Secure, SameSite=Lax) and is valid for 30 days from last use. With each session we store timestamps, the sign-in method and the browser identifier, so you can see and sign out your devices in the app.
The cookie is technically necessary for signing in and therefore needs no consent (§ 165(3) TKG 2021, Austria; § 25(2) TDDDG, Germany). The start page sets no cookies.
5. Crews and live rooms
When you start or join a crew, the server stores what you enter there together: event, sale phases and access codes, squad status and queue positions, polls, plan and settle-up. If you add payment details (IBAN, PayPal or Revolut name), only members of your crew can see them. Also stored: membership and role (organiser, admin, crew) and invites – for invite links we only keep a hash, expiry date, number of uses and an optional note.
Live rooms are deleted automatically when they haven’t been used for 60 days and no sale date is coming up. The organiser can delete a crew at any time. Legal basis: Art. 6(1)(b) GDPR.
6. Storage in your browser
The app stores settings, events, phases, checklists and history in your browser’s local storage (localStorage). This data stays on your device until you reset it in the app or clear it in the browser. The same goes for credentials you enter for this device only, such as your own Telegram bot. The start page only remembers your chosen language there.
7. Push notifications
If you turn on notifications, your browser creates a push address with its vendor’s push service (for example Google, Mozilla, Apple or Microsoft). We store this address with its keys, your crew and your squad entry. Messages are handed to the push service encrypted according to the Web Push standard; it cannot see the content, but it sees the time and the recipient address. You can turn this off in the app or in your browser settings. Legal basis: your consent (Art. 6(1)(a) GDPR).
8. Telegram, Discord and ntfy (optional)
If a crew connects a Telegram chat, a Discord webhook or an ntfy topic, the server sends alarms and updates there: title, text and a link to the shop page. Access codes are never included – only “code saved”. Further processing is governed by the privacy policies of Telegram, Discord or the ntfy server; data may be transferred to countries outside the EU. We store the Discord webhook and ntfy address encrypted.
9. Event search (Ticketmaster)
When you search for events in the app, our server forwards the query to Ticketmaster’s Discovery API. Only the search term, artist or event ID and country are sent – no account data, and Ticketmaster sees our server’s address, not yours. Buying always happens directly at the shop, under its privacy policy.
10. Emails
To confirm your email address and to reset your password we send emails via [email delivery service / SMTP provider]. We send no other emails – no ads, no newsletters.
11. What we don’t do
- No analytics or tracking services, no ads, no selling of data.
- No embedded third-party content; fonts and icons are served from our server.
- No automated decision-making and no profiling.
12. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21). You can withdraw consent at any time with effect for the future. Just email us at the address above.
You can also lodge a complaint with a data protection authority – in Austria the Datenschutzbehörde (Barichgasse 40–42, 1030 Vienna, dsb.gv.at), otherwise the authority where you live. [Check the competent authority before publishing.]