Belka Live helps group exercise instructors with short cues during a class. DRAGENOR AS, organisation number 938 718 164, is the data controller for Belka. You can contact us about privacy at post@belkabeat.com. This information covers the iPhone beta with a personal Belka account and downloads of your selected classes from Belka online. It does not cover future paid products or studio subscriptions.
Microphone and music
Belka asks for microphone access when you start listening. Audio is processed in the phone's memory to recognise music and position cues. The app does not save audio recordings. ShazamKit sends an audio fingerprint to Apple's recognition service. Apple states that the audio itself is not shared with Apple and that the fingerprint cannot be converted back into the original audio. About ShazamKit.
Stop listening with Stopp Belka (Stop Belka), or the stop button in the demo. You can also revoke microphone access in iPhone Settings. The cue example without music synchronisation does not use the microphone. Music recognition requires internet access.
Account and sign-in
You sign in through Microsoft in a separate sign-in window. Belka's server links the sign-in to an account ID, login identity, email address, role and test access. These details identify your account and determine your access. Name, studio and contact address you enter in your online profile are stored there. The app's permission covers reading your selected Live classes; it does not provide access to email content or other users' private classes. Microsoft processes information during sign-in. Microsoft's privacy statement.
Classes online and on your phone
Analyses, classes, choreography and cues you save in Belka online are stored in your account's library on Belka's server. Live downloads the finished class versions you selected for Live from app.belkabeat.com. DigitalOcean hosts the service and database; the database is established in Frankfurt. This does not guarantee that all operational and provider information is processed only within the EEA. DigitalOcean's privacy information.
Class versions are stored separately for each account on the iPhone. Sign-in credentials are stored in the iPhone's device-bound Keychain. Sign-in, downloads and the pre-class access check require internet access. Classes are not updated during teaching. Signing out removes credentials and hides classes; it does not delete your Belka account, online library or necessarily earlier class versions on the phone. Removing a class from Live is not the same as deleting the original class and every archived copy.
Song information and playback
Titles, artists and other song information come with the class from Belka. This cloud beta does not retrieve song information from Spotify or control your player. You choose the audio source; the phone must hear the same recording used by the class, and it must be in Shazam's catalogue. Older Mac betas may use a different connection flow; this description concerns the cloud beta.
When you open the help and privacy pages
These web pages are hosted by DigitalOcean, with Cloudflare providing delivery and security services. When you open a page, these providers receive your IP address and technical information from your browser's request to deliver and protect the website. Cloudflare may set the __cf_bm cookie to distinguish automated traffic from normal use. According to Cloudflare, it expires after 30 minutes of inactivity. Cloudflare states that cookie data may by default be processed in the United States. See Cloudflare’s privacy policy for information about international transfers. This concerns public pages and technical web requests. Belka processes account content online as described above. The app does not automatically upload audio recordings or technical logs. About Cloudflare cookies.
Troubleshooting and feedback
The app creates limited technical logs on the phone. New logs do not contain audio recordings or song or class names and are not sent automatically to Belka. If you contact us, we receive your email address, message and any attachments you send so that we can respond. The support address uses Google Workspace. Access to Belka’s support inbox is restricted to authorised personnel at DRAGENOR AS; Google processes the email as the service provider. Do not send passwords, pairing codes, health information or information about class participants.
Support email is processed under Google's data processing addendum. Information may be processed outside the EEA, including in the United States. Google describes the EU–US Data Privacy Framework for applicable US transfers and standard contractual clauses where required. See Google's transfer safeguards and data processing addendum. Support email is therefore not restricted to storage in the EEA.
When you use TestFlight, Apple automatically collects crash and usage information and shares it with the developer. Feedback you submit through TestFlight is also shared. Depending on the invitation, this information may include your name and email address, as well as your phone model and app version. This is separate from the app's local technical logs. Apple's information about TestFlight.
How long we keep support information
We delete closed support requests no later than six months after the last follow-up. Logs and screenshots containing personal information that we receive or download for troubleshooting are deleted within 30 days after a fix is confirmed, and no later than six months after receipt. Whichever deadline comes first applies. This also covers our own downloaded TestFlight error reports. We review this material monthly and may delete it sooner. Anonymous descriptions of errors and fixes may be kept. These deadlines apply to Belka’s own support and troubleshooting copies; the instructor’s library and classes on the phone are described separately. Apple’s own copies follow Apple’s rules. After deletion, email information may remain temporarily in Google’s recovery and technical deletion systems; this does not extend Belka’s own deadline for ending its use of the information.
Legal basis for features, contact and troubleshooting
Necessary technical processing to deliver the features you start, secure sign-in and account-scoped class downloads and respond to specific requests and errors is based on our legitimate interest in providing, supporting and improving the invitation-only beta, under Article 6(1)(f) of the General Data Protection Regulation. We limit processing as described here: you start and stop listening, audio is not saved, and technical logs are not sent automatically to Belka; account classes are processed online and downloaded to the phone as described above. The information is not used for marketing, profiling or assessing participants' health. Microphone access is a technical permission that you can revoke at any time. You can ask for information about our balancing of interests.
You can object
You can contact post@belkabeat.com at any time to object to processing based on legitimate interests. We will then assess whether the processing should stop under data protection rules.
Your rights
Contact post@belkabeat.com to request access to personal information Belka processes about you, correction or deletion. Where the conditions are met, you can also request restriction and data portability, and object to processing based on legitimate interests. We normally respond within one month. We may ask for information needed to verify that the request concerns you. You can complain to the Norwegian Data Protection Authority.
Account, retention and deletion
Account information and your private library are stored while the account is in use, or until you request deletion. Expiry of test access does not automatically delete your data. You can start deletion directly at Delete Belka account. Sign in, check the account and confirm the request. You receive a receipt and can view processing status on the same page. You do not need to send a separate email. Requests are processed manually within 30 days; we send confirmation when deletion is complete.
Deletion covers the Belka account and associated personal data, including your private profile, library, drafts, history and Live archive on the server. Shared contributions and studio roles are reviewed so personal data is removed without deleting other users' data. Any information that must be retained by law, including the basis and retention period, is explained in the confirmation. Deleting the Belka sign-in identity does not delete your ordinary Microsoft account. The request does not remove downloaded phone copies; remove app data on devices you will no longer use.
Operational and provider copies are reviewed as part of deletion. Information may remain temporarily in restricted recovery systems until the provider deletes or overwrites it; any remaining period is specified in the confirmation. Deleted information must not be put back into use during recovery. A minimal processing receipt and necessary deletion markers are kept separate from working content. The contact address in the request is removed when completed deletion and sent confirmation are recorded. The remaining processing receipt is deleted no later than six months after the last follow-up, or earlier once recovery safeguards are in place.