Privacy Policy

This Privacy Policy explains how OWLMOB LLC, a Michigan limited liability company doing business as Tonobox (“Tonobox,” “OWLMOB,” “we,” “us,” or “our”), collects, uses, discloses, retains, and protects personal information in connection with:

• the Tonobox website at tonobox.com;
• the Tonobox web application;
• Tonobox public set-list pages;
• subscription and customer-support services; and
• any related website, application, feature, or service that links to this Privacy Policy.

Together, these are called the “Service.”

By accessing or using the Service, you acknowledge the practices described in this Privacy Policy.

1. Who We Are

Tonobox is a cloud-based music planning and collaboration platform intended primarily for churches, ministries, worship teams, worship leaders, music directors, singers, musicians, bands, and similar organized musical groups.

The Service is operated by:

OWLMOB LLC Michigan, United States Privacy inquiries: info@owlmob.com Customer support: info@owlmob.com

2. Scope of This Privacy Policy

This Privacy Policy applies to personal information processed by OWLMOB through the Service.

It does not apply to:

• websites, applications, or services operated independently by third parties;
• information that a church, ministry, Group, or other organization processes outside Tonobox;
• third-party websites linked from songs, set lists, or other Tonobox content;
• Google’s independent processing of information associated with a user’s Google account;
• payment-card information processed directly by Stripe; or
• aggregated or de-identified information that cannot reasonably be linked to an identifiable person.

Third-party products and services are governed by their own terms and privacy policies.

3. Groups and Organizational Customers

Tonobox is organized around collaborative workspaces called “Groups.” A Group may represent a church, ministry, worship team, band, or similar organization.

A Group owner or authorized administrator may be able to:

• invite and remove members;
• assign roles and permissions;
• view and manage Group content;
• schedule members and other participants;
• manage songs, set lists, and calendar events;
• request AI-assisted features;
• create and revoke public set-list links;
• manage the Group’s subscription; and
• delete the Group.

When an organization creates or administers a Group, the organization may determine why and how certain personal information is entered into and used through Tonobox. For example, the organization may decide:

• who is invited to join;
• which permissions members receive;
• who is assigned to an event or song;
• which non-account participants are entered;
• which set lists are shared publicly;
• how historical performance records are used; and
• when members or content should be removed.

For information controlled by an organization, OWLMOB generally processes the information to provide Tonobox according to the organization’s instructions.

The organization operating a Group is responsible for:

• determining who should have access;
• assigning appropriate roles and permissions;
• obtaining any required authorizations from members and participants;
• ensuring that its use of personal information complies with applicable law;
• responding to internal organizational disputes;
• protecting information downloaded or copied from Tonobox; and
• providing any additional privacy notices required for the organization’s activities.

Privacy requests involving Group-managed information may require coordination with the applicable Group owner or organization.

4. Information We Collect

The information we collect depends on how you interact with Tonobox and which features you use.

4.1 Account and Profile Information

When you register for or maintain a Tonobox account, we may collect:

• email address;
• display name or account name;
• profile image or profile image URL;
• Firebase Authentication user identifier;
• Tonobox user identifier;
• authentication provider;
• account creation and modification timestamps;
• Group memberships;
• Group-specific roles and permissions;
• currently selected or active Group;
• preferred language;
• interface appearance and theme preferences; and
• lyrics-viewer and display preferences.

If you register using an email address and password, password authentication is handled through Firebase Authentication. Tonobox does not store your password in readable form.

If you sign in with Google, we may receive account information authorized through the Google authentication process, such as your email address, display name, profile image, and Google-linked authentication identifier. We do not receive your Google password.

4.2 Group and Membership Information

When users create, join, or administer Groups, we may collect:

• Group name;
• Group description;
• invitation code;
• Group owner or creator;
• creation and modification dates;
• membership list;
• member names;
• member email addresses;
• member profile images;
• membership status;
• roles and granular permissions;
• preferred language;
• religious-mode preference;
• calendar time zone;
• preferred first day of the week;
• Group plan;
• subscription status;
• feature entitlements;
• billing-contact information; and
• system-maintenance, migration, and deletion metadata.

A user’s display name, email address, and profile image may be copied into Group membership records so other authorized Group members can identify, assign, and schedule that person.

4.3 Song and Music Content

Authorized users may create, enter, import, or edit music-related content, including:

• song titles;
• artist names;
• lyrics;
• chord notation;
• ChordPro-formatted content;
• original musical keys;
• performance or override keys;
• notes;
• performer-specific preferred keys;
• external links;
• imported CSV content;
• content imported or extracted from user-supplied URLs where supported;
• creator and editor identifiers;
• creation and modification timestamps;
• song search indexes;
• last-performed information;
• associated set-list information; and
• AI-generated analysis and metadata.

