Chrome Extension Privacy Policy
What the AudioPad extension reads, sends, and stores when you look up token audio.
This policy covers the AudioPad browser extension and its token audio lookup.
Scope and purpose
This policy applies to the AudioPad Chrome extension. Its single purpose is to find and play public audio associated with an AudioPad token. It supplements the general AudioPad Privacy Policy.
The extension reads a supported page only after you open its popup. It does not monitor pages in the background or autoplay audio.
Last updated: October 3, 2026.
Data the extension handles
When you open the popup on a supported token page, the extension checks the current tab URL and, on Axiom or Padre, inspects relevant page elements to identify the token contract address (CA). You can also enter a CA manually.
The extension sends only the CA to the AudioPad API at audiopad.fun to look up public token and audio details. It does not send the full page, the original page URL, cookies, wallet credentials, or browsing history to AudioPad.
Your light or dark theme preference is stored locally with Chrome storage. It is not synced to AudioPad.
How AudioPad uses the data
AudioPad uses the CA to find the matching confirmed token record and return its public artwork and audio details. The extension keeps the detected or entered CA in popup memory while the popup is open; it does not save the CA as an extension setting.
AudioPad does not use extension lookup data for advertising, behavioral profiling, credit decisions, or lending decisions, and does not sell it.
API requests, network data, and media providers
When the API receives a lookup, the request includes the token CA and normal connection information such as the client IP address. AudioPad derives a keyed HMAC identifier from the client IP for API rate limiting and stores that identifier with request counters and an expiry value; the rate-limit database does not store the raw IP address. Hosting and network providers may process their own request logs under their service settings.
The extension may request artwork and audio from public media URLs. Those gateway operators receive standard connection information and the requested content identifier. Public IPFS content may also be accessible to others.
AudioPad hosts its API on Vercel. See Vercel's Privacy Notice for information about its infrastructure processing. For broader AudioPad data practices, see the general Privacy Policy. For background on IPFS network privacy, see the IPFS privacy documentation.
Storage and retention
The theme preference remains in Chrome's local extension storage until you clear the extension's data or remove the extension. The CA is held in popup memory for the lookup and is not saved by the extension.
AudioPad's rate-limit records include an expiry value, but AudioPad does not currently publish a fixed deletion period for those records or for hosting-provider request logs. Their retention depends on database cleanup and provider configuration. AudioPad will update this policy if those retention practices are defined or materially change.
Your choices and contact
You choose when to open the extension and can paste a CA manually instead of having AudioPad inspect a supported page. You can clear the locally stored theme preference by clearing the extension's data in Chrome or removing the extension.
For privacy questions or requests, contact audiopad.support@gmail.com. AudioPad may update this policy when its data practices change.