Privacy, without the funny business.
derpfx is a community soundboard. All community content is user uploaded. Uploaders supply sounds, titles and descriptions; derpfx hosts and reviews submissions. Being user uploaded does not mean content is endorsed, licensed for every use, or guaranteed to be accurate. Preview sounds explicitly labelled “Demo sound” are original generated development fixtures and are excluded from this community-content statement.
Who is responsible?
derpfx is operated by derpfx. For privacy questions, contact [email protected]. You can also use our request form.
What we collect, and why
- Uploads: your sound, title, description and chosen category. We use these to assess, host and play your submission. We do not ask for an account or uploader email. Original filenames are not kept in the sound database. When you choose a file in the uploader, we temporarily process it to check its length and make a private preview. Preparing a preview does not publish it. Temporary source and preview files are deleted after a successful save; abandoned uploads expire after 15 minutes. Only the clip you submit enters the usual upload and review flow.
- Removal and privacy requests: your email address, the sound link, reason and explanation. These are used to investigate, communicate about and keep a record of the request. Do not send passwords, identity documents or unnecessary sensitive information.
- Play counts: we keep a total number of plays for each sound. The total increases when playback starts successfully; it is not a count of unique listeners. We do not keep a long-term individual listening history.
- Abuse prevention: the application creates a keyed hash of a connection IP address for an hourly rate limit. This is pseudonymous data, not an anonymous guarantee. It is not published. Expired database rate-limit records are cleared by scheduled maintenance. Playback permissions and counters are held temporarily in Redis: sessions last up to 30 minutes, sound-specific permissions up to 90 seconds, and counters up to an hour. Session identifiers and connection IP addresses are stored as keyed hashes; temporary permissions associate a session hash with a sound to authorise playback.
- Technical requests: the web server, cluster ingress or hosting provider may process IP addresses, request paths, timestamps, browser information and error details to deliver and secure the service. These technical records are separate from the application’s sound and request database.
Our basis for using information
We rely on legitimate interests to operate a requested community soundboard, prevent abuse and investigate reports, balanced against the rights of affected people. Where processing is required to comply with a legal obligation, that obligation is the basis. The upload permission checkbox records your permission to host the sound; it does not waive anyone’s data protection rights or establish that you own another person’s recording. We do not knowingly seek special-category personal information. Please do not upload it.
What becomes public?
Approved audio, its title, description, category and publication date are publicly accessible. Pending uploads and removal-request contact details are not displayed publicly. A recording can identify people through their voice or what is said: only upload recordings you have the rights and permission to share.
Cookies and tracking
The application uses an essential, signed security cookie to protect submission forms and play-counter requests against forged requests. It expires after approximately six hours. An essential HttpOnly playback cookie lasts up to 30 minutes and is shared with our audio subdomain so that copied audio links alone cannot grant playback. There are no accounts, advertising cookies or analytics cookies in this version. We remember your chosen volume in this browser tab; it is not sent to our server. Custom soundboards use a secret edit link instead of an account. An essential cookie remembers edit access for up to a year, and browser local storage keeps a list of your boards and their edit links on this device. Anyone with an edit link can change that board; anyone with a share link can play it. Board names, button labels, uploaded audio and private reports are stored on our server. Infrastructure providers may use essential security cookies. Your basic analytics preference is saved in local storage on this device.
Basic usage analytics
We collect basic information about visits to public pages so we can understand which sounds and features are popular. This does not use advertising cookies, track you across other websites or record session replays. Custom soundboards, admin pages, upload and removal forms are excluded.
Connection information such as your IP address and browser details is processed to distinguish visits. We respect Global Privacy Control and Do Not Track, and you can opt out on this browser at any time.
Basic analytics are off until the analytics script runs.
How long we keep information
Approved public-library sounds remain available until removed. Custom soundboards expire after 90 days without a sound being played on that board or an edit. Simply opening a board does not reset this timer. When a board expires, its unapproved uploads are withdrawn and deleted by scheduled maintenance; sounds already approved for the public library remain available. Custom-board reports are kept while the concern is open; resolved reports are deleted after the retention period below. Unreviewed public-library-only uploads are rejected and their stored audio deleted after 90 days by scheduled maintenance. Rejected and removed audio is deleted from active storage; limited non-audio metadata can remain to record the moderation decision. Resolved removal requests and their contact details are deleted 90 days after resolution. Open requests are retained while investigation is necessary and must be reviewed regularly.
Infrastructure logs and backups follow their own rotation schedules; records may remain until rotation or replacement. Contact us if you need details about data remaining in those systems. Removal from the live site does not erase copies already downloaded by other people or cached by search engines. Information may need to be retained longer where required by law or a specific dispute; any exception should be limited and documented.
How to request removal
Use the removal request form. Include the exact sound URL, your contact email, the reason and enough detail for us to identify the concern. For copyright claims, identify the protected work and explain whether you own it or are authorised to act. For privacy claims, explain how the recording or accompanying text relates to you. Submit accurate, good-faith information.
The form gives you a reference number and places the report in a private review queue. Sending a report does not automatically delete content. The operator reviews reports, may ask for relevant clarification, and can restrict or remove content where appropriate. Urgent privacy, safety and clearly unlawful-content reports should receive priority. We do not promise a fixed response time that we cannot meet. Removal requests are not published; relevant details may be shared only where necessary to investigate, resolve a dispute or comply with law.
Your rights
Depending on the circumstances, you may have rights to access, correct, erase, restrict or object to processing of personal data, and a right to data portability where applicable. These rights have conditions and exceptions. Contact the operator or use the request form, selecting “Privacy / personal data”; no account is required. We may need proportionate information to verify a request. You can complain to the UK Information Commissioner’s Office, or the relevant data protection authority where you live.
Changes to this notice
We will update this page when the service or its data handling changes. The date above identifies the current version.