Tonobox may normalize song titles and lyrics and create derived search tokens so authorized members can search their Group’s song library.

Private treatment of song lyrics

Tonobox does not publish song lyrics.

Song lyrics entered into Tonobox are intended to remain within the authenticated Group workspace in which they were entered. Access is limited according to Group membership, roles, and permissions.

Tonobox public set-list pages do not display:

• song lyrics;
• chord sheets;
• ChordPro source content;
• song notes; or
• AI analysis of lyrics.

A public set list may identify a song by title and may include limited planning information described in Section 4.7.

Tonobox does not maintain or offer a public, globally searchable, or OWLMOB-curated song-lyrics catalog.

Users are responsible for ensuring that they own or have sufficient licenses, permissions, or other legal authority to enter, store, process, display, or use lyrics and other musical content through Tonobox.

OWLMOB does not independently verify whether a user, church, Group, or organization holds a valid copyright license for a particular song or use.

4.4 Set Lists

We may collect and process:

• set-list title;
• draft, finalized, or archived status;
• ordered song entries;
• song-title snapshots;
• assigned song leaders;
• leader-name snapshots;
• musical-key overrides;
• creator and editor information;
• creation and modification timestamps;
• associated calendar events;
• public-sharing status;
• public-link identifiers;
• AI-generated analysis and recommendations; and
• migration, history, and processing metadata.

4.5 Calendar and Scheduling Information

When authorized users plan or manage events, we may collect:

• event title;
• event description;
• location;
• local date and time;
• start and end timestamps;
• duration;
• time zone;
• all-day status;
• recurrence pattern;
• recurrence interval;
• selected weekdays;
• recurrence end date or occurrence count;
• scheduled, cancelled, or completed status;
• associated set list;
• associated singing group;
• scheduled members;
• manually entered participants;
• occurrence-specific exceptions;
• completion information;
• creator and editor information; and
• creation and modification timestamps.

4.6 Singing Groups, Assignments, and Performance History

For Groups using member scheduling or historical features, we may collect:

• singing-group or team name;
• singing-group membership;
• rotation order;
• last-scheduled date;
• event assignments;
• song-leader assignments;
• songs performed;
• performance dates;
• leader identifiers;
• leader-name snapshots;
• original and performed musical keys;
• associated set-list information;
• associated calendar-event information; and
• positions within a set list.

Historical information may remain in a Group after a member leaves because it documents past Group activity. For example, a historical record may continue to identify who led a song at a previous event.

4.7 Public Set-List Information

An authorized user may create a public URL for a set list.

A public set-list page may display limited information such as:

• set-list title;
• set-list status;
• ordered song titles;
• assigned leader names;
• performance keys; and
• set-list creation or update timestamps.

Public set-list pages never display song lyrics.

Anyone who receives a public URL may be able to view, copy, screenshot, save, or redistribute the information displayed on that page.

Tonobox configures public set-list pages to discourage search-engine indexing. However, we cannot guarantee that a search engine, browser extension, archiving service, recipient, or other third party will not capture, cache, preserve, or redistribute a public page.

Revoking a public link prevents future access through the active Tonobox URL. Revocation does not remove copies previously:

• copied;
• downloaded;
• photographed;
• cached;
• indexed; or
• redistributed by another person.

Users should not include confidential, sensitive, or unnecessary personal information in publicly shared set lists.

4.8 Information About People Without Tonobox Accounts

An authorized Group member may manually enter the name of a singer, musician, volunteer, guest participant, or other person who does not have a Tonobox account.

This information may include:

• participant name;
• internal participant identifier;
• singing-group assignment;
• calendar-event assignment;
• song-leader assignment; and
• performance-history information.

The user and organization entering this information are responsible for having appropriate authority to provide and use it.

Users must not enter unnecessary sensitive personal information about another person.

A person who does not have a Tonobox account may contact us at info@owlmob.com to ask about personal information associated with them. Because this information may be controlled by a particular church, ministry, or Group, we may need to coordinate with the applicable Group owner before changing or deleting it.

4.9 AI Feature Information

Paid Groups may have access to optional AI-assisted features. These features are initiated by an authorized user and currently use Google Gemini models through Vertex AI or related Google Cloud infrastructure.

Depending on the requested feature, Tonobox may process:

• song lyrics;
• song titles;
• artist names;
• chord or key information;
• set-list contents;
• song order;
• assigned leaders;
• performance history;
• recently performed songs;
• preferred themes;
• Bible-reference preferences;
• user-selected criteria;
• prompts assembled by Tonobox;
• generated theme labels;
• generated Bible-reference suggestions;
• suggested songs;
• set-list titles;
• summaries;
• worship-flow suggestions;
• transitions;
• speaking prompts;
• rationales;
• confidence values;
• provider and model information;
• requester identifier;
• request identifier;
• request timestamps;
• processing status;
• token or usage counts;
• estimated processing costs;
• stale-analysis status; and
• errors or diagnostic information.

AI processing of lyrics

Tonobox does not publish lyrics when they are submitted for AI processing.

When an authorized user requests an AI feature involving lyrics, the selected content may be transmitted to Google’s Vertex AI infrastructure solely to perform the requested analysis or generation.

AI submission is optional. Lyrics are not submitted to an AI provider merely because they are stored in a Group.

Users are responsible for ensuring that they have sufficient rights and permissions to submit lyrics and other content for automated processing by Tonobox and its disclosed service providers.

Based on Tonobox’s intended Google Cloud configuration and applicable enterprise service commitments, customer prompts and content are not used to train Google’s general-purpose foundation models without permission or instruction.

Tonobox does not use Group content, lyrics, set lists, prompts, or AI results to train an OWLMOB-owned general-purpose AI model.

4.10 Billing and Subscription Information

Tonobox uses Stripe to process paid subscriptions.

When an authorized user purchases or manages a subscription, we may collect or receive:

• billing-contact user identifier;
• billing-contact name;
• billing-contact email address;
• Stripe customer identifier;
• Stripe subscription identifier;
• Stripe price identifier;
• Stripe Checkout session identifier;
• subscription status;
• trial status;
• trial start and end dates;
• current billing-period dates;
• renewal information;
• scheduled cancellation status;
• failed-payment or past-due status;
• webhook-derived billing events; and
• billing update timestamps.

Stripe directly collects and processes payment-card information and similar payment credentials. Tonobox does not intend to directly receive or store full payment-card numbers or card security codes.

Stripe’s independent processing is governed by Stripe’s terms and privacy policy.

4.11 Support and Communications

When you contact us, we may collect:

• your name;
• email address;
• account information;
• Group information;
• the content of your request;
• screenshots or other materials you voluntarily provide;
• technical details;
• our responses; and
• records concerning the resolution of the request.

Tonobox does not currently provide:

• user-to-user private messaging;
• event-notification emails;
• marketing email campaigns;
• SMS messaging; or
• push notifications.

If those features are introduced, this Privacy Policy will be updated as appropriate.

4.12 Technical, Security, and Operational Information

Our application and service providers may automatically process technical information such as:

• IP address;
• request date and time;
• requested URL;
• browser type and version;
• device type;
• operating system;
• referring page;
• network status;
• application version;
• authentication state;
• session identifiers;
• authentication and security tokens;
• Cloud Function request metadata;
• database operations;
• security-rule decisions;
• errors and diagnostic information;
• function-execution logs;
• audit and administrative metadata;
• suspected fraud or abuse signals;
• asynchronous job status;
• migration and repair metadata; and
• creation and modification timestamps.

We use this information to operate, secure, maintain, troubleshoot, and protect the Service.

With your consent, the public Tonobox website uses Google Analytics 4 to understand website visits and improve the website and signup experience. Google Analytics may process page URLs, referring pages, approximate location derived from IP address, browser and device information, language, interactions with signup links, and analytics identifiers. Tonobox does not use this integration for advertising or cross-site behavioral tracking. Google Analytics is not loaded unless you choose to allow analytics.

4.13 File Uploads

Tonobox does not currently support general user file uploads or song attachments.

Users cannot currently upload sheet-music PDFs, images, audio recordings, or similar files through the normal Tonobox song-management features.

If file-upload functionality is introduced, this Privacy Policy will be updated to address:

• permitted file types;
• file size;
• attachment metadata;
• storage;
• access;
• downloads;
• malware controls;
• retention; and
• deletion.

5. Sources of Information

We obtain information from the following sources.

5.1 Directly From You

We receive information when you:

• create an account;
• update your profile;
• create or join a Group;
• enter songs or lyrics;
• build a set list;
• create a calendar event;
• schedule a participant;
• request an AI feature;
• create a public link;
• purchase a subscription; or
• contact support.

5.2 From Other Group Members

Another Group member may provide information about you when they:

• invite you to a Group;
• add you to Group membership records;
• assign you a role;
• schedule you for an event;
• identify you as a song leader;
• add you to a singing group; or
• preserve your name in performance history.

5.3 From Group Owners and Administrators

Group owners and administrators may provide or manage:

• membership information;
• permissions;
• billing information;
• schedules;
• public links;
• Group preferences; and
• subscription information.

5.4 From Google

We may receive information through:

• Google authentication;
• Firebase Authentication;
• Firestore;
• Firebase Hosting;
• Cloud Functions;
• Google Cloud logs;
• Vertex AI; and
• related Google Cloud services.

5.5 From Stripe

We receive subscription, billing-status, transaction, and payment-event information from Stripe.

5.6 From Your Browser, Device, and Network

Technical information may be generated automatically when you access or use the Service.

