Room for worship.
Clarity about your data.

Yoruba Baptist Hymns (“YBH”, “we”, “us” or “our”) is a hymn archive created and maintained by Ademola Alabi in Nigeria. This notice explains how personal information is handled when you use yorubabaptisthymns.com, create an account, use reader features, contact us, donate or enquire about sponsorship.

For the activities described here, Ademola Alabi, operating Yoruba Baptist Hymns, is the data controller: the person responsible for deciding why and how YBH handles personal information. Privacy enquiries can be sent to contact@yorubabaptisthymns.com or through our Contact page.

This notice covers this website and its browser-installed offline experience. It does not automatically cover a separate mobile app, another hymn website, a church, an advertiser, or any third-party site reached through a link. Any future separate service needs a notice matching its own data practices.

The information involved depends on the features you use. You do not need to create an account to browse and read the public hymn archive.

Information can come directly from you, from your browser/device, from your selected sign-in provider, or from a payment provider confirming a transaction. Please do not put passwords, payment-card details, identity documents, health information or another person’s private information into messages or public reflections.

What the sign-in connection is for

If you choose “Continue with Google” or accept a Google One Tap sign-in prompt, Google authenticates your Google account and shares identity information so YBH can create or connect your reader account. The basic identity information involved includes your Google account identifier, email address and verification status, and, where supplied, your name and profile-picture URL. A sign-in credential is used to verify the authentication response. YBH then uses its own account/session system to keep you signed in.

Permissions and limits

Google sign-in is used for basic account authentication. This sign-in purpose does not include access to your Gmail messages, Google Drive files, contacts or calendars. YBH does not receive your Google password through this sign-in flow. The permissions shown by Google at the time of sign-in should match that limited purpose. If a broader permission is requested, do not approve it without understanding why; contact us if it appears inconsistent with this notice.

A Google sign-in choice is separate from consent to newsletters, optional analytics or marketing. A profile name or photo supplied by Google should not be assumed to be public: public display details depend on your YBH profile and contribution settings. Check the name attached to a comment before submitting it.

Use, storage and sharing of Google identity information

Information received through Google sign-in is used to verify your identity, create or connect your YBH account, support access to reader features and help resolve account issues. Account-link information is held with the relevant YBH account records for those purposes and is reviewed as part of an account/data deletion request, subject to any lawful retention exception. Google identity information is not supplied to sponsors as part of campaign reports. Administrators and service providers may handle relevant account information for the support, infrastructure and security purposes described in this notice.

Disconnecting and deleting are different

You can review or remove YBH’s connection in your Google Account connections. Removing that connection does not by itself delete the information already held in your YBH account. Request account/data deletion using section 13. Deleting your YBH account does not delete your Google account.

If Google is your only sign-in method, contact us before disconnecting if you want to keep access to YBH. We may need to help you establish another supported sign-in method. Google handles its own authentication service under the Google Privacy Policy.

YBH uses relevant information to provide the feature you request, maintain the archive and address legitimate operational needs. These purposes include:

• Delivering hymn pages, search results and the browser-installed reading experience.
• Creating and administering accounts, responding to password/account requests and remembering reader preferences.
• Maintaining saved hymns, highlights, reactions and approved conversations.
• Responding to enquiries, reviewing corrections and communicating about your request.
• Processing donation confirmations and administering sponsorship arrangements.
• Understanding audience patterns, identifying difficult interfaces and measuring the use of reader/offline features.
• Measuring delivery and clicks for first-party sponsor placements and preparing aggregate campaign reports.
• Detecting spam, investigating abuse, maintaining technical security, handling rights requests and meeting legal obligations.

Service messages about an account, request or transaction are different from promotional messages. Any future newsletter or promotional subscription needs its own appropriate sign-up and unsubscribe arrangements.

Where applicable data protection law requires a legal basis, that basis depends on the particular activity:

A legitimate-interest basis does not replace consent where cookie or other law requires consent. Nor does a general legal basis remove additional protections for sensitive information.

Faith and personal reflections

Hymn choices, highlights or messages can reveal or suggest religious beliefs, which receive additional protection in some jurisdictions. Visiting YBH does not establish that a person belongs to a church or holds a particular belief. Please share only what you are comfortable sharing, especially in public reflections.

