> How Resomix handles audio. Uploads are deleted within 24 hours, partner catalogues stay in private indexes, and your audio is never used for training. Trust, Rights & Security // Production beta # The audio can be analysed without blurring who it belongs to. Resomix is a production-beta sonic discovery service. This page separates controls operating now, controls defined by partner agreement, and controls we do not yet claim. Current controls · Agreement-bound terms · Beta limitations · Published policies Reflects the Resomix production-beta policies effective 20 July 2026. The published legal documents control. Reflects the Resomix production-beta policies effective 20 July 2026. The published legal documents control. **Current** A control or behaviour operating now and approved for public description. **Agreement-bound** A partner or Private Library control whose exact scope, duration, access or deletion terms are governed by the applicable account terms, partner agreement or Data Processing Addendum. **Beta control** A control operating during the production beta but still being documented, expanded or verified, not presented as mature enterprise assurance. **Roadmap** A control or capability not implemented today. **Not claimed** A deliberately explicit boundary where Resomix does not currently make a certification, guarantee or technical assurance. 01 // At a glance ## What applies now, and what does not Uploaded source audio is deleted no later than 24 hours after upload or analysis. Partner catalogues are logically isolated and restricted to authorised partner access. User and partner audio is not used to train or fine-tune PYXIS-1. TLS is used on public service endpoints. The applicable partner agreement and Data Processing Addendum govern access, retention and deletion. Retained as necessary for the user-authorised catalogue-analysis and discovery service. Resomix is live in production as a beta service during its initial three-month beta period. Resomix uses encrypted HLS for controlled media delivery. Partially implemented and continuing to develop during the beta period. DDEX ERN ingestion and DDEX reporting workflows are not available today. Resomix does not currently claim SOC 2, ISO 27001 or another enterprise security certification. Resomix does not currently publish an uptime SLA or claim a fully redundant high-availability architecture. 02 // Audio lifecycles ## Not every audio upload has the same retention rule **Private Library audio is not a Temporary Reference Upload.** The three lifecycles have different purposes, retention rules and deletion triggers; the ledger above states each one separately. 03 // Rights & access ## Processing requires authority. Access stays bounded. **Who may submit audio?** You must have the right or authority to submit audio for analysis. Partner catalogue use is defined by the applicable partner arrangement. **Can another partner see our catalogue?** Partner catalogues are logically isolated and restricted to authorised partner access. Current **Who at Resomix can access partner content?** Access is restricted to the partner's authorised account users and Resomix personnel or service providers where access is necessary to provide, secure or support the authorised service. The partner agreement and Data Processing Addendum govern the specifics. Agreement-bound **Is uploaded or partner audio used to train PYXIS-1?** No. PYXIS-1 does not train or fine-tune itself using user or partner audio, and it does not generate, synthesise or recreate audio. Current **What does the analysis create?** Sonic analysis does not create a playable replacement for the source recording. PYXIS-1 and Resomix software remain Resomix proprietary technology. **What rights does a partner grant?** Partner content is processed only for the purposes authorised by the applicable partner arrangement. The partner agreement defines the catalogue-processing licence and permitted use. Agreement-bound **How do rights holders raise a concern?** Through the published Copyright & DMCA Policy, Acceptable Use Policy and Terms of Service, or directly at [legal@resomix.com](https://resomix.com/mailto:legal@resomix.com). 04 // Security ## Security controls operating today TLS on public service endpoints. Account, session and role-based access controls. Additional account-security control where available. Rate-limiting and abuse-prevention controls. API-key and token-based access where applicable, restricted by account and service roles. Logically isolated and restricted to authorised partner access. Encrypted HLS for controlled media delivery. Media controls reduce unauthorised access risk; they do not make copying technically impossible. Incident-response and GDPR breach-notification procedures. legal disclosure Partially implemented and continuing to develop during the beta period. 05 // Who helps operate the service ## Service providers and infrastructure partners Application, account and API infrastructure Austria Audio processing, media and related infrastructure Germany DNS, content delivery, traffic security and edge services Global service provider Business and transactional email administration Google service Payment processing where paid checkout is active EEA payment provider First-party product analytics where consent applies Resomix-controlled infrastructure Self-hosted publishing software Resomix-controlled infrastructure **Where data is processed.** Core application and audio-processing infrastructure uses providers in Austria and Germany. Some global service providers may process data outside the EEA under the safeguards described in the Privacy Policy. current legal disclosure 06 // Retention & limits ## Deletion depends on the data lifecycle Source audio deleted no later than 24 hours after upload or analysis. Not public, not shared with other users, not used to train PYXIS-1. Retained only as long as reasonably necessary to provide, troubleshoot and secure the requested processing. Retained as necessary for the user-authorised service; removal may follow a user request, Private Library deletion, account termination or the applicable retention schedule. Retained and processed for the authorised purposes and duration defined by the partner agreement and DPA. Retained until the user deletes them, closes the relevant Library or account, or the applicable retention period expires. Retained during the active account and for 30 days following a deletion request, subject to legal obligations. Up to 24 months, then anonymised or deleted. Up to 36 months. Typically up to 90 days, unless needed longer for security investigations or legal obligations. **Legal and accounting obligations** may require some records to be retained after account deletion. Deleting audio does not automatically delete every account, billing, consent, communication or security record. ## What Resomix does not claim today Resomix does not currently publish an uptime SLA or claim a fully redundant high-availability architecture. Backup controls are partially implemented and continue to develop during the beta period. Resomix does not currently claim a complete offsite 3-2-1 backup programme, full media-store recovery or a tested disaster-recovery guarantee. DDEX ERN ingestion and DDEX reporting workflows are not available today. Resomix does not currently claim SOC 2, ISO 27001 or another enterprise security certification. Resomix does not currently offer a public customer-selectable data-residency region or complete data-sovereignty guarantee. Controlled media delivery reduces unauthorised access risk. Resomix does not claim that streamed media is impossible to copy or extract. A public system-status destination is not currently available. 07 // The documents ## The controlling documents are published - [Privacy Policy](https://support.resomix.com/hc/categories/1/3/legal) - [Terms of Service](https://support.resomix.com/hc/categories/1/3/legal) - [Cookie Policy](https://support.resomix.com/hc/categories/1/3/legal) - [Acceptable Use Policy](https://support.resomix.com/hc/categories/1/3/legal) - [Copyright & DMCA Policy](https://support.resomix.com/hc/categories/1/3/legal) - [GDPR Summary](https://support.resomix.com/hc/categories/1/3/legal) - [Refund Policy](https://support.resomix.com/hc/categories/1/3/legal) - [Platform Disclaimer](https://support.resomix.com/hc/categories/1/3/legal) - [Open Source Licensing Transparency](https://support.resomix.com/hc/categories/1/3/legal) [privacy@resomix.com](https://resomix.com/mailto:privacy@resomix.com) [legal@resomix.com](https://resomix.com/mailto:legal@resomix.com) [/partners#contact](https://resomix.com/partners#contact) Reflects the Resomix production-beta policies effective 20 July 2026. The published legal documents control. --- Source: https://resomix.com/trust Site guide for AI systems: https://resomix.com/llms.txt