Overview
Soundling is developed by Richard van der Dys. Your privacy is simple: Soundling does not collect, transmit, sell, or share your personal information.
Microphone access and recordings
Soundling requests microphone access only when you choose to record a sound. The audio is processed locally on your device so it can be played across the app’s keyboard.
- Recordings are not uploaded to a server.
- Recordings are not shared with the developer or third parties.
- Recordings are held temporarily while you use the app and are not retained after the app closes.
You can deny or revoke microphone access at any time in iOS Settings. Recording new sounds will not work without that permission.
Information collection
Soundling does not require an account and does not collect names, email addresses, contact information, precise location, device identifiers, usage history, or recorded audio. The app does not contain advertising, analytics, or tracking technologies.
On-device functionality
Audio processing, pitch analysis, silence trimming, playback, and app preferences needed for the current session occur on your device. Soundling does not depend on a remote account or cloud service for its core functionality.
Children’s privacy
Soundling is designed to be enjoyable for people of different ages, including families. Because the app does not collect personal information or upload recordings, it does not knowingly collect personal information from children.
Third-party services
The iOS app uses Apple system services and the open-source Capacitor runtime to provide native app functionality. Soundling does not use third-party advertising, analytics, social login, or data-broker services.
Security and retention
Because Soundling does not transmit or maintain a user database, there is no developer-operated store of personal data or recordings to retain. You remain responsible for the security of your device and its operating-system permissions.
Changes to this policy
This policy may be updated when Soundling’s features or legal requirements change. The revised policy will be posted on this page with a new effective date.
Contact
Questions about this policy can be sent to richard.vanderdys@gmail.com.