Privacy Policy for DaVoce
Last Updated: October 7, 2026
This Privacy Policy explains how personal data is processed when you use the DaVoce application (“DaVoce,” the “App”).
DaVoce is designed to collect and process as little personal data as reasonably necessary to provide its functionality.
1. Data Controller
The controller responsible for processing personal data in connection with DaVoce is:
Jürgen Dömel
Nordwohlder Heide 54a
27211 Bassum
Germany
Email: info@davoce.app
The current version of this Privacy Policy is available at:
davoce.app/privacy
2. General Principles
DaVoce follows a data-minimization approach.
Where a function does not require identification of the user, DaVoce does not require information such as your name, postal address, telephone number, or email address.
Technical functions such as multi-device synchronization may use pseudonymous identifiers. These identifiers are used to associate devices and sessions technically and are not intended to establish your real-world identity.
3. Apple Music and MusicKit
DaVoce uses Apple Music and MusicKit to provide music-related functionality, including searching for music, displaying music information, controlling playback, and, where authorized by you, accessing features of your personal Apple Music library.
Depending on the features you use and the permissions you grant, the following information may be processed:
* songs, albums, artists, and other music metadata;
* music searches;
* playback information;
* playlists and contents of your music library, where access has been authorized;
* favorites and similar Apple Music information, where required for a feature.
Access to Apple Music is limited to the permissions you grant.
Authentication with Apple Music is handled using Apple’s MusicKit mechanisms. DaVoce does not receive or store your Apple Account password.
Apple independently processes information in accordance with its own privacy policies and terms.
Where processing is necessary to provide functionality requested by you, the legal basis under the General Data Protection Regulation (“GDPR”) is Article 6(1)(b). Where your consent is required, processing is based on Article 6(1)(a).
4. Sheet Music Purchases
DaVoce may allow you to browse, purchase, and display digital sheet music offered by third-party sheet music publishers or retailers.
Where this feature is used, DaVoce may display product information and catalog content provided by the respective sheet music provider within the App.
Purchase Processing
Depending on the purchasing method offered, information necessary to process and verify a purchase may be exchanged between DaVoce and the respective sheet music provider and, where applicable, Apple.
This information may include:
* the selected sheet music or product identifier;
* a pseudonymous user or transaction identifier;
* purchase and transaction information;
* information required to verify that you are entitled to access purchased sheet music.
Payment information is processed by the respective payment provider or purchasing platform. DaVoce does not receive or store complete credit card or other payment credentials.
The respective sheet music provider or payment provider may process personal data independently in accordance with its own privacy policy.
Purchased Sheet Music
After a successful purchase, the purchased sheet music may be downloaded and stored within DaVoce so that it can be displayed and used in the App.
Where purchased sheet music is stored exclusively on your device, the sheet music file itself is not transmitted to or stored on DaVoce’s backend servers.
DaVoce may retain a pseudonymous record of purchased products or access entitlements where this is necessary to verify purchases, restore purchased content, or make purchased sheet music available across your devices.
Such information is used exclusively to provide and manage the sheet music functionality and is not used for advertising, marketing, or behavioral profiling.
Additional information about the respective sheet music provider and any data exchanged with that provider will be made available when the sheet music purchasing functionality is introduced.
5. DaVoce Backend Services
Certain DaVoce features communicate with DaVoce backend servers.
These may include:
* synchronization between your devices;
* remote-control and session functionality;
* shared sessions;
* music metadata;
* artist, track, and genre information;
* technical security and abuse-prevention functions.
For these purposes, DaVoce may process technical information such as:
* pseudonymous user or device identifiers;
* session identifiers and session information;
* timestamps;
* requested resources;
* technical connection information.
Pseudonymous identifiers are used to provide technical functionality and are not intended to identify you by name.
6. Server Logs and IP Addresses
Whenever the App communicates with a server, your IP address is necessarily transmitted as part of the Internet connection.
DaVoce’s backend infrastructure may process technical server logs containing information such as:
* IP address;
* date and time of a request;
* requested API endpoint or function;
* HTTP status code;
* technical error information;
* security-related information.
This information is used to operate and secure the service, diagnose technical problems, and detect or prevent misuse and attacks.
The legal basis is Article 6(1)(f) GDPR. Our legitimate interest is the secure and reliable operation of DaVoce.
Server log data is generally deleted after no more than 31 days.
Data may be retained for a longer period where reasonably necessary to investigate a specific security incident or where retention is required by law.
7. Multi-Device Use and Remote Sessions
DaVoce allows you to use the App on multiple devices and may allow one device to control playback taking place on another device.
To provide this functionality, the following information may be exchanged through the DaVoce backend:
* pseudonymous user and device identifiers;
* session identifiers;
* session status;
* playback and control commands;
* queue information;
* music metadata required for synchronization.
This information is used to associate devices with the appropriate session and synchronize the relevant functionality.
8. Shared Sessions
DaVoce may allow you to invite other people to participate in a shared playback session.
When you join or participate in such a session, information necessary to provide the shared functionality may be transmitted through the DaVoce backend and exchanged with other participants.
Other participants may be able to see information such as:
* music currently playing;
* tracks selected by participants;
* tracks in the shared queue;
* changes made to the shared session.
Only information necessary to provide the shared-session functionality is processed for this purpose.
9. Sonos and Local Network Devices
DaVoce can discover and control compatible Sonos and other playback devices on your local network.
Depending on the device and functionality used, DaVoce may locally process information such as:
* device or room name;
* local IP address;
* device identifier;
* device model;
* group membership;
* playback status;
* volume level;
* mute status.
Where this information is used exclusively for local device discovery and control, it is not transmitted to the DaVoce backend.
iOS may require your permission before DaVoce can access devices on your local network.
10. Music and Usage Data
DaVoce processes music-related information where necessary to provide the features you use.
This may include:
* search queries;
* selected artists, albums, and tracks;
* playback history;
* playback queues;
* favorites;
* playlists;
* playback-related preferences.
Where such information is stored only locally on your device, it is not transmitted to DaVoce.
Where you use functionality requiring synchronization or shared sessions, the information necessary to provide that functionality may be transmitted to the DaVoce backend.
DaVoce does not sell Apple Music user data or use it for personalized advertising.
11. Crash Reports and Diagnostics
DaVoce does not use third-party crash analytics or user analytics services such as Google Analytics, Firebase Crashlytics, or Sentry.
For diagnosing crashes and technical problems, we may use diagnostic information made available through Apple’s operating systems and developer services, including TestFlight, App Store Connect, Xcode, and related Apple diagnostic facilities.
Whether diagnostic information is transmitted to Apple may depend on your device settings and the Apple service being used.
Apple processes this information in accordance with its own privacy policies.
DaVoce does not use crash or diagnostic information to create advertising or behavioral profiles.
12. Analytics, Tracking, and Advertising
DaVoce does not use third-party advertising or behavioral tracking services.
DaVoce does not:
* sell personal data;
* sell music usage data;
* create profiles for targeted advertising;
* use third-party advertising networks to track users across apps or websites.
If this changes in a future version of DaVoce, this Privacy Policy and the applicable App Store privacy disclosures will be updated accordingly.
13. Device Permissions
Depending on the features you use, DaVoce may request system permissions provided by iOS or iPadOS, including:
* access to Apple Music or your media library;
* access to devices on the local network;
* microphone access where required for music-recognition functionality;
* other permissions required by features you explicitly choose to use.
Permissions are used only for the functionality for which they are requested.
You can review or revoke permissions through your device settings. Revoking a permission may prevent the corresponding DaVoce feature from functioning.
14. Service Providers and Recipients
Personal data is disclosed to third parties only where necessary to provide DaVoce, where required by law, or where you have authorized the disclosure.
Relevant recipients may include:
Apple
Apple Inc. and its affiliated companies provide Apple Music, MusicKit, the App Store, TestFlight, and related platform and diagnostic services.
Apple processes data in accordance with its own privacy policies and applicable terms.
Backend Hosting Provider
DaVoce uses external infrastructure services to operate its backend and database.
Render Services, Inc. is currently used to provide backend hosting infrastructure.
Information processed by the DaVoce backend may therefore be processed on infrastructure provided by Render.
We require service providers processing personal data on our behalf to provide appropriate data-protection and security safeguards.
15. International Data Transfers
Some service providers may process information outside the European Union (“EU”) or European Economic Area (“EEA”), including in the United States.
Where personal data is transferred internationally, we rely on an applicable lawful transfer mechanism as required by Articles 44–49 GDPR. Depending on the provider and circumstances, this may include an adequacy decision by the European Commission, participation in an applicable recognized data-transfer framework, or appropriate safeguards such as the European Commission’s Standard Contractual Clauses.
16. MyStage and User-Uploaded Content
DaVoce provides a feature called “MyStage” (also referred to as “My Tracks”) that allows you to import your own audio files into the App. Supported files may include FLAC, MP3, M4A, and similar formats supported by the App.
When using MyStage, you may enter or provide metadata such as:
* track title;
* artist name;
* album name;
* genre;
* song lyrics;
* recording date;
* artwork;
* notes and other track information.
You may use MyStage purely as a private library feature. In that case, the uploaded content is processed only to provide the requested library, storage, synchronization, and playback functionality.
You may also choose to transmit selected content to the DaVoce backend for editorial staging and possible publication. Uploaded audio files may include the original file and, where required for technical purposes, a transcoded FLAC version. Individual audio uploads are limited to 50 MB. Artwork uploads may be limited to 10 MB.
For staging and publication, DaVoce may process information relating to an artist profile, including:
* artist or stage name;
* biography;
* portrait or other profile image;
* selected visual background;
* publication or staging status;
* a public URL or slug used to identify the published artist page.
17. Staging, Review, Publication, and Withdrawal
If you submit MyStage content for publication, DaVoce creates a staging record containing the information necessary to review the submission. This may include an immutable snapshot of the submitted artist profile and tracks, technical audio hashes, rights declarations provided by you, automated review results, and audit events documenting relevant actions.
Publication is performed only after the applicable review and release process has been completed. Once approved and published, the artist name, biography, profile image, track list, and the published audio content may be publicly accessible on a DaVoce artist page and playable through browser-based audio streaming.
You may withdraw publication or visibility using the functions provided by DaVoce, including unpublish, takedown, suspension, or revocation of a share link, as applicable.
A share link may be protected by a token and the associated share page may use a noindex directive to reduce indexing by search engines. This does not constitute a guarantee that content cannot be copied, cached, linked to, or made available by third parties after publication.
The legal basis for publication-related processing is, where applicable, your consent under Article 6(1)(a) GDPR. Consent may be withdrawn with effect for the future by using the available withdrawal, deletion, suspension, unpublish, or takedown functions. A rights declaration associated with a submission may be retained as evidence of the basis on which publication was requested and approved.
18. User Identity and Authentication for MyStage
The standard DaVoce account flow does not require your real name, email address, or password. For pseudonymous technical account management, DaVoce may use a hash of an iCloud account identifier (“icloud_hash”), together with a device identifier.
For authenticated device access, DaVoce may issue short-lived bearer tokens that are stored in the iOS Keychain and may typically remain valid for approximately 24 to 48 hours.
Administrative access to backend functions may use Passkeys based on WebAuthn. Optional email aliases may be stored for administrative invitation messages.
Pseudonymous identifiers are used to provide account, device, synchronization, and security functions. They are not intended to establish your real-world identity, but pseudonymous data can still constitute personal data under the GDPR where it can be attributed to a person.
19. Enrichment of MyStage Metadata
To improve metadata quality, DaVoce may enrich artist and track information using publicly available sources or external metadata services. Depending on the function, search terms such as artist names, track titles, or similar metadata may be transmitted to those services.
Possible services include MusicBrainz, Wikimedia or Wikipedia, the Apple Music API, and LRCLIB for lyric-related information. Account identifiers and authentication credentials are not intentionally transmitted to these services for the enrichment functions described here.
A previously used Groq AI endpoint is currently marked as retired and is not intended to receive MyStage content or metadata in the current implementation. Before any reactivation or use of an AI service for such processing, the applicable privacy information and legal assessment will be updated.
Where enrichment is based on the legitimate interests of DaVoce, Article 6(1)(f) GDPR may apply. You may object to such processing where the legal requirements for an objection are met.
20. MyStage Deletion, Suspension, and Retention
The MyStage deletion function (“Remove”) is designed to delete the relevant track from the App and, where applicable, from DaVoce backend storage and related catalog records. This may include the local device file, library entry, catalog metadata, audio data, artwork data, and related backend records.
“Suspend” does not delete the content. Suspension only removes the relevant content from public visibility while the associated device and backend data remain stored. Suspension may be reversed by restoring visibility (“Unsuspend”).
For published artist pages and shared access, DaVoce may provide functions to unpublish content, perform a takedown, or revoke a share link. Audit records documenting publication, approval, withdrawal, and security-relevant actions may remain stored where necessary to demonstrate the history of processing or to protect legitimate interests.
Audit events are intended to be append-only. Their precise retention period and any later anonymization procedure are subject to the storage and documentation rules defined by the controller.
21. Logs, Diagnostics, and Local Usage Statistics
Backend services may create technical logs containing information such as IP address, date and time, requested resources, technical errors, and security-related information. Log retention is configurable by the controller within the applicable technical configuration; the configured period may range from 1 to 3650 days. Security-sensitive values such as share tokens are redacted from logs where implemented.
DaVoce uses local diagnostic information for troubleshooting and development. iOS diagnostic logs may be available locally through debug-related views. Crash reports containing device-related identifiers may be made available to Apple only where permitted by your device or Apple diagnostic settings.
Listening statistics such as played track, genre, and time of playback are intended to remain on your device. DaVoce uses these local data for features such as local recommendations and does not transmit them to the DaVoce backend unless a separate feature explicitly requires such synchronization.
22. Data Security and Technical Measures
DaVoce uses technical and organizational measures designed to protect MyStage and other personal data against unauthorized access, alteration, disclosure, loss, or destruction.
Depending on the current implementation, these measures include HTTPS-encrypted transport, API-key based access controls, short-lived device bearer tokens, role-based administrative access, Passkey authentication for administrative users, rate limiting, CSRF protection, redaction of security tokens in logs, container image scanning as part of the deployment process, and protection of secrets against storage in source repositories or logs.
23. Service Providers and Possible International Transfers
The DaVoce backend and database are currently operated using Render infrastructure. The precise hosting region and the applicable data-processing agreement with Render are relevant to the data protection assessment and may determine whether an international transfer takes place.
Where external enrichment services are used, they may receive search terms or metadata required for the requested enrichment function. The respective providers may process data under their own privacy policies and terms.
Administrative invitation emails, where used, are sent through the SMTP provider configured by the controller.
Where personal data is transferred to a country outside the EU/EEA, DaVoce will rely on an applicable transfer mechanism under Articles 44–49 GDPR, such as an adequacy decision, an applicable recognized data-transfer framework, or appropriate safeguards such as Standard Contractual Clauses, as applicable.
24. Retention and Backup
Personal data is retained only for as long as necessary for the purpose for which it was processed, unless a longer period is required by law or is necessary for a documented legitimate interest.
The following retention settings are relevant in particular:
Server logs: normally retained only for the configured period; the current DaVoce implementation supports a configurable range from 1 to 3650 days.
Audit events: retained for as long as necessary for documenting publication, withdrawal, security, or other relevant events. A final default retention period and an anonymization concept for older audit data are to be defined by the controller.
Backups and database retention: the retention period depends on the infrastructure and backup configuration and must be documented separately.
Local MyStage data: remains on the device until removed by the user, by the App, or through deletion of the relevant data, depending on the type of data.
25. Your Rights and MyStage
Where the GDPR applies, you may exercise the rights described in this Privacy Policy, including access, rectification, deletion, restriction, objection, and data portability where the statutory requirements are met.
DaVoce currently provides technical functions for deletion, suspension, unpublication, takedown, and withdrawal of share access. A dedicated user-facing data export function for Article 20 GDPR is not currently provided.
Requests concerning personal data stored by DaVoce can be sent to info@davoce.app.
26. Children, Third-Party Content, and Rights to Uploaded Material
MyStage is not specifically directed at children. Where legally required, the applicable rules regarding parental or guardian consent apply.
You are responsible for ensuring that you have the necessary rights to the audio files, lyrics, artwork, artist names, biographies, photographs, samples, cover versions, and other material that you upload or submit for publication.
A rights declaration or other statement provided during staging records the basis asserted by you for the requested publication. Such a declaration does not itself create or transfer copyright or other rights and does not replace any legal permission required from third parties.
The controller should define and communicate any applicable minimum age for MyStage participation and the handling of uploads containing material created by or depicting third parties.
27. Open Data-Protection and Governance Settings
The following operational details form part of the controller’s data-protection documentation and should be maintained consistently with the actual implementation:
* the responsible controller and data-protection contact;
* the hosting region and applicable agreement with the backend hosting provider;
* the SMTP provider used for administrative invitations;
* defined retention periods for audit events, backups, and logs;
* the administrator group with access to backend and staging data;
* the final procedure and retention period for deletion or anonymization of audit records;
* whether and how a user-facing data export under Article 20 GDPR will be offered;
* age restrictions and procedures for content uploaded by or relating to third parties;
* where appropriate, whether a data-protection impact assessment is required for public audio publication and associated user-generated content.
28. Data Security
We use appropriate technical and organizational measures designed to protect personal data against unauthorized access, alteration, disclosure, loss, or destruction.
Communication between the DaVoce App and the DaVoce backend is generally performed using encrypted network connections.
Security measures are reviewed and adapted as the service and relevant technology evolve.
29. Your Rights Under the GDPR
If the GDPR applies to the processing of your personal data, you may have the right to:
* obtain information about personal data processed about you (Article 15 GDPR);
* correct inaccurate personal data (Article 16 GDPR);
* request deletion of personal data (Article 17 GDPR);
* restrict processing (Article 18 GDPR);
* receive certain personal data in a portable format (Article 20 GDPR);
* object to certain processing based on legitimate interests (Article 21 GDPR).
Where processing is based on your consent, you may withdraw that consent at any time with effect for the future.
To exercise these rights or ask questions regarding privacy and data protection, contact:
info@davoce.app
30. Right to Lodge a Complaint
You have the right to lodge a complaint with a competent data-protection supervisory authority if you believe that the processing of your personal data violates applicable data-protection law.
You may in particular contact the supervisory authority responsible for your place of residence or the authority responsible for the controller.
31. Children
DaVoce is not specifically directed at children.
Where consent is legally required for the processing of personal data relating to a child, the applicable legal requirements regarding parental or guardian authorization apply.
32. Changes to This Privacy Policy
We may update this Privacy Policy when DaVoce’s functionality, service providers, technical infrastructure, or applicable legal requirements change.
The current version will be made available at:
davoce.app/privacy
Material changes will be communicated through appropriate means where required by applicable law.