Lecture 3-3: What Must Never Be Typed In
목차 31
- Lecture 1-1: What the Word "AI" Points To
- Lecture 1-2: How a Language Model Makes Words
- Lecture 1-3: Sounding Right Is Not Knowing
- Lecture 1-4: Reading a Conversation Closely
- Lecture 1-5: Practice Lab, Read an AI Answer
- Lecture 2-1: Invented Facts
- Lecture 2-2: Old Knowledge, Missing Sources, Uneven Coverage
- Lecture 2-3: Scripture and Theology, Where to Be Most Careful
- Lecture 2-4: Building a Checking Plan
- Lecture 2-5: Practice Lab, Find the Errors
- Lecture 3-1: Asking Well
- Lecture 3-2: Checking What You Are Given
- Lecture 3-3: What Must Never Be Typed In
- Lecture 3-4: Keeping Notes and Giving Credit
- Lecture 3-5: Practice Lab, Mend the Prompts, Mark the Secrets
- Lecture 4-1: Hand It Over, Help With It, Keep It
- Lecture 4-2: Office Work and Communication
- Lecture 4-3: Teaching and Study Materials
- Lecture 4-4: Where Teachers and Leaders Draw the Line
- Lecture 4-5: Practice Lab: Hand Over, Help, or Keep
- Lecture 5-1: Preaching and AI: A Theological Question
- Lecture 5-2: Care and Counselling
- Lecture 5-3: When Members and Young People Use AI
- Lecture 5-4: The Minister's Own Life
- Lecture 5-5: Practice Lab: Judge the Scene, Write a Position Paragraph
So far this week has been about getting good work out of a chat assistant. This lecture is about what you must not put in. A minister is trusted with things that other people do not say aloud: a diagnosis, a debt, a marriage in trouble, a sin confessed, a child's name on a prayer list. That trust is part of the ministry. It does not belong to the minister alone, and it is not the minister's to hand to a service whose rules he or she has not read.
The rule of this lecture is short and has no exceptions for convenience: do not type personal, congregational or counselling information into an AI tool. Not names, not contact details, not stories that could be traced to one person, not "just this once" to save time. You can still ask for help with the shape of a task. You will see how in a moment.
This lecture states general principles. It does not give a legal opinion and it does not describe how any service works, because services differ and change. Questions of records, data law and retention belong to the course PT738E. Here we learn the habit.
이 16분으로 얻는 것
- List the kinds of information that must never be typed into an AI tool.
- Explain, at a general level, why where your input goes matters.
- Say why masking a name is not enough.
- Describe how to ask for help with a task without giving private details.
- Say what to do when a mistake has already been made.
One who brings gossip betrays a confidence, but one who is of a trustworthy spirit is one who keeps a secret." — Proverbs 11:13
World English Bible
The proverb sets two kinds of person side by side. One passes on what was trusted to him. The other keeps it. A minister is asked to be the second kind. Nothing in the verse speaks of machines. It speaks of a confidence, which is a trust given in expectation of silence, and it asks whether we can keep one.
1. What must never be typed in
Here is a plain list. Anything that fits one of these lines stays out of an AI tool.
- Personal details of anyone: names, addresses, telephone numbers, email addresses, dates of birth, photographs, identity numbers.
- Health and family matters: illness, a diagnosis, a death not yet announced, a pregnancy, a separation, a child in trouble.
- Money: a member's giving, debts, requests for help, bank details.
- Counselling and confession: anything a person said to you in confidence, anything said in a pastoral visit, anything said in the or in a prayer for the sick.
- Congregational information: membership lists, rolls, attendance records of named people, discipline matters, staff or volunteer matters.
- Anything that identifies someone, even without a name: "the widow in the third house who lost her son in March" is a name, in effect.
- Unpublished work that belongs to others: a colleague's draft, a writer's manuscript, material you were given on condition that you would not pass it on.
- Passwords, access codes and keys of any kind.
The list is not meant to be learned by heart. The test beneath it is simple: would the person be willing for these words to be read by a stranger? If you are unsure, they would not be, and you do not type it.
2. Where does what you type go?
You do not need to know how any service is built to understand the principle. When you type into a chat assistant, your words leave your own device and are sent to a service run by someone else. What that service does with them differs from service to service and may change over time. Some keep what you type for a time. Some may read it for safety or quality. Some may use it to improve the tool. Some may let you turn such things off. The rules are written in the service's terms and settings, which most people never read.
Two things follow. First, you cannot know from the screen alone where your words are going or who may see them. Second, once words are sent, you cannot always call them back. So the sound habit is to check the service's terms and your community's own rules before you use it for anything that touches people, and to assume nothing is private unless the rules say so and a responsible person has confirmed it.
This course does not say that any particular service is safe or unsafe. It says the question must be asked, and that the answer belongs to the person responsible for your community's records.
3. Why masking is not enough
A common idea is: "I will take out the name and then it is safe." It is not safe, for two reasons.
First, a story can identify a person without a name. A small community knows who "a father of four who lost his job after the factory closed" is. Age, place, job, family shape and a single unusual event can be enough. The more particular the detail, the more it points at one person.
Second, you are not the only judge of what can be traced. A detail that seems harmless to you may be the exact one that someone who knows the family would recognise. So the safer rule is the stricter one: if the story is about a real person you know, keep it out. If you want help with a type of situation, describe a made-up one, not a real one with the name taken off.
4. Asking for help without giving the secret
The rule does not forbid help. It forbids the private material. Here is how to keep the one and avoid the other.
(an invented example) A wants help writing a letter to a family after a death in the congregation.
| Do not type | Type instead |
|---|---|
| The name of the person who died, the cause, the names of the family, what the family said to you | "I need to write a short, warm letter of condolence from a church to a grieving family. Offer three possible opening sentences. Plain words. No detail about the person." |
The tool gives you a shape. You write the real letter yourself, by hand or at the keyboard, with the real names and the real memory of the person. We will see in week 4 why a letter of this kind is better written by a person from start to finish. For this lecture, the point is only that the task can be described without the people.
If you cannot describe the task without the private material, that is a sign the task is not one for a tool.
5. Documents, photographs and recordings
The same rule covers anything you could attach or paste: a letter someone sent you, a photograph of a meeting, a recording of a talk or a visit, a spreadsheet with names. Do not upload it. Some services can read a pasted document or listen to a recording. That may be useful for your own writing, or for a talk you recorded yourself, with no one else's voice or details in it. It does not make it acceptable for material that belongs to other people or concerns them.
6. Your community's rules come first
Many communities already have rules about records, confidentiality, children and safety, written or unwritten. Some have a person responsible for them. If your community has such rules, they apply to AI tools as they apply to a filing cabinet. If it has none, say so to the leader and ask for them. Lecture 6-2 shows how a community can write a short policy.
Local law may also apply to personal information, and the law differs from one country to another. This course does not say what your law is. It says: follow local law and your community's written rules, and ask a qualified person if you are unsure.
7. Where readers will not agree
This is a point where readers will not agree: how freely a minister may use AI tools in work that is only near to private matters, such as planning a visiting schedule or drafting a general letter. Some hold that any use touching a congregation's life should be avoided until the community has written rules, because the line between general and private is easily crossed and trust is easily lost. Others hold that general, non-personal tasks such as grammar, wording and layout are no different from using a dictionary, and that a ban would only push use out of sight. Both want to protect people. This course requires less than either: keep personal, congregational and counselling information out in every case, and for everything else follow your community's rules.
8. If a mistake has been made
It may happen. A volunteer pastes a paragraph with a name in it. A leader attaches the wrong file. What to do?
- Stop. Do not type more, and do not try to fix it by explaining in the same conversation.
- Tell the person responsible in your community, plainly and soon. This might be the pastor, a priest, a council chair or the person who keeps the records. Hiding a mistake makes it worse.
- Write down what was entered, when, and into which service, so that the responsible person can decide what to do. Do not retype the private details in doing so; describe them.
- Let that person decide whether anyone must be told, whether the service offers a way to ask for deletion, and whether local law requires anything. That decision is not yours alone.
Telling is not a punishment. A community that is told early can act. One that is told late, or never, cannot.
Diagram 1. Task, yes. People, no.
Diagram 2. The test before you type
| Question | If the answer is "yes" |
|---|---|
| Does it name or point to a real person? | Do not type it. |
| Was it said to me in confidence? | Do not type it. |
| Does it belong to someone else? | Do not type it. |
| Do I know where the words will go? | If not, do not type anything about people. |
핵심 요약
- Never type personal, congregational or counselling information into an AI tool, including anything that identifies a person without a name.
- Where your words go depends on the service and may change; check its terms and your community's rules first.
- Taking out a name is not enough, because a particular story can still point to one person.
- Describe the task, not the people; if you cannot, the task is not for a tool.
- After a mistake, stop, tell the person responsible in your community, and let them decide what follows.
| Front | Back |
|---|---|
| What stays out | Names, details of health, family, money, confessions, congregational records, others' unpublished work. |
| Why masking fails | A particular story can identify a person without a name. |
| How to ask safely | Describe the task or an invented case, never the real people. |
| After a mistake | Stop, tell the person responsible, write down what happened, let them decide. |
One sentence to remember A confidence is not yours to hand to a service whose rules you have not read, so describe the task and keep the people out.
This week's action Find out whether your community has a written rule about records and privacy, and who is responsible for it.
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- Think of three things that people tell ministers in confidence. Why would typing them into a tool break that trust, even if the tool seemed harmless?
- A story with the name removed can still identify a person in a small community. Why?
- How would you describe a task to a tool so that no person is in the description?
- Does your community have a rule about records and privacy? Who is responsible for it?
- Why is telling the responsible person after a mistake better than quietly hoping nothing came of it?