SoundZapper Privacy Notice
Version 1.2 · 2026-10-12
Who is responsible
Andreas Geißinger, Schumannstr. 9, 81679 Munich, Germany, is responsible for SoundZapper. Contact: [email protected].
Community feedback and Discord sign-in
The feedback board uses Discord sign-in to identify contributors and keep voting fair. We receive your Discord identifier and display name; we do not ask Discord for your email address or link this sign-in to a SoundZapper app account. A secure sign-in cookie keeps your feedback session for up to 30 days. It is separate from your app sign-in. We use a request check tied to that session to protect changes to the board.
Your display name, ideas, descriptions, optional Loom share links, vote counts and attached screenshots are visible on the board. Please leave personal details and other people’s copyrighted material out of your screenshots. We resize screenshots and remove embedded image metadata. Screenshots are held in Cloudflare R2; unposted uploads are available only to their uploader for up to 24 hours, and posted screenshots are visible with the idea. Expired unposted uploads are removed through a retrying cleanup process. A Loom link opens the video service only when you choose to follow it; we do not embed its player.
We use this information to review suggestions, manage community feedback and prevent abuse. Discord handles its own sign-in service; our hosting providers deliver the board and store its records. We keep feedback while needed for these purposes. Contact us to request removal or exercise your privacy rights. Signing out clears your board session; it does not delete your public contributions.
Your waiting list request and invitation
When you apply for access, we collect your name, email, computer type, main DAW, music genres, and the explanation you write about using SoundZapper. We use these details to review applications, manage available places, and contact you with an invitation. Requests do not subscribe you to advertising. We also process connection information to protect the form from abuse. Please avoid including sensitive information in your explanation.
Waiting list details are held by the SoundZapper service and its hosting providers. Invitations and correspondence are handled through our email service, Gmail. Cloudflare delivers the website and downloads. We keep requests while needed to manage access and correspondence; no automatic deletion schedule is currently implemented. You can contact us to withdraw your request or exercise your privacy rights. We rely on our legitimate interest in managing applications and protecting the service; account setup is needed to provide the access you request.
The invitation page receives a one-use secret from your email link. It removes the secret from the address bar and sends it to our service in the request body. Website sign-in tokens stay in the current page’s memory and are not saved in browser storage. The download portal checks account access; installer links use public delivery infrastructure and may be copied.
Your account and access
The beta requires an account and an online account check. We process your email, password credentials, account identifier and access status to register you, sign you in and manage beta access. The app keeps a sign-in token on your computer; your password is sent for registration or sign-in, not included in usage reports. Service connections also expose connection information such as IP addresses to the servers receiving them. Account processing is necessary to provide the beta service you request (Article 6(1)(b) GDPR). Security and abuse prevention serve our legitimate interest in protecting the service (Article 6(1)(f) GDPR).
Installed app and registered devices
When an updated app signs in or checks its account online, it can report its app version, operating-system platform and CPU architecture. We associate these self-reported details and the last online contact time with its registered installation and your account. The installation identifier is a randomly generated UUID saved by the app, not a hardware serial number. Older clients may not report these details. We use them to support updates, manage account access and review possible misuse. Unusual device counts are review signals, not proof of misuse or automatic grounds for blocking access.
A registered-device count describes saved sign-in sessions, not an exact count of physical computers. These details remain with the session until it is removed, for example by signing out or revoking access. We do not keep a separate lifetime history of this operational metadata. This processing supports account service and security for the purposes described above.
Your library and local files
Preset scanning, preview rendering and sound analysis run on your computer. Your original preset and audio files are not automatically uploaded as usage telemetry. The app stores previews, analysis, preferences and library information locally. Local diagnostic logs can include full file paths and error details. Exporting a support log saves a file locally; we receive it if you choose to send it to us. Please review it before sharing.
Beta usage reports
During the beta the app sends feature-use events, app and operating-system information, scan and pack statistics, preset and pack names, interaction events and error reports to the SoundZapper service. Reports use an installation identifier and, where available, your account identifier. Automatic usage reports exclude audio and full file paths. These reports help us investigate faults and improve the beta; there is no separate analytics switch in this beta.
We rely on our legitimate interest in maintaining and improving the beta (Article 6(1)(f) GDPR), subject to your right to object. Accepting the Beta Terms is not a waiver of your privacy rights or a substitute for consent where the law requires consent. Contact us if you wish to object or ask about your reports.
Website, downloads and service providers
The public website uses Cloudflare Pages; update downloads use Cloudflare R2 and its public delivery infrastructure. These services process connection data needed to deliver pages and downloads and protect the service. The app also contacts our account and beta service. Hosting and infrastructure providers may process data on our behalf. If you use separately offered Store or payment features, the information shown for that transaction also applies.
The website does not add advertising pixels or visitor analytics. If you email us, we process your message and address to respond or provide the information you requested. We do not sell your personal data.
Storage and deletion
Local preferences and library data remain on your computer until you remove them. Local support logs rotate to limit their size. The local analytics queue is capped at 500 events and removes events after successful delivery; this is not a promise about deletion from the server.
We retain account information while it is needed to provide access, and retain usage reports and support correspondence for the purposes described above. Retention depends on the need to investigate faults, resolve requests, meet legal obligations or establish or defend legal claims. No fixed automatic server-side deletion period is currently implemented. You can request deletion at the contact address above; we will explain any lawful reason why particular data must be kept.
Your rights
Depending on the applicable conditions, you can request access, correction, deletion, restriction of processing and portability of your data. You may object to processing based on legitimate interests, including beta usage reporting. Where processing requires consent, you may withdraw it for the future. You may complain to a data-protection supervisory authority, including the Bavarian State Office for Data Protection Supervision (BayLDA), or the authority where you live or work. Contact us at [email protected] to exercise your rights. Withdrawing from the beta does not remove these rights.