> For the complete documentation index, see [llms.txt](https://musenai.gitbook.io/musenai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://musenai.gitbook.io/musenai/community-and-trust/privacy-policy.md). # Privacy Policy Version 4.0 | Effective 4 September 2026 Canonical address:

Privacy should create confidence, not hidden dependency.

This Policy explains what personal data the current musen service processes, why it is processed, who may receive it, how long it is kept, and what choices and rights people have. It reflects the current public product rather than planned or research features.

| Controller | Fabio Senna | | --------------- | ---------------------------------------- | | Trading name | musen | | Service address | 483 Green Lanes, N13 4BS, United Kingdom | | Privacy contact | | This version replaces Privacy Policy v3.1.1 from its effective date. ## 1. Purpose, scope and current service This Privacy Policy explains how personal data is processed when you use musen operated websites and applications that link to this Policy. It applies to the current public musen listening service and to supporting account, analytics, security and customer support functions. The current public release is a free, account based personal Live Radio experience available on iPhone and Android. An internet connection is required. Users can shape the radio through text, voice or picture requests and may enable optional AI Host speech. The current public release does not offer paid subscriptions, in app purchases, creator uploads, user broadcasting, Segment creation, or a separate public AI DJ mode.

Status discipline

A reference in this Policy to a possible future feature does not mean that feature is currently available. Where a new feature materially changes personal data processing, this Policy and relevant notices will be updated before or when that processing begins.

## 2. Controller identity and contact details For purposes of the UK General Data Protection Regulation, the EU General Data Protection Regulation where applicable, and other applicable data protection laws, the controller responsible for the processing described in this Policy is: | Controller | Fabio Senna | | --------------- | ---------------------------------------- | | Trading name | musen | | Service address | 483 Green Lanes, N13 4BS, United Kingdom | | Privacy contact | | musen is a trading name and is not a separate legal entity. The controller identity in this Policy is intended to match the legal operator identified in the Terms, app store information, contracts and other binding notices. ## 3. Information we process The information processed depends on the features you use. We seek to limit collection to information reasonably necessary for the stated purposes and to avoid collecting information simply because it is technically available. ### Account and authentication information • Email address, account identifier, display name and profile information you choose to provide. • Authentication tokens and provider identifiers used to sign in or maintain a session. • Information received from supported authentication providers such as Apple or Google when you choose those sign in methods. • Eligibility or age related information where reasonably necessary for access, safety or legal compliance. ### Device, network and application information • IP address and approximate location inferred from network information. • Device type, operating system, app version, browser where relevant, language, time zone and similar technical information. • Network, performance, crash, authentication and security events. • Device or advertising identifiers only where the platform, law and your choices permit their use. ### Listening and radio activity • Listening sessions, duration, continuity and playback events. • Music or radio elements presented during a session and interactions with available controls. • Request history, explicit preferences and other signals used to shape the radio. • Optional AI Host settings and interactions relevant to operating the radio. ### Text, voice and picture requests • Text that you enter into a request. • Audio that you deliberately submit when you choose a voice request, and a transcript or interpreted representation where generated. • Images that you deliberately submit or capture when you choose a picture request, and descriptions or other derived representations where generated. • Limited technical and request context needed to interpret the request and deliver the radio experience. ### Support, safety and legal information • Messages you send to support or privacy contacts. • Reports, complaints, moderation information and records needed to investigate safety, rights or abuse concerns. • Information needed to comply with lawful requests, resolve disputes, establish legal claims or protect the Service. ### Analytics and advertising measurement information • App events and aggregate usage information used to understand reliability, activation and feature performance. • Crash and diagnostic information. • Campaign attribution events and, where permitted, advertising identifiers used to measure musen advertising campaigns. ## 4. Information we do not seek by default • Ordinary listening does not require continuous microphone or camera access. • We do not use submitted voice recordings or pictures to create voiceprints or facial recognition templates for the purpose of uniquely identifying you. • The current public service does not process payment card or bank account information because it does not currently offer paid features or in app purchases. • The service is not directed to children under 13, and we do not knowingly seek personal data from children under 13. • We do not require you to provide sensitive personal information in free form requests. Please avoid submitting health, identity, financial, intimate or other sensitive information unless it is genuinely necessary for the feature you choose to use. ## 5. Why we process information and the legal bases we use The lawful basis depends on the specific purpose. We do not rely on one legal basis as a universal fallback. The table below describes the main processing purposes for the current service. | Purpose | Typical information | Main legal basis | Why it is needed | | --------------------------------------------- | ------------------------------------------------------------ | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | Provide account and Live Radio | Account, authentication, requests, listening activity | Contract | To create and maintain the account, interpret requests and deliver the listening service you ask for. | | Personalise radio over time | Listening activity, requests, preferences, permitted context | Contract and legitimate interests where appropriate | To make the radio relevant and coherent between sessions without producing legal or similarly significant effects. | | Voice and picture requests | Submitted audio, image, transcript or derived description | Contract. Device permission does not by itself define the data protection legal basis. | To interpret a request you deliberately choose to submit. | | Security and abuse prevention | IP address, logs, authentication events, anomaly signals | Legitimate interests and legal obligations where applicable | To protect accounts, infrastructure, rights and the integrity of the Service. | | Support and disputes | Messages, account details, relevant logs | Contract, legitimate interests or legal obligations | To answer requests, investigate problems and establish or defend legal claims. | | Core service analytics | Usage, performance and diagnostic events | Legitimate interests where proportionate | To understand reliability, diagnose faults and improve the Service. | | Optional analytics or advertising measurement | Campaign events, identifiers where permitted | Consent where required by law or platform rules | To measure musen marketing and understand whether campaigns work. | | Marketing communications | Email address and communication preferences | Consent where required | To send optional product or community updates. | | Legal and regulatory compliance | Relevant account, safety, rights and transaction records | Legal obligation | To comply with applicable law and valid orders. | ### Legitimate interests Where we rely on legitimate interests, the relevant interests may include service security, fraud prevention, reliability, proportionate analytics, abuse prevention and protecting legal rights. We balance those interests against your rights and reasonable expectations. You may have a right to object to processing based on legitimate interests. ## 6. Text, voice and picture requests Requests are deliberate inputs used to shape the radio. Different request modes involve different data. • Text requests. We process the text you submit and limited account, radio and technical context needed to interpret it. • Voice requests. When you choose a voice request, we process the audio you deliberately submit, together with limited technical and request context, to transcribe or interpret the request and provide the radio experience. • Picture requests. When you choose a picture request, we process the image you deliberately submit, together with limited technical and request context, to interpret the request and provide the radio experience. • Derived information. A provider or musen system may create a transcript, description, classification or other representation from a submitted request. Derived information can be personal data even if the original media is later deleted. Depending on how a feature is implemented, authorised service providers may process request information on behalf of the controller or under another role described in the provider information. We do not claim that voice or picture requests are processed only on the device, and we do not claim that raw media is never retained unless the verified retention practice supports that statement.

Device permission is not blanket permission

Microphone, camera and photo library access is requested through device controls when needed. Granting a device permission does not authorise unrelated processing. Ordinary listening does not require continuous microphone or camera access.

## 7. Listening personalisation and preference inferences musen may use listening activity, request history, explicit preferences and permitted contextual signals to adapt radio over time. These records can be used to infer preferences, such as likely interest in certain moods, topics, formats or listening patterns. Personalisation records are limited according to their purpose and applicable retention criteria. Where controls are available, you can change, reset or remove relevant preferences. Personalisation is used for entertainment and does not make decisions that produce legal effects or similarly significant effects about you. The design principle is continuity without captivity: personalisation should help the radio evolve with you rather than freeze you into a permanent identity. This principle does not replace the concrete retention, deletion and access rules in this Policy. ## 8. AI Host and contracted AI services The optional AI Host is synthetic speech within the radio experience. To generate or deliver Host speech, musen may process the current request, limited radio context, language or voice settings, and text generated for speech. Contracted language, search, speech or infrastructure providers may receive the limited information needed to perform their function. The AI Host is not used to make decisions about your legal rights, eligibility for essential services, credit, employment, health care or similar matters. Host speech may be incomplete or incorrect and is provided for entertainment rather than professional advice. Permission to stream or analyse music does not, by itself, create permission to use that music for model training. Music rights and training permissions are governed separately by the applicable rights basis and contracts. This Privacy Policy does not grant a provider permission to use personal request content for unrelated training. ## 9. Device permissions • Microphone permission may be requested when you choose a voice request. • Camera or photo library permission may be requested when you choose to capture or select a picture request. • Notification permission may be requested if notifications are offered. • App Tracking Transparency permission may be requested on Apple devices where tracking or access to the advertising identifier requires it. • Platform permission choices can usually be changed in your device settings. Changing a permission may limit the feature that depends on it but should not prevent unrelated core listening functions. ## 10. Analytics, diagnostics, advertising measurement and cookies musen uses analytics and diagnostic tools to understand reliability, product use and campaign performance. The exact configuration can differ between the website and mobile applications. The current stack includes Firebase Analytics for product analytics, Sentry for crash and error monitoring, and Meta App Events for measurement of musen advertising campaigns. Apple and Google may also process platform, authentication or store related information under their own terms and privacy roles. • We do not serve third party advertising inside the current public musen service. • We do not treat App Tracking Transparency permission as a substitute for consent required under data protection or electronic privacy law, and we do not treat legal consent as a substitute for Apple platform permission. • Where an advertising identifier is used, it is accessed only where platform rules and applicable consent requirements permit it. • Website cookies and similar storage used for non essential analytics or measurement are used only where the required choice has been obtained. • Declining optional measurement should not disable unrelated core listening functionality. ## 11. Authentication and information received from other services When you choose a supported authentication provider, musen may receive information such as a provider account identifier, email address, display name where supplied, authentication tokens and login metadata. Apple may provide a private relay email address depending on your settings. The provider may also process your information independently under its own terms and privacy policy. Information may also be obtained indirectly from device platforms, app stores, analytics services or security tools. Where required, this Policy explains the source or category of source and the purpose for which that information is used. ## 12. Who receives personal data Personal data is disclosed only where reasonably necessary for the stated purposes, where required by law, or where you direct the disclosure. Recipient roles vary. Some providers act as processors on behalf of the controller, while others may act as independent controllers for their own platform services. | Recipient category | Examples and purpose | Important role note | | ----------------------------------------- | ----------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | Hosting and infrastructure | Application hosting, databases, storage, networking and content delivery. | Usually processor or subprocessor, subject to contract and actual service. | | Authentication and platform services | Apple and Google authentication, operating system and app store services. | May act independently for parts of the platform relationship. | | Analytics and diagnostics | Firebase Analytics or configured Google analytics products, and Sentry diagnostics. | Enabled products, payloads and retention are maintained against the verified runtime inventory. | | Advertising measurement | Meta App Events and platform advertising identifiers where permitted. | May involve tracking or joint or independent controller analysis depending on configuration. | | AI, speech and search services | Providers used to interpret requests, generate Host text or speech, or retrieve information. | Only the information needed for the function should be sent, subject to the applicable contractual role. | | Support, safety and professional advisers | Support tools, security providers, legal, accounting or compliance advisers where needed. | Access is limited to the relevant purpose and legal basis. | | Authorities and legal recipients | Courts, regulators, law enforcement or other parties where legally required or necessary to protect rights. | Only where there is a valid legal basis. | ### Provider register The controller maintains a current provider register identifying enabled services, relevant data categories, privacy role, processing location, transfer mechanism and provider privacy information. Provider roles depend on the actual service and configuration, and not every provider acts only on behalf of the controller. ## 13. International data transfers Some providers may process personal data outside the United Kingdom or European Economic Area. When applicable data protection law requires safeguards for a transfer, the controller uses an applicable transfer mechanism. This may include an adequacy decision or regulation, approved contractual safeguards together with supplementary measures where appropriate, or another lawful transfer mechanism. The applicable mechanism depends on the recipient, destination, role and processing context. This Policy does not claim that one transfer mechanism applies to every provider or every transfer. ## 14. How long information is kept Personal data is retained only for as long as there is a justified purpose or legal basis. Because the Service contains different data classes and service providers, retention is managed by criteria and by an internal schedule rather than by one universal period. | Data class | Retention criterion | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Account and authentication | For the active account and for a limited period afterwards where needed for deletion processing, security, dispute handling or legal obligations. | | Listening and personalisation | For as long as needed to provide continuity and personalisation, subject to account controls, deletion and the applicable retention schedule. | | Voice and picture requests | According to the verified feature design and provider retention settings. Raw media and derived transcripts or descriptions may have different retention criteria. | | Analytics and attribution | According to the configured analytics purpose, consent state, provider settings and data minimisation requirements. | | Security and abuse records | For periods reasonably necessary to detect, investigate and prevent incidents, fraud or repeated abuse and to establish legal claims. | | Support and legal records | For as long as needed to resolve the matter and meet legal, accounting or dispute requirements. | | Backups | Deleted data may remain in protected backups for a limited operational cycle before being overwritten, unless a longer period is required by law or security needs. | If musen introduces automatic inactivity deletion, the applicable rule and timing will be disclosed once implemented. This Policy does not promise an inactivity deletion process that is not operational. ## 15. Account deletion and your controls You may request deletion of your account and associated personal data through available account controls or by contacting the privacy address. Where an in app deletion control is available, it should be used for the fastest account linked request. • We may take reasonable steps to verify identity before deleting or disclosing account data. • Deletion generally covers account identifiers, profile information, personalisation records and authentication links held by the controller, subject to lawful exceptions. • Limited records may be retained where necessary for security, fraud prevention, legal claims, regulatory duties or enforcement, and are kept only for the justified purpose. • Deletion from musen does not delete information independently held by Apple, Google or another provider under that provider relationship. • Deletion requests are propagated to processors where required and technically applicable. Backup copies may expire through the normal protected backup cycle rather than being removed instantly. ## 16. Your data protection rights Where the UK GDPR, EU GDPR or other applicable data protection law gives you these rights, they may include the following, subject to the conditions and exceptions in applicable law: • Access to your personal data and information about how it is processed. • Rectification of inaccurate or incomplete personal data. • Erasure in circumstances where the law gives you that right. • Restriction of processing in specified situations. • Data portability for qualifying processing based on consent or contract and carried out by automated means. • Objection to processing based on legitimate interests and an unconditional right to object to direct marketing. • Withdrawal of consent at any time where processing is based on consent, without affecting processing already carried out lawfully. • The right to lodge a complaint with a competent data protection supervisory authority. Requests may be sent to . We normally respond within one month where the applicable law provides that period, subject to lawful extensions for complex or numerous requests. We may ask for proportionate information to verify your identity or authority to act for another person. ## 17. Children and age related safeguards The Service is not directed to children under 13. People under 13 may not use the current Service. Users aged 13 to 17 may use the Service only where applicable law permits it and subject to any parent or legal guardian authorisation required for the relevant processing or service in their country. Where consent is the legal basis for offering an information society service directly to a child, the applicable age for independent consent can be higher than 13 depending on national law. musen may restrict a feature, request age information or require parent or legal guardian involvement where reasonably necessary to comply with applicable law or protect young users. We do not use children’s data for behaviourally targeted advertising. If we become aware that personal data from a child under 13 has been collected in circumstances where use of the Service is not permitted, we will take reasonable steps to delete or otherwise lawfully resolve that data without undue delay. ## 18. Security and personal data breaches The controller uses technical and organisational measures intended to protect personal data against unauthorised access, loss, alteration and disclosure. Measures may include access controls, secure authentication, encryption in transit, appropriate storage protection, logging, monitoring and restricted internal access. No system can be guaranteed to be completely secure. When a personal data breach occurs, it is assessed and handled in accordance with applicable law. Where applicable data protection law requires notification to a supervisory authority, notification is made without undue delay and, where the UK GDPR or EU GDPR applies, within 72 hours after becoming aware of the breach when that rule is applicable. Affected people are notified where the law requires it because the breach is likely to result in a high risk to their rights and freedoms. ## 19. Profiling, AI and automated decisions Personalisation can involve profiling in the broad data protection sense because listening activity, requests and preferences may be used to infer likely interests and shape radio output. This profiling is used to provide entertainment and improve radio relevance. The current Service does not use automated decision making to make decisions that produce legal effects or similarly significant effects about users. If a future feature changes that position, musen will assess the applicable legal requirements and update the relevant information before such processing begins. ## 20. Data Protection Officer assessment and complaints The controller has assessed whether appointment of a data protection officer is currently required under the applicable data protection rules. Based on the controller’s present processing activities, a data protection officer has not been appointed. This assessment is reviewed when the nature, scope, context or purposes of processing materially change. Privacy and data protection enquiries may be sent to . Where applicable data protection law gives you this right, you may lodge a complaint with the competent data protection authority in your habitual residence, place of work or place of the alleged infringement. This Policy does not restrict any complaint or redress right available under applicable law. ## 21. Changes to this Policy This Policy may be updated when the Service, legal requirements, providers or processing practices change. Material changes will be communicated through the Service, website, email or another appropriate channel where required. An updated privacy policy is not treated as consent to a new processing activity where consent or another separate legal basis is required. Where renewed consent is necessary, it will be requested separately. ## 22. Relationship to other musen documents This Privacy Policy governs personal data processing. The Terms govern the contractual relationship with users. The Content Rights Policy governs rights in music and other content. The Community and Broadcasting Guidelines govern participation and behavioural standards. The Security Policy describes security practices. Where a binding legal instrument governs a particular right or obligation, this Policy does not replace that instrument. ## 23. Contact information • Privacy and data protection: • General support: • Security reports: • Controller: Fabio Senna, operating under the trading name musen • Service address: 483 Green Lanes, N13 4BS, United Kingdom