Privacy policy

Because it lives in your browser rather than on a server, your favourites are per-browser and per-device. Save something on your phone and it will not appear on your laptop. That is a genuine limitation, and it is the direct consequence of not having accounts.

If your browser blocks site data, in a private window or under strict privacy settings, the favourite button disables itself and says so rather than accepting taps it cannot remember. The site also writes and immediately deletes a tiny throwaway value on load, purely to test whether storage works at all. It holds nothing and does not survive the check.

To clear it: use your browser’s “clear site data”, “cookies and site data”, or “clear browsing data” option for bleepboard.com. In most browsers that setting is under Settings → Privacy. Clearing it deletes your favourites permanently and immediately. There is no copy anywhere else to delete, and nothing for us to do on our end.

Google Analytics 4 is how we know which pages people reach, which sounds are worth writing about next, and whether a change made the site better or worse. It is configured deliberately narrowly, as follows.

• What it records: the pages you view and when, the referring site or search engine that sent you, and technical details about your device such as browser, operating system, device type, screen size and language.
• Approximate location: derived from your IP address, at roughly country, region and city level. The tag is configured with IP anonymisation switched on, which asks Google to shorten the address before it is used, so the full address is not part of the reporting.
• Cookies and local identifiers: Google Analytics stores a randomly generated identifier in first-party cookies, named _ga and _ga_ followed by the measurement ID, so that a returning browser is recognised as the same browser. It is an identifier for a browser, not a name for a person.
• Google Signals is switched off. The tag sets allow_google_signals: false, so analytics data is not joined to signed-in Google accounts for cross-device reporting or advertising audiences. A soundboard does not need that, so it is not enabled.
• Nothing about you personally. We send no name, email address, account or user ID, because the site has none to send.
• Consent comes first where it is required. In the EEA, the UK and Switzerland the analytics storage permission starts denied, and no analytics cookie is written until you allow it. No consent tool is loaded at the moment, so in those regions the permission simply stays denied. The Consent section explains how that works.

The data collected by the tag goes to Google and is handled under Google’s own terms and privacy policy rather than ours. Google publishes its own account of what it collects on sites that use its services: How Google uses information from sites or apps that use our services. We can see aggregate reports in the Analytics interface. We cannot see who you are, and we cannot connect a report row to a person.

Turning analytics off

Blocking cookies for this site, or running a content blocker, stops the tag reporting anything. Google also publishes a Google Analytics opt-out browser add-on, which switches the measurement off in your browser across every site that uses Analytics rather than only this one. Nothing on this site tries to detect or work around either.

The play counter

There is one loose end worth being straight about. When you play a sound, the site fires a single tiny same-origin request intended to count plays, so that the trending list could reflect what people actually play. Nothing is listening at the other end. The counter it was written for was never connected, so the request reaches the static host, finds nothing, and is discarded. It carries only the short name of the sound, with no identifier, no cookie and nothing about you, and even that is currently counted by no one.

Bleepboard is free, and the plan for keeping it free is advertising rather than paywalls or data sales. Advertising brings other companies into the picture, and their behaviour is not something we can promise on their behalf. What follows is true of ad technology generally, and will be true here once advertising is switched on.

• Third-party vendors, including Google, use cookies and similar identifiers to serve and measure ads, including ads based on your prior visits to this website and to other websites.
• Ad exchanges and demand partners sit behind the slot itself. A single ad placement can involve many companies bidding in real time, each of which may set or read its own identifier. That chain is operated by the ad network, not by us.
• We never receive the identifiers. Advertising cookies are set by those companies under their own privacy policies. We cannot read them, we cannot delete them for you, and the opt-out routes below go directly to the parties that can.
• You can opt out of personalised advertising through Google Ads Settings and the industry pages listed below, and through your browser’s own cookie controls.

Which network

The two routes being considered are Google AdSense, which is self-managed, and Mediavine, which is a managed provider that fills the slots through its own script and a long list of advertising partners. The site’s code supports either one, and ships neither until a network and an ID are configured. When that happens, this section will name the network that is actually running and this paragraph will go.

Browser-level controls

Every major browser lets you block or delete third-party cookies, and several block cross-site tracking by default. Those settings sit under Privacy in your browser’s preferences and apply everywhere, not just here. Browser extensions and content blockers go further and can stop advertising and analytics scripts from loading at all. Nothing on this site tries to detect or work around any of that.

Google’s tags support a consent framework called Consent Mode v2, which tells them what they are allowed to store before they load rather than after. Bleepboard sends those defaults from the page head, ahead of any Google script, using four permissions: advertising storage, advertising user data, advertising personalisation and analytics storage.

• In the EEA, the UK and Switzerland, all four default to denied. That covers the 27 EU member states plus Iceland, Liechtenstein, Norway, the United Kingdom and Switzerland. Nothing is stored and no identifier is set until consent is granted, and no consent tool is currently loaded to collect it, so it stays denied. The tags wait briefly for an answer before carrying on.
• Everywhere else the four default to granted, which is the usual posture outside those regions. If you are in one of those places and would rather not be measured, your browser’s own controls and a content blocker will stop the tags loading, and the routes listed above cover ad personalisation.
• Which default applies to you is decided by Google’s tag from your request, not by us. We do not run geolocation of our own, and we never see the result.

The consent banner

No consent management platform is currently loaded. Consent Mode defaults are being sent, so storage stays denied in the EEA, the UK and Switzerland, but there is no banner in which to grant it. We are saying that plainly rather than describing a mechanism that does not exist.

