privacy
short version: this site collects nothing. the players are third-party. here is what their policies disclose and what i observed.
_this site
- no analytics, no cookies, no forms, no remote fonts, no logs on my side.
- static files only. source is public: github.com/chmikiro/petrichaos.
- hosting (this site is served live from source above): the host may keep standard request logs i can't control.
- nothing from soundcloud or audiomack loads until you click "load player". 2 hosts strictly scoped as frames.
_test setup
- browser: ironfox v157.0.1, private browsing.
- tools: firefox network log, canvasBlocker v1.12 log, localcdn log, 1hosts dns lists (on nextdns), ublock origin logs, ghostery logs.
- tested 2026-10-10, one platform per run, player clicked manually.
- my own observations, not an audit.
_soundcloud
what their privacy policy says (paraphrased):
- when you open a page with a soundcloud widget, they may receive personal data about you, including which site you were on.
- the widget may recognize you to fetch your library and knows when you interact with it.
- they log ip, access times, browser, os, device info and referring page, even without an account.
- they use cookies, pixels and local storage, and may let partners do the same.
what i observed:
- repeated screen and canvas reads logged by my fingerprint blocker. not needed for playback, but... it's common practice.
- requests to api-widget.soundcloud.com/me. looks like a logged-in-user lookup. flagged as a tracker by most blocking lists & network filters.
- requests to dwt.soundcloud.com/js. listed as a tracker in 1hosts lite, the low-false-positive tier (so also in xtra). not flagged by the other lists use. no idea what it does.
direct link, no embed: soundcloud.com/petrichaos
_audiomack
what their privacy policy says (paraphrased, version effective 2020-12-23):
- visitors without an account may have ip, browser or device type, os and carrier collected.
- usage data can include geolocation, cookie data, urls visited, the previous site and interactions with third-party widgets and ads.
- ad providers may get browser name, language, genre and location. they say they don't sell personal data.
- they share hashed email, ip and browser info with identity partners such as liveramp, which can return an identifier stored in a first-party cookie.
- they use cookies, pixel tags, web beacons and web storage, and don't respond to do not track.
what i observed:
- no fingerprinting activity detected by my tools.
- mostly ad and analytics requests: edge.aditude.io (load.js), synchrobox.adswizz.com (register2.php), cdn.adswizz.com (synchroclient2.js), googletagmanager.com (gtag), securepubads.g.doubleclick.net (gpt.js).
- all of the above was blocked
- my tools don't see server-side cookies or data sharing between companies, so "no fingerprinting detected" is not a clean bill of health.
direct link, no embed: audiomack.com/petrichaos
_caveat
both platforms can change their code or policies at any time. check with your own tools if it matters to you (it should).