👥 Kingdom Keys Presents • Meet Your Neighbor
Meet Your Neighbor Governance
Meet Your Neighbor Privacy, Personal Information & Safety Standards
Privacy • Personal Information • Boundaries • Safety • Responsible Stewardship
Standards for how Kingdom Keys collects, receives, accesses, uses, protects, shares, retains, and responsibly stewards personal information and safety concerns throughout the Meet Your Neighbor experience.
1. Why Privacy, Personal Information & Safety Matter
Meet Your Neighbor is built around something deeply human.
A person allows us to meet them.
They may tell us where they grew up.
What they do.
What they believe.
What they have experienced.
What they hope for.
What they have survived.
What they are still trying to understand.
Some of those things may become part of a public conversation.
Others may be shared only so that Kingdom Keys can prepare responsibly.
And some things may never belong in the public story at all.
Understanding the difference is part of our responsibility.
A Conversation Is Public. A Person Is Not
Participation in Meet Your Neighbor does not make every part of someone's life public.
A Neighbor may consent to being recorded and still retain reasonable boundaries around information unrelated to the conversation.
They may publicly discuss their profession without making their home address public.
They may speak about their family without identifying every family member.
They may describe a difficult experience without disclosing every private detail surrounding it.
They may tell us something during preparation that helps the host understand them but is not intended for publication.
They may reveal something accidentally that should not become a clip, quotation, profile entry, headline, or searchable archive result.
Consent to participate is not consent to expose everything we know.
Personal Information Exists in Different Contexts
Not all information entrusted to Meet Your Neighbor should be treated the same way.
Information may be:
Public Information Information the Neighbor has authorized for public presentation, such as an approved public name, biography, profession, organization, website, social link, or information intentionally shared during the published conversation.
Operational Information Information Kingdom Keys reasonably needs to coordinate participation, such as contact details, scheduling information, communication preferences, accessibility needs, consent status, or production logistics.
Preparation Information Information shared to help the host or production team understand the Neighbor, prepare responsibly, identify boundaries, or create a meaningful conversation.
Sensitive or Restricted Information Information requiring additional care because disclosure could affect privacy, dignity, safety, legal rights, family members, children, employment, personal relationships, or other significant interests.
Off-Record or Do-Not-Publish Information Information specifically identified as outside the authorized public production or subsequently restricted through an applicable governance process.
These categories may sometimes overlap.
When uncertainty exists, Kingdom Keys should not automatically choose the most public interpretation.
Uncertainty should trigger clarification—not exposure.
Privacy Begins Before Recording
Privacy does not begin when the camera turns on.
It begins when someone is nominated.
When a name enters the system.
When contact information is located or provided.
When an invitation is sent.
When preparation questions are answered.
When scheduling occurs.
When accessibility needs are discussed.
When boundaries are communicated.
When consent records are created.
When a host receives a preparation brief.
And when production personnel are given access to information necessary for their roles.
The responsibility continues after recording through editing, publication, distribution, archiving, follow-up, and future reuse.
Privacy follows the Neighbor through the entire journey.
We Should Know Only What We Have a Responsible Reason to Know
Technology makes it increasingly easy to collect information about people.
That does not mean we should.
A potential Neighbor does not need to become the subject of an unnecessary digital investigation simply because Kingdom Keys is considering inviting them.
We should not gather personal information merely because it is available.
We should ask:
Why do we need this?
How will it be used?
Who actually needs access to it?
How long should we retain it?
Would the person reasonably expect us to have it?
The ability to discover information does not automatically create a legitimate reason to collect it.
Capability is not permission.
Publicly Available Does Not Always Mean Appropriate to Republish
Information may already exist online.
A home address may appear in a public record.
A telephone number may appear somewhere on the internet.
An old photograph may remain searchable.
A family member may have posted something publicly.
A past controversy may appear in search results.
A personal detail may be technically discoverable.
That does not automatically mean it belongs in Meet Your Neighbor.
Kingdom Keys should consider context, relevance, accuracy, safety, consent, dignity, and the reasonable expectations surrounding the information before amplifying it.
There is a meaningful difference between information being findable and Kingdom Keys choosing to make it more visible .
The Neighbor Is Not the Only Person Whose Privacy Matters
A Neighbor's story may involve other people.
Children.
Spouses.
Parents.
Friends.
Coworkers.
Customers.
Patients.
Students.
Employees.
Neighbors.
Former partners.
People involved in difficult experiences.
Or individuals who never agreed to participate in Meet Your Neighbor.
Their privacy and safety deserve consideration too.
A Neighbor's permission to tell their own story does not automatically give Kingdom Keys unrestricted permission to expose someone else's private information.
This is especially important when children, vulnerable individuals, confidential relationships, sensitive allegations, medical information, private communications, or identifying details are involved.
Safety Is Part of Privacy
Privacy and safety frequently intersect.
Publishing someone's address, routine, workplace details, children's school, travel plans, private telephone number, identifying location information, or other seemingly ordinary details can sometimes create real-world risk.
Safety concerns may also arise during:
Studio participation.
On-location recording.
Remote conversations.
Travel.
Public events.
Guest communications.
Interactions with members of the public.
Post-publication attention.
Or situations involving threats, harassment, stalking, domestic conflict, legal restrictions, or other credible concerns.
For that reason, privacy should not be treated merely as a paperwork requirement.
Sometimes protecting information protects a person.
Safety Does Not Mean Fear-Based Governance
Taking safety seriously should not cause Meet Your Neighbor to become suspicious of everyone.
A different belief is not a safety threat.
An unpopular opinion is not automatically dangerous.
A difficult life history does not automatically make someone unsafe.
A mental or emotional struggle should not be casually converted into a risk label.
A neighborhood should not be presumed unsafe merely because of reputation.
And Intelligence should never manufacture danger from stereotypes, demographic characteristics, appearance, identity, or disagreement.
Safety decisions should be connected to specific, relevant, explainable concerns whenever possible.
Boundaries Should Travel With the Information
If a Neighbor tells the Guest Coordinator:
“Please don't publish my personal phone number,”
that boundary should not disappear when the record reaches the production team.
If preparation material is marked:
HOST PREPARATION ONLY,
it should not quietly become material for an AI-generated profile.
If a portion of a conversation becomes:
DO NOT PUBLISH,
it should not later appear in a short, transcript excerpt, promotional quotation, search result, compilation, or automated recommendation.
If information has a restriction attached to it, the restriction should follow that information through the system.
A boundary that disappears when information moves is not a reliable boundary.
Access Should Follow Responsibility
Not everyone working with Meet Your Neighbor needs access to everything.
A host may need preparation information without needing administrative financial records.
A production technician may need recording specifications without needing private preparation answers.
An editor may need the recording and applicable restrictions without needing unrelated personal contact information.
A Guest Coordinator may need scheduling and consent information without having final editorial authority.
An Intelligence system should receive only the information appropriate to the function it is performing.
Access should therefore be based on legitimate responsibility rather than convenience.
The question is not simply, “Can this person access the information?”
The better question is:
“Does this person need this information to responsibly perform their role?”
Artificial Intelligence Must Respect the Same Boundaries
Artificial Intelligence can help Kingdom Keys organize information, prepare hosts, identify privacy concerns, detect potentially sensitive material, manage workflows, assist with transcripts, and prevent restricted information from accidentally entering public content.
But AI access does not create a new category of permission.
Information that is private to a human role should not automatically become available to every Intelligence function.
Information provided for scheduling should not automatically become creative material.
A private preparation response should not automatically become training material.
A restricted segment should not automatically become a clip suggestion.
A confidential concern should not become an audience-personalization signal merely because technology makes that possible.
Intelligence must inherit the boundaries of the information it receives.
Technology should help Kingdom Keys honor boundaries—not quietly dissolve them.
Privacy Is Also About Human Dignity
A technically compliant system can still behave without wisdom.
It is possible to collect too much.
Retain too much.
Expose too much internally.
Ask questions that are unnecessarily intrusive.
Preserve information long after its purpose has ended.
Or use information in ways a person never reasonably expected.
Meet Your Neighbor should seek something better than minimum compliance.
We should practice responsible stewardship.
That means asking not only:
“Are we allowed to do this?”
but also:
“Is this necessary?”
“Is this appropriate?”
“Does this honor the purpose for which the information was entrusted to us?”
“Could this unnecessarily harm or expose someone?”
“Would we be comfortable explaining this use directly to the person?”
The Person Comes Before the Record
As Meet Your Neighbor grows, every Neighbor may eventually have a sophisticated record connecting:
Nominations.
Communications.
Preparation.
Preferences.
Consent.
Scheduling.
Production.
Media.
Transcripts.
Rights and permissions.
Governance flags.
Publication.
Follow-up.
Impact.
And relationship history.
That architecture can help Kingdom Keys steward the experience well.
But the record must never become more important than the person it represents.
A database entry cannot feel exposed.
A workflow cannot experience embarrassment.
A transcript cannot fear for its safety.
A profile cannot regret something it trusted us with.
The person can.
That is why privacy, personal information, boundaries, and safety are not merely technical responsibilities.
They are relational responsibilities.
And throughout Meet Your Neighbor, our governing principle should remain:
We protect information because there is a person on the other side of it.
Before we collect it—
before we access it—
before we analyze it—
before we share it—
before we publish it—
and before we decide to keep it—
we remember the person.
2. What Information We Collect & Why
Meet Your Neighbor cannot operate without information.
We need to know whom we are communicating with.
How to reach them.
How they prefer to be identified.
When they are available.
What accommodations may be needed.
Whether consent has been completed.
What boundaries have been communicated.
What materials have been provided.
And eventually, what information has been authorized for publication.
But responsible stewardship begins with an important principle:
We should collect information because we have a legitimate reason to use it—not simply because we have the ability to obtain it.
Information Should Have a Purpose
Before Kingdom Keys collects or requests personal information, there should be a reasonable connection between the information and the Meet Your Neighbor experience.
That purpose may include:
Considering a nomination.
Contacting a potential Neighbor.
Responding to an inquiry.
Preparing for a conversation.
Understanding communication preferences.
Providing accessibility accommodations.
Scheduling.
Confirming identity where reasonably necessary.
Managing consent.
Protecting safety.
Preparing a host.
Producing or editing a conversation.
Managing rights and permissions.
Creating an approved Neighbor Profile.
Publishing authorized information.
Following up after publication.
Responding to corrections or privacy concerns.
Maintaining appropriate governance records.
Or preserving information reasonably necessary for legal, operational, security, or accountability purposes.
Information should not be collected merely because it might become useful someday.
Different Stages Require Different Information
The amount of information Kingdom Keys reasonably needs should grow only as the relationship requires it.
A person who has merely been nominated does not require the same record as a Neighbor who has agreed to participate.
A potential progression may look like:
Nominated or Discovered Basic identifying information, nomination source, reason for consideration, general location where relevant, and an appropriate contact pathway.
Invitation Stage Contact information, communication history, communication preferences, response status, and information reasonably needed to explain the invitation.
Accepted / Preparation Stage Preparation responses, preferred/public name, relevant background, interests, conversation preferences, boundaries, accessibility needs, scheduling information, and other information voluntarily provided for responsible preparation.
Consent & Scheduling Stage Consent records, agreement versions, required contact and identity information, signatures or electronic signature records, scheduling details, production format, and applicable permissions.
Production Stage Recording information, production notes, boundaries, restricted segments, guest-provided materials, rights information, safety considerations, and other information needed by authorized personnel.
Editorial & Publication Stage Recordings, transcripts, approved biographical information, editorial notes, rights and permissions, governance decisions, publication status, approved links, clips, excerpts, quotations, and related production assets.
Post-Publication & Relationship Stage Publication history, corrections, updates, restrictions, follow-up communications, approved relationship history, future participation preferences, and information reasonably necessary to steward the continuing record.
The existence of a later stage does not justify collecting all later-stage information at the beginning.
The record should grow with the relationship—not ahead of it.
Information May Come Directly From the Neighbor
Whenever practical, information about a Neighbor should come from the Neighbor themselves.
This may include information provided through:
Nomination or self-nomination forms.
Invitation responses.
Preparation forms.
Email or other approved communications.
Scheduling.
Consent forms.
Conversations with Kingdom Keys personnel.
Recorded conversations.
Follow-up communications.
Correction or update requests.
Guest-provided biographies.
Photographs.
Documents.
Websites or social links submitted by the Neighbor.
Business or organization information.
And other materials voluntarily provided for an understood purpose.
Information provided directly by the Neighbor should still be used according to the context in which it was provided.
Providing information to Kingdom Keys does not automatically authorize every possible use of that information.
Information May Sometimes Come From Other People
A nominator may provide information about someone they believe Kingdom Keys should meet.
Another Neighbor may recommend someone.
A community organization may suggest a participant.
A family member, colleague, business, ministry, school, nonprofit, or other person or organization may provide an introduction.
When information comes from someone other than the potential Neighbor, Kingdom Keys should remember:
The source is not the subject.
A nominator can tell us why they believe someone may be interesting to meet.
They cannot speak for that person's willingness to participate.
They cannot provide media consent on behalf of a competent adult.
They should not be encouraged to disclose unnecessary private information.
And their description should not automatically become established fact within the Neighbor's record.
Where appropriate, information should be verified or clarified with the person it concerns.
Public Information May Sometimes Support Responsible Preparation
Kingdom Keys may sometimes review publicly available information when there is a reasonable purpose.
For example:
A public professional biography.
An organization's official website.
A business website.
Published articles.
Public interviews.
Publicly presented work.
Public social-media information relevant to the anticipated conversation.
Information necessary to verify a significant public claim.
Or public information reasonably relevant to safety, rights, identity, preparation, or governance.
But public research should remain proportional.
We should not turn ordinary preparation into unnecessary surveillance.
Research should help us prepare to meet the person—not convince us that we already know them.
Search Results Are Not Automatically Truth
Information found online may be:
Incorrect.
Outdated.
Incomplete.
Taken out of context.
About another person with the same name.
Based on rumor.
Generated or altered by Artificial Intelligence.
Copied repeatedly from an unreliable source.
Or presented without the person's knowledge.
Kingdom Keys should therefore avoid treating search results as unquestionable facts.
Where information could materially affect selection, safety, editorial treatment, reputation, or publication, appropriate verification or clarification may be necessary.
Intelligence may help locate and organize information.
It should also help identify uncertainty.
Sensitive Information Should Require a Stronger Reason
Some information deserves greater restraint.
This may include information concerning:
Children or minors.
Home addresses.
Precise personal locations.
Private telephone numbers.
Personal email addresses.
Government identification information.
Financial information.
Medical or health information.
Private family matters.
Traumatic experiences.
Legal matters.
Safety concerns.
Protective orders.
Confidential communications.
Employment matters.
Private religious or spiritual disclosures.
Personal relationship matters.
Information concerning third parties.
Authentication or account credentials.
Or other information whose misuse or exposure could reasonably create harm.
Meet Your Neighbor should not routinely request sensitive information merely because it might make a conversation more interesting.
The more sensitive the information, the clearer our reason for requesting, accessing, retaining, or using it should be.
Some Information Should Not Be Collected At All
There are circumstances where the correct data-collection decision is simply:
Do not collect it.
Meet Your Neighbor generally should not request:
Passwords.
Security answers.
Unnecessary government identification numbers.
Unnecessary banking or payment credentials.
Private medical records merely to support a story.
Private legal documents merely because they are interesting.
Confidential employer information without an appropriate reason.
Another person's private communications without appropriate rights or justification.
Or highly sensitive personal information unrelated to the legitimate purpose of the experience.
If information is not needed, avoiding its collection may be one of the strongest forms of protection.
Accessibility Information Should Be Collected With Care
A Neighbor may need:
Captioning.
Interpretation.
Translation.
Mobility accommodations.
Sensory accommodations.
Additional time.
Communication adjustments.
Remote participation.
A support person.
Or another reasonable accommodation.
Kingdom Keys may need enough information to provide appropriate support.
But we should not require someone to disclose an unnecessary diagnosis or private medical history simply to request an accommodation
.
Often the important question is not:
“What condition do you have?”
It is:
“What would help you participate comfortably and meaningfully?”
Safety Information Should Be Relevant and Proportionate
There may be circumstances where safety information is reasonably necessary.
For example:
A credible threat.
A known protective order relevant to participation.
A location-specific safety concern.
A participant's requested privacy precaution.
A concern about unwanted contact.
A known conflict affecting an on-location recording.
Or information necessary to protect the Neighbor, staff, hosts, production team, or other participants.
Safety information should be handled carefully and shared only with people who reasonably need it.
Safety records should describe relevant concerns as concretely as possible rather than using stigmatizing labels.
For example, a useful record may state:
“Guest requested that home address and exterior location not be photographed or published.”
That is more responsible than an unexplained label such as:
“High-risk guest.”
Preparation Questions Should Have Boundaries
Preparation helps Meet Your Neighbor create a thoughtful conversation.
But preparation should not become an interrogation.
We should ask questions because the answers help us:
Understand the person.
Prepare the host.
Identify meaningful areas of conversation.
Respect boundaries.
Recognize potential sensitivities.
Provide accommodations.
Or steward the production responsibly.
Neighbors should not feel that participation requires surrendering an exhaustive personal history.
They should also be able, where appropriate, to indicate:
Prefer not to answer.
Prefer not to discuss.
Host preparation only.
Okay to discuss privately before recording.
Okay to discuss on camera.
Or another meaningful preference.
Those distinctions should travel into the Host Preparation and production workflow.
Private Preparation Information Is Not Automatically Editorial Material
This distinction is essential.
A Neighbor may tell Kingdom Keys something during preparation so that the host understands the context of their life.
That does not necessarily mean they want the host to ask about it publicly.
It does not necessarily mean it belongs in the transcript.
It does not necessarily mean it belongs in the Neighbor Profile.
It does not necessarily mean Intelligence should suggest it as a clip, headline, or promotional angle.
The purpose attached to the information matters.
Preparation access is not publication permission.
We Should Distinguish Required Information From Optional Information
Forms should make this distinction clear whenever practical.
Some information may genuinely be necessary to complete a process.
Other information may simply help Kingdom Keys provide a better experience.
A Neighbor should be able to understand the difference.
We should avoid designing forms where every field appears mandatory simply because collecting more information is convenient.
Where appropriate, Kingdom Keys should explain why particularly sensitive information is being requested.
Information About Children Requires Greater Restraint
Information involving minors deserves additional protection.
Kingdom Keys should collect only what is reasonably necessary for:
Participation.
Guardian authorization.
Safeguarding.
Communication.
Production.
Rights management.
Emergency or safety needs where appropriate.
And responsible publication.
Information about a child should not be collected simply because an adult finds it interesting or believes it would improve the story.
The specialized requirements governing minors will be addressed more fully within the Meet Your Neighbor Minor Participation Standards .
Information About Third Parties Requires Context
A Neighbor may naturally mention other people while telling their story.
Not every reference creates a privacy concern.
But greater care may be required when the information:
Identifies a private individual.
Reveals sensitive personal information.
Makes a serious allegation.
Concerns a child.
Reveals confidential information.
Creates a safety risk.
Includes private communications.
Or could cause significant harm if published without context.
Kingdom Keys may need to clarify, edit, anonymize, restrict, verify, obtain additional permission, or omit information depending on the circumstances.
Collection Should Not Quietly Become Marketing
A person nominated for Meet Your Neighbor has not automatically subscribed to Kingdom Keys marketing.
A person who accepts an invitation has not automatically subscribed.
A person who completes a preparation form has not automatically subscribed.
A Neighbor's email address should not quietly move into unrelated promotional lists merely because it exists within the Kingdom Keys ecosystem.
Where Kingdom Keys offers newsletters, programs, resources, or other communications, appropriate choices and permissions should remain distinguishable from participation in Meet Your Neighbor.
Relationship intelligence can help us serve people better.
It should not erase the boundaries between different relationships.
Information Should Remain Connected to Its Source and Purpose
Where practical, important information should retain context such as:
Source — Where did this information come from?
Purpose — Why do we have it?
Status — Is it confirmed, unconfirmed, outdated, disputed, or restricted?
Permission — What are we authorized to do with it?
Access — Who needs to see it?
Restriction — Are there limits on use or publication?
Retention — How long should it remain?
This allows future staff, systems, and Intelligence to understand not merely what Kingdom Keys knows—
but why Kingdom Keys knows it.
Collect Less. Understand Better. Steward Well.
Meet Your Neighbor does not need the largest possible record about every person.
It needs the right information for the right purpose at the right stage of the relationship.
Sometimes good stewardship means asking another question.
Sometimes it means verifying what we have heard.
Sometimes it means documenting an important boundary.
Sometimes it means restricting access.
And sometimes it means choosing not to collect something at all.
Our goal is not to know everything about the Neighbor before we meet them.
Our goal is to know enough to meet them responsibly—
while leaving room for the person themselves to tell us who they are.
We collect what helps us steward the relationship.
We do not collect simply because technology makes collection possible.
Because even before information becomes part of a record—
it belongs to the story of a person.
4. Access, Confidentiality & Responsible Internal Use
Information entrusted to Meet Your Neighbor may sometimes need to be accessed by people inside Kingdom Keys.
But internal access should never be treated as unlimited access.
A person's information should not become available to everyone merely because they work within the same organization.
Access should follow responsibility.
Access should be granted because someone needs information to perform an authorized responsibility—not because they are curious, senior, convenient, or technically capable of seeing it.
Internal Does Not Mean Available to Everyone
Kingdom Keys may eventually include many departments, studios, systems, roles, and forms of Intelligence.
Meet Your Neighbor information may connect with some of them.
That does not mean every person or system within Kingdom Keys should be able to see the complete Neighbor record.
Internal information should remain governed according to purpose, role, sensitivity, and responsibility.
Use the Least Access Necessary
A person should generally receive the least amount of access reasonably necessary to perform their assigned responsibility.
That may include separate permissions to:
- View information.
- Contribute information.
- Edit information.
- Approve information or decisions.
- Apply or remove restrictions.
- Export information.
- Share information externally.
- Delete information.
Those permissions are not necessarily the same.
Sensitive Information Requires Narrower Access
Sensitive or restricted information should generally be available to fewer people than ordinary operational information.
A person who can schedule a conversation may not need access to a sensitive governance concern.
A production assistant may not need access to private family information.
A host may not need access to administrative records unrelated to the conversation.
The more sensitive the information, the more deliberate the access decision should become.
Need to Know Does Not Mean Need to Know Everything
Sometimes a person needs to know that a boundary exists without needing to know the private details behind it.
For example:
A production team may need to know:
Do not reveal the residential location.
They may not need to know the private circumstances that caused the restriction.
A host may need to know:
Do not initiate discussion about this topic.
They may not need access to unrelated administrative information.
Systems should allow the operational boundary to travel without unnecessarily exposing the private explanation behind it.
Confidentiality Is a Human Responsibility
Technology can restrict access.
Policies can define boundaries.
But people still have a responsibility to exercise discretion.
Someone with legitimate access should not:
- Discuss private Neighbor information casually.
- Share information as gossip.
- Use it for personal curiosity.
- Share it through personal social accounts.
- Use it for unrelated business.
- Use it for an unrelated Kingdom Keys function without an authorized purpose.
- Show it to people who do not have a legitimate responsibility.
Confidentiality remains a responsibility even when there is no technical barrier preventing disclosure.
Hosts Carry a Special Responsibility
A Meet Your Neighbor host may receive preparation information in order to create a more thoughtful conversation.
That access creates responsibility.
Preparation should help the host:
- Understand the Neighbor more fully.
- Avoid unnecessary surprises.
- Honor stated boundaries.
- Recognize important context.
- Ask more thoughtful questions.
- Prepare for accessibility or communication needs.
It should not be used to make the Neighbor feel that Kingdom Keys has secretly investigated them.
A prepared host should make the Neighbor feel understood—not investigated.
Production Personnel Need Production-Relevant Information
Camera, audio, lighting, technical, and production personnel may need information such as:
- Recording location.
- Arrival time.
- Accessibility requirements.
- Production restrictions.
- Do Not Publish markers.
- Environmental considerations.
- Applicable safety instructions.
They generally do not need unrestricted access to:
- Private preparation responses.
- Unrelated family information.
- Private correspondence.
- Administrative notes.
- Financial information.
- Other sensitive information unrelated to production.
The production role should see what the production role needs.
Editors Must Receive the Restrictions Along With the Media
An editor cannot responsibly work with media if the restrictions attached to that media are missing.
When recordings, transcripts, or assets move into editorial workflows, applicable boundaries should travel with them.
That may include:
- Off-record timestamps.
- Do Not Publish segments.
- Privacy restrictions.
- Minor-related restrictions.
- Rights limitations.
- Additional-consent requirements.
- Safety restrictions.
The editor should not have to discover those limitations accidentally after producing a finished asset.
Contractors & External Collaborators Require Controlled Access
Meet Your Neighbor may sometimes rely upon:
- Freelance editors.
- Camera operators.
- Translators.
- Captioning providers.
- Designers.
- Technology specialists.
- Legal advisers.
- E-signature providers.
- Cloud or production services.
External collaborators should receive only the information required for the assigned responsibility.
Where appropriate, Kingdom Keys should consider:
- Confidentiality obligations.
- Security expectations.
- Permitted uses.
- Retention limits.
- Return or deletion requirements.
- Subcontractor access.
- Whether information may be used for external Artificial Intelligence training.
Access granted for one assignment should not quietly become permission for unrelated future use.
Private Information Should Stay in Approved Environments
Sensitive Neighbor information should not be casually moved into:
- Personal email accounts.
- Personal cloud-storage accounts.
- Unapproved messaging applications.
- Unsecured notes.
- Personal Artificial Intelligence tools.
- Shared household computers.
- Public computers.
- Unapproved removable storage.
Convenience should not silently create another ungoverned copy of private information.
Shared Devices Require Additional Care
When a Kingdom Keys device may be used by more than one authorized person, appropriate controls may include:
- Individual user accounts.
- Automatic screen locking.
- Reasonable session timeouts.
- Restricted folders.
- Appropriate authentication.
- Private notification settings.
- Separate browser profiles where appropriate.
- Proper logout procedures.
A shared device should not become shared access to every person's information.
Visual Privacy Matters Inside Our Own Workspaces
Private information can be exposed without anyone intentionally sending it anywhere.
For example:
- A private Neighbor record left visible on a monitor.
- A consent document left on a desk.
- A whiteboard displaying guest details during another recording.
- A private notification appearing during screen sharing.
- A production schedule photographed accidentally.
Physical and visual workspaces should be treated as part of the privacy environment.
Printed Information Is Still Information
Kingdom Keys may occasionally print:
- Host Briefs.
- Schedules.
- Consent records.
- Production notes.
- Guest information.
Printed materials should not be left where unauthorized people may access them.
When sensitive printed materials are no longer needed, they should be disposed of securely rather than placed casually into ordinary trash where inappropriate.
Credentials Should Belong to Individuals
Shared passwords make accountability difficult.
Where systems permit, Kingdom Keys should use individual accounts so authorized actions can be associated with the person who performed them.
Credentials should not be casually shared simply because several people work on the same project.
Stronger Authentication May Be Appropriate
Systems containing sensitive Neighbor information may warrant stronger safeguards such as:
- Multi-factor authentication.
- Strong passwords.
- Device security.
- Session controls.
- Role-based permissions.
- Access alerts.
The level of security should reflect the sensitivity and consequences of the information involved.
Significant Actions Should Be Traceable
Certain actions involving sensitive or consequential information should leave an appropriate record.
For example:
- Changing a privacy restriction.
- Changing consent status.
- Exporting sensitive information.
- Approving publication.
- Removing a Do Not Publish marker.
- Accessing especially restricted information.
- Sharing information externally.
Authority should leave a responsible trail.
Audit Records Require Protection Too
Logs can reveal sensitive information about:
- Who accessed a record.
- What was reviewed.
- When an event occurred.
- What restrictions exist.
- What governance concerns were raised.
Audit information should therefore be governed rather than treated as harmless technical data.
Access Should Change When Responsibilities Change
People change roles.
Contractors complete assignments.
Volunteers leave.
Projects end.
When someone's responsibility changes, access should be reviewed accordingly.
Access should not remain permanently simply because it was appropriate once.
Emergency Access Should Remain Exceptional
There may be rare circumstances where an authorized person must access information outside the normal workflow because of an urgent safety, security, legal, or operational need.
Where practicable, such access should be:
- Limited to the situation.
- Documented.
- Reviewed afterward.
Emergency access should not become a routine shortcut around ordinary permissions.
Curiosity Is Not Authorization
Kingdom Keys may eventually hold compelling stories involving many people.
Staff, volunteers, contractors, or other authorized users may naturally become curious.
Curiosity does not create permission.
A person should not open a private Neighbor record simply because they recognize the name or want to know more.
Artificial Intelligence Is Also an Information User
Artificial Intelligence should be governed as though it is another user of information.
It should have:
- A defined purpose.
- A defined information scope.
- Applicable access limitations.
- Restrictions on output.
- Appropriate logging where necessary.
- Rules concerning retention and external processing.
Intelligence should not receive broader access simply because machine processing makes that technically easy.
Public-Facing Intelligence Should Be Separated From Private Records
Meet Your Neighbor may eventually allow visitors to search the archive, explore Neighbor Profiles, ask questions about published conversations, or receive recommendations.
Those public-facing experiences should operate from information approved for public use.
They should not quietly search:
- Private contact information.
- Preparation notes.
- Off-record transcripts.
- Consent records.
- Private safety information.
- Governance-review notes.
Public Intelligence and private operational Intelligence should be architecturally distinguishable.
Access Creates Responsibility
The fact that Kingdom Keys has entrusted someone with access to information does not make that information theirs.
It remains information held for a purpose.
That person becomes a temporary steward of what they are allowed to see.
The appropriate question is not:
“Can I open this?”
It is:
“Do I have a responsibility that requires me to open this?”
And once access is granted:
“What am I authorized to do with what I now know?”
Access is not ownership. Access is responsibility.
6. Retention, Archiving & Responsible Record Lifecycle
Information does not need to remain forever simply because Kingdom Keys once had a reason to collect it.
Some records may need to be retained for a long time.
Others may be useful only for a particular stage of the Meet Your Neighbor relationship.
Responsible stewardship includes knowing not only what to keep—but also why we are keeping it.
Information should remain because there is a responsible reason to retain it—not merely because no one remembered to delete it.
Different Information May Require Different Lifespans
There should not necessarily be one retention period for every type of Meet Your Neighbor information.
A scheduling note may be temporary.
A signed consent record may need to remain for many years.
A published conversation may become part of the long-term Meet Your Neighbor archive.
A temporary processing file may no longer be useful once the production is complete.
Retention should reflect the purpose, sensitivity, legal significance, historical value, and continuing responsibility attached to the information.
The Record Should Change as the Relationship Changes
The information needed when someone is first nominated is not necessarily the same information needed after they become a published Neighbor.
The record may grow during:
- Nomination.
- Invitation.
- Preparation.
- Consent.
- Scheduling.
- Recording.
- Editorial review.
- Publication.
- Follow-up.
- Long-term relationship stewardship.
But information that was useful for an earlier stage may later become unnecessary.
A mature record should not simply accumulate forever. It should be intentionally stewarded through its lifecycle.
A Nomination Should Not Become a Permanent Personal Profile
Someone may be nominated for Meet Your Neighbor without ever being invited.
They may be considered and deferred.
They may decline.
The project may decide not to proceed.
In those situations, Kingdom Keys should not automatically preserve an ever-growing personal dossier simply because the person once entered the selection process.
Information that no longer serves a legitimate selection, communication, governance, legal, or operational purpose should be reviewed for appropriate deletion, reduction, or archival restriction.
Declining Participation Should Not Create a Negative Permanent Record
A person may simply decide that Meet Your Neighbor is not right for them.
They may decline now and reconsider later.
They may never wish to participate.
A decline should not become an unnecessary permanent judgment attached to the person.
Records should distinguish a practical communication or workflow history from an enduring negative characterization.
Do Not Contact May Require a Minimal Continuing Record
A person may ask Kingdom Keys not to contact them again.
Honoring that request may require retaining a minimal suppression record so that future systems, staff, or Intelligence do not accidentally begin contact again.
That does not mean Kingdom Keys must retain the person's entire prior record.
The information retained should be limited to what is reasonably necessary to honor the boundary.
Consent Records Require Durable Stewardship
Signed consent and release records may need to remain available long after a conversation is recorded or published.
Kingdom Keys should preserve enough information to establish:
- Who consented.
- What agreement they accepted.
- The version of the agreement.
- The date and time of consent.
- The applicable acknowledgments.
- The e-signature or verification record.
- Any later changes or additional permissions.
- Any applicable withdrawal, restriction, or correction history.
Historical agreement versions should not be overwritten merely because a new version becomes active.
The record should be capable of showing what was actually agreed to at the time.
Rights & Permission Records May Outlive the Production
A production may continue to be used, archived, redistributed, or referenced for many years.
The permissions governing that production may therefore need to remain available for as long as Kingdom Keys continues relying upon them.
This may include:
- Media releases.
- Guest-provided asset permissions.
- Music rights.
- Photography permissions.
- Third-party licenses.
- Location releases.
- Additional-use permissions.
- Restrictions and expiration terms.
Removing the rights record while continuing to use the asset would weaken responsible stewardship.
Published Stories May Become Part of a Long-Term Archive
Meet Your Neighbor is intended to become more than a stream of temporary content.
Published conversations may become part of a growing archive of people, experiences, communities, and human stories.
That archive may have:
- Historical value.
- Educational value.
- Community value.
- Relational value.
- Research value.
- Future storytelling value.
Long-term retention of approved public content may therefore be appropriate.
But archive status should not erase the responsibilities that still travel with the story.
Archiving Is Not Abandonment
A story does not become ungoverned merely because it is old.
Archived material may still require:
- Accurate context.
- Rights records.
- Privacy restrictions.
- Corrections.
- Updated links.
- Safety review.
- Age or date context.
- Restrictions on future reuse.
An archive should be a stewarded record—not a forgotten storage room.
Historical Context Should Remain Visible
People change.
Jobs change.
Organizations change.
Relationships change.
Public understanding changes.
A conversation published years earlier should not necessarily be silently rewritten as though it happened today.
Where appropriate, archived material may display:
- Original publication date.
- Recording date.
- Historical role or title.
- Update notices.
- Corrections.
- Current profile links where available.
Context helps an archive remain honest across time.
Correction History May Need to Remain Internally Available
If Kingdom Keys corrects, clarifies, restricts, updates, or removes information, there may be value in preserving an internal record of what changed.
This can support:
- Accountability.
- Consistency.
- Future editorial review.
- Legal or rights documentation.
- Understanding downstream assets.
- Responding to future questions.
Preserving an internal correction history does not necessarily mean preserving every outdated version publicly.
Restricted Material May Be Retained Without Remaining Active
Some material may need to be preserved while being removed from ordinary use.
For example:
- A disputed segment may be retained for review.
- An unpublished recording may be preserved while a rights issue is resolved.
- A removed public asset may remain in a restricted archive for accountability.
- A legal hold may require information to remain available.
- A safety concern may require an asset to become inaccessible without immediate destruction.
Systems should therefore be capable of distinguishing:
Retained
Active
Public
Searchable
Reusable
Restricted
Retention does not have to mean continued availability.
Production Files Should Have Clear Lifecycle Categories
A single Meet Your Neighbor production may create many files.
Those files should not all be treated equally.
Useful categories may include:
Master Assets
Original or preservation-quality recordings that may need long-term retention.
Approved Derivatives
Final clips, edits, captions, images, promotional assets, and distribution versions approved for use.
Governance Records
Consent, rights, restrictions, review decisions, publication approvals, and related documentation.
Working Files
Editing projects, intermediate exports, draft transcripts, temporary design files, and other materials used during production.
Temporary Processing Files
Files created by transcription, rendering, conversion, uploading, AI processing, or other temporary workflows.
Disposable Duplicates
Unnecessary copies that no longer serve a legitimate production, backup, or governance purpose.
Temporary Files Should Eventually Be Temporary
Production workflows often create temporary copies.
A file may be downloaded to a workstation.
Uploaded to a service.
Exported for review.
Rendered into another format.
Copied to temporary storage.
Or created as part of an AI or transcription workflow.
Once those copies no longer serve their purpose, they should be reviewed for appropriate removal.
Temporary processing should not become accidental permanent retention.
Sensitivity Should Influence Retention
The more sensitive information is, the more carefully Kingdom Keys should consider whether continued retention remains necessary.
Retaining highly sensitive information forever without a continuing purpose may create unnecessary risk.
Relevant considerations may include:
- The reason the information was collected.
- Whether that purpose still exists.
- Whether a less detailed record would be sufficient.
- Whether the information remains legally or operationally necessary.
- Whether it supports an ongoing rights or safety responsibility.
- The consequences of unauthorized exposure.
Safety Information Requires Special Retention Judgment
Safety-related information may sometimes need to remain available longer than ordinary preparation information.
But unnecessary permanent safety labeling can also create unfair or stigmatizing records.
Kingdom Keys should therefore consider:
- Whether the concern is still relevant.
- Whether the circumstances have changed.
- Whether the information remains necessary to protect people.
- Whether a narrower operational boundary would be sufficient.
- Whether the record contains unsupported speculation.
- Whether review or expiration is appropriate.
Safety stewardship should protect people without creating permanent labels that no longer serve a legitimate purpose.
Legal Holds May Override Ordinary Deletion
There may be circumstances where information that would otherwise be deleted must temporarily be preserved because of:
- Pending litigation.
- A legal claim.
- An investigation.
- A regulatory matter.
- A subpoena or preservation obligation.
- Or another legitimate legal requirement.
When an authorized legal hold applies, normal deletion schedules may be suspended for the affected information.
Once the hold ends, the information should return to the ordinary retention review process rather than remaining indefinitely by default.
Deletion Should Be Described Truthfully
Modern systems may contain:
- Backups.
- Caches.
- Temporary copies.
- Archived versions.
- Distributed storage.
- Third-party service copies.
Kingdom Keys should avoid promising immediate universal erasure if its systems cannot realistically provide it.
A more accurate approach may distinguish:
- Removed from active systems.
- Removed from public access.
- Restricted from further use.
- Scheduled for deletion.
- Deleted from primary storage.
- Awaiting normal backup expiration.
Privacy commitments should reflect how the technology actually works.
Backups Are Part of the Record Lifecycle
Backups are essential for continuity and recovery.
But backups may also preserve information after it has been removed from active systems.
Backup systems should therefore have their own:
- Access controls.
- Security protections.
- Retention schedules.
- Recovery procedures.
- Deletion or expiration processes.
Restoring a backup should also restore applicable restrictions and governance state.
A restored system should not accidentally make previously restricted or removed information active again.
Artificial Intelligence Can Create Hidden Forms of Retention
Artificial Intelligence and advanced search systems may create derived forms of information that are not obvious to ordinary users.
These may include:
- Embeddings.
- Search indexes.
- Summaries.
- Topic classifications.
- Cached responses.
- Generated notes.
- Metadata.
- Relationship mappings.
These derived records may still reveal information about the original person or content.
They should therefore be considered part of the retention lifecycle rather than treated as though the source disappeared simply because the original file was deleted.
Corrections & Deletions Should Reach Derived Systems
If information is corrected, restricted, or removed, connected systems should not knowingly continue presenting the old information as current.
Where technically and operationally appropriate, changes should propagate to:
- Search indexes.
- Neighbor Profiles.
- Recommendation systems.
- Transcript databases.
- Published derivatives.
- AI retrieval systems.
- Internal summaries.
- Distribution records.
A correction should not stop at the first database if the outdated information continues appearing elsewhere.
Retention Policies Should Be Understandable
Kingdom Keys should eventually maintain practical internal retention standards for major categories of Meet Your Neighbor information.
Those standards should be understandable enough that authorized staff can determine:
- What should be retained.
- Why it is retained.
- How long it should normally remain.
- Who may approve exceptions.
- What happens when the retention period ends.
- Whether legal, governance, archival, rights, or safety considerations override ordinary schedules.
Retention should become an intentional operational process rather than a series of accidental leftovers.
Retention Decisions Should Be Reviewable
Policies may need to change as:
- Technology changes.
- Kingdom Keys grows.
- New laws apply.
- New forms of media emerge.
- New risks become understood.
- The archive matures.
- Operational responsibilities change.
Retention standards should therefore be reviewed periodically rather than treated as permanent simply because they were once established.
The Archive Should Preserve the Story Without Hoarding the Person
Meet Your Neighbor may eventually hold a remarkable historical archive.
Conversations.
Voices.
Photographs.
Stories.
Communities.
Moments in time.
That long-term preservation can serve the mission.
But the existence of an archive should not become a justification for preserving every private detail ever gathered about every person who entered the process.
The public story and the private operational record are not the same thing.
Preserve what serves the story, the relationship, the law, the rights, the safety, and the stewardship—not simply everything that once passed through the system.
Retention Should Always Return to Purpose
For information that remains in Kingdom Keys systems, we should periodically be able to answer:
Why are we still keeping this?
What responsibility does it still support?
Who still needs access?
Does the information still need to be this detailed?
Does its sensitivity justify additional restriction?
Is it part of the public archive or merely an old operational record?
Are there rights, legal, safety, historical, or accountability reasons to preserve it?
What should happen when that reason ends?
Good stewardship is not measured by how much information we can store.
It is measured by whether we understand why we are keeping what has been entrusted to us.
Keep what has a responsible purpose. Protect what must remain. Release what no longer needs to be held.
7. Personal Safety, Risk Awareness & Protective Boundaries
Meet Your Neighbor is built around human connection.
That connection should never require people to ignore reasonable safety concerns.
Guests, hosts, staff, volunteers, contractors, visitors, family members, and other people connected to the experience may sometimes encounter circumstances that require additional awareness or protective boundaries.
Safety should be approached seriously—but not fearfully.
Good safety stewardship protects the encounter without teaching us to fear the person.
Everyone May Raise a Safety Concern
A safety concern should not require a particular title before someone is allowed to speak.
A Neighbor may raise a concern.
A host may notice something.
A Guest Coordinator may receive information during preparation.
A production team member may recognize an unsafe condition.
A family member, facility representative, contractor, volunteer, or other participant may have relevant information.
Concerns should be received seriously enough to evaluate rather than dismissed merely because they came from someone without formal authority.
Safety Concerns May Take Many Forms
Relevant concerns may include:
- Unsafe recording locations.
- Threats of violence.
- Harassment.
- Stalking.
- Doxxing.
- Unwanted contact.
- Intimidation.
- Unsafe transportation arrangements.
- Unsafe equipment or physical conditions.
- Unauthorized people entering a production space.
- Exposure of residential or private locations.
- Safety concerns involving children or minors.
- Domestic or family safety concerns.
- Digital harassment following publication.
- Threatening communications.
- Security incidents affecting private information.
- Or another concrete circumstance that could reasonably affect personal safety.
The existence of a safety concern should create a reason to understand the circumstances—not permission to speculate about the person.
Difference Is Not Evidence of Danger
Safety decisions should be based upon concrete information and circumstances rather than assumptions about identity or difference.
A person's:
- Race.
- Religion.
- Culture.
- Nationality.
- Profession.
- Neighborhood.
- Political views.
- Worldview.
- Appearance.
- Communication style.
- Economic circumstances.
- Personal history.
- Or disagreement with Kingdom Keys
should not automatically be treated as evidence that the person is unsafe.
Difference is not evidence of danger.
A Concern Is Not Automatically a Conclusion
A concern may be incomplete.
It may be based on misunderstanding.
It may require context.
It may be accurate.
Or it may reveal a circumstance requiring immediate action.
Depending upon the situation, the appropriate response may be to:
- Clarify.
- Ask additional questions.
- Adjust the production plan.
- Establish a protective boundary.
- Move the location.
- Change the recording format.
- Increase staffing.
- Pause the process.
- Request specialized review.
- Or decide not to proceed under the current circumstances.
Safety review should help Kingdom Keys understand what responsible action is needed rather than label a person prematurely.
No Schedule Is More Important Than Safety
A production may already be scheduled.
Equipment may already be set up.
Travel may have been arranged.
A release date may already exist.
Money may already have been spent.
None of those circumstances should force Kingdom Keys to ignore a meaningful safety concern.
Fame, audience interest, production cost, schedule pressure, or fear of inconvenience should not override responsible judgment.
Safety Review May Temporarily Pause Production
Some circumstances may require a temporary pause while additional information is reviewed.
Appropriate workflow states may include:
SAFETY REVIEW — PRODUCTION PAUSED
ELEVATED REVIEW — RECORDING NOT YET CLEARED
These statuses should not automatically mean:
- The Neighbor has done something wrong.
- The conversation is permanently cancelled.
- The person should be labeled dangerous.
- The information should become public.
They mean the current process should not continue casually until the concern has been appropriately reviewed.
Publication Can Create New Safety Risks
A conversation may feel safe in the studio and create a different risk once it becomes public.
Publication may unintentionally reveal:
- A residential location.
- A child's school.
- A work schedule.
- A frequently visited location.
- A vehicle or license plate.
- A private entrance.
- Family routines.
- Travel plans.
- Security systems.
- Personal contact information.
- Private identifying documents.
- Or another detail that becomes risky when widely distributed.
Safety review should therefore consider not only what the Neighbor says, but also what the camera, microphone, metadata, photographs, captions, and surrounding environment may unintentionally reveal.
Visual Privacy Is Part of Safety
A camera sees more than the person speaking.
A recording may capture:
- Mail or packages containing an address.
- Family photographs.
- Computer screens.
- Calendars.
- Medication labels.
- School information.
- Security devices.
- Vehicle information.
- Documents.
- Other people.
- Private rooms or spaces.
Production teams should remain aware of the environment rather than focusing only on the person in front of the camera.
Cropping, reframing, blurring, removing, repositioning, or choosing another angle may sometimes protect privacy without affecting the story.
Audio Can Reveal Private Information Too
Sound may reveal information the camera does not.
A recording may capture:
- Someone saying a private name.
- A telephone conversation.
- An address.
- A child's voice.
- A private conversation in another room.
- Medical or family information.
- A location announcement.
- Or another unintended disclosure.
Privacy and safety review should include audio as well as visual content.
Location Information Should Be Proportionate
Kingdom Keys may need detailed location information to conduct a production.
That does not mean the audience needs the same level of detail.
For example:
Internal Production Record: exact address and arrival instructions.
Public Production Context: Athens, Georgia.
Or perhaps simply:
Recorded in the Neighbor's community.
The appropriate public level of specificity should depend upon the story and the privacy and safety circumstances.
Home & On-Location Conversations Require Additional Awareness
Recording inside someone's home or personal environment can create a uniquely warm and authentic experience.
It can also reveal more than a controlled studio.
Before and during an on-location conversation, Kingdom Keys may consider:
- Who else is present.
- Whether the location is physically safe.
- Whether minors are present.
- What areas may or may not be recorded.
- Whether private documents or objects are visible.
- Whether the exterior reveals the exact residence.
- Parking and equipment security.
- Arrival and departure procedures.
- Whether the crew should work in pairs or teams.
- Whether someone outside the production should know the team's location.
- Whether additional permission is required from a property owner or facility.
The production plan should reflect the environment rather than assuming every location carries the same considerations.
The Kingdom Keys Studio Should Remain a Controlled Environment
A Kingdom Keys-controlled studio provides greater ability to establish consistent safety and privacy practices.
Depending upon the environment, that may include:
- Knowing who is expected to be present.
- Limiting unauthorized access during recordings.
- Keeping private records out of camera view.
- Providing clear arrival instructions.
- Keeping walkways and equipment areas safe.
- Maintaining appropriate lighting.
- Managing cables and equipment.
- Providing a clear way to pause or end the conversation.
- Maintaining reasonable emergency awareness.
A warm environment and a responsibly controlled environment can coexist.
Remote Conversations Have Their Own Safety & Privacy Concerns
Remote participation avoids some physical risks but introduces different ones.
Kingdom Keys should consider:
- Secure meeting links.
- Appropriate participant access.
- Whether the session is being recorded.
- Whether another person is present off camera.
- Private information visible in the background.
- Screen-sharing risks.
- Notifications appearing on screen.
- Recording files stored by the remote platform.
- Accidental public streaming.
- Platform privacy and security settings.
Remote does not mean private by default.
Meeting Links Should Be Treated as Operational Information
Private meeting links should not be published or distributed casually.
They may provide access to:
- A private conversation.
- A guest waiting room.
- Production staff.
- Internal chat.
- Screen sharing.
- Or other information not intended for the public.
Meeting access information should be shared with the people who need it for the specific session.
Harassment & Unwanted Contact Should Have a Reporting Pathway
Public visibility can sometimes create unwanted attention.
A published Neighbor may experience:
- Harassing messages.
- Threats.
- Repeated unwanted contact.
- Impersonation.
- Doxxing.
- False profiles.
- Targeted abuse.
- Or another concerning response.
Meet Your Neighbor should provide a reasonable pathway for the Neighbor to bring a significant concern to Kingdom Keys.
Kingdom Keys may not be able to control the entire internet, but it can responsibly steward the environments and content it controls.
Kingdom Keys-Controlled Community Spaces Should Be Moderated Responsibly
If Meet Your Neighbor includes comments, community discussion, live chat, forums, or other Kingdom Keys-controlled spaces, moderation may be necessary.
Moderation may address:
- Threats.
- Doxxing.
- Targeted harassment.
- Repeated abusive behavior.
- Publication of private personal information.
- Impersonation.
- Spam or malicious links.
- Other conduct inconsistent with applicable Kingdom Keys community standards.
Moderation should not be used merely to eliminate respectful disagreement.
Safety and dignity should not become a disguise for ideological control.
Protective Measures Should Not Become Hidden Punishment
A safety boundary may sometimes be appropriate.
But safety language should not be used to quietly punish someone because:
- They disagreed with Kingdom Keys.
- They asked difficult questions.
- They criticized a decision.
- They hold an unpopular opinion.
- They come from a community unfamiliar to us.
- They communicate differently.
If a restriction is based on safety, the record should identify the actual safety concern as clearly and professionally as appropriate.
Governance should distinguish discomfort from danger.
Sensitive Safety Information Should Be Compartmentalized
Safety information may itself create risk if unnecessarily exposed.
For example, a record might contain:
- A private residence used temporarily for safety.
- A protective contact method.
- A concern involving a family member.
- A law-enforcement contact.
- A safety plan.
- A restricted arrival procedure.
- Information concerning a child.
The whole production team may need to know that a restriction exists.
They may not need the underlying sensitive details.
Safety information should be shared according to need and responsibility rather than broad curiosity.
Artificial Intelligence May Assist With Safety Awareness
Intelligence may help identify information that deserves human attention.
For example, it may flag:
- A residential address visible in a video.
- A phone number spoken during a recording.
- A threat contained in a message.
- A child's identifying information.
- A private location included in metadata.
- A potentially unsafe external link.
- A previously established safety restriction.
But Artificial Intelligence should not autonomously decide that a person is dangerous based on vague behavioral interpretation, identity, ideology, emotional tone, or speculative profiling.
A meaningful Intelligence flag should explain:
- What was noticed.
- Where it appeared.
- Why it may matter.
- What applicable standard or boundary may be involved.
Human stewardship should determine the response.
Artificial Intelligence Should Not Diagnose People
Safety Intelligence should not attempt to diagnose a Neighbor's mental condition, personality, dangerousness, or future behavior.
It may identify concrete information requiring review.
It should not convert uncertainty into a hidden psychological label.
Human beings should not become risk scores simply because technology can generate one.
Emergencies Require Human Judgment
There may be rare situations involving an immediate threat to life, serious injury, or another urgent emergency.
Kingdom Keys personnel should use reasonable human judgment and seek appropriate emergency assistance when necessary.
Meet Your Neighbor is not:
- An emergency-response service.
- A law-enforcement agency.
- A medical provider.
- A mental-health crisis service.
- Or a substitute for qualified emergency professionals.
Where urgent professional assistance is required, the appropriate response may be to contact people trained and authorized to provide it.
Safety Incidents Should Be Documented Responsibly
If a significant safety incident occurs, Kingdom Keys may need to create an internal record.
That record should be:
- Factual.
- Proportionate.
- Limited to relevant information.
- Professionally written.
- Protected according to sensitivity.
- Available only to appropriate roles.
Where possible, the record should distinguish:
- What was directly observed.
- What was reported by someone else.
- What action was taken.
- What remains uncertain.
- What follow-up is required.
Incident documentation should support responsible action rather than become a collection of permanent assumptions.
Safety Decisions Should Be Reviewable
Circumstances change.
A restriction appropriate today may not remain necessary forever.
A concern may later be clarified.
New information may strengthen or weaken the original concern.
Appropriate safety decisions should therefore be capable of review where circumstances permit.
Review does not mean ignoring prior concerns. It means avoiding permanent restrictions that no longer have a responsible purpose.
No Story Is Worth Preventable Harm
Meet Your Neighbor may eventually produce powerful conversations.
Important conversations.
Rare conversations.
Conversations people want to hear.
But no story is so important that Kingdom Keys should knowingly ignore a reasonable opportunity to prevent unnecessary harm.
Sometimes responsible stewardship may mean:
- Changing the location.
- Removing identifying details.
- Adjusting a camera angle.
- Delaying publication.
- Restricting an asset.
- Seeking additional review.
- Or deciding not to proceed.
Those decisions should not be viewed as failures of storytelling.
They may be evidence that the people involved remained more important than the production.
We do not protect the production from the person.
We protect the people entrusted to the production.
8. Third Parties, Families & People Who Did Not Choose the Camera
Every person's story is connected to other people.
Parents.
Children.
Spouses.
Former partners.
Friends.
Coworkers.
Employers.
Neighbors.
Teachers.
Pastors.
Doctors.
Business partners.
And many others may appear within the story even though they never agreed to participate in Meet Your Neighbor.
Respecting the Neighbor's right to tell their own story must therefore be balanced with responsible care for people who did not choose the camera.
One person's consent does not become another person's consent.
A Neighbor May Tell Their Own Story
Meet Your Neighbor should not prevent people from speaking honestly about their own lives merely because other people were present in those lives.
A Neighbor may describe:
- Their childhood.
- Their family.
- Their marriage or relationships.
- Their workplace.
- Their community.
- Their education.
- Their faith experience.
- Their healing journey.
- Their conflict.
- Their loss.
- Their successes and disappointments.
Those experiences belong within the Neighbor's story.
But the way another person is identified, described, accused, exposed, or visually presented may require additional care.
Mentioning Someone Is Not the Same as Exposing Them
A story can sometimes preserve its meaning without giving the audience every identifying detail.
For example:
“A teacher once told me I would never succeed.”
may tell the necessary story without identifying the teacher by full name, school, photograph, and current workplace.
Sometimes identification is relevant.
Sometimes it is already public.
Sometimes the third party has agreed to be identified.
And sometimes identification adds little to the story while greatly increasing another person's exposure.
A Person Can Be Identifiable Without Their Name
Removing a name does not always make someone anonymous.
A person may still be identifiable through:
- Their relationship to the Neighbor.
- Their job title.
- Their workplace.
- Their neighborhood.
- A photograph.
- A unique event.
- A business name.
- A recognizable voice.
- A social-media profile.
- A combination of otherwise ordinary details.
Privacy review should therefore consider practical identifiability, not merely whether a full legal name appears.
Sensitive Third-Party Information Requires Greater Care
Additional care may be appropriate when a story includes another person's:
- Health information.
- Financial information.
- Private family matters.
- Sexual or intimate information.
- Legal disputes.
- Criminal allegations.
- Trauma.
- Immigration circumstances.
- Personal contact information.
- Private correspondence.
- Information involving a child.
- Or another detail that could create meaningful privacy, dignity, safety, or legal consequences.
The question is not simply:
“Did the Neighbor say it?”
We should also ask:
Is it necessary?
Is it sufficiently supported?
Is the person identifiable?
Could the story remain truthful with less exposure?
Does this require additional review?
Children Deserve Greater Protection
Adults frequently tell stories involving their children.
A parent may have legitimate reasons to discuss:
- Parenthood.
- A family challenge.
- A child's achievement.
- A parenting lesson.
- A difficult season.
- A family transformation.
But children generally have less ability to understand or control the long-term consequences of public exposure.
Kingdom Keys should therefore consider whether it is necessary to reveal:
- A child's full name.
- School.
- Exact age or birth date.
- Location.
- Medical details.
- Private struggles.
- Photographs.
- Social accounts.
- Future plans.
- Other sensitive identifying information.
A child should not inherit unnecessary public exposure simply because an adult was willing to tell the story.
When a Minor Is Actually Participating
If a child or minor is not merely mentioned but is actually participating in Meet Your Neighbor, additional standards should apply.
Those standards may involve:
- Parent or guardian consent.
- Age-appropriate assent where appropriate.
- Additional privacy protections.
- Stronger limitations on sensitive topics.
- Safeguarding procedures.
- Additional publication review.
- Restrictions on identifying information.
These circumstances should be governed through the separate Meet Your Neighbor Minor Participation Standards rather than treated as an ordinary adult conversation.
Families May Remember the Same Experience Differently
Two people can live through the same family experience and remember it differently.
A Neighbor may sincerely describe what an event meant to them without claiming to provide the only possible account.
Where appropriate, language may help preserve this distinction:
“This is how I experienced it.”
“This is what I remember.”
“At the time, I understood it this way.”
This does not make the experience less meaningful.
It helps distinguish personal testimony from a declaration that every other person's memory or interpretation must be false.
Former Relationships Require Particular Care
Stories involving former:
- Spouses.
- Partners.
- Friends.
- Employers.
- Business associates.
- Churches.
- Organizations.
- Or other relationships
may involve unresolved conflict.
Meet Your Neighbor should not casually become a vehicle for retaliation, humiliation, or public score-settling.
When a conversation begins moving in that direction, an important editorial question is:
Are we hearing someone's story—or being recruited into their conflict?
The existence of conflict does not mean the story cannot be told.
It means the story may require greater attention to fairness, relevance, verification, context, privacy, and potential harm.
Serious Allegations Require Stronger Editorial Care
A Neighbor may sometimes describe serious misconduct by another person or organization.
Kingdom Keys should distinguish among:
- Personal experience.
- Opinion.
- Suspicion.
- Allegation.
- Disputed claim.
- Documented event.
- Official finding.
- Established public fact.
Those categories should not be blurred.
Depending upon the seriousness of the claim, appropriate steps may include:
- Seeking clarification.
- Reviewing supporting materials.
- Verifying public records or other reliable information.
- Preserving appropriate qualifiers.
- Reducing unnecessary identification.
- Seeking additional editorial review.
- Seeking legal review where appropriate.
- Omitting material that cannot be responsibly presented.
A compelling allegation should not become a shortcut around responsible editorial judgment.
Meet Your Neighbor Is Not a Courtroom
Meet Your Neighbor may sometimes encounter stories involving:
- Family disputes.
- Employment conflicts.
- Church conflicts.
- Business disagreements.
- Legal disputes.
- Community controversies.
Kingdom Keys does not need to become the final tribunal deciding every disputed event.
It may sometimes be appropriate to present a person's experience honestly while making clear that:
- The account reflects that person's perspective.
- Other perspectives may exist.
- Certain claims remain disputed.
- Kingdom Keys is not independently establishing every contested fact.
Transparency about what is known and what remains disputed can preserve both truth and dignity.
Professional Confidentiality Must Be Respected
Some Neighbors may work in professions that carry confidentiality or privacy responsibilities.
Examples may include:
- Healthcare.
- Counseling.
- Legal services.
- Education.
- Ministry.
- Financial services.
- Government.
- Human resources.
- Social services.
A Neighbor should not be encouraged to disclose information they are legally, ethically, professionally, or contractually required to keep confidential.
A compelling story does not make someone else's confidential information ours to publish.
Workplace Information May Affect Other People
A Neighbor may discuss their work and professional experiences.
But workplace stories may involve:
- Coworkers.
- Clients.
- Students.
- Patients.
- Customers.
- Confidential projects.
- Internal documents.
- Private employment records.
- Trade secrets.
- Restricted locations.
Kingdom Keys should remain attentive to whether the Neighbor has authority to disclose the information being presented.
Private Communications Often Involve More Than One Person
A text message, email, private letter, direct message, or recorded voicemail may belong to the Neighbor's experience while still containing another person's words and personal information.
Before reproducing private communications publicly, Kingdom Keys should consider:
- Why the communication matters.
- Whether the full communication is necessary.
- Whether the sender is identifiable.
- Whether sensitive third-party information appears.
- Whether rights or legal concerns exist.
- Whether summarizing or paraphrasing would preserve the relevant meaning with less exposure.
The ability to display a private message is not the same as an obligation to display it.
Incidental People May Appear in Recordings
On-location and public-space recordings may capture people who are not part of the planned conversation.
This may include:
- Customers.
- Employees.
- Family members.
- Children.
- Pedestrians.
- Neighbors.
- Event attendees.
- Other people present in the environment.
Appropriate treatment will depend upon the circumstances, the location, applicable law, identifiability, prominence, and intended use.
Possible responses may include:
- Obtaining permission where appropriate.
- Reframing the shot.
- Cropping.
- Blurring.
- Removing audio.
- Using another camera angle.
- Excluding the segment.
Incidental Visibility Should Not Become Automatic Identification
Future technology may make it easy to identify people appearing briefly in a recording.
Facial recognition.
Voice matching.
Location matching.
Social-profile matching.
Or other technologies may infer identity even when the person was never part of the Meet Your Neighbor process.
Being visible to the camera is not the same as volunteering to become known by the system.
Kingdom Keys should not silently use facial recognition or similar identification technology to identify incidental people merely because the technology makes it possible.
Intelligence Should Not Build Hidden Third-Party Profiles
Artificial Intelligence may encounter names and references to people who are not Meet Your Neighbor participants.
It should not automatically create full internal profiles about each person mentioned in a story.
A reference such as:
“My sister helped me through that season.”
should not automatically trigger:
- Identity discovery.
- Social-media research.
- Employment discovery.
- Relationship mapping.
- Background research.
- Persistent third-party profiling.
Intelligence should process only what is reasonably necessary for the approved purpose.
Third-Party Research Requires Purpose
There may be circumstances where researching another person becomes necessary.
For example:
- Verifying a serious factual claim.
- Confirming whether information is already public.
- Evaluating a legal or rights concern.
- Understanding a published public event.
- Reviewing a safety issue.
Even then, the research should remain proportional to the actual need.
The existence of one relevant question should not become permission for unlimited investigation into another person's life.
Anonymizing or Generalizing May Preserve the Story
Sometimes privacy can be protected without weakening the truth of the story.
Kingdom Keys may sometimes:
- Remove a surname.
- Use a relationship description rather than a name.
- Generalize a location.
- Remove an unnecessary employer name.
- Blur a photograph.
- Remove identifying details.
- Use a summary rather than reproduce private correspondence.
These choices should remain truthful.
Privacy protection should not become deceptive rewriting. It should reduce unnecessary exposure while preserving the meaning of the story.
Additional Permission May Sometimes Be Appropriate
There may be situations where another person's:
- Image.
- Voice.
- Creative work.
- Private communication.
- Personal story.
- Property.
- Or other protected interest
is important enough to the production that Kingdom Keys should obtain additional permission or release.
When that occurs, the additional permission should be recorded appropriately.
Permission should travel with the relevant asset or use rather than remain as an undocumented assumption.
Permission Does Not Eliminate Editorial Judgment
Even if a third party gives permission to be identified, shown, or quoted, Kingdom Keys should still consider:
- Relevance.
- Context.
- Accuracy.
- Dignity.
- Safety.
- Potential exploitation.
- The effect on children or vulnerable people.
Consent may make a use possible. It does not make every possible use wise.
Third Parties May Raise Concerns After Publication
Someone who appears in or is discussed within a published Meet Your Neighbor story may later contact Kingdom Keys with a concern.
They may believe:
- Information is inaccurate.
- Private information was disclosed.
- A photograph or communication was used without appropriate permission.
- A safety issue exists.
- Context is missing.
- They were unnecessarily identified.
Kingdom Keys should provide a reasonable pathway for such concerns to be reviewed.
Receiving a complaint does not automatically mean the material must be removed. It means the concern deserves appropriate review under the applicable standards.
Restrictions Should Follow Related Assets
If Kingdom Keys determines that a third-party name, image, statement, or other detail should be restricted, that decision should not apply only to the original long-form conversation.
The restriction may also need to reach:
- Clips.
- Shorts.
- Reels.
- Promotional trailers.
- Transcripts.
- Quotes.
- Neighbor Profiles.
- Search results.
- Newsletters.
- Social posts.
- Compilation productions.
Privacy protection should follow the information across the production ecosystem.
A Mention Should Not Automatically Create a Digital Identity
As Kingdom Keys develops advanced search, archive Intelligence, relationship mapping, and recommendation systems, care should be taken with people who were merely mentioned in someone else's story.
A third party who never participated should not automatically receive:
- A public profile.
- A searchable identity page.
- A relationship graph.
- An automatically generated biography.
- A collection of every conversation in which their name appears.
Advanced discovery should not quietly turn incidental mention into involuntary participation.
Privacy Should Not Erase Honest Storytelling
Responsible privacy does not mean removing every other person from every story.
Human lives are relational.
Families matter.
Communities matter.
Relationships matter.
Conflict sometimes matters.
The goal is not to make every story vague and anonymous.
The goal is to tell the story honestly without creating unnecessary exposure for people who did not choose to participate.
Before identifying or exposing a third party, we should consider:
Does the audience need this detail to understand the story?
Is the information accurate enough to publish responsibly?
Is the person already legitimately public in this context?
Could we preserve the meaning with less identification?
Does the information involve a child or vulnerable person?
Could publication create unnecessary privacy or safety consequences?
Would additional permission or review be appropriate?
A Neighbor should be free to tell the truth about their own journey.
Kingdom Keys should help steward that truth in a way that remembers the other human beings who may be standing just outside the frame.
A Neighbor has the right to tell their story. Our responsibility is to help them tell it without unnecessarily taking ownership of someone else's privacy.
10. Neighbor Choices, Privacy Requests & Control Over Personal Information
Privacy stewardship should not be something Kingdom Keys does around the Neighbor while leaving the Neighbor without a meaningful voice.
A person should be able to ask questions about the information Kingdom Keys holds about them.
They should have reasonable ways to correct inaccurate information.
They should be able to communicate preferences and boundaries.
And where appropriate, they should be able to request changes to how their information is used, displayed, retained, or shared.
Responsible stewardship should leave room for the person whose information is being stewarded.
Privacy Requests Should Have a Clear Human Pathway
A Neighbor should not need to understand the internal architecture of Kingdom Keys in order to raise a privacy concern.
Meet Your Neighbor should provide a reasonable way for someone to ask:
- What information do you have about me?
- Why do you have it?
- Is this information public or private?
- Can something be corrected?
- Can a contact preference be changed?
- Can a public profile detail be updated?
- Can something be restricted from future use?
- Can information be deleted?
- Who can I contact if I believe something has been mishandled?
The request should reach an appropriate human steward rather than disappear into an automated system with no accountable owner.
Identity May Need to Be Verified Before a Request Is Fulfilled
Protecting privacy sometimes requires confirming that the person making a request is actually the person entitled to make it.
Otherwise, someone could misuse a privacy request to gain access to another person's private information.
Verification should be proportionate to the sensitivity of the request.
For example:
Correcting a spelling error in a public Neighbor Profile may require less verification than requesting a copy of restricted consent records or private preparation information.
Kingdom Keys should avoid collecting excessive identification simply to verify a request when a less intrusive method would reasonably work.
Neighbors May Request Correction of Inaccurate Information
Information changes.
Names may be misspelled.
Titles may change.
A business may move.
A website may change.
A record may contain an error.
A Neighbor should be able to bring a meaningful factual correction to Kingdom Keys.
Appropriate corrections should be made in the relevant records and, where needed, propagated to connected systems and published materials.
Correction Is Not the Same as Rewriting History
A request to correct inaccurate information is different from a request to rewrite a historical event because someone's perspective has changed.
A person may later describe an old experience differently.
They may change professions.
They may change their beliefs.
They may want current context added.
Kingdom Keys may sometimes respond through:
- A correction.
- An update.
- A clarification.
- A date marker.
- Additional context.
- A current-profile link.
The appropriate response should preserve both accuracy and historical integrity.
Public Profile Choices Should Be Distinct From Internal Records
A Neighbor may authorize some information for their public Profile while other information remains private.
Public profile choices may include:
- Preferred public name.
- Photograph.
- Short biography.
- Profession or role.
- Business or organization information.
- Website.
- Approved social links.
- Public contact pathway.
Changing or removing a public Profile field should not automatically delete unrelated internal records required for consent, rights, governance, legal, or operational purposes.
Public presentation and internal stewardship should remain distinct.
Communication Preferences Should Be Respected
A Neighbor may have preferences about how Kingdom Keys contacts them.
Where reasonably possible, the record may identify preferences such as:
- Email preferred.
- Telephone preferred.
- Text preferred.
- Do not text.
- Do not call.
- Contact through representative.
- Contact only regarding the current production.
- Do not send promotional communication.
The existence of a private email address or telephone number does not create unlimited permission to use it for every Kingdom Keys communication.
Participation Does Not Automatically Mean Newsletter Enrollment
A person who participates in Meet Your Neighbor should not automatically be subscribed to unrelated promotional or newsletter communications simply because Kingdom Keys has their contact information.
If the Neighbor independently chooses to subscribe to another Kingdom Keys communication, that relationship may be governed through the applicable system.
Participation consent and marketing consent should remain distinct.
A Neighbor May Ask Kingdom Keys to Stop Certain Future Uses
A Neighbor may later become uncomfortable with a particular future use of their information or content.
Depending upon the existing consent, rights, publication history, applicable law, and circumstances, Kingdom Keys may consider requests such as:
- Do not use this photograph in future promotions.
- Do not display this public contact link anymore.
- Do not include this segment in future compilations.
- Do not use this quote in new promotional assets.
- Restrict this information from future public Profile use.
- Do not contact me about future Meet Your Neighbor opportunities.
A request for future restriction should be reviewed thoughtfully and, where approved, should travel to related assets and systems.
Future Restrictions May Not Automatically Undo Past Authorized Uses
A request to limit future use does not necessarily mean every prior authorized publication can be erased.
Content may already have been:
- Published.
- Distributed.
- Shared by others.
- Archived.
- Indexed.
- Included in a completed production.
Kingdom Keys should therefore distinguish between:
Stopping a new future use
Restricting Kingdom Keys-controlled content
Removing content from Kingdom Keys-controlled channels
Attempting to erase copies already distributed beyond Kingdom Keys control
These are not always the same practical or legal action.
Deletion Requests Should Be Considered Honestly
A Neighbor may ask Kingdom Keys to delete information about them.
Some information may be appropriate to delete.
Other information may need to remain because it supports:
- A signed consent record.
- A rights or permission record.
- A completed publication.
- A legal obligation.
- A financial or administrative record where applicable.
- A security or incident record.
- A correction history.
- A Do Not Contact request.
- A legitimate archival responsibility.
Kingdom Keys should not promise deletion where continued retention remains legitimately necessary.
Where only part of a record must remain, unnecessary information may sometimes be removed while the essential governance record is retained.
Deletion From Kingdom Keys Does Not Mean Erasure From the Internet
Once information has been publicly distributed, Kingdom Keys may not be able to retrieve every copy.
Third parties may have:
- Downloaded it.
- Reposted it.
- Quoted it.
- Screen-recorded it.
- Indexed it.
- Archived it.
Kingdom Keys can responsibly address the systems and channels it controls.
It should not falsely promise that a public story can always be completely erased from every external system.
Requests May Involve Restriction Rather Than Deletion
Sometimes the most responsible response is not complete deletion.
Information may instead be:
- Removed from public access.
- Removed from search.
- Restricted from future distribution.
- Archived internally.
- Marked Do Not Publish.
- Removed from promotional use.
- Limited to governance or legal access.
Restriction may preserve necessary accountability while preventing unnecessary continued exposure.
Off-Record & Do-Not-Publish Boundaries Should Remain Actionable
If a valid boundary has been established, the Neighbor should not have to rely solely upon someone remembering it.
Appropriate systems should preserve restrictions so that they can affect:
- Editing.
- Search.
- Clip generation.
- Profile creation.
- Promotional use.
- Distribution.
- Future reuse.
- AI-assisted discovery.
A privacy choice is stronger when the architecture itself helps honor it.
Requests From Authorized Representatives May Require Verification
A Neighbor may sometimes ask another person to act on their behalf.
Depending upon the request, Kingdom Keys may need to verify:
- The identity of the Neighbor.
- The identity of the representative.
- The representative's authority.
- The scope of the request.
Representation should not become a shortcut for someone else to obtain information the Neighbor did not authorize them to receive.
Privacy Requests Should Not Create Retaliation
A Neighbor should be able to ask a reasonable privacy question without being treated as difficult, disloyal, ungrateful, or unsafe.
A person may:
- Ask what information is being retained.
- Question a use.
- Request a correction.
- Ask for a restriction.
- Decline additional publication.
- Change a contact preference.
Those actions should not automatically harm their relationship with Kingdom Keys.
A privacy question is not an act of hostility.
Requests Should Be Tracked to Completion
Significant privacy requests should not depend entirely upon memory or informal conversation.
An internal request record may identify:
- Who made the request.
- Date received.
- Request type.
- Identity-verification status where needed.
- Systems or assets affected.
- Assigned steward.
- Decision.
- Actions taken.
- Date completed.
- Any continuing restrictions.
This helps prevent a request from being acknowledged politely but never actually carried through the connected systems.
Connected Systems Should Receive Approved Changes
A privacy change may affect more than one location.
A public name correction may need to reach:
- The Neighbor Profile.
- The archive.
- Search results.
- Video descriptions.
- Distribution metadata.
A future-use restriction may need to reach:
- The Production Library.
- The Rights & Asset Ledger.
- The Distribution Center.
- Editorial Intelligence.
- Promotional workflows.
Privacy stewardship should follow the information through the ecosystem rather than stop at the first screen where the request was entered.
Artificial Intelligence May Assist With Request Fulfillment
Intelligence may eventually help identify where information appears across Kingdom Keys systems.
It may assist with:
- Locating related assets.
- Finding duplicate records.
- Identifying downstream uses.
- Checking whether a restriction propagated.
- Surfacing outdated public information.
- Preparing a request summary for human review.
But Artificial Intelligence should not silently decide that a person has no privacy rights, deny a significant request, or permanently delete governed records without authorized human review.
Intelligence may help us find the information. Human stewardship should determine what happens to it.
Requests May Need Different Outcomes
A responsible response is not always simply yes or no.
Possible outcomes may include:
- Request approved.
- Request partially approved.
- Information corrected.
- Public information updated.
- Future use restricted.
- Content removed from Kingdom Keys-controlled channels.
- Information deleted from active systems.
- Record retained but restricted.
- Additional information requested.
- Request referred for legal or specialized review.
- Request declined with an appropriate reason.
Where a request cannot be fully granted, Kingdom Keys should communicate the reason as clearly as reasonably appropriate rather than simply ignoring the request.
Control Has Limits, But the Neighbor Still Deserves a Voice
Participation in public media necessarily involves some loss of control once information is lawfully and intentionally published.
Kingdom Keys cannot truthfully promise that a Neighbor will control:
- Every audience reaction.
- Every external repost.
- Every search-engine result.
- Every lawful reference by another person.
- Every copy created outside Kingdom Keys-controlled systems.
But the existence of those limits does not mean the Neighbor should have no continuing voice at all.
Kingdom Keys can still steward the information, assets, profiles, communications, and publication systems it controls.
Privacy Choice Should Return to Relationship
A Neighbor is not merely a person who signed a release.
They are someone who trusted Kingdom Keys with part of their story.
That relationship deserves enough flexibility for questions, corrections, changed circumstances, and reasonable boundaries to be heard.
Before responding to a privacy request, we should be able to ask:
What is the person actually asking us to change?
What information or asset is affected?
What rights, consent, legal, archival, safety, or governance responsibilities remain?
Can we honor the concern fully?
If not, can we honor part of it?
What systems need to receive the decision?
How do we communicate the result respectfully and clearly?
Privacy does not require that the Neighbor control everything.
It does require that we remember there is still a person with a voice on the other side of the record.
11. Privacy & Safety Review Before Publication
A conversation may be recorded successfully and still not be ready for publication.
Consent may be signed.
The edit may be complete.
The story may be compelling.
And important privacy, safety, rights, or governance questions may still remain.
Publication therefore requires a final moment of stewardship in which Kingdom Keys asks not only whether the production is finished—but whether the people and information within it have been responsibly prepared for public exposure.
Consent may authorize publication. Review determines whether publication is ready.
Privacy & Safety Review Is a Publication Gate
Privacy and safety review should not be treated as an optional final glance.
It should become part of the publication-readiness process.
A production that contains unresolved privacy or safety concerns should not automatically continue toward distribution simply because the production schedule says it is complete.
Where appropriate, the system should be capable of placing a publication hold until the concern is reviewed.
Consent Verified Is Not the Same as Privacy Cleared
A signed Guest Media Consent & Appearance Release establishes important permission.
It does not automatically answer every privacy question that may arise during the actual conversation.
A Neighbor may reveal:
- A private address.
- A child's identifying information.
- A third party's private information.
- A confidential document.
- A sensitive health or family detail.
- A private telephone number.
- An off-record statement.
- A detail that creates an unexpected safety concern.
The existence of general recording permission does not eliminate the need to evaluate whether those particular details should be published.
Permission creates authority. Stewardship governs how that authority is exercised.
Review Should Cover the Whole Production
Privacy and safety review should look beyond the spoken words.
Depending upon the production, review may include:
- Video.
- Audio.
- Transcript.
- Captions.
- On-screen text.
- Photographs.
- Thumbnails.
- Neighbor Profile.
- Business or organization information.
- External links.
- Metadata.
- Descriptions.
- Quotes.
- Clips.
- Promotional assets.
A private detail removed from the long-form conversation may still remain in a transcript, clip, caption, image, description, or promotional asset if connected systems are not reviewed together.
Public Information Should Be Confirmed as Public
Before information is placed into a public Neighbor Profile or publication package, Kingdom Keys should confirm that the field is appropriate for public use.
This may include:
- Preferred public name.
- Approved biography.
- Photograph.
- Profession or role.
- Business or organization name.
- Website.
- Approved social links.
- Approved public contact pathway.
Internal operational information should not become public merely because it exists in the same Neighbor record.
Restricted Information Should Be Accounted For
Before publication, the production should be checked for active restrictions such as:
- DO NOT PUBLISH.
- OFF RECORD.
- HOST PREPARATION ONLY.
- ADMINISTRATIVE ACCESS ONLY.
- GOVERNANCE REVIEW ONLY.
- LEGAL REVIEW.
- SAFETY RESTRICTED.
- MINOR — RESTRICTED.
- DO NOT SHARE EXTERNALLY.
- ADDITIONAL CONSENT REQUIRED.
These restrictions should affect not only the main conversation but also related:
- Clips.
- Quotes.
- Profiles.
- Search results.
- Transcripts.
- Promotional assets.
- Compilation uses.
A restriction is not fully honored if it protects one format while the same information escapes through another.
Off-Record Material Requires Explicit Confirmation
Off-record boundaries deserve a specific pre-publication check.
Review should confirm that off-record material has not entered:
- The final edit.
- Clips.
- Shorts or reels.
- Quotations.
- Captions.
- Search indexes.
- Neighbor Profiles.
- Promotional copy.
- AI-generated summaries.
If the status of a segment is uncertain, publication should pause long enough to clarify the boundary rather than assume permission.
Third-Party Privacy Should Be Reviewed
The publication should be reviewed for information about people who did not choose to participate.
Particular attention may be needed when the story includes:
- Children.
- Family members.
- Former partners.
- Coworkers.
- Clients.
- Patients.
- Students.
- Private individuals named in a conflict.
- People appearing incidentally in video or photographs.
Review should consider whether identification is necessary, appropriate, supported, and proportionate.
An honest story should not create unnecessary exposure simply because another person happens to appear within it.
Minor-Related Information Requires Elevated Attention
Any production involving identifiable children should receive stronger privacy and safety review.
Review may consider:
- Whether the child is actually participating.
- Whether specialized consent is required.
- Whether identifying information is necessary.
- Whether location or school information appears.
- Whether sensitive personal information is disclosed.
- Whether the child can reasonably understand the exposure.
- Whether the content may create future safety or dignity concerns.
Where a minor is actually participating, the separate Minor Participation Standards should govern the additional requirements.
Sensitive Information Should Be Reviewed in Context
Sensitive information should not automatically be removed merely because it is sensitive.
Some deeply personal information may be central to the Neighbor's story and intentionally shared.
The review should therefore ask:
Was this intentionally shared for publication?
Is the Neighbor clearly speaking about their own experience?
Does the disclosure unnecessarily expose another person?
Could publication create a foreseeable safety concern?
Is additional consent or clarification appropriate?
Would editing preserve the meaning while reducing unnecessary exposure?
The goal is thoughtful stewardship—not automatic censorship of vulnerability.
Serious Allegations May Require Additional Review
If a conversation contains a serious allegation about another person or organization, privacy review may overlap with editorial, legal, and integrity review.
Depending upon the circumstances, Kingdom Keys may need to consider:
- Whether the person or organization is identifiable.
- Whether the statement is opinion, experience, allegation, or established fact.
- Whether additional verification is appropriate.
- Whether the language preserves necessary qualifiers.
- Whether legal review is appropriate.
- Whether the identifying detail is necessary.
Privacy review should work together with the Editorial & Integrity Standards rather than attempt to resolve every contested claim by itself.
Visual & Audio Privacy Should Be Checked
Before publication, reviewers should consider details captured unintentionally by the production environment.
Examples may include:
- Addresses.
- License plates.
- Mail.
- Computer screens.
- School names.
- Calendars.
- Private photographs.
- Medication labels.
- Security devices.
- Private voices in the background.
- Telephone numbers spoken aloud.
- Notifications appearing on screen.
Appropriate responses may include:
- Cropping.
- Blurring.
- Muting.
- Replacing a shot.
- Removing a segment.
- Generalizing a location.
A detail does not need to be central to the story to create a privacy or safety consequence.
Location & Routine Information Deserves a Safety Check
The final production should be reviewed for information that may reveal where a person lives, works, studies, travels, or can routinely be found.
A single detail may appear harmless.
Several details together may create a much clearer picture.
Review should consider:
- Exact residential location.
- Children's schools.
- Daily routines.
- Regular travel patterns.
- Private entrances.
- Vehicle information.
- Security arrangements.
- Upcoming travel plans.
Public specificity should remain proportionate to the actual storytelling need.
Guest-Provided Materials Should Be Rights & Privacy Cleared
Photographs, letters, screenshots, videos, audio, documents, artwork, and other materials supplied by a Neighbor may contain additional privacy or rights issues.
Review should confirm:
- The intended use.
- Whether the Neighbor has authority to provide the material.
- Whether third parties appear.
- Whether confidential information is visible.
- Whether permission or a license is required.
- Whether any restriction applies.
The Rights & Asset Ledger should eventually help preserve these decisions alongside the asset itself.
External Links Should Be Checked Before Publication
A Neighbor Profile may include approved links to:
- A business.
- Organization.
- Ministry.
- Website.
- Social profile.
- Public project.
Before publication, the link should be checked to confirm that it:
- Matches the intended destination.
- Appears appropriate for the stated purpose.
- Does not expose private contact information unintentionally.
- Does not conflict with an established restriction.
The separate Business, External Links & Commercial Reference Standards should govern the broader relationship between guest information, links, commercial references, and Kingdom Keys editorial independence.
Metadata Should Not Be Ignored
Information may be embedded in files even when it is not visible in the finished production.
Depending upon the file and workflow, metadata may reveal:
- Location.
- Device information.
- Creator names.
- Dates.
- Internal file paths.
- Other production details.
Publication workflows should consider whether unnecessary sensitive metadata should be removed from public-facing files.
Derived Assets Need Their Own Review
A long-form conversation may be appropriately cleared while a short clip creates a different privacy or safety issue.
Context may disappear.
A name may become more prominent.
A sensitive statement may become the entire clip.
A thumbnail may reveal a private detail that was barely visible in the video.
Therefore:
- Shorts.
- Reels.
- Trailers.
- Quotes.
- Images.
- Social posts.
- Compilation segments.
should inherit the relevant restrictions and receive appropriate review for their own context.
Artificial Intelligence May Assist With Pre-Publication Review
Intelligence may help detect information that human reviewers could overlook.
It may assist by flagging:
- Addresses.
- Telephone numbers.
- Email addresses.
- Minor-related information.
- Third-party names.
- Off-record segments.
- Restricted assets.
- Potentially sensitive documents visible on screen.
- Possible rights concerns.
- Safety-related location information.
- Previously established governance flags.
These flags should explain:
- What was noticed.
- Where it appears.
- Why it may require review.
- What standard or restriction may apply.
Intelligence should assist the review process—not silently decide the final outcome.
Artificial Intelligence Should Not Clear Its Own Work
If Artificial Intelligence helped create:
- A clip.
- A quote.
- A summary.
- A title.
- A Neighbor Profile.
- A translation.
- A promotional asset.
the system should not treat the fact that AI created it as evidence that the material is automatically privacy-safe or publication-ready.
AI-generated or AI-assisted material should remain subject to the same relevant human review as other production assets.
Uncertainty Should Trigger Review, Not Assumption
If reviewers cannot determine whether a particular detail is:
- Public.
- Private.
- Restricted.
- Authorized.
- Off record.
- Safe to publish.
the appropriate response may be to:
- Clarify with the Neighbor.
- Check the applicable record.
- Review the original preparation or consent context.
- Request additional consent.
- Seek governance or legal review.
- Restrict the information temporarily.
- Leave the material out.
Uncertainty is a reason to clarify—not a reason to expose.
Publication Holds Should Be Real
When an unresolved concern reaches a meaningful level, the system should be capable of stopping publication.
A possible status may be:
PUBLICATION HOLD — PRIVACY / SAFETY REVIEW REQUIRED
A hold should prevent:
- Final public release.
- Automated distribution.
- Scheduled social publication.
- Promotional clip release.
- Public Profile activation where the concern affects the Profile.
A hold is not an accusation.
It is a temporary governance state requiring authorized human review before progression.
Human Review Determines the Outcome
After review, authorized human stewards may determine that the appropriate outcome is to:
- Approve as presented.
- Approve with modification.
- Remove or redact information.
- Generalize identifying details.
- Request clarification from the Neighbor.
- Obtain additional consent.
- Seek legal or specialized review.
- Restrict a particular asset or segment.
- Delay publication.
- Decline publication.
Artificial Intelligence may help surface the question. Human stewardship remains responsible for the decision.
The Decision Should Be Documented
Meaningful privacy or safety review decisions should be recorded so that connected workflows understand what was decided.
The record may include:
- The issue reviewed.
- The affected asset or timestamp.
- The applicable standard.
- The decision.
- Any modification made.
- Additional permission obtained.
- Continuing restrictions.
- The authorized reviewer.
- Date of decision.
This prevents a resolved issue from becoming an undocumented memory that later systems cannot understand.
Privacy & Safety Should Join the Larger Publication Readiness Gate
Privacy and safety review should not operate in isolation from the other publication responsibilities of Meet Your Neighbor.
A mature publication-readiness gate may eventually confirm:
- Consent Verified ✓
- Guest Materials Cleared ✓
- Rights & Assets Cleared ✓
- Privacy Review ✓
- Safety Review ✓
- Restricted Segments Resolved ✓
- Third-Party Concerns Resolved ✓
- Governance Review ✓
- Editorial Review ✓
- External Links Checked ✓
- Neighbor Profile Ready ✓
- Final Human Approval ✓
Only when the applicable requirements are satisfied should the production move to:
READY TO PUBLISH
Readiness Should Mean More Than Technical Completion
A video may be rendered.
A thumbnail may be finished.
A caption file may be complete.
A publication date may be scheduled.
None of those facts alone mean the story is ready to leave Kingdom Keys.
Before publication, we should be able to ask:
Have we honored the Neighbor's boundaries?
Have we protected information that was not meant for the audience?
Have we considered the people who did not choose the camera?
Have we addressed identifiable safety concerns?
Have we confirmed the permissions and restrictions connected to the assets?
Have unresolved concerns been reviewed by the appropriate human steward?
Are we prepared to stand responsibly behind the decision to publish?
If the answer to an important question is still no, the production may be finished—but the stewardship is not.
READY TO PUBLISH should mean more than ready to distribute.
It should mean ready to steward what happens when the story becomes public.
12. Our Privacy & Safety Promise
Meet Your Neighbor exists because people choose to let us see something real.
A story.
A memory.
A struggle.
A hope.
A season of becoming.
That willingness deserves more than technical compliance.
Privacy is not merely about protecting data. It is about protecting the dignity, boundaries, and trust of the person behind it.
We Will Remember That Public Storytelling Has Private Foundations
A public conversation may rest upon many private elements.
Preparation.
Scheduling.
Consent.
Boundaries.
Private communication.
Internal notes.
Safety considerations.
Rights records.
Governance decisions.
The existence of those private foundations should never be forgotten simply because the finished story becomes public.
We Will Not Confuse Visibility With Permission
Something may be visible.
Searchable.
Technically accessible.
Publicly posted somewhere else.
Or discoverable by Artificial Intelligence.
None of those facts automatically answer the deeper question:
Should Kingdom Keys use it here, for this purpose, in this way?
Capability is not permission.
We Will Respect the Difference Between Public, Private & Restricted
Kingdom Keys should not treat every piece of information as though it belongs in one large pool.
Public information should remain public because it was appropriately cleared for that purpose.
Operational information should remain connected to operational responsibilities.
Preparation information should remain preparation information unless another use is appropriately authorized.
Sensitive information should receive greater care.
Restricted information should remain restricted.
Off-record information should remain off record.
A boundary should remain a boundary even when the information changes format, moves between systems, or becomes easier to process.
We Will Collect With Purpose
Kingdom Keys should not attempt to know everything that can be known about a Neighbor.
We should collect what helps us responsibly:
- Invite.
- Prepare.
- Communicate.
- Schedule.
- Record.
- Protect.
- Edit.
- Publish.
- Follow up.
- Honor rights and boundaries.
We should not build unnecessary dossiers simply because modern technology can gather more.
We Will Limit Access According to Responsibility
Not everyone involved in Meet Your Neighbor needs to know everything about a Neighbor.
A host may need preparation information.
A Guest Coordinator may need scheduling and consent information.
A production team may need recording and location information.
A governance reviewer may need access to a restricted issue.
None of that means every role should see the entire record.
Access is not ownership. Access is responsibility.
We Will Carry Boundaries Across the Kingdom Keys Campus
Kingdom Keys is becoming an interconnected ecosystem.
Meet Your Neighbor may connect with production, communications, publishing, distribution, television, radio, archive, and other Campus systems.
Those connections should make stewardship stronger—not dissolve the boundaries established at the source.
Information should carry its permissions, restrictions, classifications, and governance status wherever it appropriately travels.
Connected systems still need boundaries.
We Will Remember the People Outside the Frame
A Neighbor's story may involve people who never signed a release.
Family.
Children.
Friends.
Coworkers.
Former partners.
People passing through the background of a camera.
Responsible storytelling should allow the Neighbor to tell their own truth without treating every connected person as though they also volunteered for public exposure.
One person's consent does not become another person's consent.
We Will Give Children Greater Protection
Children should not be treated as smaller adults when privacy and public exposure are involved.
Information involving minors deserves greater care because today's publication may remain searchable long after the child becomes an adult.
When minors actually participate in Meet Your Neighbor, specialized safeguards should govern their participation.
When children are merely part of an adult's story, we should still ask whether their identity or private information truly needs to become part of the public record.
A child should not inherit unnecessary public exposure simply because an adult was willing to tell the story.
We Will Take Safety Seriously Without Turning Difference Into Danger
Safety concerns should be heard.
Concrete risks should be reviewed.
Production should pause when necessary.
People should not be asked to ignore real threats for the sake of content.
But fear must not become a hidden standard by which unfamiliar people are treated as dangerous.
Religion, culture, worldview, neighborhood, appearance, profession, disagreement, or difference should not be transformed into unsupported safety judgments.
Difference is not evidence of danger.
We Will Protect People Before Protecting the Schedule
A production date can change.
A location can change.
An edit can change.
A release date can change.
A person cannot always undo the consequences of unnecessary exposure or preventable harm.
Kingdom Keys should therefore remain willing to pause, change, restrict, delay, or decline a production decision when responsible safety stewardship requires it.
No story is worth preventable harm.
We Will Respond When Something Goes Wrong
Good stewardship is not proven by pretending incidents can never happen.
It is also revealed by what we do when they do.
Kingdom Keys should:
- Contain meaningful incidents.
- Understand what happened.
- Protect affected people.
- Notify appropriately.
- Correct what can be corrected.
- Strengthen the system afterward.
We should not hide a meaningful privacy or security failure merely because acknowledging it is uncomfortable.
We Will Not Promise What Technology Cannot Guarantee
Kingdom Keys should use reasonable safeguards and continue improving them.
But we should not promise absolute security.
We should not promise that every public copy can always be erased from the internet.
We should not claim that a deleted record disappears instantly from every backup, cache, or service.
Responsible trust is built through truthful commitments rather than impossible guarantees.
We Will Give the Neighbor a Continuing Voice
Publication does not mean every future question becomes irrelevant.
A Neighbor may discover an error.
A public Profile may need updating.
A contact preference may change.
A new safety concern may arise.
A person may ask Kingdom Keys to review a future use.
Not every request can necessarily be granted exactly as asked, but every meaningful request deserves responsible consideration.
Privacy stewardship should leave room for the person whose information is being stewarded.
We Will Use Intelligence as a Stewardship Tool—Not a Hidden Authority
Artificial Intelligence may eventually help Kingdom Keys identify privacy concerns that humans could miss.
It may help find:
- Private contact information.
- Addresses.
- Minor-related information.
- Off-record material.
- Rights issues.
- Restricted assets.
- Downstream uses.
- Possible safety concerns.
It may help preserve boundaries across systems.
It may help us remember what human beings are capable of overlooking.
But Intelligence should not quietly become the final authority over:
- Whether a person is dangerous.
- Whether a privacy request deserves to be heard.
- Whether a restricted story should be published.
- Whether someone deserves access.
- Whether significant governed information should be permanently deleted.
Intelligence identifies risk. Humans exercise authority.
We Will Remember That Data Can Become a Person Again
Inside a system, a Neighbor may appear as:
- A Guest ID.
- A consent record.
- A transcript.
- A profile.
- A media asset.
- A workflow status.
- A search result.
- A governance flag.
Those structures help Kingdom Keys operate responsibly.
But none of them should make us forget what they represent.
The Guest ID can become a person answering the door.
The transcript can become someone's voice.
The safety restriction can become a family trying to feel secure.
The privacy request can become someone asking us to hear them.
Good architecture should help us steward the person more faithfully—not make the person disappear behind the architecture.
Before We Publish, We Will Remember Why the Trust Matters
Someone allowed us to hear their story.
They may have told us things they do not normally tell strangers.
They may have invited us into their home.
They may have introduced us to their family.
They may have spoken about a painful season.
They may simply have allowed us to sit across from them long enough to discover that the label we began with was incomplete.
That trust should remain visible in how we collect, protect, edit, publish, archive, and respond.
The Neighbor is a person before they are a production record.
Beyond the Labels. Meet the Person.
Privacy helps us honor what should remain unseen.
Safety helps us protect what should not be harmed.
Integrity helps us determine what should be shared.
And relationship reminds us why any of it matters.
Because we are not asking everyone to become the same.
We are learning to see one another beyond what makes us different.
To do that responsibly, we must learn not only how to see—
but also when not to expose.
Not only how to listen—
but also how to protect what was entrusted in the listening.
Not only how to publish the story—
but how to remember the person after the story leaves our hands.
We protect information because there is a person on the other side of it.
And before the record, before the archive, before the publication—we remember the person.
Questions or Concerns About These Standards?
If you have a question about these Privacy, Personal Information & Safety Standards, or a concern about how personal information or safety has been handled within Meet Your Neighbor, we invite you to contact Kingdom Keys.
We would rather receive a thoughtful question or concern than leave an important matter unaddressed.
Contact Kingdom Keys
Version 1.0 • Effective 9/7/2026 • Last Revised 9/7/2026