How do you build an LGBTQ+ emergency contact network without centralising sensitive data?

A network protects better than one overloaded person

An emergency may concern health, transport, housing, violence, digital exposure or simply confirming that you arrived safely. Giving one person every key, document, location and decision creates dependency and a single point of failure.

Trans, travesti, non-binary, femboy, gay, lesbian and bi experiences are different, not synonyms. The plan must follow the person's risks and choices without assuming family, transition, orientation, legal name or disclosure level.

Define situations and roles before choosing names

List the situations where help would actually be useful: a missed check-in, a lost phone, health care, an online threat, leaving an unsafe place or temporary housing loss. Give each scenario one concrete action and a clear boundary.

Then distribute roles: a check-in contact, transport contact, local-resource contact and an out-of-routine backup. Nobody needs every detail. Confirm that each person accepts the role and can decline without guilt.

Share the minimum in layers

A basic layer may contain the name you use, a safe contact method, city or region and a simple trigger. Exact address, legal name, medication, documents, live location or family contacts go only to someone who needs them for that scenario and with specific permission.

Do not send a master file to everyone. One person can know the confirmation word, another the meeting point and another where a document is kept. If data does not change that person's action, they probably do not need it.

Create redundancy without group surveillance

Choose a primary contact, a backup and, where useful, someone outside the area. Agree who tries first, how long they wait and when the task passes on. Avoid automatic alarms based on brief silence or constant location demands.

Use clear messages such as “arrived”, “call me” or an agreed code. A code never replaces contacting regional emergency services in immediate danger; it only reduces ambiguity among people who accepted the plan.

Store the plan without creating uncontrollable copies

A small paper card works without power; a protected device copy can be updated; phone emergency settings may help but can sometimes be visible from the lock screen. Choose for your risk rather than convenience alone.

Avoid open spreadsheets, large groups, public notes and non-expiring links. Use unique passwords and two-factor authentication. Track who received each item so it can be updated or revoked, and never include someone else's secrets without consent.

Test the route and keep an exit

Run a non-emergency test: send the agreed word, verify numbers and confirm the action. Review after changes to phone, home, relationship, work, care or disclosure level. Delete old copies rather than merely making new versions.

Anyone may leave the network. Replace the role before sharing new data and revoke unnecessary access. If coercion, stalking or an outing threat appears, remove that person from the flow and rebuild with independent support.

Preserve autonomy and escalate carefully

Contacts should follow the agreement, share only what is needed and record facts without guessing identity or relationships. When safe, confirm before involving family, employers, moderators or authorities. Never post a help request with photo, name or location without permission.

For immediate danger, contact the appropriate regional emergency service. A community network complements rather than replaces medical, violence-response, legal or public services. Afterwards, review what worked without blaming the person who asked for help.

• List real scenarios and one action for each.
• Distribute roles and keep a backup.
• Give each contact only the data they need.
• Set messages, wait times and escalation criteria.
• Test without simulating real danger.
• Update, revoke and delete old copies.
• Use regional emergency help for immediate danger.