Destroy the SilenceSoundMemes privacy
Privacy without the mystery box.
What SoundMemes collects, why it is used, where it goes, and the choices you have.
The short version
Your email stays private. Your public contributions do not.
You can browse, search, play, and download available sounds without an account. If you create an account, we use the information needed to sign you in, secure your account, show the profile you choose, and operate your contributions.
We do not sell personal information. We do not use Google account data for advertising.
Information we handle
Account and profile data
For email sign-in, we process your email address and authentication records. For Google sign-in, we receive the Google account identifier, email address, and basic profile details supplied through Google and our authentication provider. We do not request access to Gmail, Google Drive, contacts, calendars, or other Google product content.
Your chosen display name, handle, icon, and bio may appear publicly. Your email address does not.
What you add
Uploads and community activity
We store sounds, titles, descriptions, tags, source details, votes, suggestions, reports, and other information you submit. Published uploads and their public metadata can be seen, played, downloaded when enabled, and connected to your public profile.
Reports, moderation history, security records, and private draft information stay restricted to the people and systems that need them.
How we use it
Run the product, protect the community, improve the experience.
We use account data to authenticate you, create and manage your profile, attribute contributions, prevent abuse, respond to requests, and keep the service secure. We use contribution data to publish and organize sounds, situations, soundboards, and related metadata.
Optional analytics starts only after you choose “Allow analytics.” It records a limited set of page, playback, search-result, and sharing events without sending search text, audio, email addresses, or profile details. You can change that choice from the footer.
Providers
Who helps us operate SoundMemes
Supabase provides authentication, database, and server-function infrastructure. Cloudflare provides storage, delivery, and security services. Vercel hosts the public site. Resend delivers sign-in emails. Google provides Google sign-in and, only when you consent, Google Analytics.
These providers process information for the services they supply and may handle it in countries other than yours under their own legal safeguards.
Browser storage
Sign-in and preference data on your device
SoundMemes stores your sign-in in local storage so you stay signed in when you return. Unfinished email and Google sign-ins use temporary session storage. Email-request cooldowns and the analytics choice are stored in local storage. Providers may also use cookies or similar technologies for authentication, security, and delivery.
Retention and control
Keep what is needed, remove what is not.
We keep account information while the account is active and retain other records only as long as reasonably needed to operate the service, meet legal obligations, resolve disputes, prevent abuse, and maintain security. Withdrawing an upload removes it from public SoundMemes surfaces; restricted records or backup copies may remain for a limited period where they are needed for those purposes.
You can update profile details from your account and withdraw eligible contributions from your contribution history. Depending on where you live, you may also request access, correction, deletion, restriction, objection, or portability for personal information.
Young users
Use an account only when local law allows it.
If you are not old enough to consent to data processing where you live, use SoundMemes only with the involvement and permission of a parent or legal guardian. Do not create an account or upload personal information when local law does not allow you to do so.
Questions and requests
Contact us
Email admin@escalera.ai for privacy questions or personal-data requests. For a problem with a specific sound, use the report page so we can identify the exact upload.
Effective August 30, 2026. We will update this page when our data practices materially change.