Privacy Policy

Mi Tiempo Con Jesús in Mexico (“Worship DB,” “we,” “us,” or “our”) is responsible for deciding how personal data is processed in the Worship DB public website, authenticated web application, installed progressive web app, Free, Plus, Pro and managed VIP access, billing, support, and legal-document records.

Privacy questions and requests may be sent to contacto@worshipdb.com. Mi Tiempo Con Jesús has not yet designated the complete physical domicile required for this integral notice. This version therefore remains unavailable for legal acceptance and will not become effective until that truthful domicile and the remaining release requirements are approved by qualified Mexican counsel.

We process only the categories listed below for the current Service. Some information comes directly from you, some from Google or Stripe, some from your device and our infrastructure, and some may be entered by another authorized Team member.

• Account and profile: Supabase and Google user or provider identifiers, email address, name, profile image, authentication provider, session records, the display name and photo you choose in Worship DB, and your language, notation, theme, accent, lyrics-view, font-size, feature-flag, and selected-Team preferences.
• Teams and collaboration: Team name and image, invite code, membership, role, join date, ownership, invitations, role and membership changes, actor attribution, and related audit records.
• Worship content: singer and leader names, assigned keys, song titles, artists, authors, lyrics, chords, tags, external reference URLs, set lists, Quick-list content, and the changes synchronized among authorized members.
• Plans and billing: selected Plan and interval, Stripe customer and subscription identifiers, checkout and quote records, amount, currency, tax, status and dates, billing name and postal address, tax identifiers, invoices, and partial payment-method details such as brand and last digits. Complete payment credentials remain with Stripe.
• Support and rights requests: the email address, message, attachments and other information you choose to send, together with request status and our response.
• Technical and security records: IP address, request time, device and browser information, request identifiers, session and authentication events, and limited request, error, security, network and diagnostic records processed by Supabase, Cloudflare and the application.
• Legal records: user identifier, exact Terms and Privacy versions, selected language, server acceptance time, and any separate consent evidence required before a reviewed version becomes effective.

The necessary purposes are to authenticate accounts; maintain profiles and preferences; create and administer Teams, invitations, roles and limits; store, display and synchronize worship content; attribute important changes; provide Plans, trials, subscriptions, taxes and invoices; answer support and privacy requests; protect accounts and the Service; diagnose failures; enforce our Terms; and meet legal obligations.

If you refuse or revoke processing that is necessary for a feature, we may be unable to provide that feature or the protected Service. Worship DB currently has no optional advertising, behavioral analytics, profiling or marketing purpose. A new optional purpose will require a revised notice and the appropriate prior choice; it will not be authorized by broad language in this document.

Team membership, ministry participation, singer or leader assignments, worship content and related activity can reveal or allow an inference about religious beliefs. Mexican law treats religious beliefs as sensitive personal data.

Before this notice becomes effective, Mi Tiempo Con Jesús and qualified Mexican counsel must confirm which current processing is sensitive, remove anything unnecessary, document each specific service purpose, and implement separate express written or authenticated electronic consent wherever required. A Privacy link, silence, or acceptance of the Terms will not be treated as that consent. Required legal acceptance remains disabled while this work is pending.

Once a reviewed consent is available, it may be revoked through contacto@worshipdb.com without retroactive effect. Revocation may prevent the features that cannot lawfully operate without the affected information.

Authorized members of a Team can see one another’s display name, email address, avatar, role and join date, together with shared worship content, singer and leader assignments, and synchronized changes. Owners and Administrators have the controls shown in the Service. Anyone with a valid invite code may be able to request membership, so invite codes should be shared only with intended participants.

Audit history may preserve the name of the person who made or received an important change after a role change, removal or departure. Users can also enter names or other personal data about people without a Worship DB account in singer, leader, song, list or free-text fields. The person entering that data must have authority to do so, provide any required notice or consent, enter only what is necessary, and direct the affected person to contacto@worshipdb.com for a request.

Custom profile and Team images are currently stored in a public-by-link Supabase bucket. Anyone who obtains the file URL can retrieve the image, even if that person is not a Team member. Do not upload identification documents, confidential material or sensitive images. You can replace or remove a profile or Team image through the available settings; deleted Teams also have their Team image purged after the seven-day recovery period.

This access model must receive legal and security approval or be restricted before this notice becomes effective. The final notice will describe the configuration actually deployed at that time.

Production sign-in uses Google through Supabase Auth. Worship DB does not ask Google for access to Drive, Gmail, Calendar or other Google products. The configured sign-in receives the basic identity information Google makes available for authentication: a provider and user identifier, email address, name and profile image where available. Worship DB does not receive your Google password.

You may replace the display name and profile image shown in Worship DB. Your email and underlying Google identity remain controlled through Google. Signing out ends the current Worship DB session on that device; you may also manage connected access and account security with Google. Google’s notice applies when you interact directly with Google.

Google Privacy Policy

When you use paid features, Worship DB sends Stripe your authenticated email address and processes the billing name, postal address, tax identifiers, purchase choice and billing requests you submit. Stripe returns customer, subscription, checkout, quote and invoice information, plus limited payment-method details used for account management. Our database keeps the related identifiers, Plan, interval, amount, currency, status and dates needed to operate and reconcile billing.

Stripe-hosted payment fields send complete card or other payment credentials directly to Stripe. The complete card number and security code do not enter or remain on Worship DB servers. Stripe separately processes and retains payment, billing, tax and fraud-prevention information under its own notice.

Before this notice becomes effective, the exact financial or patrimonial data and the express-consent basis required under Mexican law must be approved and implemented. Billing cannot be used to authorize unrelated purposes.

Stripe Privacy Policy

