Listen ↗

INFORMATION / TRUST / ACCOUNTABILITY

Privacy Policy

Last updated October 13, 2026. Contact the appropriate officer with questions.

Effective September 13, 2026 · Last updated October 13, 2026

01

About this policy

02

Controller, operator, and Data Protection Officer

03

Scope

04

Categories of information

05

Sources

06

Music submissions

07

Professional, licensing, press, partnership, and booking inquiries

08

Community information

09

Accounts and authentication

10

Blindbandit Mobile: profiles, posts, messages and calls

11

Audio converter and Media Suite

12

Browser utilities and local storage

13

Advertising

14

Google Analytics

15

European advertising consent

16

Purposes and legal grounds

17

Service providers and recipients

18

Cookies and similar technologies

19

Do Not Track, Global Privacy Control, and privacy signals

20

Retention

21

International processing and transfers

22

Security

23

Individual privacy rights

24

Philippine data-subject rights and complaints

25

European and United Kingdom privacy rights

26

California and other United States state privacy rights

27

Children and minors

28

Marketing communications

29

Automated decision-making and profiling

30

Security incidents and breach response

31

Policy changes and contact

Send a privacy rights request

First-party page counts and public analytics

The website keeps permanent aggregate counts for public page loads and publishes those totals on the analytics dashboard. It also records hour-level totals, referring-site domains, country codes supplied by the hosting network, and general device, browser and operating-system categories. It does not store IP addresses, precise locations or raw user-agent strings for this dashboard.

For the real-time display, the browser creates a random identifier in session storage for the current tab. The server stores only a one-way hash and treats it as active briefly after the most recent signal. It estimates active browser sessions and does not identify a person.

Information by feature

Privacy supplement updated October 13, 2026. These distinctions help you decide which features to use. A browser-only tool, a public community post and a private label record do not have the same data flow.

Typical information and purpose by website feature
FeatureInformation involvedPurpose and visibility
Public pages and site countsPage requests, permanent visit totals and coarse source, country, device or browser information.Deliver pages and understand aggregated site use. The site counter does not store raw IP addresses or raw user-agent strings in its statistics tables.
Browser media toolsFiles and settings you choose; software downloads needed by the tool.Local processing unless a tool explicitly says otherwise. Download providers receive ordinary network request information.
Forms and submissionsContact details, project information, files or references you intentionally submit.Answer the request, review a project or handle support; not automatic enrollment in unrelated marketing.
Mobile participationProfiles, posts, uploads, follows, reactions and account activity.Operate the social service with visibility determined by the feature and available settings. Uploaded posts differ from local file conversion.
Private communicationsParticipants, messages, attachments where supported, call and notification records.Requested communications, delivery, safety and relevant support or legal obligations; not public feed content or ad-targeting inputs.
Private label workspaceInvited-account records, projects, rights, contracts and financial administration.Role-limited business operations. See the public Portal Privacy notice.
Optional advertisingProvider requests, cookies, device/browser information and ad interactions when enabled and allowed.Eligible editorial advertising. Ads are currently disabled; provider loading requires the site and visitor consent gates.
Privacy and security requestsReply details, an account or content reference, necessary verification and a decision record.Handle a rights request, report or appeal without exposing the case as public content.

Foundation-related information

Mr. Blindbandit Access and Opportunity Foundation Incorporated is a separate Virginia nonstock corporation. The Foundation's document and information pages are hosted within this website. Public formation and governance records may include names, signatures or other information which is part of the intentionally published document. Reading such a record does not authorize reuse of its personal information for an unrelated purpose.

Foundation inquiries, volunteer or program interests and supporting documents should be used for the Foundation activity for which they were supplied. A music inquiry does not automatically become a Foundation application, and a Foundation inquiry does not enroll a person in unrelated artist marketing. Do not put sensitive health, financial or child information into an ordinary public message. The Foundation contact is [email protected]; website privacy questions can also be sent to [email protected]. If a future program, donation or application collects additional information, its collection notice should explain the purpose and required information before collection. Foundation pages do not carry advertising.

Retention and deletion in practice

There is no single retention period for every category. Account, requested communication and submission information follows the relevant relationship or request; security and moderation records support safety and review; financial and contractual records can be subject to longer lawful preservation requirements. Expiring a session or hiding a story changes its usability or visibility and does not establish that every historical record or backup has been erased. A rights response should explain any record which must be retained and the applicable reason. Copies made by another user or external publisher are outside the site's direct control.

Making an accessible privacy request

Use the privacy rights form or email the privacy address with a reply contact and the account, submission, post or transaction concerned. Describe the outcome you need without sending a password, a one-time code, a complete card number or unnecessary identity documents. Additional verification should be limited to what is needed to protect the person and the records involved. Tell us if the verification method is inaccessible so an accessible alternative can be considered. Applicable rights and exceptions depend on the circumstances and governing law; the operator should explain the decision rather than promise an unqualified deletion or disclosure.

For messages, calls, uploads and device alerts, read the expanded Mobile Privacy notice. For cookies, consent withdrawal and provider technologies, read the Cookie and Storage Notice. The notices are readable without opting in to advertising.

Keep the connection.

LET’S MAKE
SOMETHING. ↗

Listen

Playback and availability are provided by Apple Music.