Last Updated: October 15, 2026
Effective Date: October 15, 2026
L&P Inventions, LLC, doing business as WorshipMetrics ("we," "us," or "our"), provides the WorshipMetrics cloud application, desktop Tech Manager, related monitoring and support, and hosted media and public-facing features (the "Service"). This Policy explains how we collect, use, disclose, retain, and protect personal information through those services and our websites.
It applies to account holders, organizational personnel, support participants, website visitors, public viewers, and people whose information is submitted through our features. Not every feature collects every category described here. Collection depends on the feature, configuration, and information supplied.
For ministry records supplied by a church or other customer organization, the organization generally determines the purposes and means of processing, and we act as its processor or service provider under applicable agreements. For our own account administration, billing, website operations, security, and other independently determined purposes, including disclosed support improvement where applicable, we act as the responsible business or controller. Our role depends on the particular processing; a label does not override our actual responsibilities.
If a request concerns information a church controls, contact that church or contact us for assistance identifying the appropriate organization. We act on its lawful instructions where required, while handling requests involving our own processing directly. A church's independent activities and third-party services have their own notices. Accepting organizational terms or receiving this Policy is not a substitute for any separate consent required by law.
We process names, email addresses, telephone numbers, organizational affiliations, roles, invitations, account identifiers, authentication and session information, preferences, and verification records. We also process support contacts, plan and subscription information, invoices, billing addresses, payments, refunds, and usage needed to administer charges.
Our payment processor receives payment credentials through its payment interfaces. We receive transaction details, payment references or tokens, and limited payment-method information needed to administer the account. Do not send full card numbers, bank credentials, or security codes through support or general-purpose fields.
Giving records entered into ministry features are distinct from the organization's payment to WorshipMetrics. The existence of a giving record does not mean we processed the underlying donation.
Depending on the features used, an organization may supply member and household details, contact information, photographs, birthdays, attendance, service plans, volunteer schedules, availability, assignments, registrations, check-in information, giving records, documents, messages, notes, and prayer requests.
Supported adult-managed workflows may contain information about children, guardians, accommodations, allergies, or other care needs. Organizations should limit collection to information necessary for the intended feature and configure access appropriately.
Authorized organizational users may view, update, export, or otherwise manage records within their permissions. Leaving an organization or deleting an individual login does not automatically delete organizational records about that person. Those records may remain subject to the organization's retention obligations and individuals' applicable rights.
Tech Manager and connected integrations may collect device names, identifiers, IP and MAC addresses, network topology, software versions, operating-system and hardware status, connected-device configuration, connectivity results, performance, audio levels, stream and recording status, errors, and diagnostic logs.
Disclosed discovery and monitoring may run in the background while enabled. Information needed for cloud dashboards, alerts, support, and authorized remote operations may be transmitted from the local environment to our systems and providers. This does not mean we collect every file or all network traffic on a computer.
We retain records of relevant commands, results, approvals, and administrative actions, including the actor, time, scope, and communication method where available. Controls can disable or limit supported monitoring features, with corresponding effects on functionality and support.
This telemetry describes equipment rather than people, although a device identifier or log entry can sometimes relate to a person. It is used for live monitoring, diagnostics, Sunday-service reliability, and Self Healing. It is also used to improve the Service, as described in Section 8.
Self Healing watches the streams and recordings started from WorshipMetrics. When one stops unexpectedly, Self Healing does not restart it by itself; it asks a person first. The request appears on the booth computer and under Alerts in the WorshipMetrics app, where anyone at the booth or signed in to your organization can approve the restart or leave it off, and people who opt in can also receive it by email or text message. Nothing is restarted unless someone approves, and a request nobody answers ends after ten minutes with nothing restarted. We keep a record of each request and of who answered it. Self Healing is on by default and can be switched off for each Tech Manager. The only things the Tech Manager restarts without asking are its own parts: if the Tech Manager or its presentation output closes unexpectedly, it can reopen itself and put back what it was already showing, and it reports each time it does so on the booth and under Alerts.
Depending on enabled features, we process uploaded files, livestreams, recordings, images, audio, transcripts, captions, thumbnails, clips, presentation content, and associated metadata. Remote previews may transmit still frames or other disclosed preview information to authorized operators. Media can contain identifiable congregants, visitors, volunteers, or other people.
Some detection operates locally, such as supported in-browser MediaPipe processing. Other features send selected snapshots, audio, or other relevant inputs to cloud vision, transcription, or AI providers. Setup and feature disclosures identify material processing differences.
Our people-counting feature is intended to count people rather than identify them by face. We do not use that feature to create named facial-recognition profiles. Images can nevertheless be personal information. Where enabled, demographic estimates or other inferred characteristics are estimates and may be inaccurate; they are not identity verification or appropriate substitutes for individual facts in consequential decisions.
Authorization to preview a camera does not itself authorize making its feed public, recording a support session, or using private camera material for general support-model training. Organizations must provide the notices and obtain the permissions required for their own cameras, recordings, and broadcasts.
When someone views or interacts with a hosted page or player, we may process IP address, browser and device information, session or viewer identifiers, approximate location, page and media requests, playback events, watch duration, and abuse-prevention information. We use this information to deliver media, measure usage and performance, provide the organization's available analytics, and protect the Service. Reporting may include aggregate counts and information associated with a particular viewer or session where the feature supports it; viewing is not necessarily anonymous.
Public chat and other public contributions are visible to the audience identified in the feature. Prayer requests and private submissions are routed to the relevant organization rather than public chat, unless a feature clearly offers publication and the user selects it. They may be accessible to organizational users under the account's permissions and designated recipients; they are not automatically limited to a pastor. Submission notices should be reviewed before providing sensitive information.
Public material may be indexed, downloaded, copied, or redistributed. Unlisted links can be forwarded. Restricted access does not prevent an authorized recipient from making an independent copy. External embeds, social destinations, and podcast clients may process information under their own policies.
We collect support messages, contact details, recordings, transcripts, summaries, attachments, screenshots, diagnostic context, troubleshooting actions, resolutions, and feedback. Screen sharing may expose notifications, other applications, and files visible on the shared display. Close unrelated material and avoid supplying unnecessary sensitive information.
Support-line calls are recorded and transcribed, including transfers to staff unless recording is stopped or another arrangement is expressly provided. We give notice before recording and obtain consent as required. Participants who do not agree should use an available non-recorded channel, such as email, or ask about alternatives. Screen and video capture have their own authorization. Using email avoids a call recording but does not automatically exclude eligible correspondence from disclosed improvement uses.
Designated personnel may access information reasonably needed for support, testing a fix against real customer data, operating or securing the Service, or complying with law. This may include an administrative view without your password and access outside an active support request. Access is purpose-limited, subject to confidentiality and access controls, and administrative support sessions and remote actions are logged.
Staff access does not independently authorize publication or training. We do not need your account password to provide administrative support. If a credential or unrelated sensitive item is inadvertently captured, we restrict and remove it from ordinary support or improvement use when identified, subject to necessary legal preservation.
Member data, attendance records, AV inventory, and church information are isolated to your organization. Other churches can never see them, and within your church only the people you invite can use your account.
A small number of WorshipMetrics support staff can also open your organization's account when that is reasonably needed: to help with something you asked about, to confirm that a fix we made is working on your real data, to keep the service running and secure, or to meet a legal obligation. Staff use a support view that never needs your password, look only at what the task needs, and every such session is logged.
Support transcripts, chats, and case history are kept while your account is active, so we can help with problems that come back and improve our support; you can ask us to delete them at any time.
AI features may send relevant prompts, conversations, documents, media, technical context, and tool results to providers to return an answer, analyze information, generate content, or perform an authorized operation. This can include assistants, transcription, snapshot analysis, artwork, captions, summaries, and clips. Sending a request for processing is different from using it to train a model.
Features such as Journey (the automated assistant in the app and on our 910-WORSHIP support line), sermon transcription, and content generation send the relevant text, audio, or diagnostic context to AI providers (which may include Anthropic, OpenAI, and Google) and transcription providers (such as AssemblyAI) to produce a result. We send only the data needed for the requested feature and do not authorize these providers to train foundation models on your congregation's private data.
Eligible support recordings, transcripts, messages, technical attachments, diagnostic information, troubleshooting steps, outcomes, and feedback may be used to improve support quality and reliability. Specific activities include improving code and diagnostic logic; finding recurring failures; developing technical documentation, prompts, and retrieval knowledge bases; and developing, training, fine-tuning, testing, and evaluating our support, speech, and diagnostic models.
This learning may benefit multiple organizations. We do not claim that every interaction enters a training run or that every described technique is currently in use. A retained recording or transcript is not necessarily a trained model, and a stored knowledge-base example is not the same as a change to a model's underlying parameters.
The defined improvement use is disclosed during organizational enrollment as part of the service model. Where processing requires separate consent, we obtain it and honor applicable withdrawal and privacy rights. Organizational acceptance does not replace an individual's legally required consent. If a restriction affects a feature, we explain the effect and available alternatives. We do not silently apply materially expanded uses to data collected under an earlier contrary commitment.
The agreement your church accepts at setup. This is the wording presented during enrollment, which every church accepts as a condition of use:
Using WorshipMetrics includes agreeing that we may use your church's support calls, chats, and troubleshooting history, and the system data the Service collects (such as device status and history, network outages, devices that stop responding, and disk and performance measurements), to operate and improve the Service, including to train and test WorshipMetrics' own AI and to study patterns across many churches. Before this use we remove passwords and personal details such as names, phone numbers, and email addresses, and we never use member lists, pastoral notes, children's information, or camera footage for it. Anything we share or publish from this work never identifies a church or a person. Our AI providers are not authorized to train their own models on this data. Your church agrees to this during setup, and it is a condition of using WorshipMetrics. Questions: [email protected].
We exclude credentials, payment credentials, unrelated personal identifiers, member lists, pastoral or prayer confidences, health information, children's information, private camera footage, and unrelated documents from general support-training datasets. These exclusions follow the information even if it appears in a support screenshot, transcript, or attachment. We screen and redact material for those datasets and correct identified failures; we do not claim sensitive information can never be incidentally submitted.
Audio can identify a speaker even after names are removed. Eligible raw audio is used only for disclosed support and voice-system improvement within the applicable retention period and permissions. We do not use this permission to clone a person's voice, create an identity voiceprint, or publicly distribute an identifiable recording.
Providers for our managed service process information under applicable contractual restrictions. We do not authorize them to use supplied customer information for their independent general-purpose model training. Their operational retention, abuse monitoring, and deletion processes remain relevant and are evaluated for the service we use. Independent services a customer connects may have different terms disclosed for that connection.
We do not sell identifiable support conversations, publicly identify a church or person in training examples without permission, or intentionally expose one organization's private records in another's support answers. Appropriately deidentified examples and generalized technical knowledge may be retained separately from identifiable sources where lawful. Removing a name alone is not sufficient if the remaining material can reasonably identify someone.
Source retention, closure, and withdrawal are described in Section 15. Deleting sources does not automatically reverse completed lawful model training, but legal obligations concerning unlawful collection, retention, or model use still apply.
Information comes from you; an organization and its authorized users; parents, guardians, or authorized representatives; devices and Service activity; connected integrations; and outputs or inferences produced by requested features. Referral or publicly available business information may also be used where lawful for customer relationships and support. We do not treat public availability as unrestricted permission for every use.
We use relevant information to:
Where a legal basis is required, it depends on the activity and may include contract performance, legal obligations, valid consent, or legitimate interests that are not overridden by individuals' rights. Sensitive information may require an additional legal condition. An organization's contract is not a blanket legal basis for all information about other people. We do not generally claim that ordinary use of the Service amounts to explicit sensitive-data consent.
We use providers appropriate to the enabled feature. These may include:
| Provider or category | Purpose |
|---|---|
| Clerk | Authentication and account sessions. |
| Stripe | Subscription payments, billing, and related payment administration. |
| Resend | Email delivery. |
| Twilio | Supported telephone, recording, and messaging functions. |
| Railway and Neon | Application hosting and database services. |
| Cloudflare, including R2 and streaming services | Storage, content delivery, streaming, and related security or media processing. |
| Anthropic, OpenAI, Google, AssemblyAI, and Moondream | Applicable AI, transcription, speech, or vision features. |
| Sentry and other error-monitoring, security, and technical-support providers | Diagnosing faults and protecting the Service (Sentry receives error reports from the app and Tech Manager), with data limited according to their function. |
| Backblaze B2 | Encrypted backups of files and the database. |
| Google Ads and applicable website-measurement services | Disclosed advertising measurement and website activity described in Section 14. |
Not every provider receives every category of information. Locally executing software, such as a local detection library, is not necessarily a recipient of the images it processes. Use of an S3-compatible storage interface does not by itself mean information is stored by Amazon Web Services.
We maintain provider information appropriate to the services in use and make current details available through our published provider information or on request at [email protected]. Contracted processors are restricted to authorized purposes and appropriate confidentiality and security obligations. We apply any additional provider-change notice or objection procedures required by an applicable data-processing agreement.
Customer-connected destinations, such as YouTube, Facebook, Instagram, Planning Center, or other supported services, may process information under their own terms and the permissions granted. A provider acting independently is not necessarily our processor merely because it connects to the Service. Integration permissions do not override restrictions on training or other use of provider-sourced information.
Where supported and authorized, connected social accounts may provide account or Page identifiers, profile and contact information, access tokens, granted permissions, publication metadata, and available engagement or audience information. We use the granted access for the requested connection, publishing, streaming, reporting, troubleshooting, and security functions. We do not collect every category an external platform makes available merely because an account is connected.
Disconnecting an integration stops new access through that connection as described in the product. You may also revoke permissions in the external provider's account settings. Neither action necessarily deletes information previously imported into organizational records or copies held independently by that provider.
To request deletion of connection credentials or imported personal information we hold, email [email protected], identify the integration and organization if known, and explain what you want deleted. We distinguish deletion from deactivation, verify authority where appropriate, and explain any retention exception. A request is not invalid solely because you have not first completed every available disconnection step. Provider-side information must also be addressed through that provider where outside our control.
We disclose relevant information to organizational users and designated recipients according to the feature and permissions; contracted providers; destinations selected by authorized users; and advisers who need it for professional services and are subject to appropriate duties.
We may disclose necessary information to respond to lawful process, comply with reporting obligations, investigate fraud or serious abuse, protect people or systems where legally permitted, or establish and defend legal claims. Copyright notices and counter-notices may be forwarded to affected parties as part of that process. A complaint does not automatically authorize disclosure of unrelated account records.
In a merger, financing, reorganization, or sale of the relevant business, information may be disclosed to participants subject to appropriate safeguards and existing privacy obligations. We may disclose information at your direction or with valid consent. Properly deidentified or aggregate information may be used and disclosed where it does not reasonably identify a person or organization; we do not seek to reidentify it except as permitted for assessing deidentification or other lawful purposes.
We do not sell member records, prayer or pastoral information, children's records, health information, private media, or identifiable support conversations. Advertising-related information and applicable choices are described separately below; a statement about receiving no money would not by itself resolve whether an activity is a legally defined sale or sharing.
We use contact information to deliver account, security, billing, support, scheduling, and other requested communications. Marketing permissions are handled separately where required. Accepting Terms, being listed in an organization, or receiving a support message does not automatically authorize every type of marketing or automated call.
For supported text programs, applicable SMS terms describe message types, frequency, carrier charges, help, and opt-out methods. We honor recognized revocation methods and required suppression. A stopped text channel may affect the delivery of service alerts, but does not necessarily cancel a subscription or prevent necessary notices through another lawful channel.
Marketing email includes an unsubscribe method. Necessary account and legal notices may continue through appropriate channels. Organizations initiating communications must maintain their own lawful recipient permissions. We remain responsible for the communications we initiate and for our applicable duties as a service provider.
If you opt in to text messages from WorshipMetrics, we use your mobile number only to send the texts you signed up for. WorshipMetrics Sunday readiness texts are operational text messages from WorshipMetrics, the church production and operations platform run by L&P Inventions, LLC. The program covers Sunday readiness alerts to the volunteers who run a church's audio, video and livestream, status updates on support tickets to the people who opened or follow them, one-time verification codes to people who ask the app for one, and internal alerts to our own on-call staff. They are never marketing or promotional messages. Message frequency varies, usually a few messages a week around your services. Message and data rates may apply. Reply STOP to cancel, HELP for help.
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Information sharing to subcontractors in support services, such as customer service, is permitted. All other use case categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.
Mobile numbers and text opt-in consent are never sold, rented or shared with third parties or affiliates for their marketing or promotional purposes. Reply STOP to any text to cancel. For help, reply HELP to any text, email [email protected], or call (910) 967-7447. The full SMS terms, including how consent is collected for each kind of message, are published at https://worshipmetrics.com/sms-terms/.
See our SMS terms for the full program terms.
Calls to our support line, (910) 967-7447, are recorded and transcribed to help our team support your church and to keep improving our help. The greeting says so first, and by staying on the line you agree to the recording. Support PINs are never recorded. Recordings are deleted 90 days after the call; transcripts are kept (see Section 15, Retention and deletion).
We use cookies, local storage, and similar technologies for authentication, security, preferences, and functionality. Website activity may also be processed for analytics and advertising measurement, including through Google Ads. Such tools may receive identifiers, IP and device information, visited pages, referral information, and conversion events, depending on configuration and your choices.
We distinguish marketing-site measurement from the processing of private ministry and support content. We do not use private ministry records or support conversations to create third-party advertising audiences. Advertising technologies must not be treated as essential merely because they support our marketing.
Where law requires it, we obtain consent before nonessential technologies operate and provide an accessible way to change preferences. Browser storage can also be managed through browser settings, although disabling essential storage can affect functionality. Embedded third-party services may have separate controls and notices.
Some advertising disclosures can constitute a sale, sharing, or targeted advertising under applicable law even when no money is paid for information. Where such activity occurs and the law provides a choice, we offer the applicable opt-out and honor recognized Global Privacy Control signals as required. Older Do Not Track signals do not have a uniform effect; they are handled where law requires. You may contact [email protected] for privacy choices or help locating available controls. Request handling does not substitute for automatic signal recognition where required.
We retain information for the described purpose and applicable period, considering sensitivity, account status, contractual instructions, and legal duties. We periodically review continuing need rather than treating an active account as permission to keep every item forever.
| Category | Normal retention approach |
|---|---|
| Support-call audio | Deleted 90 days after the call, including recording-provider copies under our control. A recording is kept longer only when the call involved a threat or a possible risk of harm to someone, until it is no longer needed for safety or legal purposes. |
| Support transcripts, messages, case records, and relevant attachments | Retained during the active account while reasonably needed for support history and disclosed improvement, subject to periodic review and applicable deletion requests. |
| Raw monitoring telemetry | Up to 60 days. Selected diagnostics retained in a case follow the case schedule; billing usage and security evidence have separate purposes. |
| Member, ministry, scheduling, and giving records | Retained according to organizational instructions, available controls, continuing service needs, and applicable legal duties. |
| Hosted streams, recordings, clips, and media | Retained according to the actual plan, disclosed settings, deletion controls, and account status. Temporary processing files may have shorter lifecycles. No permanent archival service is implied. |
| Identifiable support-improvement source copies | No longer than the underlying source period. Copying material into a dataset does not restart its clock. |
| Account, billing, consent, approval, and audit records | Retained as reasonably necessary for the relationship, accounting, proof of authorization, security, disputes, and legal duties; access and purpose are limited accordingly. |
| Properly deidentified examples, aggregate statistics, and generalized technical knowledge | May be retained while useful and lawful, separately from identifiable source information. |
Deleting audio does not automatically delete its transcript or summary. Deleting a source document may also require deleting associated identifiable excerpts, retrieval records, or other source copies; calling a copy a dataset does not exempt it from applicable deletion.
After organizational termination, an authorized administrator may request available exports for 30 days unless immediate deletion was requested, the information already expired, or release is restricted by law or security. We delete Organization Content from active systems within 30 days after a verified organizational deletion request or within 30 days after that export window ends, subject to the exceptions below. Residual backup copies expire on a fixed schedule: file backups within 30 additional days and database backups within 120 additional days. They are isolated from ordinary use, and applicable deletions are reapplied after restoration.
Information may be preserved beyond normal periods where needed for legal obligations, lawful preservation requests, security investigations, fraud prevention, billing, or disputes. We limit such retention and access to the relevant purpose. Sensitive evidence retained for reporting or legal process is not eligible for ordinary support training.
Individual privacy requests are handled within applicable legal timeframes and may involve the organization controlling the information. We direct contracted processors to perform required deletion and address their copies through applicable agreements. Independent providers, customer devices, published podcast copies, and recipients' downloads are not all under our control.
On an applicable withdrawal or closure, affected future improvement use stops and identifiable sources are removed according to the applicable requirements. Completed lawful training is not automatically undone by deleting a source; this does not excuse unlawful retention or use or override a legally required remedy.
Ministry records may reveal religious affiliation, health conditions, accommodation needs, or other sensitive matters. Not every prayer request, date of birth, or image is health data, but its content and context may bring it within a legal definition. Organizations must not assume a general membership or terms acceptance supplies all necessary permissions.
We limit access and processing according to the feature, applicable instructions, and law. General support-training datasets exclude health information, pastoral and prayer confidences, and children's information even if accidentally included in technical-support material. Customer-directed AI processing of a sensitive record to deliver a specific feature is a separate activity that requires appropriate notices, safeguards, and legal authorization.
Where applicable law requires a separately published health-data notice or consent, we will publish that notice or obtain that consent; it is not satisfied merely by accepting these general terms. The Service is not offered as a HIPAA-compliant medical-record system unless expressly agreed with the required arrangements in place; other privacy obligations may still apply.
Independent accounts are not intended for children under 13, and they may not create them. Organizations may use supported adult-managed features to maintain information about children. They are responsible for the notices, parental or guardian permissions, access restrictions, and recordkeeping appropriate to their activities. We remain responsible for our own applicable legal obligations.
Information supplied by an adult about a child and information collected directly from a child can have different legal requirements. We do not treat an account-age restriction as permission to collect children's information through public forms or other unsupported workflows.
If you believe a child directly supplied information without required authorization, contact [email protected]. We will investigate and delete or restrict information as required. Parents and guardians may contact us or the responsible organization about access, correction, and deletion. Children's information is excluded from our general support-training datasets.
We use administrative and technical safeguards appropriate to the information and processing, including access controls, authenticated connections, suitable encryption, logging, and provider review. The specific safeguards depend on the feature and storage environment. No system can guarantee absolute security.
Customers should protect credentials and devices, use available stronger authentication, limit permissions, update software, and promptly report suspected compromise to [email protected]. Do not include passwords or unnecessary sensitive records in the report.
We notify affected organizations of qualifying personal-information incidents without undue delay and provide information and cooperation required by law and applicable agreements. We notify individuals, regulators, or others where our role and the law require it. A notice may be supplemented as investigation establishes further facts. Legitimate investigative or legally required restrictions may affect the timing or contents of a notice.
Depending on applicable law, you may have rights to confirm processing; access, correct, or delete personal information; obtain a portable copy; withdraw consent; object to or restrict processing; limit certain sensitive-data uses; opt out of sale, sharing, targeted advertising, or certain profiling; and appeal a denied request. Rights may be subject to legal exceptions and do not all apply to every person or activity.
Email [email protected] with the request type, a way to contact you, the relevant organization if known, and enough detail to locate the information. State whether you act for yourself, a child or dependent, an organization, or another person who authorized you. Residence may help determine applicable rights. You do not need to create an account. Do not send identity documents or sensitive supporting records unless we request them through an appropriate method.
We request only verification reasonably necessary and permitted for the request. Authorized agents may need to establish authority; administrators requesting organizational deletion or export must establish appropriate authorization. We do not impose identity verification on an opt-out where law prohibits doing so.
We respond within the timeframe required by the applicable law and notify you of permitted extensions when necessary. If we deny or limit a request, we explain the basis and applicable appeal rights. To appeal, reply to the decision or email [email protected] with "Privacy appeal" and the request reference. We provide the required response and regulator-contact information where applicable. We do not unlawfully discriminate for exercising privacy rights.
For church-controlled records, we may route the request to the church and assist it under our agreement and law. We do not use that routing to avoid obligations involving our own processing. Correcting or deleting a login does not automatically alter all church records, and organizational authority does not eliminate an individual's nonwaivable rights.
Where California law applies, the categories, sources, purposes, recipients, and retention described in this Policy also explain our relevant California practices. Applicable rights can include knowing, accessing, correcting, and deleting information; opting out of sale or sharing; limiting certain sensitive-information use; and receiving equal treatment. Advertising-related practices and controls are described in Section 14. We do not knowingly sell or share information of individuals under 16 for cross-context behavioral advertising.
Other United States laws may provide additional choices, appeal rights, or sensitive-data protections. We do not assume that nonprofit customers or small business size exempt every processing activity from applicable law.
Where European Economic Area, United Kingdom, Swiss, or other applicable law provides rights, these may include access, correction, erasure, restriction, portability, objection, consent withdrawal, and complaints to a supervisory authority. Religious and other specially protected information may require an additional processing condition beyond the ordinary legal basis. We do not rely on a general website-use statement as explicit consent for all such information.
Our core offering is directed to United States organizations, and information may be processed in the United States and other countries where relevant providers operate. We apply legally required transfer arrangements when applicable. Merely using the Service or declaring it lawful does not waive transfer protections or determine which laws apply.
We update this Policy when practices or legal requirements change and identify its effective date. We ordinarily provide at least 30 days' notice of material changes through email or a prominent notice, except where a shorter period is necessary for law or urgent security.
Changes apply prospectively. We provide additional notices and obtain separate consent where required before applying materially different collection, recording, training, or other processing. Continued use is not automatically consent to those uses. Existing contractual and legal commitments remain relevant to information collected under an earlier notice.
Operator: L&P Inventions, LLC, doing business as WorshipMetrics
Privacy requests, appeals, and general inquiries: [email protected]
Security concerns: [email protected]
Mailing address: L&P Inventions, LLC, 305 West Miner Street, West Chester, PA 19382
Please identify the relevant organization and feature when possible, and do not include unnecessary sensitive information in ordinary email.