Worship DB uses cookies or equivalent browser storage needed to sign you in and remember the language, notation, theme, accent, lyrics view, font size, feature flags and selected Team. Session-only storage supports the sign-in appearance and billing return or reconciliation flow. The installed progressive web app uses a Workbox cache for static application files; the current configuration does not add API responses or Team content to a runtime offline cache.

These technologies support requested features and are not used for advertising. Signing out removes the active authentication session, while some local preferences may remain. Browser or operating-system controls can clear site data and the installed app’s cache; doing so signs you out, resets local preferences and may require static files to download again. Disabling necessary storage can prevent sign-in or other features from working.

Worship DB will not add non-essential analytics, advertising or profiling storage without first updating this notice and providing any required prior opt-in and withdrawal control.

We use Google for sign-in; Supabase for authentication, database, Realtime, file storage and Edge Functions; Stripe for billing and payments; and Cloudflare for hosting, network delivery and operational observability. They receive only the categories needed for those services and process them under their contracts, security terms and privacy notices. Music-reference links are direct visits to the destination selected by the user, not hidden Worship DB processors.

These providers and their subprocessors may process information outside Mexico. The final provider register must verify the contracted legal entity, role, production region, subprocessor chain, deletion controls, international flow and whether each disclosure is an encargado relationship or a transfer requiring another legal basis. This draft does not guess those facts.

Supabase Privacy PolicyStripe Privacy PolicyCloudflare Privacy Policy

Active account, profile, membership and worship content remains while needed to provide the Service. Scheduling Team deletion makes it read-only and disables its invite code immediately; an Owner can restore it for seven days. At the end of that period, Worship DB purges the live Team database records and Team avatar. Deletion from live systems does not mean that every provider backup disappears at the same moment.

Song audit history retains creation attribution and the latest 30 update events currently displayed by the Service. Billing, tax, invoice, subscription and legal-acceptance records may be blocked and retained for the applicable contract, tax, dispute, security or legal period. Support and privacy-request records remain only for fulfillment, evidence and applicable responsibility periods. Browser data remains until it expires, is replaced, or you clear it.

Account closure currently begins at contacto@worshipdb.com and may require cancellation of a Subscription and transfer or deletion of owned Teams. We then block and delete or irreversibly disassociate information when its purpose and lawful conservation period end, except for shared records another authorized rights holder keeps or records that law requires us to preserve.

Exact backup, infrastructure-log, provider and statutory retention periods are still being verified. They are release blockers for the final retention schedule and are not replaced by an indefinite “as long as necessary” promise.

You may request Access to your personal data, Rectification of inaccurate or incomplete data, Cancellation when it should no longer be processed, or Opposition to a specific use. You may also revoke consent or request a limit on use or disclosure. Revocation is not retroactive and may stop features that require the affected data. Editable profile information can be corrected in Settings; other requests use contacto@worshipdb.com and do not require an active Account.

A request should identify the person and a response email; describe the right and the data involved; state the requested correction and include supporting information when applicable; and identify any representative. We will request only the identity or representation evidence reasonably needed to prevent unauthorized disclosure and will delete verification copies after review unless law requires limited retention.

For a complete request, we will communicate our decision within 20 days and, if granted, fulfill it within the following 15 days. Each period may be extended once for an equal period when justified, with notice. Access is provided electronically where practical. We charge only a lawful reproduction or delivery cost and explain any full or partial denial.

If corrected or canceled data was sent to a recipient that still processes it, we will notify that recipient when required. The final notice will add the confirmed physical request address, assigned privacy owner, and the current filing instructions for the competent Mexican authority after legal review.

Worship DB uses safeguards appropriate to the reviewed risk, including encrypted network transport, Supabase row-level access rules, Team roles, restricted service-role operations, session controls, limited diagnostics, and Stripe-hosted payment fields. We require confidentiality and limited access from people and providers who handle data. No Internet service can promise absolute security.

If an incident occurs, we will assess the affected data and people, contain it, preserve necessary evidence, work with providers, and take corrective action. When a breach significantly affects a person’s economic or moral rights, we will notify affected people immediately as required by Mexican law, explain the event and affected data in useful terms, recommend protective steps, and provide a contact channel.

Worship DB is not directed to children. An Account holder must have the legal capacity required by the Terms. Because worship teams may include minors, Team managers must not enter a minor’s member, singer, leader or other personal data without lawful authority and any required notice or consent.

We do not collect a birth date or identity document merely to make an unsupported age claim. A parent, guardian or other representative may report unauthorized minor data and request its review or removal through contacto@worshipdb.com. Counsel must approve the minor-account and representation process before this notice becomes effective.

Current code review found no sale or rental of personal data, targeted advertising, cross-service profiling, session replay or third-party behavioral analytics in Worship DB. Operational request, error, security and billing records are used to run and protect the Service, not to build advertising profiles. Production settings must be reverified before this statement becomes effective.

Users may open reference links to external music or other services. The destination receives the normal information produced by that direct visit and applies its own privacy notice. Worship DB does not control that destination.

Every approved release will receive an immutable version and date. We will explain material changes and their effective date through the documented channel before they take effect, and we will obtain new consent before any new sensitive, financial, optional-purpose or non-exempt transfer processing that requires it. Prior approved versions will remain available.

The Spanish notice controls in Mexico. This English version is a convenience translation. You may contact contacto@worshipdb.com with a question, complaint, rights request, consent revocation, account-closure request or report of unauthorized minor data.

The current federal law assigns private-party personal-data protection functions to Mexico’s Secretaría Anticorrupción y Buen Gobierno. Qualified Mexican counsel must confirm the authority name, filing channel, remedy instructions and all incomplete release details on the publication date. Until then, this draft remains noindex and legal acceptance stays disabled.