Alpha data use · Draft
What this preview remembers
This draft describes the current local preview. We’ll update it before inviting testers to the hosted alpha.
In this local alpha
A manually issued user code associates activity with an operator-maintained participant record. A recognized user code is required before entering the Designer. Missing or unknown codes cannot continue. We do not ask for your email address or record IP addresses or device details in the alpha tables.
A backend-issued browser cookie remembers your participant and accepted agreement version for 30 days. A new agreement version requires acceptance again. Activity sessions restart after 30 minutes of inactivity.
We record the agreement version, exact text, and acceptance time; journey actions; search parameters, outcome, compact result context, and software versions. Each authorized submitted search is durably recorded before execution, independently of feedback. Private operator records preserve original and effective parameters, available normalized intent, search phases and counters, and interruption or stop reasons across server restarts. Your browser tab also remembers journey choices.
Feedback and diagnostics
The full request and ACE-response diagnostic bundle is held temporarily in backend memory for up to one hour, subject to memory limits and server restarts. It is saved in Postgres only when you submit related feedback. If it is unavailable, your feedback can still be saved with its available search context.
The local Results cache separately keeps the reduced response needed to browse journeys. It is temporary and does not provide permanently saved journeys.
Provisional retention
The local-development policy is 90 days for activity and search summaries. Feedback is retained until a later review. Automatic deletion is not enabled yet. We will finalize retention and the agreement before real testers participate.
Feedback sent by email includes what you choose to send. Questions? Email info@tangenttravel.com.