Skip to main content
IntentrailNavigation
HomeMission LabWeb3WhitepaperTerms

Your mission data stays in the browser by default.

Intentrailmission evidence
HomeMission LabWeb3WhitepaperPrivacy
Privacy / 01Last updated 13 October 2026

Local by default.
Limited by design.

This notice explains what the current browser-only Intentrail prototype reads, stores, and deliberately does not collect.

01

Mission processing

Mission grids, commands, traces, imported receipts, and anchor envelopes are processed in the browser. Intentrail does not provide an application backend, file-upload endpoint, analytics service, or mission database in this release. Refreshing or closing the page may remove in-memory mission data.

Downloaded JSON and CSV files are created only when you press an export control. After download, you decide where those files are stored or shared.

02

Wallet information

Wallet connection is optional. When you choose Connect Wallet, the interface requests access to a public account and reads the active network identifier. Explicit read tools may also request public block, balance, transaction, and receipt data through the connected provider.

Intentrail does not request private keys, recovery phrases, arbitrary signatures, typed-data signatures, network changes, token approvals, payments, or transaction broadcasts.

03

Browser storage

A short session flag may remember that you previously chose to connect, allowing the page to re-read public wallet state without showing another access prompt. The latest receipt digest may be held in session storage for the homepage preview. Full mission receipts are not persisted automatically.

If you separately activate local points after importing a passed receipt, the points value is stored in localStorage under a key scoped to the public address and active network. Clearing browser data removes this state. Points are not an asset or public balance.

04

Hosting metadata

Ordinary hosting infrastructure may process request information such as IP address, user agent, requested path, timestamps, and security logs to deliver and protect the static site. Intentrail does not add its own tracking pixels or behavioral analytics.

05

Data you should not enter

Do not enter private keys, recovery phrases, robot control credentials, production facility maps, restricted routes, personal information, confidential sensor data, or real operational secrets. Use synthetic or public-safe mission scenarios only.

06

Optional review

The 0.21 BOT upgrade is review-only. Recipient and target network are unavailable, confirmation is disabled, and no payment request can be made. Opening the dialog stores no payment state.

07

Your controls

You can use the simulator without a wallet, decline a connection request, disconnect through your wallet, clear site data through browser settings, remove downloaded files, and avoid sharing exported receipts. Because the prototype has no user account or mission database, there is no hosted mission profile to retrieve or delete.

IntentrailKeep mission intent intact.
ProductMission LabWeb3Whitepaper
LegalPrivacyTerms
© IntentrailNo account · no mission upload