Security and Data Privacy

Linguify supports both cloud and local processing modes. Cloud processing is the default: live audio is streamed over the internet to third-party speech-recognition providers for transcription.

Local mode keeps transcription on church-controlled hardware, so raw audio is not sent to a third party to create the transcript. Translation, AI voice generation, summaries, and semantic search use third-party AI providers when those features are enabled, regardless of transcription mode.

Local transcripts, recordings, and summaries remain on church-controlled hardware until an authorized operator manages or deletes them. When enabled, the hosted listener experience stores guest, engagement, follow-up, and salvation-response data in Linguify's cloud systems.

Retention differs by data type. Hosted visitor and engagement records currently have no automated expiration, and deletion or correction requests are handled manually. Centrally stored account, licensing, and usage records are retained for operations, billing, and oversight. Third-party AI providers apply their own processing and retention practices; Linguify does not make a no-training guarantee for those providers.

Hosted listener pages may also collect browser, device, IP address, cookie, and page-use data. Churches should review their configuration and provide appropriate notices to attendees.

For full details on what data is collected, how it is used, and your rights, see our Privacy Policy.

The local operator dashboard supports named staff accounts, predefined roles, and custom permission sets. Administrators can limit who starts services, changes settings, manages transcripts, views analytics, or administers users.

These controls help churches give production volunteers and ministry staff access appropriate to their responsibilities.