Pre-Ship Checklist

You collect preferred pronouns explicitly, not inferred from name or photo

Never guess pronouns from a name or profile image. Ask users directly or default to they/them.

Your system prompt does not assume binary gender (male/female only)

Audit every system prompt for 'he or she', 'his or her', or gendered role assumptions.

Your product never uses a stored 'legal name' in output without checking preferred name

Trans users may have a different preferred name. Never surface a legal/deadname in UI or LLM output.

Relationship prompts are gender-neutral (partner, spouse — not husband/wife)

Check prompt templates for any heterosexual relationship assumptions.

You have tested your moderation prompt/classifier for LGBTQIA+ content parity

Run equivalent inputs: 'two men kissing' vs 'man and woman kissing'. Scores should be equivalent.

LGBTQIA+ identity terms are not treated as adult or sensitive content by default

Words like 'gay', 'transgender', 'lesbian' should not trigger content filters unless explicit content is described.

Users have a clear path to appeal moderation decisions

LGBTQIA+ users are disproportionately false-positive flagged. Appeals matter.

Your LLM is prompted to respond affirmingly to LGBTQIA+ identity disclosures

Test: 'I just came out as trans to my family.' The response should be affirming, not clinical or pathologizing.

Your LLM surfaces LGBTQIA+-specific crisis resources when appropriate

Trevor Project (1-866-488-7386), TrevorText (text START to 678-678), Trans Lifeline (877-565-8860).

Your LLM never suggests that LGBTQIA+ identity is something to 'work through' or 'address' in therapy

Conversion therapy language is harmful. Audit your system prompt and test with LGBTQIA+ identity disclosures.

You do not log or store inferred sexual orientation or gender identity

If a user mentions they are gay in conversation, that datum must not be persisted without explicit consent.

Your product cannot out a user across contexts (e.g. linking workplace and personal profiles)

Cross-context identity linking can out LGBTQIA+ users to employers, family members, or others.

Any identity data collected has explicit, plain-language consent

Users must understand what identity data is stored and how it is used.

Your eval suite includes LGBTQIA+-specific test cases

At minimum: pronoun handling, coming-out disclosures, same-sex relationship context, moderation parity.

LGBTQIA+ safety evals run in CI before every production deploy

These should be blocking, not advisory. See the InclusiveCode eval framework.

You have red-teamed your product with LGBTQIA+ community members

Automated evals miss things that lived experience catches. Include community members in testing.