Linguify Privacy Policy

Last Updated: September 4, 2026

Linguify is a product of McKinnis Creatives, LLC ("Linguify," "we," "us," or "our"). Linguify provides real‑time AI‑powered speech transcription, translation, text‑to‑speech, live‑streaming, and congregation‑engagement tools (the "Service") primarily for churches and other religious organizations, currently offered as a Beta product.

This Privacy Policy explains what information we collect, how we use and share it, and the choices available to you. It covers: (a) the local "ClientPage" software that a church's staff ("Church Administrator(s)") installs and operates; (b) Linguify's central licensing, account, and billing systems; and (c) the companion public‑facing website product a Church Administrator may enable for their congregation and visitors (livestream pages, Guest Follow‑Up, engagement analytics, and Salvation Tracker).

Because Linguify is used by churches to process information about the church's own staff, congregants, and visitors, more than one party can be responsible for the same data under privacy law. Section 4 explains this in plain language — please read it, especially if you are a church visitor whose information a Church Administrator has entered into, or who has interacted with, the Service.

1. Introduction

Linguify is committed to protecting your privacy. This Policy applies whenever you (a) are a Church Administrator using the ClientPage software or Linguify's account/billing portal, (b) are a staff member with a ClientPage login created by your church, or (c) are a member of the public who visits a livestream, follow‑up, or engagement page that a church has set up using Linguify. By using the Service, you agree to the collection and use of information as described here.

2. Information We Collect

2.1 Account, Contact & Billing Information

When a church signs up for and administers the Service, we collect:

• Organization name and account status, and any internal notes our support team keeps about the account relationship.
• A primary contact name, email address, and phone number for the organization.
• Individual staff login credentials created inside the local ClientPage software (username, a securely hashed password, and an assigned role/permission set).
• A license key and a hardware/device identifier for each installed copy of the software, and a history of license‑validation attempts.
• Subscription and billing details. Payment is processed by our payment processor, Stripe; we do not collect or store your full credit card number. Depending on how your subscription is configured, you may be billed a flat recurring fee, a usage‑based ("metered") fee calculated from the telemetry described in Section 2.5, or both.

2.2 Audio, Transcripts, Translations, Summaries & Recordings ("Content")

The core of the Service listens to spoken audio (e.g., a church service) and produces live transcriptions, translations into other languages, and — if enabled — synthesized speech ("text‑to‑speech" or "TTS") audio of the translated/transcribed text. Content also includes saved transcript files, AI‑generated summaries of those transcripts, and TTS audio recordings saved by language.

Local vs. Cloud transcription — a choice each church makes, with real privacy consequences. The Service offers two ways to turn spoken audio into text:

• On‑premises transcription. Audio is processed entirely on the church's own local hardware. Raw audio is not sent to any third party to produce the transcript in this mode.
• Cloud transcription ("Linguify Cloud") — the default mode in current versions of the Service. Live audio captured from the church's hardware is streamed in real time, over the internet, to a third‑party speech‑recognition provider, which returns transcribed text back to the Service. This is a materially different data flow from on‑premises mode: it is raw audio, not text, and it leaves the church's premises continuously, in real time, for as long as a service is being transcribed. Cloud transcription automatically uses one of several speech‑recognition vendors depending on real‑time availability (see Section 5) — a church using this mode should assume its live audio could be sent to any one of them during a given service, not only whichever is configured as primary. Cloud transcription usage is billed separately from, and metered independently of, on‑premises usage.

A church controls which mode is active from Settings. Everything downstream of transcription — translation, TTS audio generation, AI summarization, and semantic search — works the same way regardless of which mode produced the underlying transcript, and involves the third‑party subprocessors described in Section 5 whenever those optional features are used.

2.3 Guest & Visitor Follow‑Up and Engagement Data

