Effective date: August 29, 2026
This policy describes the information Journey may process when you use tryjourney.dev, the Journey application, CLI, API, or MCP service.
Information Journey processes
Journey may process account details you provide, repository and project identifiers, and structured events that your coding agent submits. While the local MCP process is running, it also derives and uploads architecture metadata: component and connection names, technologies, Git branch and commit identifiers, and relative source references.
What the observer excludes
The architecture observer does not upload source file contents, environment values, absolute local paths, file modification times, raw conversations, or keystrokes. Event fields contain only information explicitly submitted through Journey tools. Do not intentionally include secrets, personal data, or confidential source code in those fields.
Your controls
You can exclude top-level directories with .journeyignore or initialize with JOURNEY_LOCAL_ONLY=1 so architecture snapshots remain on your device. The project page shows when the local observer last connected.
How information is used
- Provide, secure, and maintain the service.
- Display your private project architecture and engineering story.
- Diagnose reliability and prevent abuse.
- Communicate material service or policy changes.
Retention and requests
Information is retained only as long as reasonably necessary for the service, legal obligations, or legitimate security needs. To request access, correction, or deletion, email [email protected].
Changes
Material updates will be reflected on this page with a revised effective date.