5.7 From User-Supplied Websites

Where supported, an authorized user may submit a URL for an external song resource or content-import function.

Users are responsible for having authorization to provide and use the URL and any resulting content.

6. How We Use Information

We may use information for the following purposes.

6.1 Providing the Service

We use information to:

• register and authenticate users;
• maintain accounts and profiles;
• create and administer Groups;
• manage memberships, roles, and permissions;
• provide song-library functionality;
• create search indexes;
• manage set lists;
• provide calendar and recurrence features;
• schedule members and participants;
• provide performance mode;
• preserve performance history;
• create and revoke public set-list pages;
• synchronize paid feature access;
• process account and Group deletion; and
• respond to support requests.

6.2 Providing AI-Assisted Features

When requested by an authorized user, we use information to:

• analyze songs;
• identify possible themes;
• identify possible Bible references;
• recommend songs;
• generate set-list titles;
• analyze set-list flow;
• generate summaries and transitions;
• identify missing source information;
• monitor request status;
• identify stale results;
• control usage and cost; and
• investigate failures or abuse.

AI results are suggestions. They may be inaccurate, incomplete, misleading, biased, fabricated, or contextually inappropriate.

Users must independently review AI-generated content before relying on or sharing it.

AI output is not:

• pastoral advice;
• theological advice;
• legal advice;
• medical advice;
• financial advice;
• mental-health advice; or
• other professional advice.

6.3 Managing Subscriptions

We use billing information to:

• create Stripe Checkout sessions;
• create Stripe Billing Portal sessions;
• administer free trials;
• verify subscription status;
• enable or restrict paid features;
• process cancellations;
• identify failed or past-due payments;
• prevent billing fraud;
• maintain transaction records; and
• comply with accounting and tax obligations.

6.4 Maintaining Security and Integrity

We use information to:

• authenticate users;
• enforce Group membership and permissions;
• prevent unauthorized access;
• detect fraud, abuse, and suspicious activity;
• protect invitation codes and public links;
• enforce our Terms of Use;
• investigate security incidents;
• maintain audit records;
• protect our infrastructure; and
• protect the rights and safety of users, OWLMOB, and others.

6.5 Operating and Maintaining Tonobox

We use information to:

• troubleshoot errors;
• monitor service health;
• repair incomplete data;
• reconcile performance history;
• process recurring events;
• perform data migrations;
• maintain search indexes;
• test and deploy updates;
• support browser and device compatibility; and
• maintain service reliability.

OWLMOB does not use identifiable Group content, lyrics, set lists, or performance history for:

• targeted advertising;
• consumer profiling;
• sale to data brokers;
• unrelated marketing analytics;
• training a general-purpose AI model; or
• creating a shared commercial song database.

6.6 Legal and Compliance Purposes

We may use information to:

• comply with applicable law;
• respond to subpoenas, court orders, and lawful government requests;
• investigate unlawful activity;
• respond to copyright or other rights complaints;
• prevent fraud and abuse;
• establish, exercise, or defend legal claims;
• preserve information subject to legal hold; and
• enforce our agreements.

7. How We Disclose Information

OWLMOB does not sell personal information for money.

OWLMOB does not disclose personal information for cross-context behavioral advertising or targeted advertising based on activity across unrelated websites or services.

We may disclose information as described below.

7.1 Within a Group

Information may be available to authorized Group owners, administrators, leaders, and members according to their permissions.

Group-visible information may include:

• names;
• email addresses;
• profile images;
• roles;
• permissions;
• song information;
• private lyrics;
• chord notation;
• notes;
• preferred keys;
• schedules;
• assignments;
• singing-group membership;
• set lists;
• AI results; and
• performance history.

Users should understand that other authorized members may copy information they can access. OWLMOB cannot control copies lawfully downloaded, recorded, photographed, or otherwise retained outside Tonobox.

7.2 Through Public Set Lists

When an authorized user creates a public link, Tonobox makes the limited public set-list information described in Section 4.7 available to anyone with the URL.

Lyrics are never included in public set-list pages.

7.3 Service Providers

We may disclose information to vendors that process information on our behalf, including:

• Google Firebase;
• Google Cloud;
• Google authentication services;
• Google Vertex AI and Gemini infrastructure;
• Stripe;
• infrastructure, database, security, and logging providers;
• customer-support tools used to respond to requests; and
• accountants, insurers, auditors, and legal advisers.

These providers may process information for the purposes of providing services to OWLMOB, subject to applicable agreements and law.

7.4 At Your Direction

We may disclose or transmit information when you or an authorized Group administrator requests a feature that requires it, including when:

• generating a public set list;
• opening an external song link;
• initiating a Stripe billing session;
• submitting selected content to an AI feature; or
• using another third-party function.

7.5 Legal and Safety Disclosures

We may disclose information when we reasonably believe it is necessary to:

• comply with applicable law or legal process;
• respond to a lawful government request;
• enforce our agreements;
• investigate fraud or unlawful activity;
• investigate or prevent a security incident;
• respond to a copyright or other rights complaint;
• protect the rights, property, or safety of OWLMOB, users, or others; or
• establish, exercise, or defend legal claims.

Where permitted and appropriate, we may attempt to notify the affected account holder before disclosing information in response to legal process.

7.6 Business Transactions

If OWLMOB is involved in a merger, acquisition, financing, reorganization, bankruptcy, sale of assets, or similar transaction, information may be reviewed or transferred as part of that transaction.

Any successor’s use of personal information will remain subject to this Privacy Policy unless users receive legally required notice of materially different practices.

7.7 Aggregated or De-Identified Information

We may use and disclose aggregated or de-identified information for lawful purposes such as:

• system-capacity planning;
• understanding error rates;
• security analysis;
• subscription administration;
• feature operation; and
• business planning.

We will not attempt to re-identify information maintained as de-identified except as permitted by law, including testing the effectiveness of de-identification controls.

8. Song Lyrics, Copyright, and Rights Complaints

Song lyrics and other musical materials may be protected by copyright.

Tonobox does not provide users with a preloaded song-lyrics catalog and does not publish user-entered lyrics.

Users, churches, ministries, Groups, and organizations are responsible for determining whether they have sufficient rights to:

• enter lyrics;
• store lyrics electronically;
• display lyrics to Group members;
• reproduce chord sheets;
• use imported musical content;
• submit lyrics to an AI provider;
• create adaptations or arrangements; and
• otherwise use content through Tonobox.

OWLMOB does not verify:

• church copyright licenses;
• catalog coverage;
• license expiration dates;
• geographic restrictions;
• congregation-size restrictions;
• licensing-provider reporting requirements; or
• whether a particular use is permitted by a particular license.

If OWLMOB receives a credible claim that content infringes copyright or another person’s rights, we may:

• investigate the complaint;
• restrict access to the content;
• remove the content;
• notify the affected user or Group;
• request additional information;
• preserve records concerning the complaint; and
• suspend or terminate repeat infringers where appropriate.

Copyright complaints may be sent to:

OWLMOB LLC Email: info@owlmob.com Subject: Copyright Complaint

A separate Copyright and DMCA Policy may provide additional notice, counter-notice, and repeat-infringer procedures.

9. Cookies, Browser Storage, and Similar Technologies

Tonobox may use cookies, browser storage, authentication tokens, cache storage, and similar technologies necessary to:

• keep users signed in;
• maintain secure sessions;
• remember the active Group;
• store language and interface preferences;
• store theme preferences;
• store lyrics-viewer preferences;
• support progressive-web-application functionality;
• detect application updates;
• enforce security controls; and
• provide requested features.

These technologies are primarily necessary or functional.

Tonobox does not currently use:

• advertising cookies;
• third-party behavioral-advertising pixels;
• cross-site advertising trackers; or
• third-party consumer analytics tools in the authenticated Tonobox application.

With your consent, the public Tonobox website uses Google Analytics cookies and browser storage to measure visits and interactions with signup links. You can decline analytics without losing access to the website, and you can change your choice at any time through the Analytics settings control. Advertising storage, advertising user data, and ad personalization remain disabled in the Google tag configuration.

Restricting cookies or browser storage may prevent authentication or other Tonobox features from operating correctly.

Google Fonts

The public Tonobox website may obtain the Plus Jakarta Sans font through Google Fonts.

Depending on how the production website delivers and caches the font, a visitor’s browser may send technical information such as an IP address, browser details, and the requested font resource to Google.

10. External Links and User-Supplied URLs

Users may associate songs with links to:

• YouTube;
• lyrics websites;
• chord resources;
• publisher websites; or
• other third-party services.

Tonobox does not control third-party websites and is not responsible for their:

• availability;
• accuracy;
• security;
• legality;
• copyright practices;
• data collection;
• tracking;
• privacy practices; or
• terms.

Where Tonobox supports extraction or import from a user-supplied URL, the user is responsible for ensuring that:

• the user is authorized to submit the URL;
• the resulting access and copying are lawful;
• the source permits the requested use;
• no paywall or access control is circumvented; and
• the imported content may lawfully be stored and processed through Tonobox.

Tonobox may restrict or discontinue access to a particular source or import function if it creates legal, security, reliability, or operational concerns.

11. Data Retention

We retain information for the period reasonably necessary to provide the Service and fulfill the purposes described in this Privacy Policy.

11.1 Active Accounts and Groups

Account and Group information generally remains stored while the applicable account or Group exists.

Group-owned content may remain available to the Group after the individual who created it leaves.

This may include:

