FICTIONAL DEMO / DATA BOUNDARIES

Your context deserves clear boundaries.

This page describes the current pre-release ReturnTrail implementation. It is not a promise of production consumer-case handling. Do not enter personal addresses, phone numbers, order receipts or other sensitive real records.

What the demo stores

Fictional source text, selected recorded claims, quotations, local follow-up tasks and manual notes are stored in the instance’s FalkorDB graph. Access is linked to a server session.

Guest access

Guest workspaces expire after two hours of inactivity and are cleaned up by this instance. Restarting the backend ends in-memory guest access. Export a brief before expiry, reset or sign-in. Guest sources are not automatically copied into an account.

Optional saved sign-in

When a provider is configured, ReturnTrail uses its verified stable account identity and a display name to reopen a separate saved demo graph. The browser receives a session cookie; provider API access tokens are removed from session storage after sign-in. Google OIDC identity claims remain in the server’s authenticated session. No provider password, inbox or repository access is requested by this implementation.

AI requests

An explicit AI investigation sends case quotations and saved manual context to the configured Groq service to perform bounded tool calling. Do not enter personal information. Rule review and Context lab do not call an AI provider. An AI run can prepare a local task; it does not contact a merchant.

Retention and deletion

Saved demo graph data remains while the deployment database is retained. Signing out ends browser access and does not delete that graph. This release has no self-service account deletion or real-data retention settings. The deployment operator must provide a private contact and deletion process before accepting real-user records; public real-data onboarding is outside this release.

Infrastructure and logs

The host, authentication provider and AI provider handle requests under their own terms. Operational logs can include request and failure information. Never publish secrets or complaint contents in bug reports. There is no advertising or marketing analytics integration in the reviewed source.

Errors and questions

Use the source repository for non-sensitive technical issues. Do not post personal case information publicly. For a self-hosted copy, the host operator is responsible for backups, access, retention and a suitable private contact.

Read the supported workflow →