Live translation on its own stores very little. The moment you archive a service that changes: a transcript is a written record of things people said, sometimes about their health, their families, or their beliefs. That is personal data, and in Europe beliefs and health are a category treated with particular care.
What follows is practical guidance from building the tooling, not legal advice. For anything consequential, ask a professional in your jurisdiction.
Separate the three things
Churches conflate these, and they carry very different weight:
- Translating live. Words pass through and nothing is kept. The lightest case by far, and the one most churches worry about unnecessarily.
- Archiving the transcript. Now you are storing a record. Who can read it, and for how long, both matter.
- Publishing it openly. Now a search engine can index what somebody said from the floor, permanently, findable by their name.
Most of the risk sits in the third row, and most of the anxiety sits in the first. Getting that the right way round makes the rest of this straightforward.
Tell people, in the room
The single most effective step costs five seconds: say it in the welcome.
"This service is being translated, and the text is saved to our archive" gives anyone about to share something personal the chance to decide. It also transforms the atmosphere around the whole subject — people are relaxed about being recorded when they were told, and upset when they discover it.
Put a sign at the entrance as well, for people who arrive late, and put a line on your website. Three places, written once.
Be careful with the open microphone
The risk is rarely the sermon. The preacher knows they are being recorded and has prepared what they will say.
The risk is the prayer request from the third row that names a member's illness. The testimony that identifies a family member who never agreed to anything. The person who stands up in a members' meeting and says something about their finances. If your microphone reaches the congregation, decide deliberately whether those parts are archived — and the safe default is that they are not.
The parts that should never be archived
Make this a list rather than a judgement call, because judgement calls get made by whoever happens to be at the desk on a difficult morning:
- Testimonies
- Prayer that names people
- Anything involving a child
- Members' meetings, unless kept private to members
- Pastoral or safeguarding announcements
Pin it next to the operator's checklist. It takes one line on a card and it removes an entire category of mistake.
Decide before, not after
The decision belongs at the start of a service, not the end, for a simple reason: afterwards is too late. Material that was publicly readable for two hours on a Sunday morning may already have been crawled, copied or shared.
If the answer to "should this be public?" is "I'll decide later", the answer is members-only. Promoting something later is one click. Retrieving something already read is not possible.
Keep less, for less long
Storage is cheap, which makes it tempting to keep everything forever. Resist, because everything you hold is something you are responsible for.
A written retention rule — archive sermons, never archive prayer and testimony, delete anything else after a set period — is far easier to defend and far easier to explain than an archive that grew by accident over six years and that nobody has ever reviewed.
A related guard worth having: a minimum length before anything is archived at all. A two-minute test broadcast or a microphone left on before a service should never become a permanent page with a fragment of a private conversation on it.
Make deletion possible, and know who does it
Somebody will eventually ask you to remove something. It may be the person who gave a testimony three years ago, or a family after a bereavement, or someone whose circumstances have changed.
Know in advance who can do it and how long it takes. A church that can honour that request within a day is in an entirely different position — practically and legally — from one that has to explain that it cannot.
Test it once, on something unimportant, so that the first time you do it is not under pressure.
Members-only is only as good as your definition of member
If anyone who fills in a form is instantly a member, a members-only setting is decorative. Most churches want a small gate: somebody signs up, and a leader confirms they are part of the congregation before they can read internal material.
Keep that gate narrow. Being unapproved should stop somebody reading the archive; it must never stop them following this Sunday's service in their own language. A visitor on their first morning should not meet a permission screen.
The practical minimum
If you do nothing else on this page, do these five:
- Say it in the welcome, and put a sign at the door.
- Keep a written list of what is never archived.
- Decide each service's storage before it starts.
- Write down how long you keep things, and stick to it.
- Know who can delete something, and how fast.
None of that requires a lawyer, and all of it is the sort of thing that is very hard to add after something has gone wrong.
Built in rather than bolted on
InMyTongue lets you decide per sermon whether it is saved and who can see it, set a minimum length before anything is archived at all, and delete a saved sermon outright. New accounts include free credit. See the controls.