Privacy, security, and self-hosting.

ReasonTrail is in private beta. The operator identity, business address, registration details, VAT details, and final public contact address will be published before general availability.

For current access questions, use the private-beta request form. This page does not invent a legal contact address that is not yet monitored.

For a self-hosted installation, the person or organization running the deployment controls the project data stored in that deployment.

For the private beta request form on this site, the operator of this website controls the contact details submitted through the form.

The early-access form may collect name, email, role, active project count, current AI tools, hosting preference, and optional message content.

A self-hosted ReasonTrail deployment may store projects, conversations, tasks, decisions, resources, review items, usage records, local account details, and configuration settings.

A contributor's raw conversation remains private to that contributor. Project or organization membership does not grant access to its transcript, detail, search, review payload, or private graph edges.

Authorized project members can share approved project knowledge separately. Source references preserve provenance without widening access to the private transcript.

AI features are optional. If enabled, selected project context may be sent to the configured AI provider or local model runtime to answer a request.

The self-hosted database remains local to the deployment, but provider requests are governed by the provider configured by the operator.

The public marketing pages should use no external analytics by default. If optional analytics, pixels, embedded media, or marketing tools are added, they require a cookie disclosure and consent controls before activation.

Authenticated app sessions use necessary server-side session cookies for login and security.

EU users may have rights to access, correction, deletion, restriction, portability, objection, and complaint to a supervisory authority, depending on the final operator and processing context.

Before public launch, the final privacy notice must identify the contact point for these requests and the retention period for private beta submissions.