Where a feature involves legally protected sensitive information, an additional condition or permission may be required under the applicable law. A public reflection is not permission to use all of your other account activity for unrelated purposes. Reader information is handled for the requested features, support and permitted reporting. YBH’s sponsorship terms exclude targeting by private highlights, inferred beliefs or individual reading history.

Approved comments or reflections and their associated display names can be visible to other visitors and may be indexed by search engines, copied or shared. Moderation does not make a published contribution private. Avoid including contact details or sensitive information about yourself or someone else.

Saved hymns, personal highlights and reading preferences are intended for your account experience rather than public display. The live account page explains that administrators can review saved words for support and reporting. These features are therefore not an encrypted private journal and should not be treated as accessible only to you.

Ask us to review a public contribution if you want it removed or anonymised. We can assess what YBH controls; we cannot directly erase copies held by people, search engines or independent websites.

The offline experience uses browser technologies, including a service worker, Cache Storage and IndexedDB, to keep the reader interface and selected hymns available on your device. Reading preferences and dismissed notices can also use local storage. Adding the website icon to your home screen is different from downloading a separate app from an app store.

Offline activity can sync later

The current offline client can queue records of feature activity, including downloads, offline usage and guide interactions. The records contain an event identifier, event type, time, a reader identifier, device category and, where relevant, the guide device and step. When connectivity returns and the appropriate reader session is available, queued records can be sent to YBH for reporting. Offline therefore does not mean that activity can never be reported later.

The client code removes accepted events after a successful sync and applies a 90-day age check and a queue limit when recording new events. The current theme also schedules removal of server-side offline event records older than 90 days and performs an age-based cleanup during accepted sync requests. Actual removal depends on these processes running; this is not a 90-day retention rule for every kind of reader record. Inactive browser storage can persist until the browser, device or user clears it.

Removing local copies

Use the offline reader’s removal controls where available, or clear this website’s stored data in your browser settings. Clearing site data may remove downloaded hymns, local settings and sign-in state. Removing a home-screen icon alone may leave browser data behind. Signing out or deleting an account does not remotely wipe an offline device.

On a shared device, sign out and clear YBH’s site data before handing it to another person. Remove local copies on every browser/device you used. Our offline guide explains how the offline reader works.

Cookies are small records stored by a browser. YBH also uses local/session storage, IndexedDB and cached files; those technologies can have privacy implications even when they are not called cookies.

Hymn activity counters also use browser-session identifiers, short-lived active-session records and daily hymn-visit totals. These records are distinct from account-linked reader analytics and third-party analytics.

Google Analytics and Microsoft Clarity scripts are present on the live website. Their actual collection depends on configuration, browser controls and any consent settings. Cookie names and lifetimes can change; the retention discussion below does not imply that all tools use the same expiry period.

Where the law requires permission before non-essential storage or tracking, that permission must be obtained before the relevant processing. Merely visiting this page, continuing to browse or creating an account is not consent to optional tracking.

You can block cookies, delete site data, use browser privacy controls, or use the Google Analytics opt-out browser add-on where supported. Blocking technologies can affect functionality. Do Not Track and Global Privacy Control support varies by tool; do not assume that one browser setting disables all collection. Contact us to exercise a right or ask how a particular signal is handled.

Read the Google Privacy Policy, Microsoft Privacy Statement and Cloudflare Privacy Policy for the providers’ practices. Do not submit passwords, payment information or sensitive personal information in public page content; session-replay masking must not be treated as an absolute guarantee.

YBH uses Bachs for donation checkout and payment confirmation. Starting a donation can pass the relevant donor and transaction details to Bachs. If supported by the donation form, your signed-in name and email may be prefilled so you can review or edit them before continuing.

Payment instructions and any sensitive payment credentials should be entered only in the relevant provider/bank interface. Donation confirmations and references can return to YBH to match a payment, update its status and support administration. Bachs, banks and other payment participants may have their own legal obligations and privacy notices; review the notices displayed at checkout.

A donation does not require a YBH reader account. Deleting a reader account does not automatically cancel a recurring donation, reverse a payment or erase financial records that must be kept. Use the recurring-support management link supplied by the payment service, or contact us for help identifying the right route. Ask separately about any donation records you want included in a privacy request.

