Know what the observatory uses.
This notice describes the current MetaTray application. A deployment operator’s actual hosting, logging and support arrangements also determine how information is processed.
Information you provide
The current interface has no account registration, identity form, payment form, wallet connection or user-media upload. You can inspect the observatory without giving the application your name, email address, seed phrase or signing key.
If you separately contact an operator or post an issue on the source repository, the information you choose to include is handled through that channel. Public repository issues are public; do not include sensitive personal information there.
Web requests and hosting
Your browser sends normal requests to load pages, fonts, scripts and read APIs. A hosting or security provider may process your IP address, request time, browser information, requested path and diagnostic or abuse-prevention records in providing its service.
The application does not add an advertising analytics SDK or custom visitor-tracking system. This does not mean the hosting environment collects no logs. The operator must check the actual provider configuration, retention periods and applicable notices for the deployed service.
Public chain observations
A configured indexer reads public transaction and contract-event information for the selected market. Displayed receipts can include a chain ID, contract address, transaction hash, log index, block hash, timestamp and trade amounts. Such information can sometimes be linked with other public records.
MetaTray does not infer a trader’s real-world identity or match a visitor to a wallet. Demo records are synthetic. Public blockchain records are maintained by the relevant network and cannot be erased by removing a local copy from this website.
Information used by the model
The GPU worker constructs audiovisual inputs from recorded market observations and the paper account. Model artifacts can include generated video, narration, alignment events, predictions, provenance and processing records. They are not recordings of a website visitor or a trader’s brain.
The intended deployment runs the configured model on an operator-managed GPU service. The supplied code does not upload a visitor’s media to a hosted Meta inference API. Obtaining model dependencies and weights is a separate operator setup step.
Browser storage and downloads
The current application does not set a custom tracking cookie or persist visitor preferences in local storage. UI choices such as the selected viewer tab are held in the current page session. Fonts are served with the application rather than requested from a remote font service.
A receipt export is generated in your browser and downloaded to your device. The export action does not itself upload that file to a sharing service. If you later share a receipt, review its contents first. Infrastructure providers may use separate security mechanisms under their own policies.
Retention, recipients and rights
Recorded market data, jobs and predictions are stored in the operator’s database, with generated media and raw outputs on worker storage. The source does not impose a universal deletion schedule. Retention depends on the operator’s configuration and legal obligations.
Hosting, database, RPC and GPU providers may process information needed to deliver their services and may operate in different countries. The operator must identify its actual providers, locations and retention practices when deploying the service. The source contains no sale-of-personal-data integration.
Depending on applicable law, you may have rights to access, correct, delete or object to processing of personal information. These rights have legal limits and cannot remove immutable public blockchain history. Contact the deployment operator through a private channel for a request.
Contact and notice changes
A private contact channel has not yet been configured for this deployment. Do not post sensitive information in public repository issues. The deployment operator must provide any contact information required by applicable law.
Changes to the application’s data practices should be reflected in this notice before those practices are introduced. The version and date above identify the current notice. See the terms of use for the service’s experimental scope.