• songs;
• private lyrics;
• chord notation;
• notes;
• set lists;
• calendar events;
• assignments;
• AI results; and
• performance history.

11.2 Historical Records

Historical records may preserve:

• former member names;
• song-leader names;
• prior assignments;
• songs performed;
• performance dates;
• set-list information; and
• musical keys used.

This information may remain because it records the Group’s historical activities.

11.3 Deleted Accounts and Groups

Users may delete their accounts through the account settings page.

Under Tonobox’s current design:

• deleting a Group owner’s account also deletes the owned Group;
• an active Group subscription must be cancelled before account deletion is completed; and
• Group ownership is not currently transferable.

When content, an account, or a Group is deleted:

• active records may be deleted or marked for deletion;
• cleanup may occur asynchronously;
• deletion may not occur simultaneously across every database, cache, log, and processing system;
• information may remain temporarily in provider-managed backups;
• security and fraud records may remain where reasonably necessary;
• billing and transaction records may remain where legally required; and
• information subject to a legal hold may be retained.

Tonobox cannot delete copies previously downloaded, copied, photographed, or independently stored by another user.

11.4 Billing Records

Billing and transaction records may be retained as reasonably necessary for:

• accounting;
• taxation;
• audits;
• payment disputes;
• fraud prevention;
• legal compliance; and
• enforcement of our agreements.

Stripe may independently retain payment and transaction information under Stripe’s policies and legal obligations.

11.5 AI Records

AI inputs, results, request metadata, provider and model information, token usage, requester identifiers, errors, and processing status may remain associated with the Group while the Group exists, unless deleted earlier through available functionality or a valid request.

Google may retain provider-side service, safety, and abuse-monitoring information according to the applicable Google Cloud terms and configured settings.

11.6 Logs and Backups

Technical, security, and operational logs may be retained for a reasonable period based on:

• security needs;
• troubleshooting;
• fraud prevention;
• system maintenance;
• legal obligations; and
• dispute resolution.

Tonobox relies on standard Firebase and Google Cloud replication, backup, logging, and disaster-recovery capabilities.

OWLMOB does not currently maintain a separate customer-accessible archival backup system or promise a specific recovery point, recovery time, or backup-retention period.

Information deleted from active systems may remain temporarily in isolated or provider-managed backup systems until overwritten or removed through applicable provider retention cycles.

12. Security

OWLMOB uses administrative, organizational, and technical safeguards designed to protect information.

These may include:

• Firebase Authentication;
• password and federated identity controls;
• Group-based authorization;
• role and permission checks;
• Firestore security rules;
• server-side validation;
• restricted backend functions;
• limited public-data projections;
• encryption provided by Google Cloud in transit and at rest;
• access logging;
• billing-event verification;
• abuse-prevention controls; and
• backend cleanup and repair processes.

No internet service, authentication method, transmission method, database, or storage system is completely secure.

We cannot guarantee that information will never be:

• accessed without authorization;
• altered;
• disclosed;
• lost;
• intercepted; or
• destroyed.

Users are responsible for:

• maintaining the confidentiality of their passwords;
• using strong and unique passwords;
• protecting devices used to access Tonobox;
• signing out of shared devices;
• limiting distribution of invitation codes;
• assigning appropriate Group permissions; and
• notifying us of suspected unauthorized access.

Suspected security incidents may be reported to info@owlmob.com.

13. Children’s Privacy

Tonobox is not directed to children under 13.

Children under 13 may not create Tonobox accounts.

We do not knowingly collect personal information directly from children under 13. If we learn that a child under 13 created an account or directly submitted personal information, we may suspend or delete the account and associated information.

Churches and youth ministries may use Tonobox for organizational planning. In that context:

• account holders must be at least 13;
• users between 13 and the age of legal majority should use Tonobox only with the involvement and permission of a parent or legal guardian;
• organizations are responsible for determining whether youth-team use is appropriate and lawful;
• administrators must not enter unnecessary personal information about minors;
• public set lists should not include unnecessary personal information about minors; and
• users must not enter identifiable information about a child under 13 unless they have appropriate parental or guardian authorization and a lawful basis to provide it.

A church or organization may use an adult administrator’s account to schedule a youth participant by name. The organization is responsible for obtaining any authorization required for that activity.

If you believe Tonobox has received personal information directly from a child under 13, contact info@owlmob.com.

14. Your Privacy Rights and Choices

Depending on where you live and whether applicable law covers OWLMOB’s processing, you may have rights concerning your personal information.

OWLMOB will make reasonable efforts to provide the request options described below to United States users, even when a particular state privacy statute may not legally require every listed right.

14.1 Access

You may request:

• confirmation that we process personal information associated with you;
• access to personal information associated with your account; and
• information concerning the categories of personal information we process.

14.2 Correction

You may correct certain account and profile information through Tonobox.

You may also request correction of inaccurate personal information by contacting us.

Some historical or Group-managed records may preserve the information that existed at the time of an event. We may coordinate with the applicable Group owner or preserve a record where reasonably necessary for security, legal, billing, or historical purposes.

14.3 Deletion

You may delete your account through the account settings page.

You may also request deletion by contacting us.

Deletion may be limited where information must be retained to:

• complete a transaction;
• provide a requested service;
• protect security;
• prevent fraud;
• comply with law;
• preserve billing or tax records;
• establish or defend legal claims;
• document a copyright complaint; or
• preserve legitimate Group historical records.

Deleting an individual account does not necessarily delete Group content created by that individual when the individual does not own the Group.

When a person deletes an account but does not own a Group, Tonobox may replace the account's Firebase identifier in Group-managed records with the person's existing Group display name. This removes the account linkage while allowing collaborative and historical Group records to remain understandable.

Scheduling cancellation of a Group subscription does not schedule deletion of the account or Group. The user must return and request deletion manually. If the user deletes the account before a canceled subscription's paid-through date, the remaining access period is forfeited without refund except where required by law.

14.4 Portability

You may request a portable copy of certain personal information where technically feasible or legally required.

Tonobox does not currently provide a comprehensive self-service export for all songs, set lists, calendar records, history, or Group files.

14.5 Withdrawal of Consent

Where processing is based on consent, you may withdraw that consent for future processing.

Withdrawal does not affect processing that occurred before consent was withdrawn.

Some processing is necessary to operate Tonobox. Withdrawing authorization for essential processing may require you to stop using the relevant feature or delete your account.

14.6 Public-Link Controls

Authorized users may revoke public set-list links through Tonobox.

Revocation does not remove copies previously accessed or preserved by others.

14.7 Advertising and Sale Opt-Outs

Tonobox does not currently:

• sell personal information;
• share personal information for cross-context behavioral advertising;
• use personal information for targeted advertising; or
• use automated profiling to make decisions that produce legal or similarly significant effects.

Tonobox therefore does not currently display a “Do Not Sell or Share My Personal Information” link.

If these practices change, we will update this Privacy Policy and provide any legally required choices.

14.8 Submitting a Privacy Request

To submit a request, contact:

Email: info@owlmob.com Subject: Privacy Request

Please include:

• your name;
• the email address associated with your Tonobox account;
• the relevant Group, if applicable;
• the right you wish to exercise; and
• sufficient information for us to understand the request.

We may require reasonable verification before fulfilling a request. Verification may include confirming control of the account email address.

Information collected to verify a request will be used only to verify, document, and respond to the request, except where otherwise required by law.

14.9 Authorized Agents

Where permitted by applicable law, you may authorize another person to submit a request on your behalf.

We may require:

• proof that the person is authorized to act for you;
• verification of your identity; and
• direct confirmation that you authorized the request.

14.10 Appeals

If we deny a privacy request, you may appeal by replying to our response or emailing info@owlmob.com with the subject:

Privacy Request Appeal

The appeal should explain why you believe the decision should be reconsidered.

14.11 No Unlawful Discrimination

OWLMOB will not unlawfully discriminate against a user for exercising an applicable privacy right.

Certain information is necessary to provide Tonobox. Deleting that information may prevent us from maintaining the account, membership, subscription, or requested feature.

15. Supplemental United States Privacy Disclosures

This section supplements the rest of this Privacy Policy for residents of states with comprehensive consumer privacy laws.

The applicability and scope of these laws may depend on:

• OWLMOB’s revenue;
• the amount of personal information processed;
• the nature of the customer relationship;
• statutory exemptions;
• whether an organization acts in a commercial or nonprofit capacity; and
• the particular state involved.

15.1 Categories of Personal Information

During the preceding 12 months, we may have collected the following categories:

Category Examples Identifiers Name, email address, account identifier, Firebase identifier, Stripe identifier, IP address Contact and account information Profile information, membership records, billing-contact information Commercial information Subscription plan, trial status, billing status, renewal and transaction records Internet or electronic activity Authentication activity, requests, browser information, device information, logs Approximate location General location that may be inferred from an IP address Visual information Profile image and screenshots voluntarily provided to support Organizational information Church, ministry, Group, team, role, and permission information User-generated content Songs, private lyrics, chords, notes, set lists, schedules, assignments, links, and prompts Inferences and generated information AI-generated themes, summaries, suggestions, references, and confidence values Authentication information Password-related authentication records, security tokens, and login state

Tonobox does not request precise device geolocation.

15.2 Categories of Recipients

We may disclose relevant categories of information to:

• Group owners and authorized members;
• Google Firebase and Google Cloud;
• Google authentication services;
• Google Vertex AI;
• Stripe;
• security, infrastructure, and support providers;
• professional advisers;
• government or legal authorities where required; and
• parties involved in a business transaction.

15.3 Sale and Targeted Advertising

During the preceding 12 months, OWLMOB has not sold personal information for monetary consideration.

OWLMOB has not knowingly sold or shared personal information of users under 16 for behavioral advertising.

OWLMOB does not currently disclose personal information for cross-context behavioral advertising or targeted advertising.

15.4 Sensitive Information

Tonobox may process authentication information necessary to secure accounts.

Tonobox is not intended to collect:

• Social Security numbers;
• driver’s-license numbers;
• passport numbers;
• financial-account passwords;
• medical records;
• precise location;
• biometric identifiers;
• immigration records;
• private sexual information; or
• other highly sensitive information unrelated to music planning.

Users must not submit such information through songs, notes, events, Group descriptions, support requests, or other fields unless specifically requested by OWLMOB for a lawful and necessary purpose.

15.5 California Residents

Subject to applicable thresholds, exceptions, and verification requirements, California residents may have rights to:

• know the categories of personal information collected;
• know the sources and purposes of collection;
• know the categories of recipients;
• access specific pieces of personal information;
• request correction;
• request deletion;
• opt out of sale or sharing;
• limit certain uses of sensitive personal information; and
• receive nondiscriminatory treatment.

Tonobox does not currently sell or share personal information for cross-context behavioral advertising.

California residents may submit requests through the process in Section 14.

15.6 Residents of Other States

Depending on applicable law, residents of other states may have rights to:

• confirm whether personal information is processed;
• access personal information;
• correct inaccuracies;
• request deletion;
• obtain portable information;
• opt out of sales;
• opt out of targeted advertising;
• opt out of certain profiling;
• obtain information about recipients; and
• appeal a denied request.

The availability and scope of these rights depend on the applicable state law.

16. Consumer Health and Other Sensitive Information

Tonobox is a music-planning service and is not intended to collect consumer health information.

Information such as:

• musical-key preferences;
• vocal assignments;
• singing-group membership;
• rehearsal participation; or
• performance history

is collected for music planning and is not intended to describe a medical condition or health status.

Users must not use Tonobox to store:

• diagnoses;
• treatment information;
• medication information;
• medical histories;
• counseling records;
• reproductive or sexual-health information;
• disability records; or
• other consumer health data.

Contact info@owlmob.com if health-related information is accidentally submitted and should be removed.

17. Data Location and International Processing

Tonobox is operated from the United States and is currently intended for users in the United States.

Tonobox’s primary Firebase and Google Cloud resources are configured in the central United States.

However:

• Google and Stripe operate distributed infrastructure;
• network traffic may be routed through other locations;
• support and security operations may occur from other jurisdictions;
• subprocessors may operate in other countries; and
• provider-managed logs or service metadata may be processed outside the primary region.

Use of Tonobox may therefore involve processing in the United States and other locations where our service providers operate.

Tonobox does not currently market the Service specifically to residents outside the United States.

18. Data Processing Agreements

A church, ministry, or other organizational customer may act as the primary decision-maker for personal information entered into its Group.

OWLMOB may act as a service provider or processor for that information by providing storage, authentication, scheduling, AI processing, and related application functions.

OWLMOB does not currently provide a standard Data Processing Addendum through the public website.

An organizational customer that believes it legally requires a Data Processing Addendum may contact info@owlmob.com.

Availability of a Data Processing Addendum is not guaranteed unless separately agreed in writing by OWLMOB.

19. Service Availability and Data Recovery

Tonobox depends on third-party cloud infrastructure, including Firebase and Google Cloud.

We do not guarantee:

• uninterrupted operation;
• error-free operation;
• a specific uptime percentage;
• continuous availability during a performance;
• offline availability;
• a specific recovery time;
• a specific recovery point; or
• restoration of every deleted or corrupted record.

Users should maintain legally permitted independent copies of information that is essential to a rehearsal, service, performance, regulatory obligation, or organizational record.

20. Changes to This Privacy Policy

We may update this Privacy Policy to reflect:

• changes to Tonobox;
• new features;
• new service providers;
• changes to our information practices;
• legal or regulatory developments;
• security requirements; or
• organizational changes.

We will update the “Last Updated” date when the Privacy Policy changes.

If a change materially affects how we collect, use, or disclose personal information, we may provide additional notice through:

• the Service;
• email;
• a website notice; or
• another reasonable method.

Where applicable law requires affirmative consent for a new processing activity, continued use alone will not substitute for that consent.

21. Contact Us

For privacy questions, requests, complaints, or concerns, contact:

OWLMOB LLC Michigan, United States

Privacy email: info@owlmob.com Support email: info@owlmob.com

Suggested subject lines:

• Tonobox Privacy Inquiry
• Privacy Request
• Privacy Request Appeal
• Security Report
• Copyright Complaint