Blindbandit Mobile Privacy

Updated October 23, 2026. This notice explains the social, messaging, calling and notification features of Blindbandit Mobile. It supplements the website Privacy Policy. The service is operated by Kaeleb Savon Heck, professionally known as Mr. Blindbandit, in connection with Blindbandit Records. Contact privacy@mrblindbandit.net about information practices or a rights request.

Account and profile information

Clerk supports sign-in and account authentication. When you use an account, the service processes account identifiers, a verified email address, your chosen username and display name, profile details you provide, and account and security events. Your public profile can display your username, name, biography, avatar, public posts and other activity allowed by your settings. An email address used for sign-in is not published simply because you create a profile. Information you put into a public biography or post can still be copied by other people.

Posts, images and community activity

Posts, comments, reactions, follows, stories and short videos support the social experience. Uploading media to a post sends that media to the service; this differs from the website's browser-only conversion tools. Public content can be viewed, shared or copied by others. Use an image description to make a shared image accessible without exposing private information in the description. A story's expiry controls visibility in the feature; it should not be understood as a promise that every backup or recipient copy disappears at the same moment.

Settings may limit post visibility, who can message you, and display of your following list. Blocking and muting are participation controls. They cannot recall an existing screenshot, a copied public post or material already shared outside the service. Your bookmarks, drafts, notification inbox and account settings are account features rather than public feed items.

Messages and calls

Direct messages are shown to participants through account access rather than published in the public feed. Message records, delivery or read state, attachments where supported, participant identifiers and call-related records may be processed to operate communications, prevent abuse and answer relevant support or legal requests. Calls use calling infrastructure, including LiveKit, and may require the microphone or camera permissions of your browser or device. Do not assume that messages or calls are end-to-end encrypted. Staff access is limited by role and purpose, but a private interface is not a guarantee that no lawful or authorized processing can occur.

Never send passwords, one-time sign-in codes, payment credentials or private keys in a message. Use your device controls to withdraw microphone and camera permissions, and use the service's messaging and blocking settings to control future contact.

Push notifications and devices

If you enable notifications, the service may process a browser subscription or device notification token, an account association and delivery or revocation information. Web push and Apple or Google notification services handle delivery according to the platform used. A token helps deliver a notification; it is not permission to read other applications on your device. Notification text can appear on a lock screen, so use device notification previews and permission settings to control what is visible. Disabling a device permission can stop device alerts without deleting the underlying account or message.

Reports, moderation and security

Reports may include a content reference, a reason you select, details you supply and moderation or security records. They are not intended as public posts. Authorized reviewers use them to investigate abuse, apply restrictions, review appeals and protect the service. Do not reproduce illegal imagery or include unnecessary identity documents in a report. Use the reporting form, appeals information or security reporting route for the relevant issue.

Providers, advertising and external media

Relevant service infrastructure includes Sites and Cloudflare-backed hosting, databases and storage; Clerk for authentication; Resend for requested transactional email; LiveKit for calling; and the browser or device push provider for notifications. Opening an external link or using a provider's media player can connect you to that provider and reveal ordinary request information such as IP address and browser details. The provider has its own terms and privacy notice. Blindbandit Mobile routes do not carry Google AdSense or Ezoic advertising. Private messages, call content, drafts and account records are not sent as advertising targeting data.

Retention and removal

Different records have different purposes and retention needs. Account and communications records support the account or feature while required; security, moderation, contractual or legally required records can need a longer period. Expired tokens and revoked sessions are not usable as current credentials. Deleting a visible item or closing an account may not immediately remove restricted backups, legal holds, necessary abuse records or copies held by another participant. A rights response should explain any applicable limit rather than promise that every copy has already disappeared.

Your choices and rights

Review Mobile settings, account sign-in and device permissions. You may request access, correction, deletion, restriction, objection or other rights that apply to your circumstances through the privacy rights form. Identify the account or feature and provide a reply address; do not email your password or a full identity document unless a proportionate secure verification process has specifically requested it. Questions about accessible use can go to accessibility@mrblindbandit.net.

The service is not directed to children under 13, and those children may not create an account or participate. See the Child Safety Policy. This notice can be read without signing in or turning on JavaScript. Material changes will be reflected here and in the website-wide policy.

In the Mr. BlindBandit Mobile app

The native Android app, available on Google Play, follows the notice above. These points describe how the app itself handles information.

No ads and no tracking

The app shows no advertising and does not track you across other companies' apps or websites. When the app opens pages from mrblindbandit.net in its built-in browser, it sends the Global Privacy Control signal, and the website's consent manager then keeps advertising and analytics switched off inside the app.

Sign-in

Sign-in uses Clerk with Google or an email address and a one-time code. The app holds only public identifiers; reusable secrets for sign-in, calling and notifications stay on the server, not in the app.

Permissions, asked in context

The app asks for the microphone when you start a call, the camera when you turn on video, file access when you choose a file, and notifications when you turn alerts on. It does not request every permission at first launch. You can withdraw any permission in your device settings.

Calls, messages and notifications

Calls and messages go through the Blindbandit API using your active sign-in. For each call, the server issues a short-lived LiveKit pass after checking your session. If you enable notifications, the app registers a device token with the Blindbandit API so that Google's push service (Firebase Cloud Messaging) can deliver alerts about messages and calls.

Stored on your device

Your app settings, such as haptics, speech feedback, high contrast, reduce motion, appearance and the offensive-language filter, are stored on your device. The Chronicle reader keeps a copy of stories it has loaded so they can be read offline.

Deleting your account

Settings includes Delete account. It asks the Blindbandit API to delete your data, deletes your Clerk sign-in account and erases data stored by the app on your device. You can also request deletion on the web at mrblindbandit.net/account. Limits on removal, such as copies held by other participants or records kept for legal or safety reasons, are explained under Retention and removal above.

Loading interactive features…