Bleepboard does not sell personal information for money, and never has. California law also covers “sharing”, which is a wider idea: handing identifiers to advertising partners for cross-context behavioural advertising counts, even when no money changes hands and even when the collection happens through the partner’s own code rather than ours.

With no ad network switched on, nothing is being shared in that sense right now. There is no advertising identifier to withdraw and no profile to switch off. The routes below are the ones that will apply when advertising is added, and the browser-level ones are worth setting now regardless, since they cover every site rather than only this one.

The catalogue here is Roblox, Five Nights at Freddy’s, SpongeBob and Minecraft audio, so a good share of the people playing it are children. Bleepboard is a general-audience site rather than one directed at children, but we are under no illusions about who plays a soundboard.

There are no accounts, no sign-up, no profiles, no comments, no uploads and no forms. There is nowhere on this site for a child, or for anyone, to enter a name, an age, an email address or a photograph, because no such field exists. We do not knowingly collect personal information from children. If you believe a child has somehow provided personal information to us, contact us and we will delete it. Realistically the only route is an email sent to one of our addresses, and an email we are asked to delete gets deleted.

Child-directed treatment

Ad networks offer a child-directed setting that turns off personalised advertising for a whole site. Bleepboard is set to standard treatment rather than child-directed. That has no practical effect today, because no ad request is made at all, and it becomes live the moment an ad network is switched on. If the setting changes, this paragraph changes with it, because both read from the same line of configuration.

Whatever the setting, the controls sit with the ad network. We can configure what our account offers. We cannot audit what a third party does with a request, and we will not claim otherwise.

Bleepboard holds no accounts and keeps no user records, so there is normally nothing on our side to look up, correct, export or erase. The favourites list is already yours: it is on your device, we cannot see it, and you can delete it yourself in seconds. Analytics data sits with Google, keyed to a random browser identifier rather than to you, and we have no way to match a report row to a person or to a request from one.

EEA and UK (GDPR)

If you are in the European Economic Area or the United Kingdom, you have the right to access the personal data held about you, to have it corrected or erased, to restrict or object to processing, and to data portability. You also have the right to lodge a complaint with your national data protection authority.

• Access, portability, correction and erasure: we hold no personal data of our own to produce, correct or erase. Your favourites are erased by clearing site data for bleepboard.com in your browser.
• Objection and restriction: there is no profiling or automated decision-making by us. Where advertising or analytics is running, the consent tool and the opt-outs above are how you object to it.
• Withdrawing consent: where consent has been given, you can withdraw it at any time, and it must be as easy to withdraw as it was to give. The privacy controls above are that route.
• Server logs are held by our host, not by us. Requests about them are directed to GitHub, whose privacy statement governs them.

California (CCPA/CPRA)

If you are a California resident, you have the right to know what personal information is collected and how it is used, to request deletion, to request correction, and to opt out of the sale or sharing of personal information. You also have the right not to be discriminated against for exercising any of these, and nothing on this site behaves differently depending on what you have opted out of.

• Right to know and to delete: Bleepboard collects no personal information through accounts or forms, so there is no profile of our own to disclose or delete. Your favourites are deleted by clearing site data.
• Sale or sharing: we do not sell personal information. Nothing is currently shared for cross-context behavioural advertising, because no ad network is switched on. Do Not Sell or Share My Personal Information sets out the controls either way.
• Authorised agents: a request may be made on your behalf. Since there is no account to verify against, an agent request resolves to the same browser-level controls that you can use directly.

Each sound page offers a snippet that puts a small play button on another website as an inline frame. If you are reading this because you met one of those buttons somewhere else: it is a minimal page containing a play button, the sound’s title and a link back here.

The embedded player is a standalone document rather than a normal page of this site, and it does not carry the site’s analytics or advertising code. It sets no cookies, saves nothing to your device, loads no third-party script and does not track you. It does not carry the favourites feature, and it does not send the play request described above. Your browser does fetch the player and the audio file from bleepboard.com, which means the request reaches our host in the same way as any other page request, and is subject to the same server logs described below.

The site the embed appears on is a different matter entirely. That site has its own analytics, its own cookies and its own privacy policy, and none of that is under our control or covered by this page. The same applies to any advertising it runs around the embed.

Bleepboard is a static site hosted on GitHub Pages. Every page is generated ahead of time and published as a plain file. There is no application server, no database, and nothing that could hold a user record even if we wanted one.

Like every web host, GitHub receives the requests your browser makes and keeps standard access logs. These typically include your IP address, the page requested, the time, and your browser’s user-agent string. This is how the web has worked since the beginning: a server cannot send you a page without knowing where to send it.

Those logs belong to GitHub and are handled under GitHub’s privacy statement. We do not have access to them, we cannot query them, and we do not receive any report derived from them. That also means we cannot look up, export or delete a log entry on request. The honest answer is to point you at the host rather than to imply a control we do not have.

This policy changes when the site does, most obviously when analytics or advertising is switched on or switched between networks. The sections above read from the same configuration that decides what actually loads, so they describe the site as it is rather than as it was when someone last remembered to edit this page. The date at the top is set by hand and moves when the substance moves.

Bleepboard is a static site, so an update takes effect when the site is next rebuilt and published, and caches may serve an older copy for a short while after that.

Questions about this policy, or about anything on the site, go to dmca@bleepboard.com. It is the same address used for copyright and content reports, and it is read by a person rather than a ticket queue.