Last reviewed: 2026-05-06. This is draft launch copy for commercial review and is not legal advice.
Format-name rule
File-format and application names may be used descriptively to explain compatibility, recovery interest, or roadmap research. They should not be used in a way that implies sponsorship, endorsement, or affiliation.
Live support wording
Use “live import” only when the parser is implemented, connected, tested with sample files, and documented in the app. Current live imports are .imx, .itmz, .mmap/.mmat, .xmind, .smmx, .mm, .opml, .md/.txt and .csv, plus .bridge/.json — each tested.
Roadmap wording
Use “roadmap”, “planned recovery research”, “sample-driven development”, or “vote for this format” for .mindnode, .mind, .isf/.ins, and other formats until tested support exists.
Non-affiliation disclaimer
MindBridge is independent. References to third-party application names, product names, or file extensions are for descriptive compatibility and recovery context only. All trademarks remain property of their respective owners.
No logos or trade dress
Do not use third-party logos, icons, screenshots, or brand styling on format pages unless permission or a legally reviewed fair-use basis exists. Use neutral text and MindBridge styling.
Parser honesty checklist
Before a roadmap format moves to live: file detection, parser, node recovery, connection recovery where possible, notes/resources report, .bridge save, error handling, sample tests, and customer-facing limitations must be present.
Solicitor review
Before launch, solicitor review should confirm trademark language, interoperability framing, refund policy, affiliate terms, privacy claims, and jurisdiction-specific consumer rules.