Mezmur Privacy Policy
Mezmur Privacy Policy
Last updated: October 27, 2026
Mezmur (the “App”) is an Ethiopian Christian hymn app published by Biniyam G/slassie (“we,” “us,” or “our”). The App lets people browse hymn categories, search and read lyrics, stream audio, save favorites, and download audio and cover images for offline use. This Privacy Policy explains what information the App handles, how it is used and shared, and the choices available to you.
If you submit feedback or a donation-related message through the App, we receive the message, its type, and any name you choose to provide. A name is optional. The message form does not ask for your email address, but we will receive any contact details you choose to include in the message. Messages are stored in Convex, our backend service, so we can review them and respond where possible. Please do not include sensitive personal, authentication, or financial information.
The App has a restricted administrator area and uses Clerk for authentication. If you enter an email address that Clerk does not recognize, the App’s email sign-in flow can start account registration and send a verification code. After you verify the email address, Clerk may create an account that can be used to sign in to the administrator area. Google sign-in is also available through Clerk; whether a first-time Google sign-in creates a Clerk account depends on the authentication settings.
Creating or signing in to an account does not grant administrator privileges. Administrator features are restricted to accounts we separately authorize with an administrator role. Ordinary hymn browsing, listening, favorites, and downloads do not require an account.
Clerk processes information needed to create and authenticate an account, such as an email address, account identifiers, and authentication and session information. If you choose Google sign-in, Google and Clerk may process information needed for that sign-in, such as your Google account identifier and basic profile information made available through the sign-in flow. The App does not ask you to provide your Google password to us.
An authorized administrator may select audio files and cover images from a device and upload them to Convex Storage to maintain the shared hymn catalog. These files are stored by Convex and may be delivered to App users as catalog content. Do not upload files containing sensitive personal information. Shared catalog files may remain available until an authorized administrator removes or replaces them.
When you browse or stream, the App requests hymn, lyric, category, audio, and image content from Convex, our backend and cloud-storage provider. Downloaded audio and images are saved locally on your device. Convex and our authentication providers may process routine technical and connection information, such as request logs and network or device information, as needed to provide, maintain, and protect their services. Their own privacy notices describe their processing in more detail.
The App stores favorites, preferences, cached hymn and category information, and audio or cover images that you choose to download. Favorites and preferences are stored locally and are not synced to our servers as part of those features. Downloaded files are stored on your device for offline use.
We use submitted messages to review feedback and donation-related inquiries; administrator account information to authenticate access to restricted features; administrator uploads to maintain the shared hymn catalog; and locally stored information to provide favorites, preferences, cached content, and offline playback. We use service providers as needed to operate authentication, the backend, and cloud file storage.
We do not sell personal information. Information is processed by the following providers as needed to operate the App:
•Clerk provides administrator-area authentication and account services.
•Convex provides the backend database, functions, and file storage. It processes catalog requests and stores messages and administrator uploads submitted through the App.
•Google may process information if you choose Google sign-in or use the embedded YouTube player. Google's processing is described in its Privacy Policy.
•YouTube receives information when its embedded player loads or is used. The App uses YouTube's embedded player; basic information may be sent when the player loads, and additional information may be sent during playback or interaction. Use of YouTube is subject to the YouTube Terms of Service and YouTube Developer Policies.
•External social services may receive information when you choose to open a link to them from the App. Those services handle information under their own privacy policies.
These providers may process information on systems located in countries other than your own, subject to their terms, privacy notices, and applicable service arrangements. We may also disclose information where reasonably necessary to comply with law, protect users or the App, or respond to a valid legal request.
The donation screen displays payment account details and lets you copy the selected details to your device’s clipboard so you can make a donation through a bank or payment service of your choice. The App writes the selected details to the clipboard; it does not read clipboard contents, process the payment, or receive your bank, mobile-money, card, or transaction details through this feature. Any payment you make is handled by the payment provider you choose and is subject to that provider’s privacy terms.
The donation screen may display a video hosted by YouTube. Loading the embedded player may send basic information to YouTube; playback or other interaction may send additional information. We do not control YouTube’s data practices. See Google’s Privacy Policy and YouTube’s Terms of Service.
The App also contains links to external social-media services. If you open one of those links, the service you visit handles your information under its own privacy policy.
Favorites, preferences, cached content, and downloaded files remain on your device until you remove them, clear the App’s data, or uninstall the App. Individual downloads can be removed through the App where that control is available. Clearing app data or uninstalling the App removes locally stored App information, subject to your device and backup settings. Deleting an administrator account does not automatically remove local favorites, preferences, or downloads from the device.
Messages are retained in Convex while they are needed to review or respond to them. There is no fixed automatic deletion period. To request deletion of a message you submitted, email banspace21@gmail.com with the subject “Mezmur message deletion.” Include enough information for us to identify the message, but do not send sensitive information.
You may request deletion of your Mezmur account and the associated account information we control by emailing banspace21@gmail.com with the subject “Mezmur account deletion.” You do not need to be signed in to make a request. We may ask for information reasonably needed to verify that you control the account. After verification, we will delete the account from Clerk and delete or de-identify associated personal information under our control, and request deletion from service providers where applicable. We may retain information only when required by law or reasonably necessary for security or fraud-prevention purposes. Any retained information will be limited to that purpose and deleted when no longer needed.
Messages submitted through the App and media placed in the shared hymn catalog are not automatically linked to an administrator’s Clerk account. Deleting an account therefore does not automatically delete a submitted message or remove shared catalog media. You may separately request deletion of a message or removal of specific catalog content using the contact address above. We will review those requests and remove personal information we can identify, subject to applicable legal requirements and necessary security or fraud-prevention retention. Account deletion does not delete your separate Google account; manage that account through Google.
We use service providers and technical measures intended to protect information handled by the App. Clerk’s Expo token-cache integration is used for administrator session tokens on mobile devices. Convex states that its platform encrypts customer data at rest and encrypts data in transit. See Convex Platform Security. No method of storage or transmission can be guaranteed to be completely secure.
Mezmur is a general hymn and music app and is not specifically designed to collect personal information from children. Ordinary listeners do not need to create an account. We do not knowingly seek personal information from children. If you believe a child has sent us personal information, contact us at banspace21@gmail.com so we can review the request.
We may update this Privacy Policy when the App or its data practices change. We will post the updated version at the same URL and revise the “Last updated” date. Please review this page from time to time.
For questions or privacy requests, contact:
Biniyam G/slassie banspace21@gmail.com