Privacy Policy

Operator of the KADOSH product at kadoshworshipband.com · Last updated: October 6, 2026

Content and rights. KADOSH does not sell or grant licenses to user music. Users are responsible for rights in what they upload. KADOSH stores and processes that content only to provide the service and does not acquire ownership of it.

1. Scope

This Policy describes how KADOSH handles personal and operational data when you use the website and application. It does not invent collection that the product does not perform.

2. Data we process

The live application database and file store process:

Account data: display name, email, password hash (not the password in clear text), and session authentication tokens.
Organization data: organization name and slug, memberships, roles, and permissions.
Invitations: invited email, role, token, status, and expiry if set.
Songs and library metadata: titles, artists, key, tempo, draft and published versions, instrument materials, and related notes.
Files you upload: audio, lyrics, chords, scores, images, and other documents, plus filename, MIME type, size, checksum, and storage key.
Events, event membership, instruments, setlists, and setlist song order.
Share-link tokens for authorized setlist playback without a full account, when a leader creates that link.
Chat: thread membership, message text, replies, reactions, delivery and read receipts, optional image or document attachments, and references to existing project assets.
Moderation records: when a director or admin hides a message, KADOSH stores a short snippet, actor, rule, and action for security and audit. The product UI may not show every alert to every user.

The application database does not store device identifiers or browser fingerprints as user-profile fields. HTTP clients send technical headers (for example User-Agent) as part of ordinary requests. IP addresses are used in memory for rate limiting and abuse protection. Persistent IP or device logs are not stored in the application database. Reverse-proxy, tunnel, and operating-system logs used to keep HTTPS available may record connection metadata for reliability and security; those logs are operational, not a user-facing product feature.

3. Chat and moderation

Chat processes message text, reply and reaction metadata, delivery and read state, optional private attachments, and references to existing project assets. Real-time chat events are sent only to members of that thread. Email and phone numbers are not published on public pages. Member email addresses are shown inside the team list only to directors and admins of that organization; musicians see names and roles. Attachments are not stored as public files. Organization membership or Chat does not automatically grant music access; a referenced score or track is re-checked against organization, event or project, invitation, membership, role, and permissions when opened. KADOSH uses moderation and security systems and may log attempts to share restricted information or to hide messages. A contact-information filter exists in the product; for internal general, event, and direct chats it is currently not blocking sends. Directors and admins can still hide messages. KADOSH does not currently send account-recovery email; password reset in the interface explains that and does not claim a message was sent.

4. Purpose

We process data to authenticate users, deliver the service, isolate content by organization and song, enforce permissions, operate playback and chat, improve reliability, and comply with law.

5. Sharing

We do not sell personal data. Content is shared only with users authorized by your organization, event, project, invitation, role, and permissions, or as required by law. Public website pages do not expose private rehearsal files.

6. Storage, access, and security

Application data is stored in the KADOSH self-hosted database and local private file storage. The public site and app are reached over HTTPS through the operator’s reverse proxy and tunnel. Private asset URLs require authorization. Access inside the product is limited to authenticated sessions (or a valid share token where a leader has enabled one). See also the Security page.

7. Retention and deletion

We retain account, organization, content, and chat data while the account or organization uses the service, plus backup, security, fraud-prevention, and legally required logs. Calendar-day retention periods have not been published. Deletion of an account removes associated data from the live application database and, when you are the only member of an organization, that organization’s live content and files, subject to backup and legal windows. Deletion is not instant across every backup or operational log. Shared-organization content belonging to remaining members is not destroyed.

You can start account deletion in the KADOSH app or web client: Configuración → Cuenta → Eliminar cuenta (Settings → Account → Delete account). The public instructions are at https://kadoshworshipband.com/account-deletion. That page does not wipe data by itself; you must sign in and confirm. The process is a live-account deletion, not a pause or hide.

8. Providers

KADOSH currently operates on self-hosted application servers, PostgreSQL, local file storage, and Cloudflare Tunnel for public HTTPS. The public site may load fonts from Google Fonts and may embed public YouTube videos on marketing pages only. Those third parties process whatever is necessary to serve those public resources.

9. Your choices

You may request access or correction where applicable through the Contact page once an official channel is published. You may delete your account as described at /account-deletion. An official privacy email has not yet been designated on this page.