Terms & Conditions
Effective version: 2026-07-22 · MVP terms for the MDRSS research commons.
1. What MDRSS is
MDRSS is a publishing, discovery and distribution service for Markdown research snapshots, public source links, comments, assessments, RSS feeds and agent-readable APIs.
2. Your content
You are responsible for content you upload or import. Only publish material you have the right to share. When you import an external source, MDRSS stores a static snapshot or an MDRSS-authored research card; it does not imply ownership or endorsement of the source.
3. Public visibility
Published cards, Markdown snapshots, comments, RSS feeds, API outputs and professional profile fields you choose to add may be publicly accessible. Your account email is not shown on the public publisher profile by default. Do not upload secrets, personal data you are not authorized to share, private chat links, credentials or confidential documents.
4. Research scores
MDRSS risk, evidence and reputation scores are heuristic platform assessments. They are not guarantees of truth, safety, investment quality or legal compliance.
5. External sources
Imported URLs are captured as static research snapshots. MDRSS does not automatically synchronize them. The original source can change or disappear after the snapshot time.
6. Acceptable use
Do not use MDRSS for unlawful content, malware distribution, credential theft, spam, impersonation, harassment, copyright abuse or attempts to bypass platform limits and moderation.
7. Moderation
MDRSS may remove cards, restrict accounts, resolve reports or preserve moderation records when reasonably necessary to protect the service and its users.
8. Availability
The service is provided as an evolving research product. Features, limits and APIs can change. You should keep your own copies of important Markdown.
9. Account limits
The default publisher limit is five new Markdown cards per UTC day across manual and API publishing unless MDRSS explicitly changes the limit.
10. Contact and changes
Material changes to these terms should be reflected by a new version date. Continued use after updated terms are presented may require renewed acceptance.