Sponsorship enquiries are used to assess the proposed organisation and offer, respond, agree campaign details and administer a booking. Approved creative and the organisation’s destination link become public when a campaign runs.

YBH’s published sponsorship terms describe first-party placements and aggregate delivery/click reports, without sharing readers’ names, email addresses, saved hymns or private highlights with sponsors. They also exclude advertiser scripts and tracking pixels from approved creative and do not offer targeting based on private highlights, inferred beliefs or individual reading history.

Clicking a sponsor, donation, social-sharing or other external link takes you to another service. That service can receive information such as your IP address, browser details and information you provide to it. Its own privacy notice applies. A link or placement does not make YBH responsible for that service’s independent handling of information.

Relevant information may be disclosed to the people and providers needed for the purpose involved:

• Site administration and support: people authorised to maintain the service, review submissions and resolve issues.
• Hosting and infrastructure: providers delivering website hosting, content delivery, database services, security, logs and backup services where configured.
• Identity and security providers: Google when you choose its sign-in option, and Cloudflare for relevant security/form verification.
• Analytics providers: Google Analytics and Microsoft Clarity for the processing described above, subject to the applicable configuration and legal requirements.
• Communication providers: services used to deliver account notifications and handle submitted messages.
• Payment participants: Bachs and relevant payment services for the transaction you request.
• Professional advisers or authorities: where reasonably necessary for legal advice, a valid legal obligation, protecting rights or investigating misuse, subject to applicable law.
• Other visitors: when you submit content that is approved for public display.

A provider may act on YBH’s instructions for some processing and independently for other purposes described in its own notice. Sponsor reporting is described separately in section 10. We do not describe information as anonymous simply because direct names have been removed; identifiers and pseudonymous event records may still be personal data.

Depending on where you live, the applicable law and the circumstances, you may have rights to:

• Be informed about the collection and use of your personal information.
• Ask whether information about you is held and obtain access or a copy.
• Correct inaccurate information and complete information that is incomplete.
• Request deletion, restriction of processing or portability of relevant information.
• Object to certain processing, including direct marketing where applicable.
• Withdraw consent for future processing that relies on that consent.
• Exercise relevant rights concerning significant decisions made solely by automated processing.
• Complain to the relevant data protection authority and, where applicable, appeal a request decision.

Rights have conditions and lawful exceptions. A request may need to be assessed against financial-record duties, other people’s rights, security needs or legal claims. Withdrawing consent does not change the lawfulness of processing that happened before withdrawal.

Email an access or export request ↗

Use your account controls for changes those controls support, or contact us. You can ask for accessible assistance if a particular format is difficult for you.

1. Tell us what you want removed

Write from the email associated with your account where possible. Include that account email, the scope of the request and any comment/page links that help us locate a record. Tell us if you used Google sign-in and whether you want public reflections reviewed for removal or anonymisation. Do not send your password, payment credentials or identity documents with the initial request.

2. We verify the request and review the records

Before releasing or deleting account information, we may need proportionate confirmation that you control the account or are authorised to act for the person concerned. If verification needs more information, we explain what is needed and why. A request sent on someone else’s behalf needs appropriate authority.

3. We explain the outcome

When assessing a deletion request, we review the account, saved hymns, highlights, preferences, identifiable reactions and related reader/offline records that can be linked to you, plus any other records you identify. This includes Google account-link information held by YBH where applicable. Public contributions may need removal or anonymisation. Data stored by separate plugins or services needs a separate check; account deletion alone must not be assumed to remove every related record.

Some information may need to be retained for a legal obligation, transaction records, security investigations, disputes or legal claims. Where an exception applies, we explain the category and reason and limit further use to that retained purpose. Information that has been irreversibly anonymised so it no longer identifies you is different from an identifiable account record.

We respond to privacy requests within the period required by the law that applies. Where GDPR or UK GDPR applies, the usual response period is one month, with a permitted extension for qualifying complex or numerous requests and notice of that extension. Other laws may use different periods. If we cannot fulfil a request in full, we explain the reason and the complaint or appeal route available.

Important follow-up steps

