Privacy Notice

Banditron creates a server-side guest identity and necessary session cookie. It may store a protected IP-derived value and limited browser information. Google sign-in adds the name, email, profile image, and stable Google account identifier returned by Google.

The service stores content you provide or create, including songs, stems, mixes, recordings, prompts, lyrics and transcripts, musical analysis, chats, generated media, training material, private band or instrument models, voice references, project settings, shares, and job state.

For billing and AI-minute accounting, Banditron stores your plan and paid-through state, Stripe Customer and Subscription identifiers, payment or invoice references, webhook receipt records, issued minute grants, reservations, and measured usage. These records help explain access and balances; they are separate from card details held by Stripe.

Data is used to provide playback, storage, generation, transformation, stem separation, analysis, transcription, training, sharing, billing, support, security, abuse prevention, reliability, and account administration. Authorized administrators can inspect operational records and complete Bandi Mate conversations when needed to support and operate the service.

Stripe provides hosted Checkout and billing management and processes payment and billing information. Stripe collects and handles payment-card details; Banditron does not store full payment-card numbers. Banditron receives the payment, subscription, and invoice status and identifiers needed to provide paid access and reconcile AI-minute grants.

Banditron uses Google for sign-in and, only after your choice, Google Analytics. Configured music, speech, and language jobs may send relevant content, prompts, lyrics, analysis, or conversation context to AI processors, including OpenAI when enabled. Infrastructure providers process database, object-storage, queue, log, and compute data.

The session cookie is necessary to connect you to your workspace. Optional Google Analytics does not load until you accept it, and the choice can be changed in Account & privacy. Internal operational metrics, job counts, failures, latency, security, and service telemetry continue without optional browser analytics.

Private project data is scoped to the owning guest identity or account. If you create a link share, anyone with that link can access the shared snapshot until you revoke it. Imported copies may remain in another user’s workspace.

Connecting the plugin authorizes access to your Banditron account through OAuth. Tools return the song metadata, musical analysis, lyrics you explicitly request, asset identifiers, or job progress needed for your request. Creation and editing tools can store content and start processing jobs; they use your account permissions and existing Terms acceptance.

Requested results are sent to the host you use, including OpenAI for ChatGPT and Codex. Playback and download tools issue private links that expire within five minutes; anyone holding a link can access that audio until expiry. Disconnect Banditron in the host to remove the connection. Disconnecting does not delete your Banditron content; use account deletion separately.

You can delete individual projects, clear a guest workspace, or request account deletion in Settings. Project and private account content is removed through those workflows; guest work remains server-side until cleared or otherwise removed under service operations. Account deletion immediately cancels a confirmed active Stripe subscription before account content is removed. Unused AI-minute balances become unavailable when account deletion completes.

Account/profile information is kept while the Banditron account exists. Uploaded audio, generated songs, stems, recordings, derived assets, project chats and analysis are kept while their project exists. Private training material and models remain until the account or their applicable stored item is removed. Deletion removes active-storage content when cleanup succeeds; running work or a failed cleanup keeps the request pending for retry. A minimal disabled account identifier and project-deletion marker remain to prevent deleted work or access from being recreated. The shared sign-in service may retain its identity while it is used by another connected service; contact Support to request review of that identity too.

Activity records are retained for up to 180 days and completed model-run records for up to 365 days, then removed by daily cleanup. Recorded administrator audit events expire after 365 days. Support and privacy-request messages submitted in Banditron expire 365 days after the request is closed. Terms, Privacy and capability-confirmation records are kept while the identity is active and expire 730 days after its deletion. Completed deletion-request records expire after 730 days. Expired or revoked sessions are removed by daily cleanup. Cleanup runs at least daily when operating normally, so removal can take an additional 24 hours after a period ends; failures are recorded for follow-up.

Open support requests, unresolved deletion requests and records documenting outstanding processor cleanup stay until the issue is resolved; they are not expired while action is pending. Minimal deletion markers contain no stored music. Share links remain valid until revoked or their snapshot/project is deleted, and copies already saved by recipients remain in those recipients’ projects. Plugin playback/download links expire within five minutes and tool retry records within 24 hours.

Inactive application log files in the service runtime directory are removed 30 days after their last write. Active service logs and historical log copies elsewhere still require verified rotation and expiry settings. Backup copies are not erased by active-storage deletion; a verified maximum backup lifetime is not yet established. Email support copies follow the mailbox settings, whose retention period has not yet been verified. These infrastructure limits must be confirmed separately, and Support can explain what remains in a deletion request.

Limited billing references, payment and webhook evidence remain for accounting, tax, fraud, disputes and reconciliation under the applicable legal retention obligations; their exact legal schedule still needs confirmation. Full payment-card details remain with Stripe. Optional analytics data is held by Google under the configured property retention settings, which still need verification; withdrawal stops further optional browser events.

Content sent to processors can remain under their contracts and account settings. The remote training service currently has no verified job/artifact deletion API. Requests involving those records remain awaiting processor cleanup until Support obtains confirmation of removal; Banditron does not label that data erased. The same review applies to AI processor retention settings and backup copies, whose maximum periods cannot yet be verified.

Use Account & privacy for data requests, session, analytics, and Banditron-account deletion controls. Guests can choose “Clear temporary workspace” from the account menu; clearing browser data alone does not erase server content. You can also use Support or email support@banditron.com for privacy, copyright, or abuse requests. Submitted requests are recorded for review.

The Banditron Privacy Officer reviews the request, verifies access/identity where needed, and coordinates account cleanup or access/export/correction. Unresolved processor deletion stays open for follow-up and status updates. A request is closed only after its disposition is recorded; pending requests are not silently removed by retention cleanup.

For privacy questions and requests, contact the Banditron Privacy Officer at support@banditron.com.

Banditron uses scoped sessions, ownership checks, and restricted media access, but no service can promise perfect security. Contact support@banditron.com if you have a security or privacy concern.