The web should serve human understanding — not harvest it. These are the principles that guide TruthAngel’s design, data practices, and behavior.
Core Principles
- Human dignity first. People are ends, never means. We refuse manipulative design and attention traps.
- Truth with context. Facts are paired with sources, uncertainty notes, and clear causal explanations.
- Current, not careless. We value up-to-date answers while acknowledging when evidence is mixed or evolving.
- Privacy by default. We minimize data collection and avoid selling or sharing personal data.
- Non-exploitation. No emotional bait, outrage loops, or deceptive patterns.
How This Works in Practice
1) Sourcing & Transparency
- When answers reference current events or specific claims, we favor primary or highly credible sources.
- We label uncertainty (“preliminary,” “disputed,” or “consensus forming”) instead of overstating confidence.
2) Privacy & Data
- We avoid collecting personal data beyond what’s needed to respond (e.g., contact form email).
- We don’t sell personal data. We don’t build advertising profiles.
- Server logs are used for security and reliability and are periodically purged.
3) Safety & Boundaries
- No guidance that enables harm, abuse, or illegal activity.
- We discourage harassment and dehumanizing language. Critique policies and actions, not inherent identities.
4) Fairness & Non-Manipulation
- We avoid dark patterns (fake urgency, disguised ads, consent shaming).
- We design for clarity: clear labels, undo paths, and plain-language explanations.
Political Content
- Candor with balance. We describe mechanisms candidly (e.g., money in politics) while distinguishing fact from opinion.
- Source diversity. For contested topics, we cite across reputable perspectives and note where interpretations differ.
- Reader agency. We encourage questions and provide pathways to primary materials.
When We’re Wrong
Mistakes can happen. When they do, we:
- Flag the issue and correct it promptly.
- Note what changed and why.
- Where possible, link to the corrected source trail.
Contact & Feedback
See something that could be clearer or more responsible? Tell us.
Last updated: