Privacy Policy

Last updated: 5 September 2026

1. Who is responsible for your information

Farai Ikeleng operates the Maestro app, website and related services (we, us, our). Contact our privacy contact at hola@maestrodance.app.

This policy describes information we receive from you, your device, sign-in providers and purchase providers, how we use and share it, and your choices. Private music practice and community posting are different: we do not upload your imported song files, but a community video you choose to upload includes its recorded audio.

2. Information we handle

Visiting or practising without an account

You can use available guest features without creating an account. Your device stores settings, imported music, library references, playback positions and other local practice information. When you visit our website, load the catalogue or stream videos, our infrastructure and providers process request information such as IP address, requested resource, time, browser or device information and response or error details. Guest access is therefore not anonymous to every service provider, even though you have not created a Maestro profile. Where the purchase SDK is active, it may also assign an anonymous app-user identifier.

Account and profile

When you sign in, we receive your email address, account identifier and authentication information. If you choose Apple or Google sign-in, we receive the identifier and available profile information that provider supplies, which may include a name, email or profile image. Apple may provide a private relay email address. We store session and verification information to authenticate you and prevent misuse.

Your profile can include a display name, avatar, language, preferred dance genres and styles, learning goals, level, dance role, onboarding selections and notification preferences. We also record community-terms acceptance, moderation restrictions and deletion requests.

Practice activity and personal music

For signed-in practice, we record progress, favourites, class activity and session information such as the practice module, start and end times, duration, session identifier and relevant content identifier. Song practice can include a track fingerprint, a technical reference associated with your account. A fingerprint is not an audio upload and is not necessarily anonymous.

Imported song audio, local file paths and Apple Music library identifiers remain on-device. Locally stored information can include titles, artists, waveform data, loops, playlists and playback settings. Apple processes its own library and playback activity under its policies when you use Apple Music.

Community and profile media

If you post to Rate me, we receive the video and its audio, thumbnail, caption, associated move, technical file details and timestamps. We also store comments, likes, reports, block relationships and moderation records. Profile pictures you upload are stored separately. Media may reveal information about you, other people, or your surroundings; choose what you share carefully.

Purchases

Apple or Google handles payment details for store purchases. We and our purchase-management provider process identifiers, product and transaction information, purchase and renewal events, subscription status, expiry and refund information to recognise your purchases, restore access, prevent fraud and understand subscription performance. Maestro account identifiers link these records to your account. We do not receive full card numbers from these store purchases.

Notifications, support and technical records

If you enable push notifications, we store the push token, a device identifier, platform, app version and delivery information. Notifications can include activity by other members. If you enable email notifications for Maestro feedback, we use your email and relevant activity details to deliver them. Sign-in emails are sent when you request them.

If you contact us or report content, we handle the message, reply address, relevant account or content references, and any information you choose to include. Infrastructure logs help us operate, secure and troubleshoot the service. We plan to use product analytics and operational logging as described below.

Analytics and advertising measurement

We plan to use analytics and attribution tools to understand how people find and use Maestro, assess feature performance and measure our paid advertising. Depending on the settings enabled and your choices, this can involve app or device identifiers, device/app version, IP address, referral or campaign information, app interactions, install events and purchase events. Records linked to an account or device are not anonymous merely because they omit your name.

3. Purposes and optional uses

We use information to provide accounts, personalise practice, record progress, deliver media, manage purchases, send requested communications, handle support and privacy requests, moderate the community, prevent abuse, meet legal obligations and maintain the Services. Dance-preference totals and subscription reporting also help us decide what to improve.

We run paid advertising to promote Maestro and plan to use analytics and advertising measurement. Buying advertising does not by itself mean we share your Maestro activity with an advertising platform. Any sharing of identifiers or events for attribution, audience matching or retargeting depends on the specific integration and applicable permissions.

We do not use imported songs or user contributions to train AI models or provide AI analysis of dance technique. We may use AI-assisted captions or translations for our own courses. Separately, AI tools may assist the team in assessing whether comment or report text is harmful. We remove user identifiers before submitting text and do not submit user videos or images. Human reviewers make moderation decisions. Removing account identifiers does not necessarily make a comment anonymous: text can itself contain identifying details.

We intend to feature selected community contributions in marketing, including our website, social media and paid advertising. As explained in our Terms, you authorise this when accepting the signup Terms where legally permitted, with an option to opt out before use or later without losing app access. This can make the selected video, audio, likeness and displayed name visible to the public and to advertising-platform providers. It does not include private device files or support/report messages. Promotional use ends following an opt-out, deletion of the contribution or account-deletion request under the removal process in the Terms; independent copies already distributed may remain outside our control.

Enabling a device permission does not authorise an unrelated use of your information. If we introduce a materially different purpose, we will explain it and obtain consent where required before that use begins. Marketing emails, advertising tracking and promotional reuse of your contributions are separate activities with their own applicable notices and choices. Permission for one does not automatically authorise the others.

Where EEA or UK data-protection law applies, we rely on the following legal bases, as applicable: performance of our agreement for account access, requested practice features, purchases and support; legitimate interests in service security, abuse prevention and proportionate service improvement after considering your rights; legal obligations for records and lawful requests; and consent where required for non-essential analytics, advertising tracking, optional communications and promotional use of contributions. You can withdraw consent without affecting the lawfulness of earlier processing.

