Privacy
What stepwise keeps, where it lives, and how it goes away. There are no accounts: we never ask for your name or email address.
When you add a clip, we store
- The video you uploaded, or the video we fetched from the link you pasted.
- What we build from it: a 3D body for each dancer, sized to their estimated limb lengths (the body's surface is a standard shape, not theirs), and the lesson data the viewer plays — timings, poses, hand and foot close-up areas, and counts proposed from the music.
- Processing records: how the job went and how long each step took.
- A fingerprint of the video (a checksum and small frame hashes) and, for a pasted link, which post it came from. This is how the same video added twice becomes one lesson, and how a shorter cut of the same dance gets the same counts.
- For a pasted link, the post's public credits: the poster's @handle, and any choreographer @handles and song named in its caption or sound. We keep those names, not the caption.
- When the lesson was last opened.
One lesson per video
- If a video is recognised as one that is already a lesson, whoever adds it gets that same lesson and link. So there is one copy, and removing it removes it for everyone who has the link.
Kept only in your browser
- My lessons (with a small picture from each video's first frame), the counts and parts you set, and whether a lesson has already done its opening turn. These are stored by your browser on this device and are never sent to us (the usage notes below carry a loop's length and start and how far count 1 moved, not your saved counts and parts). Clearing this site's data in your browser deletes them.
- If a lesson is removed, its entry leaves My lessons the next time its link is opened on this device.
No accounts, and how limits work
- To stop one person using up the day's processing, each new lesson and each removal is counted against a keyed hash of your IP address. The key is random, is used for one day and is then deleted, so one day's counts cannot be matched to the next, even by us. The address itself is not written to our database, and these counts are kept after a lesson is deleted.
- The site runs on Cloudflare, processing runs on Modal, files are stored on Modal and Cloudflare, and our database runs on Neon. Fonts load from Google Fonts and Fontshare. Like any web host, these services see your requests, including your IP address.
Usage counts
- To learn which parts of stepwise help people practise, the lesson page sends us a short note when you open a lesson, for every 30 seconds of playing, and when you make a loop (its length, where it starts and how you made it), change the speed, Build up, the click or a view, correct count 1, pick a dancer, or copy a link. Each note has the control, its setting and the lesson's id. Nothing you type, no mouse movements, no screen recordings, nothing from the video.
- When you open a lesson we note which website sent you there: its name only, not the page.
- On our side we count each clip added (how long it is, file or link) and how each job ended: finished or which error, how many retries, how long it took, and how many dancers.
- Nothing is stored in your browser for this. We group the notes by a keyed hash of your IP address and browser name. The key is random, is used for one day and is then deleted, so we can count visitors each day but cannot link one day to the next. The address itself is not saved.
- If your browser sends Global Privacy Control or Do Not Track, no notes are sent.
- In our own database the notes are kept for 13 months, then reduced to daily totals and deleted.
- To draw charts of these counts we pass a copy of the same notes to PostHog, an analytics company hosted in the US, which processes them for us. It gets exactly what is in each note plus the day's keyed hash, from our server, never from your browser: no cookies, no PostHog code on the page, and not your IP address or browser name. We tell it not to build a profile of you or look up your location. PostHog keeps its copy under its own retention period.
Error reports
- When something breaks, an error report goes to Sentry, our error tracker. Before it leaves, links, email addresses and @handles in it are replaced with placeholders. Addresses of pages on this site are kept, without anything after the question mark, so we can tell which lesson broke. Sentry also gets timings for about one in ten requests to our server, with the same placeholders, so we can see what is slow.
- When a lesson is removed we get an alert with the lesson's id and which option was picked. The words you typed are not in it.
How long we keep it
- We keep the clip while the lesson exists. Lessons nobody opens for six months are deleted, and a removal request deletes one straight away.
- The one exception is a lesson reported as sexual content involving a minor, or intimate images shared without consent: it is taken down straight away, but instead of being deleted at once it is kept apart from the site, where no page can reach it, and reported to the authorities as the law requires.
- After a deletion we keep a short note that the lesson was removed — when, the option picked and anything typed — so the link can say it was removed instead of pretending it never existed. The usage counts above keep the lesson's id (not the video, the 3D or anything from it) for as long as those counts are kept.
Removing a lesson
- Use Report or remove this video on the lesson, or paste the lesson's link below. It deletes the video and the 3D lesson for everyone, straight away. Anyone with the link can do it; you do not have to be the person who added the clip.
- You need the lesson's link. For anything else (a rights claim, a question, or if the button does not work) email stepwisedance.help@gmail.com. A person reads it and replies by hand.