GDPR compliance

This guide helps church boards, trustees, and legal committees understand how Breeze Translate handles data under the UK GDPR and EU GDPR. It supplements our Privacy policy and Terms of service — it is not legal advice for your specific situation.

Special Category Data

Under GDPR Article 9, certain types of personal data receive extra protection. Religious or philosophical beliefs are Special Category Data.

Church attendance, participation in worship, and use of translation in a religious service can imply religious belief or affiliation. Even when Breeze does not ask listeners for their name or faith, the context of processing matters to data-protection reviewers.

Churches should:

• Treat translation use as potentially sensitive in privacy notices and risk assessments.
• Limit access to operational data to people who need it for ministry or tech roles.
• Document why translation processing is necessary for welcoming your congregation and guests.

What Breeze collects — and what we do not

Churches (account holders)

We collect what is needed to run your account: contact details, church name, billing where applicable, and team member logins. See Privacy policy §1 for detail.

• No permanent sermon archive — full transcripts of talks are not stored as a historical record on our systems. The control panel stores transcriptions and translations on the device. These can be cleared or downloaded as required, but they are not stored by Breeze.
• Ephemeral audio — audio for real-time translation is processed for the live session, not retained as a long-term recording by Breeze for replay or analytics of your sermon content.

Listeners (end users)

• No routine PII — listeners use the stream anonymously; we do not require sign-in for standard listening.
• No permanent sermon archive — full transcripts of talks are not stored as a historical record on our systems. The client app stores translations on the device for 6 days, and translations can be shared or stored from the client app to different apps and services.

Support and diagnostics

When you submit a bug report, we may receive short, relevant transcription snippets, device metadata, and session identifiers to diagnose issues — as described in the Privacy policy. This is distinct from normal operation.

How translation streams are processed

1. Audio is sent securely from the control panel to our infrastructure and transcription/translation providers for real-time processing.
2. Captions and optional spoken output are delivered to listener devices during the active session.
3. Retention — Breeze is designed so that listener translation streams are not kept as long-term retention logs of your congregation’s listening activity. Operational logs are minimised to what is needed to run and secure the service.
4. Anonymised improvement — the Privacy policy notes that brief, anonymised text snippets may be used to improve service quality; this is not a full archive of your services.

Security measures

We implement technical and organisational measures appropriate to the risk, including:

• Encryption in transit (TLS) for data between browsers, our services, and essential providers.
• Tenant isolation — church accounts are logically separated; your stream configuration and team access belong to your organisation’s account boundary.
• Access control — production access to systems is restricted; we do not sell listener data to third parties for marketing.

For a fuller statement, see Privacy policy §4.

Subprocessors and international transfers

Translation and hosting rely on vetted service providers (transcription, translation, cloud hosting). They process data only to deliver the service, under contractual obligations.

For church boards and legal committees

When presenting Breeze for approval, you may find it helpful to provide:

Topic	Where to point reviewers
Privacy summary	Privacy policy
Contractual terms	Terms of service
Special Category context	This page, § Special Category Data
Data Processing Agreement	[Board pack detail to follow — contact privacy@breezetranslate.com to request a DPA]

Questions or documentation requests: privacy@breezetranslate.com

We are happy to work with dioceses, networks, and national bodies reviewing tools for member churches.