4. Who can see information

Other users. Members with access to a community post can see its video, audio, caption, comments, displayed name, avatar and interaction information. Email addresses are not displayed as community author names. Community video delivery requires authentication and access checks. Profile-avatar links are publicly accessible to anyone who has the link. Other people may capture or copy content they can see; deleting a post cannot recall their independent copies.

Staff and moderators. Authorised people may access relevant information to provide support, operate the service, investigate reports and meet legal duties. Reports and block records are not presented as community posts, but relevant information may need to be used to investigate a complaint.

Service providers and other recipients. We describe our providers by their functions below. We give them the information relevant to those functions, subject to applicable permissions and safeguards:

Legal requirements and business transfers. We may disclose relevant information where legally required, to protect people or investigate abuse, or to obtain professional advice and establish or defend legal claims. A merger or business transfer may involve limited disclosure with confidentiality protections. We will notify you of a change of operator and any material change to information handling, and obtain consent where required. These circumstances do not grant a general right to sell user data for advertising.

5. Overseas processing

An Australian operator does not mean all information stays in Australia. Our providers and authorised personnel may process information overseas.

We take reasonable steps required by applicable law to protect personal information handled overseas. Accepting this policy is not a waiver of those protections.

6. Permissions, device storage and your choices

You can withdraw device permissions in system settings. Withdrawal stops future permission-based access; it does not delete media already posted or information already received. Delete those items or request account deletion separately.

The app uses local storage for settings, authentication and music practice. Browser authentication and service operation may use necessary browser storage. Analytics and advertising technologies, where enabled, may use additional storage or pixels.

Local data may be affected by your operating system's backup and restore settings. Our promise not to upload song files to Maestro does not describe backups you configure with your device or cloud-account provider. Keep your own originals.

7. Retention and deletion

We retain personal information for the purposes described above, then delete or de-identify it when it is no longer needed, subject to legal requirements. Retention depends on the type of record, whether your account is active, and any unresolved safety, payment or legal issue.

You can request deletion of your account and associated personal information through Delete account in the app's profile/account area. We will delete that information, except records we must retain for a lawful, explained reason. You can also contact hola@maestrodance.app about your information. We may verify that a request is yours in a proportionate way.

After we accept an in-app deletion request, account access is disabled and an automated job removes account and authentication records, synced practice information, community contributions and associated interactions, notifications, uploaded clips and profile photos, and the linked purchase-management customer record. The welcome screen on the requesting device shows progress after sign-out. We allow at least 20 minutes for existing upload links to expire before completing media cleanup. Our target is completion within 24 hours; provider outages or failed cleanup can take longer. We retry failures, keep the request pending rather than report an incomplete deletion as finished, and provide a support contact in the status notice. We send a completion email when cleanup has finished, where an account email is available.

We retain a minimal deletion record containing the former internal account identifier and request/completion status to prevent delayed events or a database restore from recreating deleted account data. It does not retain your profile, email, uploaded content or Apple authorization tokens after completion notification. A private receipt stored on the requesting device permits access to deletion status only. Copies already cached on other devices may remain until their cache expires; profile-photo responses permit caching for up to one day and community media for up to one hour. Backup copies follow their separate expiry cycle and are not made available as active account data; any recovery must reapply completed deletions before service resumes.

We keep opaque storage keys for seven days to repeat removal of uploads that finish unusually late. We remove those key records after the final successful cleanup; failures may extend this period until removal can be confirmed. The key records do not contain the uploaded media.

For Sign in with Apple accounts, we revoke the stored Apple authorization where available. Older accounts may not have a revocation token; in that case we still delete the Maestro account and show instructions to remove Maestro from your Apple Account's Sign in with Apple settings.

Requesting deletion or uninstalling the app does not cancel a store subscription. Cancel separately in Apple or Google subscription settings. Store transaction records may remain with the store under its policies and legal duties. Local music originals are not removed from your external library by an account-deletion request.

8. Access, correction and complaints

You can edit available profile fields and preferences in the app. Contact us to request access to or correction of personal information, a copy of your information, deletion, or withdrawal of consent to an optional use. Depending on applicable law, you may also have rights to portability, restriction, objection, or review of a decision. We will assess requests under the law that applies to you and explain any lawful limitation or refusal.

Privacy complaints can be sent to hola@maestrodance.app. Describe the issue and how we can reach you; do not send passwords or unnecessary identity documents. We will investigate and respond within applicable legal time limits. You may complain to the relevant regulator, including the Office of the Australian Information Commissioner where it has jurisdiction. Contacting us does not remove your right to a regulator or court.

9. Children and young people

Our minimum age is 13, with a higher age where required by applicable law.

The Services are not directed to children below the applicable minimum age. We do not knowingly permit them to hold accounts. If you believe an ineligible child has provided information, contact us so we can investigate and take appropriate action.

10. Security and changes

We use access controls and technical protections designed to safeguard information, including authenticated access to account data and community video delivery. No system is completely secure. We will respond to incidents and notify affected people and authorities where required by law. Publicly accessible avatar links and content shared with other members have the visibility described above.

We will publish updates with a new effective date and give additional notice of material changes through the app or email where appropriate. If a change requires consent, we will request it before applying the new optional use.

Privacy contact: hola@maestrodance.app.