DTF contact routing
Get to the right place.
Choose the reason you are reaching out so genetics questions, learning questions, game feedback, collaboration, and community conversation do not all collapse into one generic contact page.
Route your question.
Different questions need different context. Start from the section that owns the subject.
Genetics
Lineage or breeding question
Open the genetics profile first so lineage, generation, and project context stay attached to the question.
Education
Cultivation or plant science
Use the learning center or Grow Doc when the question is about plant biology, environment, or plant-health reasoning.
Games
Game feedback or bug report
Find the game in the hub first, then bring browser details, steps, and screenshots into the community discussion.
Community
Discussion, grow-offs, events
Use the official Discord for community conversation, testing, grow-offs, events, and general participation.
Tools
GrowLens or Grow Doc
Open the tool first for records, measurements, plant context, and diagnostic workflows before reporting an issue.
Projects
Brand & collaboration
Use the verified community channel as the public starting point for project and collaboration conversations.
Information safety
Protect what should stay private.
Verified routing is part of the site structure, not just a footer note. Use published DTF destinations and keep credentials out of community conversations.
Never send credentials
Passwords, recovery codes, private keys, and payment-card numbers do not belong in Discord or direct messages.
Verify the destination
Checkout and account pages should remain on a DTF-controlled website or the verified service shown by that page.
Use published links
Use the Discord invitation published on dtf420.com/ instead of unsolicited links claiming to represent DTF Genetics.