Privacy policy

1. Controller

The controller within the meaning of the General Data Protection Regulation (GDPR) is:

2. What data we process

• Without an account: viewing and searching events and using the map work without signing in. If you save an event in the app as a guest, that list stays on your device only. We move it into your account once you sign in.
• Anonymous usage statistics (app and website, with or without an account): To see how many people use Dancyra, we count visits anonymously. We store nothing on your device for this (no cookie, no identifier) and no IP address. From the IP address and the browser or app identifier (when you are signed in: from your account) we form a key that stays the same on the same day only. Its secret is made anew every day and deleted afterwards, so nobody can be recognised across days. Stored per day: app or browser and which device (phone, tablet, computer), operating system, browser, app version, language, approximate country and region (from the IP address, with our database on our own server), in which hours, how many pages, which page the visit started on and which website it came from, and whether someone was signed in. We also count per day how often each page was opened.
• Account: email address, display name, date of birth, password (stored only as a cryptographic hash, never in plain text), language, time of registration and whether your email address is confirmed. We need the date of birth only for the age limits (see section 11); nobody else sees it.
• Sign in with Apple or Google (optional): Apple or Google confirms who you are. We store the provider, the identifier it sends us for you and the email address it confirms. With Apple you can hide your address; we then receive a relay address from Apple. We never learn your password with the provider.
• Staying signed in in the app: the app keeps its access keys encrypted in the iOS keychain or the Android keystore. On our server we store only a check value from which the key cannot be recovered, and when it expires.
• Saved, going, following: which events you saved, where you said "I'm going" or "Interested", which organizers and people you follow and which you blocked or hid. On an event, others see only the number of people going, not who they are. For your news we also keep when you last opened it and which kinds of news you switched off. The news itself is put together from these and the events' changes when you open it.
• Use of your account: when you last signed in and last used Dancyra, on which days you used the app or the browser (the date only, not what you looked at), and from which country and region your last sign-in came. We derive country and region from the IP address with a database on our own server (DB-IP); the address does not leave the server for this and is not stored for it. Only the operator sees this, to narrow down errors and detect abuse.
• Public profile: Your display name, your username and your profile picture (if you upload one) are public at dancyra.com/u/<username>, together with the names of your organizer profiles and the events you added without a switched-on organizer profile. Search engines do not index pages without events. You can change your username and picture in your profile or remove the picture; when you delete your account we delete the picture at once.
• Organizers: if you create an organizer profile, its name, address (@name), description, website, contact email and links are public, as are the events you enter: title, venue, times, program, prices, descriptions, pictures, links and the line-up with the names of DJs, teachers and other people involved. Please only enter names of people who agree or who appear publicly for the event. We also store who manages a profile; that is not public.
• Pictures: uploaded pictures are scaled down and saved anew. Embedded metadata such as camera, time taken or GPS position is removed. In the app, only the picture you choose yourself is uploaded.
• Address search: when you search for a city or address, for example for "events within ... km" or when entering a venue, our server sends the search text to the address service Geoapify and, when Geoapify finds nothing or cannot be reached, to Photon (see section 5). Neither service learns your IP address. The search text is not stored in your account.
• Location (optional): if you use "Near me" on the website or "My location" in the app, your browser or phone asks for permission first. For the search the app only asks for your approximate location. The position (rounded to about 10 metres) is sent to us for the search only and is not stored in your account. The app remembers your last radius search on your device only.
• "I'm here" (optional): While an event is running, you can confirm on its page that you are there. Only when you tap it does your browser or phone ask for your precise location. The position and its accuracy are sent to us once. We check that you are no more than 500 metres from the venue and then keep only the result: that and when you checked in, the distance rounded to 10 metres and the accuracy. We do not store your coordinates. For now only you see the result; later it may serve as "Was there", for example so that only people who were there can rate an event. It is deleted with your account.
• "I'm here" at schools and shops (optional): In the same way you can confirm on the page of a dance school or shop that you are there, and then say whether it still exists. We check that you are no more than 250 metres away and keep only the result (when, the distance rounded to 10 metres, the accuracy) and your answer, never your coordinates. Answers only count together: if two people say the place no longer exists, we stop showing it in search and on the map for now and write to its owner. We show your name to nobody. Everything is deleted with your account.
• Confirming your phone number (optional): You can confirm your mobile number with a code we send you by WhatsApp, Telegram or SMS, whichever you choose. While the code is on its way (10 minutes at most) we keep the number to send it. After that we only keep an encrypted fingerprint of the number (a hash with a secret key), so that a number belongs to one account only, and the date of the confirmation. We do not keep the number itself. Others only see "Phone confirmed", never the number. Deleting your account removes the fingerprint too.
• Entering events, schools and shops for everybody: If you enter an event, a school or a shop you know of (for example with "Enter an event"), the entry is public with your display name as "Entered by", together with your few words about it and the dance styles you named. If you confirm an event that is already entered, we show you as one more person who entered it. We store what you entered, when, and whether we checked the entry; this tells how reliable your entries are. Only the operator sees this rating.
• Quick entry: If you send us a post with text and up to five pictures, we store the text and the pictures (scaled down, without metadata) with your account. They are not public: only the operator sees them, to read the event from them and enter it in your name, and to be able to see later what exactly was sent. When automatic reading is switched on, we send the text and pictures to Anthropic's Claude API to read them (see section 5); otherwise we read the posts ourselves. When the account is deleted, we delete the text and the pictures.
• Information from messenger groups: Dancyra is a member of some WhatsApp and Telegram groups and Telegram channels about dance events that we were invited to or that are open to the public. From posts in these groups we take information about dance events in order to list them and keep them up to date, for example changed dates, places or cancellations. For this we process the text and pictures of such posts, the name of the group and the time. We do not store the names, phone numbers or usernames of the people who wrote them. Only the event itself is published, never the post, its author or the group. To read text and pictures we use the same service provider as for "Quick entry" (Anthropic, see section 5).
• Friends: if you send someone a friend request, we store who sent it to whom, when and whether it was accepted; this also works with the QR code on your profile, which the app reads with your phone's camera (the camera image does not leave your device). Friends see which events you are going to or interested in, and can send you messages.
• Messages: if you write to someone, we store the conversation: the text, photos and events you send, the time, whether a message was read, and earlier versions when you edit a message. Photos are kept on our server. You can write to friends and - through a video's link - to the person who sent it. We do not read conversations; only when a conversation is reported do we look at the reported messages. Messages to someone who blocked you are not delivered. The push notification shows only the name, not the text.
• Pinboard: from 18 and with a confirmed e-mail address you can offer or look for a pass at an event, a partner for a couple pass or a place to sleep. We store what you enter (such as the kind of pass, role, price, nights, gender if you give it, a few words) and how you can be reached (WhatsApp, Telegram, Instagram, phone or e-mail). Only someone whose request you accept sees this contact, and the other way round. Entries end by themselves with the event or the deadline for name changes.
• Translating: if you have an event description translated, our server sends its text to a translation service (see section 5), without your name. We keep the translation so the same text is translated only once, and count who asks for translations: for an account the account, for guests only a short, irreversible key made from the IP address (never the address itself), to recognise misuse of the free amounts.
• Flight prices: for festivals and weekends we show an approximate flight price from your home city (from your profile) to the event. For this our server asks only for the two airports and the days, without anything about you. If you tap "Search flights", Aviasales' flight search opens through a Travelpayouts partner link; from then on their privacy policies apply.
• Sharing dance videos: sharing videos needs a confirmed phone number. If you send a video to friends or as a link, we store the video itself, its file name, size and length, a still from it (made by your phone or browser), whom you sent it to or that it has a link, the time and how far the upload is. Downloads are counted once per person. Whoever opens your link sees your name, the still and the length and can write to you through Dancyra; whoever writes to you that way appears as a contact for this video in your messages. We do not watch or analyse the videos.
• Reports: if you report an event, an organizer, a school, a shop or a person, we store what was reported, the reason, your text, the time, your account and how we handled the report. If we block an event or organizer profile, we store our decision with its ground, explanation and what prompted it.
• Emails: we only send emails that belong to your account: confirming your email address, links to reset your password, answers to your support requests, the receipt and the outcome of your reports and, when we block, hide or reject something you entered or run, our decision with reasons. We do not send newsletters or advertising.
• Push notifications (app, optional): If you allow the app to send you notifications, it gets an ID for your device from Firebase Cloud Messaging (Google); on iPhones delivery also runs through Apple's push service. We store this ID with your account and the platform (Android or iOS) while you are signed in to the app, so that we can send you notifications, currently for example when support has answered your request. Which notifications you get is set in the app under Settings; you can switch them off completely in your phone's settings.
• Error reports (app): if an error occurs in the app, it sends us the error message, the program state at that point, the app version, the platform (Android or iOS) and system version and, if you are signed in, the link to your account. If it cannot send the report right away, for example without network or because it crashed, it keeps it on your device and sends it at the next start. Errors on our server are recorded with the address and program state, without IP address.
• Technical data: when you use the website or app, the server processes IP address, time, requested address and browser or app identifier (server logs). To prevent abuse we briefly count how often an IP address or account tries to sign in, register or request emails.
• Cookies: the website only sets a technically necessary session cookie when you sign in or use a form. We use no cookies for statistics, advertising or tracking, and no analytics tools of other providers. Fonts are served from our own server.

