Contributor privacy

Browsing and downloading sounds does not require an account. To submit a sound, sign in with GitHub or Google. We use the provider account identifier, name, email address, and email verification status to create your account and associate submissions with you.

What becomes public

A published sound includes its title, prompt, synthesis code, audio, metadata, and any public credit you choose. Your sign-in email, private account identifier, login credentials, and unpublished submissions are not part of the public directory.

Account and review records

Account and submission records are stored using Cloudflare. Session cookies keep you signed in. We retain submission ownership and review records so contributors can follow progress and administrators can investigate reports. Administrators can see the submitter’s account identifier and contact email, code, prompt, and review results.

Submissions may be processed by automated services for code and content review. Warning emails to the directory administrator can contain your submission details, contact email, and review findings. Automated checks help surface concerns; they do not establish that a submission is lawful.

Agent access

Agent tokens are stored as hashes and can be revoked from your account. They allow submission and access to your own submission status, but do not grant account management access. Session and abuse-prevention records can include IP addresses and browser information.

Usage analytics

We use PostHog to understand page visits, searches, sound previews and reuse, sign-in provider choices, and contribution steps. Browser identifiers help count repeat visits and follow steps in a session. Explicit sign-in and form events do not include your email, credentials, agent tokens, or draft submission text. Browser analytics respects Do Not Track. Aggregate plays, copies, and download clicks also help order popular sounds.

Requests and corrections

To ask about account data, deletion, or a submission, contact the maintainers through the repository’s contact options. Do not post private credentials or personal information in a public issue. Already published CC0 material may have been downloaded or reused by others.