StepFlow
Log in

Legal

Privacy Policy

What we collect, why, who sees it and how long we keep it — for the platform, the app and DanceInfo.

Last updated 20 September 2026 Draft 0.4

1. Who is responsible

[legal entity], Dubai, UAE, is the controller of personal data processed through DanceInfo. We process personal data under the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021, supervised by the UAE Data Office) and, for people in the EU, EEA and UK, the GDPR and UK GDPR — see the GDPR page for those rights. If the operating company is registered in the DIFC or ADGM free zone, that zone’s own data protection law applies in place of the federal PDPL; this page will name the law that applies once the brand decision fixes the entity.

A school using DanceInfo is a separate controller for the member data it holds about you; DanceInfo processes that data on the school’s instructions under a data processing agreement.

2. What we collect

Only what the Service needs to work.

  • Account: name, email, phone number, preferred language, dance role (leader / follower) and styles.
  • Bookings and attendance: courses booked, check-ins, waitlist positions, passes and credits.
  • Payments: amount, date, school or organizer, and paid / pending status recorded by the school. Payments are made through the school’s own payment link, so we never see or store card numbers.
  • Device and usage: app version, device type, crash reports and the pages you use, so we can keep the Service working.
  • Communication preferences: whether you want WhatsApp, email or push reminders.
  • DanceInfo visitors need no account. We collect aggregated, non-identifying analytics only, and only if you accept analytics cookies.
  • DanceInfo reports: if you report a listing, the description you write and — only if you add them — your email address and a screenshot or PDF. Reports can be read only by the platform team.

3. Where it comes from

From you, when you create an account or book; from your school, when it adds you to a roster or imports its member list; and, for DanceInfo, from organizers’ public channels — which contain organizer details, not attendee details.

4. Why we use it

To run bookings, passes and attendance; to move waitlists; to send the reminders you chose; to email receipts; to keep accounts secure; to improve the Service; and to meet legal obligations such as keeping payment records.

We do not sell personal data and we do not use it for third-party advertising.

5. Who sees it

Your school sees your bookings, passes and attendance with that school only. An instructor sees the roster and attendance for the sessions they teach — nothing else. Organizers see nothing about you unless you book their event through DanceInfo.

Service providers process data for us under contract: payment processing, cloud hosting and storage, messaging (WhatsApp, email, push) and crash reporting. Media is served through signed, short-expiry URLs.

6. How long we keep it

Account data for as long as your account is open and up to 24 months after, unless you ask us to delete it sooner. Payment records for five years, as UAE tax law requires. Attendance history stays with the school as part of its records. DanceInfo listings are public by nature and kept as an archive of the scene. Reports about a listing are kept until the listing is fixed and for 12 months after, then deleted with any attachment. Your cookie choice is remembered for 12 months.

7. Your rights

You can access, correct, export or delete your data, and object to or restrict certain processing. Contact DanceInfo support to make a request. We answer within 30 days (one month under the GDPR) and may ask you to confirm your identity. You may also complain to the UAE Data Office or, in the EU, EEA or UK, to your local supervisory authority.

Email DanceInfo support about a privacy request

8. Security

Data is encrypted in transit and at rest. Access is role-based and enforced in the database itself, so an instructor cannot query member records even by mistake. Media URLs are signed and expire. We review access regularly and notify affected people and the regulator of a breach as the law requires — within 72 hours of becoming aware under the GDPR.

9. Children

The Service is not for children under 16 to use alone. A parent or guardian may book for a child from their own account; the child’s data is then held under the guardian’s account.

10. Community posts

When you take part in an event’s community space — polls, song requests, questions or ideas — your post and your display name are visible to the organizer and to other people going to that event. Organizers can moderate their space. You can delete your own posts at any time.

11. Emails from schools and organizers

Schools and organizers that use DanceReach can send you emails about their courses and events. They are the controller for those emails; DanceInfo sends them on their behalf. Every marketing email has an unsubscribe link, and you can manage email preferences in your account.

12. International transfers

Data is hosted in the UAE or in regions with equivalent safeguards. Where a provider is elsewhere, we rely on contractual safeguards recognised under the PDPL and, where relevant, the GDPR.

13. Changes and contact

We announce material changes in the app and by email before they take effect. Privacy questions: privacy@[domain pending]. Post: [registered office, Dubai, UAE].

Related