Route5Route5
Route5 Constitution
Our commitments to operators: follow-through is infrastructure, AI proposes but humans confirm, and your data stays yours.
Jump to full textOperating principles
Human confirm, visible ownership, and automation that escalates — not hides — risk.
Core principles
What we will not compromise on while building the accountability desk.
Capture and Intelligence may propose owners and dates — nothing ships to the desk until a person confirms.
Operator rights
- Export commitments and activity for boards, clients, and compliance.
- Disconnect integrations without losing historical commitments.
- Use Classic assistant from live desk data — no API key required for core Q&A.
- Escalate blockers with named owners and due dates, not shared inboxes.
Full constitution
- Article I — Purpose: Route5 exists so decisions made in meetings become owned work with due dates, not forgotten threads.
- Article II — Human confirmation: No AI output becomes a commitment without explicit human approval in Capture or on the desk.
- Article III — Data ownership: Your org owns its commitments, feed history, and integration tokens. Route5 is the processor, not the owner.
- Article IV — Transparency: Product, marketing, and sales copy distinguish live features from preview and roadmap items.
- Article V — Safety: Assistants answer from your desk context first; they do not invent owners, dates, or commitments.
- Article VI — Portability: Export and API access remain available on paid tiers so you are never locked into opaque status slides.
- Article VII — Accountability culture: The product rewards clear owners and honest due dates — not performative busywork.
- Article VIII — AI honesty: Assistants must not invent live facts; web search or clear uncertainty is required for current events.
- Article IX — Team collaboration: Workspace members share commitments and explicitly shared chats; private threads stay private until shared.
- Article X — Security: Encryption in transit and at rest for credentials; prompt breach notification; users report suspected access issues.
- Article XI — Legal transparency: Terms, Privacy, and this Constitution are public and linked in-product.
- Article XII — No training on customer content: Route5 does not use your workspace data to train public models.
Legal documents
- Terms of Service — /terms (AI outputs, liability, arbitration, team workspaces)
- Privacy Policy — /privacy (breach notification, cookies, subprocessors, your rights)
- Security & compliance — /security-compliance
- Responsible scaling — /responsible-scaling-policy
Read how we scale responsibility as the product grows.
Responsible scaling policy