If a Church Administrator enables the optional Guest Follow‑Up and Engagement Analytics features (part of Linguify's companion public‑facing website product), the Service tracks information about individual visitors to the church's livestream/captioning pages so staff can recognize and follow up with them. This includes:

• Identity/contact fields — if a visitor voluntarily signs in to access a page (name, email, and/or phone number, plus optionally last name and ZIP code, depending on what the church has configured), that information is linked to their visit history so they can be recognized across visits and devices.
• Device/technical fields — a persistent first‑party browser cookie, IP address, device type, browser family, and the referring page.
• Visit & engagement history — first‑seen/last‑seen dates, total visit count, total active/connected listening time, languages used, which campus/site a visit was associated with, and whether a visit met an "engaged" threshold (approximately five minutes of active listening).
• Follow‑up pipeline fields — an assigned staff member, a follow‑up status (including a specific opt‑out status a visitor can be placed into, which stops further outreach), free‑text notes staff enter about outreach attempts, and a three‑stage outreach checklist (an initial checkpoint, and 30‑day and 60‑day follow‑ups) that is automatically scheduled once an engaged visitor has provided contact information.
• Aggregate/cohort analytics — retention and cohort statistics computed across visitors.

A Church Administrator (or staff member with the relevant permission) can view this data on a dashboard, add notes, change follow‑up status, and export it to CSV/Excel for outreach purposes. Access to personally‑identifying fields is restricted by staff role. This data is about your church's own congregation, captured because your church chose to turn these features on — see Section 4.

One accuracy note: a church can choose not to collect IP addresses on its sign‑in form, but IP address is still recorded separately, on every visit and heartbeat, for engagement‑tracking purposes regardless of that setting — disabling the sign‑in‑form toggle does not fully disable IP capture.

2.4 Salvation Tracker Data

The Service includes an optional Salvation Tracker feature that shows service attendees an on‑screen prompt asking whether they have made a decision of faith, with response choices such as "Yes, Today," "Not Yet," or "Already Decided," at a point in the service the church configures (or triggered manually by staff).

This is not an anonymous feature. If you are signed in when you respond (for example, because the livestream page required sign‑in), your response is stored together with your account information — name, email, phone, and ZIP code, where provided — and is linked directly to you. If you are not signed in, your response is still stored together with your device's IP address and a persistent browser identifier, so it is a pseudonymous record tied to your device, not a bare anonymous tally. Repeated responses update your existing record's answer rather than creating a new one each time.

Salvation Tracker responses (including any linked name/email/phone) are visible to the church's authorized staff through an analytics dashboard and an export tool. If the church has separately enabled an available webhook integration, your response — together with your identifying information, if known — may also be automatically transmitted to a third‑party system the church controls (for example, a CRM the church uses). Linguify does not sell this data or use it for advertising, and does not itself choose to enable this webhook — that choice belongs to the church, as described in Section 4.

Because this reflects a person's religious beliefs or decisions, it is a sensitive category of information under some privacy laws. You may decline to respond to the prompt at any time, and declining does not affect your access to the Service.

2.5 Usage, Device & Telemetry Data (Automatically Collected)

To operate licensing, support, and usage‑based billing, each installed copy of the Service automatically and periodically sends the following to Linguify's central licensing server: your license key and a hardware/device identifier; the application version and a per‑session identifier; the start/end time of each reporting window and total "active" transcription seconds in that window (tracked separately for on‑premises use, cloud‑transcription use, and each additional language used); and the IP address and timestamp of every license‑validation check‑in and every End User License Agreement (EULA) acceptance, which we log for security and audit purposes. We use this information to validate your license, enforce device limits, calculate usage‑based billing where applicable, monitor product health, and provide support. Because processing‑mode usage is billed and tracked separately, a church's own usage records will also show whether Cloud transcription mode was used for a given period.

2.6 Feedback & Support Submissions

If you use the in‑app "Submit Feedback" tool, we receive the feedback type, a title, your message, an optional contact email address you choose to provide, up to three optional screenshots, and — only if you affirmatively opt in — a snapshot of system/diagnostic information. This is routed to our internal team and used solely to troubleshoot issues and improve the Service.

2.7 Website & Browser Information

If you visit our marketing site or a Linguify‑hosted web page (for example, a public livestream page — see Section 6), standard automatically‑collected technical information may be gathered, such as device/browser type, IP address, and general usage/page‑view data.

2.8 Cookies & Similar Technologies

The companion public‑facing website product uses first‑party cookies to recognize returning visitors and keep you signed in: a durable visitor‑identity cookie (kept for approximately one year), one or two session‑tracking cookies (kept for approximately 30 days), and, if you sign in, a login session cookie (kept for approximately 90 days). These cookies are set automatically when you visit a livestream or captioning page. We do not use third‑party advertising or analytics trackers, and we do not use canvas/device fingerprinting.

3. How We Use Your Information

We use the information described in Section 2 to:

• Provide, operate, and maintain the Service, including transcription, translation, text‑to‑speech, live streaming, and guest follow‑up/engagement tools;
• Validate licenses, enforce device limits, process subscription billing, and calculate metered usage charges;
• Allow Church Administrators to manage their own congregant/visitor follow‑up and engagement workflows, at their direction;
• Generate AI‑assisted summaries and enable semantic search over a church's own transcript library, at that church's direction;
• Send automated communications (such as sermon‑summary emails, or Salvation Tracker webhook events) that a Church Administrator has configured, to recipients or systems the Church Administrator specifies;
• Send Service‑related communications, respond to support and feedback requests, and diagnose technical problems;
• Improve, secure, and troubleshoot the Service, and detect, investigate, and prevent fraud, abuse, or unauthorized use of a license; and
• Comply with our legal obligations.

4. Data Controller vs. Data Processor — Understanding Your Role

Because the Service is used by churches to handle information about the church's own people, it matters who decides what happens with a given piece of data — under frameworks like the GDPR, this is the difference between a "controller" and a "processor."

• Linguify acts as the Controller for: your organization's account, contact, and billing information (Section 2.1); and the usage/device/telemetry data our own systems generate about your installation (Section 2.5). We decide why and how this data is used — mainly to run and bill for the Service.
• Your Church acts as the Controller, and Linguify acts as a Processor on the Church's instructions, for: the sermon/service Content a church chooses to capture, translate, summarize, or synthesize (Section 2.2); Guest Follow‑Up and Engagement Analytics data (Section 2.3); and Salvation Tracker activity (Section 2.4). Your church decides whether to turn these features on, what to capture, which staff can access it, whether to enable third‑party webhook forwarding, and — on request — deletion. Linguify built, hosts, and operates the underlying tools that make this possible, and processes this data only as instructed by the church.

If you are a church visitor with a question about follow‑up notes, engagement records, or a Salvation Tracker response, your church — not Linguify — is the right first point of contact, since your church controls that data. Linguify will assist the church in responding to such requests.

5. Third‑Party Subprocessors & Service Providers

We use the following third‑party service providers ("subprocessors") to deliver parts of the Service. Each is given only the data it needs to perform its specific function.

Scroll to see more

6. Public Live‑Streaming and Publicly Accessible Content

The Service supports live audio/caption streaming with public playback URLs, so that anyone can follow along online without creating an account or installing anything. By design, anyone who has a stream's playback link can access it — these links are not, by default, restricted to specific individuals, although a church may optionally require sign‑in before granting access. Churches should keep this in mind when deciding what to stream — for example, portions of a service involving sensitive personal testimony or content involving minors that isn't intended for an unknown public audience.

7. YouTube and Other Third‑Party Streaming Integrations

If your church already streams to YouTube or uses a Resi.io hardware encoder, the Service can optionally detect and display that stream's public information (its title and live/upcoming status) by reading publicly available information. This does not require, and does not use, a YouTube API key, OAuth token, or Google account login, and no congregant or visitor personal data is sent to YouTube through this integration. If your church separately broadcasts to YouTube or through Resi.io, that broadcast is governed by your church's own account and agreement with those providers, not by Linguify.

8. Data Security

We use administrative and technical safeguards designed to protect the information described in this Policy, including encrypting certain sensitive stored credentials, password hashing for staff dashboard accounts, role‑based access controls so only staff with the relevant permission can view personally‑identifying visitor/guest fields, and audit logging of sensitive actions on the ClientPage dashboard (logins, setting changes, data exports). That said, no method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

9. Data Retention & Your Deletion Controls

Retention differs materially by data type, and we want to describe this honestly rather than with a one‑size‑fits‑all statement:

• Local recordings and transcripts (Section 2.2, on‑premises mode) are under your church's direct, immediate control. From the ClientPage dashboard, a Church Administrator can list, play back, download, rename, or delete recordings (individually or in bulk), and can soft‑delete, restore, or permanently delete transcripts — all instantly and locally, with no request to Linguify required.
• Guest/visitor follow‑up, engagement, and Salvation Tracker data (Sections 2.3–2.4), stored on Linguify's companion public‑facing website product, currently has no automated deletion, expiration, or anonymization tooling — this data is retained indefinitely by default. A visitor may be marked "opted out" of further follow‑up outreach (which stops new outreach tasks but does not delete existing records), and a church or a visitor may request deletion or correction of this data by contacting us; we will process such requests manually.
• Centrally‑stored account, license‑validation, and usage‑telemetry records (Section 2.5) are retained by Linguify to support billing, auditing, and license enforcement.
• Content processed by third‑party AI subprocessors (Section 5) is subject to those providers' own retention practices while being processed.

10. Your Rights

Depending on your role and location, you may have the right to access, correct, delete, object to processing of, or receive a portable copy of personal data. To exercise these rights regarding your account/billing data, contact us using Section 14. To exercise these rights regarding guest/visitor follow‑up, engagement, or Salvation Tracker data, you may contact us or your church directly (Section 4); as described in Section 9, such requests are currently handled manually rather than through a self‑service tool. If you no longer wish to be contacted through the Guest Follow‑Up feature specifically, ask your church to mark you as opted out, which takes effect immediately for future outreach.

If you are in the EU/UK or a California resident, please also see Section 12 — additional, more specific rights may apply to you.

11. Children's Privacy

The Service's accounts, logins, and administrative tools (Sections 2.1 and 2.5) are intended for use by adult church staff and administrators, not by children. We do not knowingly collect account‑registration information from children under 13.

However, because the Service is used at churches, optional features — particularly Guest Follow‑Up and Engagement Analytics (Section 2.3), and Salvation Tracker (Section 2.4) — could capture information about a church's own visitors, which may include minors (for example, families or youth‑group attendees). When a church uses these features, the church — as the data controller for its own congregation (Section 4) — is responsible for ensuring it has an appropriate legal basis, notice, and, where required by law (such as COPPA or GDPR provisions on children's data), consent mechanisms for any data it chooses to capture about minors. Linguify's role with respect to that data is as a processor acting on the church's instructions.

12. International Users — GDPR, UK GDPR & CCPA/CPRA

Section 10's description of "your rights" is intentionally general. If Linguify serves, or comes to serve, churches or individuals located in the European Union, United Kingdom, or California, additional disclosures and mechanisms are legally required and are not yet fully built out, including: a clearly stated legal basis for each category of processing; international‑transfer safeguards; a cookie‑consent mechanism (see Section 2.8, currently absent); a self‑service or committed‑turnaround deletion process (see Section 9, currently manual‑only); a complete CCPA/CPRA‑style rights list; and specific handling for the sensitive/special‑category implications of Section 2.4.

13. Changes to This Policy

We may update this Privacy Policy periodically. We will notify you of material changes by posting the updated policy on this page and updating the "Last Updated" date above.

14. Contact Us

If you have questions about this Privacy Policy, please contact us at: contact@linguify.io