Privacy Policy
OLQA Music — the music ministry app of Our Lady Queen of Angels Catholic Church (olqa.church-management.com) · last updated October 13, 2026
OLQA Music is used by the music ministry of Our Lady Queen of Angels Catholic Church to plan services, schedule musicians and choir members, share sheet music and send emails to the people involved. Only people who have been given an account by the music director can sign in.
Information we store
- Your name, email address, phone number, address and birthday as entered by you or the music office.
- Your roles and assignments (e.g. cantor, organist, choir), availability and absences.
- Records needed for payroll and reimbursements, where they apply to you.
Google user data
OLQA Music offers “Sign in with Google” and, if you allow it, sending email from your own Gmail address. This section describes exactly which Google user data the app accesses and how it is used, stored, shared, protected, retained and deleted.
Data accessed
- Basic profile (scopes
openid,email,profile): your Google account ID, email address and name. Google also offers your profile picture; the app does not use or store it. - Send email on your behalf (scope
https://www.googleapis.com/auth/gmail.send): the permission to send messages from your Gmail address. With this scope the app cannot read, search, list, change or delete any of your emails, and it has no access to your contacts, calendar, Drive or any other Google data. - OAuth tokens issued by Google for these permissions (a refresh token and a short-lived access token).
How the data is used
- Your Google email address is used only to match you to your existing account and sign you in. Accounts whose Google address is not registered in the app are not let in, and no account is created automatically. Your name is used only to show who is signed in.
- The
gmail.sendpermission is used only when you yourself click “Send” on an email in the app — for example a request to a cantor or a message to the choir. The app then sends exactly that message, with the recipients, subject and text you wrote, through the Gmail API from your address; it appears in your Gmail “Sent” folder. The app never sends email with your account automatically, in the background or on behalf of another user. - Google user data is not used for advertising, profiling, analytics or any purpose other than the two functions above, and it is not used to develop, improve or train generalized or non-personalized AI or machine-learning models.
Sharing
Google user data is not sold, shared with, or transferred to any third party. It is processed only on our own server and sent only to Google itself (to sign you in and to deliver the emails you send). No person other than you can use your Gmail permission. Staff of the music office do not look at your tokens.
Storage and protection
- The refresh token is encrypted with AES-256-GCM before it is stored in our database; the encryption key is kept outside the database and outside the web folder.
- The access token (valid for about one hour) is kept only on our server and is never shown to users or sent anywhere except to Google.
- The text of emails you send is passed to Gmail at the moment of sending and is not stored by the app. A technical log keeps only the date, sender, recipients and subject, to diagnose delivery problems.
- All connections, to the app and to Google, use HTTPS/TLS.
Retention and deletion
- Your Google email address and name stay with your account for as long as you have one.
- The tokens are kept until you disconnect Google. You can do this at any time in the app under Dashboard → Edit Profile → “Disconnect”, or in your Google account at myaccount.google.com/permissions. When you disconnect in the app, the permission is revoked at Google and the stored tokens are deleted immediately.
- When your account is removed, all Google user data stored for it is deleted. To request deletion, write to the contact address below.
Limited Use
OLQA Music’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
AI assistant
Some functions of the app use a large language model (Claude by Anthropic, reached either through the parish's own Anthropic account or through Amazon Bedrock). This happens only when a user starts such a function: the in-app assistant, suggestions for repertoire, organ music or hymn tunes, the analysis of uploaded scores, help with drafting an email or a worship-aid text. What is sent is the text of that request and the data it needs, which can include names of services, works, choirs and, for the assistant, names and roles of people in the app. The provider processes the request and returns an answer; under its API terms it does not use the content to train its models. Google user data (see above) is never sent to the AI provider. The app keeps a log of each call with the user, the function, the model and the token counts, for cost control, but not the text of the request.
How we protect your data
- Encryption in transit: the app is only reachable over HTTPS (TLS, with HSTS). Connections to Google’s servers also use TLS.
- Encryption at rest: the Google refresh token that allows sending is encrypted with AES-256-GCM before it is stored; the key is kept outside the database. The short-lived access token (valid for about one hour) is kept only on our server and is never shown to other users or sent anywhere except to Google.
- Passwords are never stored in readable form, only as Argon2id hashes. Repeated failed sign-ins are rate-limited.
- Sessions use cookies marked HttpOnly, Secure and SameSite.
- Access control: only people with an account can sign in, and each user sees only what their role allows. Your Google permission is used only for emails you send yourself; no other user can send with it.
- Server: the database is not reachable from the internet, credentials are kept outside the web folder, and backups are stored on a separate server.
- Revocation: when you disconnect Google, the app revokes the permission at Google and deletes the stored tokens.
Sharing
We do not sell or share your information with third parties for advertising or any other purpose. Data is processed only to run the music ministry and is hosted on our own server.
Deleting your data
Ask the music director to remove your account. Disconnecting Google removes the stored sending permission immediately.
Contact
Our Lady Queen of Angels Catholic Church · Music Office · chintermueller@olqa.org