The danceworkout.ai app
Privacy policy
Version 2026-11-16.draft, from .
This is a draft, and it may change before the app is released.
The short version
- Your health answers and your workout history stay on your phone, encrypted. We don't send them to our server.
- Videos you choose to film stay on your phone too. The app never uploads them.
- Our server keeps your account, which versions of our terms and consent you accepted, and, if you join a squad, what your squad needs.
- If a friend invited you, our server keeps who did. The friend who invited you sees only that you joined and your first name.
- Unless you turn it off in Settings, the app sends our server a few usage counts, such as "started Day 1" or "finished Day 7". We look only at totals, to see whether the app helps people keep dancing.
- Our server keeps when your free days started and run out, and, if you subscribe, what the payment service tells us about your plan. Never your card details.
- No ads. No advertising, analytics or tracking tools from other companies. We never sell your data.
- You can delete your account in the app at any time: in Settings, or in Legal and privacy while you are still setting up.
This policy is for the danceworkout.ai app. Our website has its own privacy policy. Health data has its own policy too: the health-data privacy policy.
On your phone
These stay on your phone. They are not sent to us, except the usage counts described under "Usage counts" below (that you started or finished a workout, with its program day), unless you turn them off. Your setup answers and your workout history are encrypted, with a key kept in your phone’s secure storage (the Keychain on iPhone, the Keystore on Android). The key never leaves the phone.
Your answers and settings, from setting up and later in the app:
- Your age, and the day you told us (it sets your heart-rate zones).
- Your goals, such as a stronger core or losing weight.
- How active you are now.
- Whether you have danced before.
- Your yes or no answers to the seven safety questions (heart, chest pain, dizziness, bones and joints, medicine, pregnancy or a recent birth, any other reason).
- Your body notes: knees, back, hips, ankles, no jumping, pregnant, or a birth in the last year.
- Whether you dance in a small space.
- Whether you want quiet mode (no jumps, for neighbors below).
- How long you want each workout to be.
- The time of day for your reminder, if you chose one.
- The habit your reminder follows, if you chose one.
- Your camera setting: off, or on (filming the dances you choose).
- Whether you want daily reminders.
- Your account id, so nobody else signed in on the phone can read your answers.
- The setup screen you reached.
- Which version of the terms you accepted, and the day.
- Which version of the health-data consent you gave, and the day.
- The day you finished setting up.
- That setup stopped because you said you are under 18.
From your workouts:
- The day you danced.
- Whether it was a program day or a comeback.
- Which program day it was.
- The level it used (low impact, standard or high).
- How long it was meant to be.
- Whether you finished it.
- How it felt, if you said.
- A camera score (empty: the camera is not built yet).
- A heart-rate note from a watch (empty: watches are not connected yet).
- Any move you said hurt.
- Any move you skipped, so a move you skip twice can be swapped out.
- Any move you swapped before a workout and the move you picked, so your next workouts can use your pick where it fits.
- Which dance moves it used, so Day 30 can repeat Day 1.
- How many seconds you danced.
- Whether you pressed "Stop if it hurts".
- The moment you started it.
- Your time zone then (for your streak, when you travel).
- Your level, when the app changed it or you chose a level-up.
- The fun facts you have heard each time through a program, so none repeats in it.
- The moves you have danced.
- Your player switches (cues, voice, music, mirror) and your music and voice balance.
- That you said you have checked with your doctor or midwife, when your answers asked you to.
- The programs you have danced: which program, the day you started it, whether it is in progress, paused, done or stopped, and the milestone days you have seen celebrated in it.
- A list of the videos you film, if you choose to: which day each one shows, its date, length and size, and which beats of the dance are where in it (so your Day 1 and Day 30 can be lined up).
Also on your phone:
- Your sign-in session, encrypted, so you stay signed in.
- Your reminders, held by your phone’s own notification system: they never mention health or the days you danced. The ones about your free days come even with daily reminders off.
- A milestone card picture (yours, or your squad’s), as a plain picture file, while you are looking at it. It is deleted when you leave that screen (the Squad tab, for a squad card) or sign out. If the app closes suddenly first, it can stay in the app’s cache until your phone clears it.
- While your side-by-side video is being made: the two pictures drawn over it (your numbers card and the frame), as plain picture files in the app’s cache. They are deleted as soon as the video is made or stopped; one left by a crash is deleted the next time the app starts.
- If you sign in with Google: Google’s sign-in library keeps your Google email, name and photo address in the app’s own storage until you sign out.
- Your "Share usage counts" setting, and, while it is on, up to 50 usage counts waiting to be sent (for example while you are offline), with your account id. They are kept encrypted in the app’s own folder, with a key in your phone’s secure storage, and are sent as soon as the app can reach our server. They are erased when you sign out, turn the setting off, take back your health-data consent, or delete the app.
Videos, only if you film:
- Only if you turn on "Film today" before you start, on any day you choose: your dance, filmed by the front camera. The app never uses the microphone, so no sound is recorded. Afterwards, the phone adds the workout’s own music to the video.
- For each time you dance a program, the phone keeps your Day 1 dance (or a starting point on a later day), your Day 30 dance and the side-by-side video the app makes from them. It also keeps your latest dance; a newer latest video replaces the one before.
- Only the dance part is filmed, with a few seconds either side. Filming stops whenever you pause, leave the app, or press "Stop if it hurts".
- They are video files in the app’s own folder on this phone. The app never uploads them, and they are left out of iCloud, computer and Google backups and of phone-to-phone transfers.
- The app doesn’t encrypt them itself. Your phone’s lock and its own storage encryption protect them.
- A video is shared only if you tap Share and pick an app in your phone’s share sheet.
- You can delete any of them in My videos. Signing out, deleting your account, or taking back your health-data consent deletes them all from this phone.
- If "Stop if it hurts" is pressed, or a video catches too little of the dance, it is deleted. So is a file the camera fails to finish. A half-finished file left by a crash is deleted the next time the app starts.
Signing out erases your answers, your workout history and your videos from this phone. If you sign in again, you'll set up again.
On Android, the app turns off Android's cloud backup and phone-to-phone transfer for all its files. On iPhone, your videos are left out of backups. Your phone's own backup (to iCloud or a computer) may include your answers and workout history. They stay encrypted, and the key can't leave the phone, so the copy can't be opened on another phone. If you restore a backup onto the same iPhone, they may come back.
On our server
Our server keeps only what is listed here.
Your account:
- Your email address (with Apple’s "Hide my email", Apple’s relay address).
- If you sign in with Apple or Google: their id for your account, and whether Google checked your email.
- The time of each sign-in.
- For each signed-in phone: its internet address (IP address) and the short text its requests send to say what app and system they come from.
- A sign-in log with your email and your internet address, kept for 30 days.
- One-time sign-in codes and sign-in requests that are still waiting, until they are used or expire.
- Your account id.
- A display name (empty: nothing in the app sets it yet).
- When you joined.
- When that record last changed.
What you agreed to:
- Which version of the terms and health notice you accepted.
- When you accepted them.
- Which version of the health-data consent you gave (not your answers).
- When you gave it.
Only if you start or join a squad:
- Your squad’s id.
- Your squad’s weekly goal.
- When the squad started.
- Which squad you are in.
- Your account id, as a member.
- The name you show your squad.
- When you joined the squad.
- Who invited you (for a future reward; the app can’t read it).
- The invite codes you make.
- Which squad an invite is for.
- Who made the invite.
- When it was made.
- When it expires.
- Whose danced day it is.
- The plain dates you danced, while you are in a squad (no time, no workout details).
- A "let’s go" nudge’s id.
- Which squad it was sent in.
- Who sent it.
- Who it was for.
- The day it was sent.
- When it was sent.
- When it was seen (the sender can’t read this).
- A cheer’s id (a one-tap cheer for a friend who danced today).
- Which squad the cheer was sent in.
- Who cheered.
- Who was cheered.
- The day the cheer was sent.
- When the cheer was sent.
- When the cheer was seen (the sender can’t read this).
- When the friend you cheered thanked you for it (your thanks reach the friend who cheered you).
- When the thanks was seen (the friend who thanked can’t read this).
Only if you report or block someone in a squad, or someone reports or blocks you:
- Who made a block.
- Who was blocked (only the person who blocked can see it; the person blocked is never told).
- When the block was made.
- A report’s number.
- Who sent a report (never shown to the person reported).
- Who the report is about.
- The squad it is about.
- The name the reported person showed that squad at the time.
- The reason, picked from a short list.
- The note written with the report, if any.
- When the report was sent.
- When we dealt with it.
- What we did: nothing, took the person out of the squad, or stopped their account from signing in.
Invites: your own invite codes (your invite link’s, made the first time you share or view it, and your squad link’s, made the first time you invite a friend to your squad), and, only if a friend invited you, who did:
- Your invite codes, for your invite link and your squad link: random letters and numbers.
- Whose code it is.
- The kind of code: personal, or a class or community code for a Captain.
- Whether the code came from our website’s waitlist.
- Whether the code is your squad link, which adds friends to your squad, or your invite link, which never does.
- When the code was made.
- Who was invited.
- The code that brought you, which shows who invited you.
- How you came: a link you opened, a code you typed, or our website’s waitlist.
- When your invite was saved.
Also kept in a part of our database the app can’t read:
- A short memory of your squad actions and their times (starting, inviting, joining, changing the goal, reporting, blocking, sending usage counts), to stop abuse. Kept 2 days.
- Who sent a "let’s go" to whom, and the day, so one friend can’t be nudged twice a day. Kept about 3 days, even if you leave the squad.
- When you leave a squad: which squad, when you had joined it and when you left, so that week and the week before keep the goal they began with. Nothing else. Kept about two weeks, even if you leave the squad.
- Only if we remove you from a squad after a report: which squad and when, so no link can add you to it again. Kept while that squad exists, until you delete your account.
- Who cheered whom, and the day, so one friend can’t be cheered twice a day. Kept about 3 days, even if you leave the squad.
- Your squad’s weeks, for the squad streak: whether each week reached its goal, and the goal a week began with when it was changed that week. Nothing about any one person. Kept while part of the current streak, and deleted with the squad.
- Only if you joined our website’s waitlist: a one-way scrambled form of your email (a SHA-256 hash, not the email itself), your website invite code, the code that invited you, and whether you were one of the first 500. So your website invite and early-bird price carry over to the app. Kept a year after we copy it at launch.
- Your usage counts (listed under "Usage counts" below): your account id, which moment it was, the program day where there is one, and the day it reached our server (no time). Kept 13 months.
- Your free days: when they started (once you were set up) and which rule applies (the free January, a trial, or the rest of an earlier one). Also when a friend first started through your link during your first 7 days, and whether you were one of the first 500 on our waitlist (your early-bird price). Deleted with your account.
- One free period per person: a keyed scramble of your email and the date your free days run out. The scramble uses a secret key kept in our database, so without that key nobody can check a guessed email against it. Kept 12 months after that date, even if you delete your account, so free days can’t be had twice by deleting and coming back.
- The secret key for that scramble. It says nothing about anyone.
- If you subscribe: what the payment service tells us about your subscription (which service, its id there, your plan, its status, when the current period runs out, and when you first paid). For our website, also whether you started from the iPhone or the Android app. Never your card or bank details: the payment service keeps those. Deleted with your account.
- Free months you earned when a friend you invited first paid: which friend’s payment earned it, when, and whether it was used or taken back (if that payment was refunded). Deleted with your account; if you are the friend, your account id is removed from it.
- Only if we gave you free access by hand (a Founding Dancer, a Captain, or a short free period we gave you through support): why, and until when. Deleted with your account.
- Only when you open our website to subscribe or manage your plan from the app: a scrambled form of a 30-minute link (never the link itself), which plan you picked, whether the phone is an iPhone or an Android phone, and the address and id of the payment page it opened. Deleted within 2 days, or with your account.
- Only if you subscribe on our website: your customer id at Stripe, our payment service, so you can manage your plan there. Deleted with your account.
- If you subscribe: for each payment, the payment service’s id for it, when it was paid, whether it was your first, and whether it was refunded. Never the amount, your card or bank details. Deleted with your account.
- The ids of the messages the payment services sent us (Stripe and RevenueCat), and their kind, so none is counted twice. Nothing about you in them. Kept 90 days.
- Only if you subscribe on our website: which reminder emails we sent you (before a first charge or a yearly renewal) and for which date, so each goes once. Deleted with your account.
- Switches for the whole service: whether paid plans are open (and when that last changed), and whether test builds may pretend to subscribe. Nothing about anyone.
- Only if you delete your account while subscribed on our website: Stripe’s id for that subscription, until we have canceled it (within the hour). Nothing else about you.
- The Captain program’s terms for the whole service (the 30% share, the 60-day hold, the $25 minimum and the payment fee rates). Nothing about anyone.
- Only if you are a Captain: your Captain status, when you started, when your Captain year started and ends, whether we keep you on at its end, and when we emailed you your Captain welcome (so it goes once each time you become a Captain). Deleted with your account.
- Only if you are a Captain: each change of your Captain status, and when it took effect. Deleted with your account.
- Only if you joined through a Captain’s link and pay, or you are a Captain: for each payment, what was paid, its sales tax and payment fee, and the Captain’s 30% of it, with both account ids; the same for a refund. The Captain sees only counts and totals, never who paid. Account ids are removed when an account is deleted; the amounts are kept up to 7 years for the books.
- Only if you are a Captain: each payout to you (the amount, the date, PayPal or Wise, and the transfer’s id). Never a tax id or bank details. Your account id is removed if you delete your account; the record is kept up to 7 years for the books.
- When payouts to Captains were made, and the minimum used. Nothing about anyone.
- Only if you are a Captain: which monthly statements we emailed you, so each goes once. Kept 2 years, or until you delete your account.
- Only if you joined through a Captain’s link and pay: your first payment’s id at the payment service, when it was made and what it charged, whether it was refunded in full, and both account ids. It counts once towards that Captain’s new paying people in her Captain year; she sees only counts, never who. Your account id is removed if you delete your account; if the Captain deletes hers, the record goes.
- Only if you are a Captain: which Captain year emails we sent you (the reminder 30 days before your Captain year ends, the renewal, or the end), so each goes once. Kept 2 years, or until you delete your account.
- Only if you test the app before launch, or for the one account Apple’s and Google’s app reviewers use: your account id, whether it is a tester or that review account, when it was added and when it runs out (a week after launch, or 24 hours when added later), so the workouts open early. For the review account only, also until when it sees paid plans (30 days after each review sign-in). We look your email up in our sign-in records when we add you; it is not copied here. Deleted when it runs out, or with your account.
- The times of sign-in tries to the one account Apple’s and Google’s app reviewers use, and whether each worked, to stop guessing. Nothing about anyone. Kept 7 days.
- The oldest app version allowed on iPhone and on Android, so an app too old to work as it should asks you to update. Nothing about anyone.
We don't keep your health answers, how a workout felt or what hurt on our server.
Usage counts
To see whether the app works (for example, how many people who start Day 1 are still dancing on Day 7, or whether squads help), the app counts a few moments and sends them to our server. Each count is one of these:
- You started a workout, with its program day (for example Day 7).
- A workout reached its end, with its program day.
- You shared your Day 30 video: yes only, never the video, the app or the people.
- You shared your invite link: never with whom.
- The paid-plan screen was shown, with your program day (once paid plans start).
- You started a free trial (once paid plans start; recorded by our server, not the app).
- A free trial became a paid plan (once paid plans start; recorded by our server, not the app).
With each count our server keeps your account id and the day it arrived (no time of day). Never your name, email, health answers, how a workout felt, minutes, scores or videos. Squads and invites are counted from what our server already keeps for them (listed above), not sent again.
Why your account id: so we can tell one person's Day 1 from her Day 7. We look only at totals, such as "40 of 100 people reached Day 7". Nobody in the app can see your counts, not even you, and they go to no other company. They are deleted after 13 months, or at once when you delete your account.
To stop them: Settings, then Camera and privacy, turn off "Share usage counts". From then on this phone sends none, and it erases any it was still waiting to send. The app works the same either way. The setting stays off on this phone if you sign out and back in. Counts already sent stay until they are deleted as above; write to us if you want them deleted sooner.
Who can see what
Our database locks every table, so each person can read only her own records, and squad records only inside her own squad.
If you join a squad, the people in it can see:
- The name you choose for the squad.
- When you joined the squad.
- Your account id (a long random code that says nothing about you).
- Which squad you are in (theirs).
- The squad’s id.
- The squad’s weekly goal, which any member can change.
- When the squad started.
- Your account id, next to your two numbers below.
- Whether you danced today: yes or not yet.
- How many days you danced this week (from the day you joined).
- Whether you are a Captain, shown as the Captain badge by your name (only while you are one).
- The goal your squad’s week began with (a change counts from the next Monday).
- How many dances your squad needs this week (fixed each Monday from who was in the squad then).
- The squad streak: how many weeks in a row your squad reached its goal.
- Whether your squad reached this week’s goal.
- That you sent them a "let’s go", when you do.
- That you cheered them, when you do (any cheer you send).
- That you thanked them for their cheer, when you tap Thanks.
They can't see your email, your health answers, your workouts, your minutes, or how a workout felt. They see only today's yes or not yet, so a friend who looks every day can tell which days you danced. They never see times or workout details.
Reports and blocks are private. Nobody in the app can read a report, not even the person who sent it. If you are reported, you are never told who reported you. In the app, only you can see whom you blocked, and they are never told.
The people who run danceworkout.ai read reports only to keep squads safe. A report keeps the name the reported person showed their squad at the time, so we can see what was reported even after they leave.
If you invite friends, or a friend invites you:
- To the friend who invited you: that you joined through her link, as part of a count.
- To the friend who invited you: the first word of the name you show a squad, once you are in one.
- To a friend you invited: whether you are in a squad, and whether it has room for her.
- To a friend you invited: the first word of the name you show your squad, while it has room for her.
- To a friend who uses your code: whether your squad has room for her.
- To anyone who opens your squad link or types its code: whether you are in a squad, and whether it has room for her (your invite link says nothing about your squad).
- To anyone who opens your squad link or types its code: the first word of the name you show your squad, while it has room for her.
- To the friend who invited you, once paid plans start: that you paid for the first time, as a free month she earned (never your plan or price).
- To the friend who invited you, the same way if she wasn’t paying then: a free month waiting for her.
- To a Captain whose link you joined: that you joined, as part of a count.
- To that Captain, in the app and in her monthly statement, only once at least 5 people she brought are paying: whether you pay, as part of that count.
- To that Captain, only then too: her 30% of what you paid last month, inside her monthly total (never who paid what).
- To that Captain, in the app, in her monthly statement and in her yearly reminder, only once at least 5 people she brought made their first payment in her Captain year: that you made yours then, as part of that count.
Nobody sees your email through an invite, and the friend who invited you sees nothing about your workouts or answers. Your invite link is a random code: someone who opens it learns nothing about you or your squad, and it never adds anyone to your squad. Your squad link, which only Invite a friend sends, is different: someone who opens it sees your first name and whether your squad has room, and can join while there is room. A block in a squad, whoever made it, also stops either of you joining a squad the other is in, by any link or code, without saying why. So does being removed from a squad after a report.
Our website’s waitlist and the app
If you joined our website’s waitlist, your website invite carries over to the app. At launch we copy the waitlist to our server as a one-way scrambled form of each email (a SHA-256 hash), never the email itself, with each person’s website invite code and the code that invited them. When you reach "Your 30 days", the last step of setting up the app, and later when the app starts or you use Invite friends, our server scrambles the email you signed in with in the same way. If it matches, your website code becomes your code in the app (so friends who used your website link still count), and the invite that brought you to the website is saved. Nothing about this is sent from your phone.
A hash can be matched by someone who already knows an email, so we handle it as personal data: it sits in a part of our database the app can’t read, and we delete it a year after we copy it. If you signed in with Apple’s "Hide my email", it won’t match; you can type your friend’s code instead.
When you share an invite or a milestone card, you choose the app and the people. A milestone card shows the day, your floor of danced days, your minutes and your streak. Today it doesn't show calories, heart rate or your body.
At 4, 8 and 12 weeks of your squad streak, then every 4 weeks, the Squad tab offers a squad milestone card. It shows your first name (from the name your squad sees), the squad streak in weeks, and how many friends are in your squad, never their names. It is drawn on your phone and is shared only if you tap Share and pick an app.
Your side-by-side video shows your two dances, the days, your minutes and your streak. It shows no calories and no heart rate. It is shared only if you tap Share and pick an app.
The people who run danceworkout.ai can see what is on our server when they need to, for example to fix a problem or answer your request.
Services we use
- Supabase runs our database and sign-in. It stores what is listed above under "On our server", in the United States (East US).
- Resend sends our emails: the sign-in emails for Supabase, payment reminders if you pay on our website, and, if you are a Captain, your Captain welcome, monthly statements and Captain year emails. It gets your email address and the email itself.
- Apple only if you sign in with Apple. Apple tells us your id and email (or its relay address). When you delete your account, we ask Apple to disconnect Sign in with Apple, with a one-time code from Apple; we keep nothing it sends back.
- Google only if you sign in with Google. Google tells us your id, email, name and photo address; our database drops the name and photo address.
- Stripe only if you subscribe on our website: our payment service. It gets what you type on its payment page (your email, card or wallet, billing postal code) and your account id from us, never your health answers. It works out sales tax and tells us your plan’s status. It keeps payment records the law asks for. If you delete your account, we cancel your subscription there.
- RevenueCat only if you subscribe through Apple or Google Play: it checks those purchases for us. It gets your account id from us (never your email or health answers) and what the store reports about your plan, and tells us your plan’s status.
What we don't do
- No ads in the app.
- No advertising, analytics, tracking or crash-reporting tools from other companies in the app. Our own usage counts (above) stay on our server.
- We don't sell or rent your data. We never share health data with advertisers.
- No AI service sees your data. Your plan is worked out on your phone.
- The app doesn't ask for your location, contacts, photos or microphone.
- It asks for the camera only when you choose to film your dance.
- No push messages from our server. Your reminders are scheduled on your phone.
- Invite links use no advertising or tracking tools. We know who invited you only from the code you used, or from your website waitlist entry.
If you allow it in your phone’s settings, Apple or Google may share basic crash reports about the app with us. The app adds nothing to them.
How long we keep things
- Your account and the record of what you agreed to: until you delete your account.
- The dates you danced, for your squad: up to 10 days.
- "Let’s go" nudges: 7 days.
- Cheers: 7 days.
- Squad codes from older versions of the app (the app now uses your personal link instead): they work for 7 days, and are deleted 1 day after that.
- Your squad’s record of which weeks reached their goal, for the squad streak: while those weeks are part of the current streak. It goes with the squad when the squad ends.
- The sign-in log: 30 days.
- Reports: until we have dealt with them, then 90 days, so we can notice if the same person is reported again.
- Your invite code, and the record of who invited you: until you delete your account.
- Usage counts: 13 months.
- The waitlist match: 365 days after we copy it at launch.
- Your free days, subscriptions, free months and any free access we gave you: until you delete your account.
- The one-free-period record (a keyed scramble of your email and a date): 12 months after your free days run out, even if you delete your account.
- Blocks: until the person who blocked unblocks, or either account is deleted.
- If we stop an account from signing in because it broke our squad rules, its data stays until the person writes to us to delete it.
- The record of a signed-in phone (with its internet address): until you sign out while online, or delete your account.
- Supabase also keeps short technical logs of requests, such as internet addresses. They delete them on their own schedule.
Deleting your account
Tap Delete my account in Settings, or in Legal and privacy while you are still setting up. At once, this deletes your account, the record of what you agreed to, your squad name, danced dates, invites, nudges and cheers, the short squad memories above, and any sign-in code or request still waiting. It also deletes the blocks you made, any block on you, the reports you sent and any report about you, your invite codes, the record of who invited you, your waitlist match and your usage counts. It deletes your free days, subscriptions and free months too. Friends you invited keep only the fact that they were invited, with nothing about you; a free month your payment earned a friend stays hers, without your account id. The one-free-period record stays for the time above, so deleting an account doesn’t give a second free period. Your lines in the sign-in log go within a day.
It also signs you out and erases your data from this phone, including your videos. If you used Google to sign in, it also takes away the app’s access to your Google account. If you used Apple on an iPhone, you confirm with Apple first, and we ask Apple to disconnect Sign in with Apple. If that doesn’t work, your account is still deleted, and the app tells you how to disconnect it yourself. It can’t be undone.
Leaving a squad removes your name, your danced dates, your invites, your nudges and your cheers from it. The short records of who nudged or cheered whom, and that you left, stay only for the short times listed above. Blocks and reports stay as described above.
Our website’s waitlist is a separate list. To be removed from it, write to privacy@danceworkout.ai.
Your rights
You can ask for a copy of what our server holds about you, ask us to correct it, or ask us to delete it. Write to privacy@danceworkout.ai. We'll answer within 45 days.
Some states give you these rights by law, such as California and Washington. We give them to everyone, wherever you live.
We don't sell or share personal data for advertising, so there is nothing to opt out of.
If you live in the EU, EEA, Switzerland, the UK or Brazil
Devender Bohra is the controller of your personal data: the one who decides how it is used.
Why we may use it (the legal basis):
- To give you the app you signed up for: your account, squads, invites and any plan you pay for.
- Health data (your answers, and the workout counts and squad days that leave your phone): only with your explicit consent, which you give on "Your health answers" and can take back at any time.
- Our legitimate interests: keeping squads safe, and giving one free period per person.
- Where the law requires it, such as payment records.
The app chooses your plan with simple rules on your phone. No decision with legal or similarly serious effects on you is made automatically.
You can also ask for your data in a form you can take elsewhere, ask us to limit how we use it, and object to what we do for our legitimate interests. We answer within one month (up to two months more for a hard request, and we tell you if so). In Brazil, we send a full copy within 15 days.
You can complain to the data protection authority where you live (in Brazil, the ANPD).
Our server and most of the services we use are in the United States, so your data goes there to run the app. We are putting the European Commission's standard contractual clauses (and the UK's and Switzerland's versions) in place with each of those services. Write to privacy@danceworkout.ai and we'll tell you where that stands.
Not decided yet: Our representative in the EU and the UK (GDPR Article 27), if we need one, and how to reach them.
Age
The app is for adults, 18 and over. If you tell the app you are under 18, setup stops. The app erases your answers, your workout notes and your videos from the phone, and keeps only that setup stopped. Our server erases your squad, the days you danced, your own invite codes, your usage counts and which versions of our terms and consent you accepted. It keeps who invited you, because that counts toward your friend’s rewards, and the short record of recent squad actions for its few days. Your account itself stays until you delete it; that screen offers Delete my account.
Security
You sign in with an email link or code, or with Apple or Google. We never store passwords. The app talks to our server over an encrypted connection.
We work to keep your data safe, but no system is completely secure. If someone gets into your personal data on our server, we'll tell you as the law requires.
Our server is in the United States. If you live somewhere else, what it keeps about you is kept there.
Changes
If we change this policy, the version at the top changes. If a change affects your health data, we change the health-data policy too, and the app asks for your consent again first.
Contact
danceworkout.ai is run by Devender Bohra.
Privacy requests: privacy@danceworkout.ai
Anything else: support@danceworkout.ai