3. Purposes and legal bases

4. How long we keep data

• Account, saved events, going, following, blocks: until you delete your account. When you delete it, we remove your name, email address, password, origin, the link with Apple or Google, the push notification ID and all sign-ins at once. For 30 days we keep only non-reversible check values of your email address and of your link with Apple or Google, and what hangs off your account without a name (saved, going, following, organizer profiles). That keeps your address reserved, and you can bring your account back: by signing in again with the same Apple or Google account during that time, or by naming your address to us. Then we delete everything automatically and for good.
• App access keys: at most 60 days after last use; immediately when you sign out or delete your account.
• Password reset link: valid for one hour and deleted after use. The email confirmation link is not stored; it is valid for three days.
• Organizer profiles and events: they are public content and remain until deleted. If you delete your account, write to us if your profiles and events should go as well.
• Reports: as long as needed to handle them and to recognise repeated violations.
• Abuse prevention counters: a few minutes up to one day.
• Backups: our nightly backups contain the data named above as well. They are kept on our server in the EU and deleted after 14 days; one backup per week stays 4 weeks, one per month 6 months. An encrypted copy of them is also kept by us in Germany (not reachable from the internet) and deleted after 200 days at the latest. Deleted data leaves the backups at the latest when these periods end.
• Push notification ID: until you sign out in the app or Firebase reports it as invalid, for example because the app was removed. If you delete your account, we delete it at once.
• Shared videos: we delete the video itself 48 hours after its upload is complete; in a browser it can only be downloaded in the first 24 hours, in the app until the end of the 48 hours. You can delete it yourself at any time before. Uploads given up are deleted after 24 hours. Independently, the storage itself deletes anything older than two days. The page behind the link (your name, the still, the length) stays for 90 days so recipients can still reach you; after that we delete the still too. The details of the sending (file name, to whom, when, how often downloaded) likewise stay in your "Sent" or "Received" list for 90 days; after that we delete everything about this video, including the possibility to write to you through its link.
• Friends and messages: a friendship until one of you ends it or deletes their account. A conversation until one of the two accounts is deleted; then it disappears for both. "Delete conversation" only removes it on your side. If you delete a message, it shows "Message deleted"; what it contained (text, photo, event) we keep hidden for 30 days only in case of a report, then we delete it. Earlier versions of edited messages likewise for 30 days. If a report is open, we wait until it has been handled.
• Pinboard: entries and requests until you delete them, the event is deleted or you delete your account; after they end nobody sees them any more.
• Translations: the translated texts as long as the description exists. We keep the count of requests for statistics; if you delete your account, it stays without any link to you.
• Error reports (app and server): 90 days, then deleted automatically.
• Phone number while confirming: only as long as the code is valid, 10 minutes at most; after that only the number's fingerprint and the date, until you delete your account.
• Server logs: at most 30 days, then deleted. The logs of our mail server (when an email went from which address to which, without its content) are kept for 90 days, so that delivery problems and abuse can be looked into.
• Posts from messenger groups: posts that are not about an event are deleted after 30 days at the latest. Posts that led to an entry are kept as a record as long as the entry exists.
• Anonymous usage statistics: once the day is over, the day's key can no longer be linked to anyone. We keep the anonymous figures to see how things develop over the years.

5. Recipients and services of other providers

• Hosting: website, app interface and database run on a server of Host Europe in a data centre in the EU, under a data processing agreement according to Art. 28 GDPR.
• Email: we send and receive our emails through our own mail server, also at Host Europe in the EU. No other email service is involved.
• Map tiles (OpenStreetMap): your browser or the app loads map images directly from servers of the OpenStreetMap Foundation (United Kingdom). Your IP address and the map sections shown are transmitted. The European Commission has issued an adequacy decision for the United Kingdom. Legal basis: Art. 6(1)(f) (legitimate interest in showing a map).
• Address search (Geoapify, KEPTAGO LTD, Paphos, Cyprus; data centres in the EU): when you search for a city or address, our server sends the search text to Geoapify, without your IP address and without reference to your account. By its own account Geoapify keeps such requests for 24 hours at most.
• Address search as a fallback (Photon, komoot GmbH, Germany): when Geoapify finds nothing or cannot be reached, our server sends the search text to Photon, likewise without your IP address and without reference to your account.
• Phone confirmation by WhatsApp (Meta Platforms Ireland Ltd., Ireland): For the code we send your mobile number and the code through the WhatsApp Business Platform to Meta, which delivers the message. Meta processes them for us as a processor; data may also go to Meta Platforms, Inc. in the USA, based on the EU-US Data Privacy Framework or standard contractual clauses. Legal basis: Art. 6(1)(a) (your consent when you ask for the code).
• Phone confirmation by Telegram (Telegram Messenger Inc., outside the EU): If you choose Telegram, we send your mobile number and the code through "Telegram Gateway" to Telegram, which delivers the code in your Telegram app. This only works if you use Telegram with that number; Telegram knows your number then anyway. Telegram is based outside the EU, in a country without an adequacy decision of the EU Commission; the transfer rests on your explicit consent (Art. 49(1)(a) GDPR) when you choose this way. Legal basis: Art. 6(1)(a).
• Phone confirmation by SMS (SMScarrier.eu, interactive digital media GmbH, Lübeck, Germany): If you choose SMS, we send your mobile number and the code to this provider, which delivers the code to you as a text message over the mobile networks. It processes the data on our behalf for this purpose only. Legal basis: Art. 6(1)(a) (consent when you ask for the code).
• Automatic reading (Claude API, Anthropic, PBC, USA): When it is switched on, our server sends the text and pictures of a quick-entry post to Anthropic to read the event details from them, without your name and without any link to your account. Anthropic processes them for us as a processor and does not use them to train its models. The transfer to the USA is based on the European Commission's standard contractual clauses. Legal basis: Art. 6(1)(b) GDPR.
• Translation (Google Cloud Translation, Google Ireland Limited, with processing also in the USA; DeepL SE, Cologne; Claude API, Anthropic, PBC, USA): for translating, the text of the event description goes to these services one after the other: first Google while its free amount lasts, then DeepL, Claude as the last resort. Only the text and the target language are sent, not your name or your account. The services process the text for us as processors and, under their terms, do not use it for training. Transfers to the USA are based by the providers on the EU-US Data Privacy Framework or the European Commission's standard contractual clauses. Claude also recognises the language of a description. Legal basis: Art. 6(1)(b).
• Flight prices (Travelpayouts): our server asks Travelpayouts only for the two airports and the travel days, without anything about you. Only when you tap "Search flights" does your browser or the app open Aviasales' flight search through a Travelpayouts partner link; from then on these providers' privacy policies apply.
• Storage for shared videos (Cloudflare R2, Cloudflare, Inc., USA): the videos themselves are not on our server but in Cloudflare's storage service R2, in a location under EU jurisdiction (the data stays in the EU). Your phone or browser uploads the video directly there, and recipients download it directly from there; Cloudflare sees the IP address of the device doing so. Cloudflare processes the data for us as a processor under Art. 28 GDPR. Where data goes to Cloudflare, Inc. in the USA, this is based on the EU-US Data Privacy Framework or the European Commission's standard contractual clauses. Legal basis: Art. 6(1)(b).
• Sign in with Apple (Apple Distribution International Limited, Ireland, and Apple Inc., USA) and Sign in with Google (Google Ireland Limited, with processing also in the USA): only if you use this sign-in. The provider checks your account and sends us the data named in section 2. Legal basis: Art. 6(1)(b). For transfers to the USA the providers rely on the EU-US Data Privacy Framework or the European Commission's standard contractual clauses.
• Push notifications (Firebase Cloud Messaging, Google Ireland Limited, with processing also in the USA; on iPhones also the Apple Push Notification service, Apple Inc.): only if you allow notifications. What is sent is your device's ID and the text of the notification, not your name or email address. For transfers to the USA the providers rely on the EU-US Data Privacy Framework or the European Commission's standard contractual clauses.
• Route: if you tap "Route" on an event, we open Google Maps or Apple Maps with the venue's coordinates. From then on the privacy terms of that provider apply.
• Organizers' links (ticket shops, Facebook, Instagram and others) open other websites. Their providers are responsible for how they process data.
• App Store and Google Play distribute the app. We do not pass any personal data to Apple or Google for this.