• Google connection: remove YBH in your Google Account connections if you also want to revoke the sign-in connection. This is separate from deleting YBH-held data.
• Offline devices: clear YBH site data on each device/browser to remove local downloads, preferences and queued events. We cannot remotely clear a disconnected device.
• Recurring donations: cancel through the relevant payment management route if you want recurring support to stop; an account deletion request is not itself a cancellation.
• Public copies: search-engine caches, shared copies and independent sites may require requests to their operators.

A deletion request is reviewed; the button is not an automatic delete command or confirmation that deletion has already occurred. If you create a new account later, it is a new account and previously deleted reader information may not be recoverable.

Different types of information need different retention rules. Relevant factors include the feature requested, whether an account remains active, the need to resolve an enquiry, applicable financial-record requirements, security investigations, legal claims, and whether information has been genuinely anonymised.

A single universal retention period is not asserted here. You can ask which period or criterion applies to your particular information. A deletion confirmation should identify any records retained and why, rather than imply immediate removal from every backup or independent provider.

YBH is operated from Nigeria and is accessible internationally. Your information may be processed in Nigeria and in other countries where the providers used for the service operate. The location of a visitor does not determine the location of every server or support operation.

Cross-border processing may be subject to additional requirements. Where applicable law requires an adequacy basis, approved contractual safeguards, a specific exception or another transfer mechanism, the relevant mechanism must apply to that transfer. Accessing the website is not, by itself, consent to a restricted international transfer.

You can ask us about the providers involved in processing your information, the relevant processing locations and any applicable safeguards. Information is not necessarily stored in Nigeria, and the applicable transfer requirements depend on the provider, processing activity and law involved.

Rights in different locations

Nigeria: the Nigeria Data Protection Act 2023 and relevant regulatory requirements may apply. You can contact the Nigeria Data Protection Commission about a complaint.

European Economic Area and United Kingdom: GDPR or UK GDPR rights and transfer rules apply where the relevant law’s scope is met. You may complain to your local supervisory authority, including the UK Information Commissioner’s Office where appropriate. Global availability alone is not a claim that every foreign privacy law applies in the same way.

United States and other locations: applicable state or national laws may provide additional rights, including rights to know, correct, delete, obtain a copy, opt out of certain uses or appeal a decision. These depend on the law’s scope and thresholds. Contact us to make a request and identify your location if that helps determine the relevant rights. This notice does not claim that YBH automatically meets every threshold under California or other US state privacy laws.

Hymns may be read by people of different ages. Parents, guardians and teachers should supervise younger children’s use of account features, public reflections and forms. Please avoid posting a child’s full name, contact information, school, photographs or other identifying details in a public contribution.

Creating a reader account or submitting personal information may require parental/guardian involvement or permission under the law that applies to the child. Please contact us before providing a child’s personal information if you are unsure whether the necessary permission has been obtained.

If you believe a child’s personal information has been submitted without the permission required by law, contact us with enough information to locate the account or contribution. We review the issue and arrange deletion, restriction or another appropriate response based on the circumstances and applicable law. Do not include unnecessary sensitive documents in your first message.

YBH uses HTTPS for the website and sign-in sessions. Cloudflare Turnstile is used on relevant forms to help distinguish legitimate submissions from automated misuse. These controls do not make the service immune to unauthorised access or loss.

No internet service or storage method can promise absolute security. Use a unique password where password sign-in is used, protect the email or Google account linked to YBH, and sign out on shared devices. Send suspected security issues through the Contact page without posting exploit details or personal information publicly.

If a personal-data incident occurs, any investigation, remedial steps and notifications must be assessed against the duties and time limits in the law that applies. This notice does not claim that an incident can never occur.

YBH’s features, providers and privacy obligations can change. A revised notice carries an updated date; material changes are communicated through an appropriate notice. Where a new purpose or permission requires consent or another legal step, publishing revised text alone does not replace that requirement.

Any additional sign-in provider, separate mobile app or material change to tracking, advertising or the purposes for which personal information is used requires a privacy review and an updated notice where appropriate.

For privacy questions, access/correction requests, objections, account deletion or concerns about a child’s information, contact:

Please describe the issue, use your account email where possible and identify any relevant page or record. We may request proportionate verification. You do not have to raise a concern with us before exercising a right to complain to a competent regulator where that right exists.