Bandkit Privacy Policy

Bandkit is a Chrome extension that adds playback, playlist, cart-recovery, listening-history, appearance and DJ controls to Bandcamp pages. This policy explains the information Bandkit handles to provide those features.

Information Bandkit handles

Bandkit may read and process the following information from Bandcamp pages that you visit:

• Bandcamp page URLs and page type.
• Track, release and artist metadata, including titles, artwork URLs, durations and Bandcamp links.
• Bandcamp-provided audio stream URLs for tracks that are currently available to play.
• Cart product information, including item names, prices, currencies and selected product options. Bandkit does not collect payment card details, billing addresses or Bandcamp passwords.
• A signed-in fan's public Bandcamp username or feed URL when needed for the optional feed-homepage feature.
• Playback actions and listening activity used for the visible queue, player, playlists, DJ tools and local activity log.
• Settings, layouts, themes, playlists, cart backups, analysis results and other content that you deliberately create in Bandkit.

Bandkit handles this information only on Bandcamp pages and only to provide its user-facing Bandcamp companion features.

How information is used and stored

Bandkit stores settings, saved playlists, cart backups and listening activity in Chrome's local extension storage on your device. Current playback state may be kept in Chrome's session storage so playback controls can continue across Bandcamp navigation. Audio analysis for BPM, musical key and waveforms happens locally in the extension.

Bandkit does not collect or store bank account details, payment-card numbers, passwords or Bandcamp cookies. Bandcamp handles purchases and payment information on its own pages.

The optional Settings → Support → Support Bandkit link opens a Stripe-hosted page for a one-off tip supporting Bandkit's continued development. Bandkit does not receive, process or store payment-card, billing or payment credential information. Payment information is provided directly to Stripe only if you choose to use its external checkout.

Chrome's local extension storage is Bandkit's live working copy and is not removed by normal cache, cookie or browsing-history clearing. Users can manually create one portable BandKit Backup.json file containing their playlists, carts, current state and deletion history. Bandkit writes the file only when the user chooses Save, and reads a selected file only when the user chooses Restore. Restoring merges saved playlists and carts into the current Chrome copy rather than replacing the whole local library. Bandkit can show an optional periodic reminder to save a fresh file.

Bandkit does not operate an analytics service or developer server. The developer does not receive the settings, playlists, cart backups, activity or playback data stored by the extension. Bandkit does not sell data, use data for advertising or build advertising profiles.

Network connections and sharing

Bandkit communicates directly with Bandcamp and Bandcamp's bcbits.com media hosts over HTTPS to load the pages, metadata and audio needed for the features you request. These services receive ordinary network information such as your IP address as part of serving their content and are governed by Bandcamp's privacy policy.

The optional Settings → Feedback → Send feedback link opens a public Notion form operated by Notion Labs, Inc. Nothing is sent merely by opening Bandkit. If you choose to submit the form, the project, request type, description and any attachment you add are sent to Notion and intentionally published in Bandkit's public feedback list. Do not include personal, confidential or sensitive information. Notion receives ordinary network information such as your IP address and handles submitted content under Notion's privacy policy.

The optional Settings → Support → Support Bandkit link opens a payment page operated by Stripe, Inc. Opening that page makes an ordinary HTTPS request to Stripe, which receives standard network information such as your IP address. If you choose to pay, Stripe collects and processes the contact, billing and payment information required to complete the transaction under Stripe's privacy policy. Bandkit does not have access to card or payment credentials entered there.

Playlist, cart, activity and theme files are created or shared only after you choose the relevant download, share or import action. Public cart share files omit Bandkit's private cart-restore details. You control any exported file after it leaves the extension.

Retention and deletion

Locally stored information remains until you delete individual content, use Settings → Privacy and data → Delete all Bandkit data, clear the extension's storage through Chrome, or uninstall Bandkit. Session playback information is also cleared when the browser session ends. Exported files must be deleted separately from the location where you saved or shared them.

Feedback submitted to Notion is separate from Bandkit's local extension storage. Deleting Bandkit data or uninstalling the extension does not delete a submitted report. To request removal of a public submission, use the support contact shown on Bandkit's Chrome Web Store listing.

Security

Bandkit limits its page access to HTTPS Bandcamp properties needed for its features, restricts accepted playback streams to HTTPS Bandcamp media hosts and does not download or execute remote code.

Chrome Web Store Limited Use

Bandkit's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Bandkit uses user data only to provide or improve its disclosed single purpose and user-facing features.

Changes and contact

Material changes to Bandkit's data practices will be disclosed before the changed practices take effect, and this policy's effective date will be updated.

For privacy questions, use the monitored support contact shown on Bandkit's Chrome Web Store listing.