Beyond that we only pass on data if the law requires it, for example on the order of an authority.

6. Moderation

Organizers publish their events right away. We look at new events afterwards and review reports. We can hide, block or reject events, organizer profiles, schools, shops or community entries that are wrong or break the rules. Whoever reports something gets a receipt and later our decision. If we block, hide or reject something, we tell the person who entered or runs it by email what, why and what prompted it. These decisions are made by a person on our team, not by a program. Every one of these emails can be answered, and we then look at the decision again. We keep such answers together with ours in the case, as long as the report itself.

7. Security

• All connections between browser or app and server are encrypted (HTTPS).
• Passwords, access keys and password reset links are stored only as hashes.

8. Your rights

Under the GDPR you have the right to:

• access to your data (Art. 15)
• rectification of incorrect data (Art. 16)
• erasure (Art. 17)
• restriction of processing (Art. 18)
• data portability (Art. 20)
• object to processing based on legitimate interests (Art. 21)
• withdraw consent with effect for the future (Art. 7(3)), for example for location in your browser or phone settings

An informal email to hallo [at] dancyra.com is enough. You can delete your account yourself at any time: in the app under Settings or on the web at https://dancyra.com/it/delete-account.

9. Right to lodge a complaint

You have the right to complain to a data protection supervisory authority. The authority responsible for us is:

10. Automated decisions

There is no automated decision-making, including profiling, within the meaning of Art. 22 GDPR.

11. Minimum age

You can create a Dancyra account from the age of 16. Features where you get in touch with other members, for example messages or requests such as shared accommodation for a festival, are only available from 18, once they exist. That is why we ask for your date of birth when you sign up, also with Apple or Google, so both limits apply exactly from the birthday. Without an account, as a guest, we ask nothing. We do not knowingly process data of younger people and delete an account as soon as we learn that it belongs to someone under 16.

12. Changes

We update this policy when Dancyra or the law changes. The current version is always at https://dancyra.com/it/privacy.