‖ Jev Trader
Terms of ServicePrivacy Policy

LEGAL · ENGLISH

Local review draft. The operator’s legal name and deployment-specific privacy information must be confirmed before publication. These documents are not yet effective terms or a final privacy notice.

Privacy Policy

This draft describes the data flows implemented for jev-trader.com. It covers browsing the website and viewing its public market demonstrations. It does not cover independently operated exchanges, AI providers or linked websites.

1. Who is responsible

Jev Trader is operated by an individual based in Singapore.

For privacy questions or requests, contact [email protected].

The individual operator’s legal name remains to be confirmed before this draft becomes a published privacy notice.

2. Information involved in using the website

  • Request information. Serving pages and API connections involves network information such as an IP address and request details. The deployment configuration enables web-server access and error logs; their exact fields and retention need operator confirmation. Hosting and delivery providers may also process request metadata.
  • Language preference. The browser stores your selected language under jev-trader-language in localStorage. The application uses it to restore a reading preference; it does not intentionally send that stored value to the trading API.
  • Market selection. A dashboard sends the selected venue to the configured market API and opens a connection for market updates. A selection may start a shared simulation, rather than create a private account or personal trading session.
  • Public market and model information. Dashboards may show public market activity, model inputs and outputs, simulation records and operator-configured public wallet identifiers. These records are not evidence that the visitor owns a wallet or placed a trade.

The current website has no registration, payment or visitor-wallet connection form. It does not ask for a name, password, payment-card number, seed phrase or private key.

3. Why this information is used

Request information is used to deliver pages and live updates, diagnose failures and protect the service. The language preference supports your reading choice. Market selections determine which public demonstration the dashboard displays.

The current application does not implement advertising profiles or visitor-based credit, eligibility or investment decisions. Its AI examples evaluate market states and teaching examples, not a visitor’s personal financial situation.

4. Browser storage and analytics

The application uses localStorage for language preferences and does not implement application-level advertising cookies or analytics trackers. This statement does not rule out cookies or logging introduced by the production hosting, CDN or security configuration, which must be checked before publication.

You can remove the language preference by clearing this site’s browser data or block local storage through browser settings. The preference has no application-defined expiry; clearing it may reset the interface language. FAQ article language is determined by its URL.

5. Infrastructure and external services

Hosting, reverse-proxy and content-delivery services process requests needed to serve the site. The market API can be hosted separately from the frontend, so the browser connects to the API host configured for that deployment.

Server-side integrations retrieve market data from Hyperliquid and Monad/Kuru infrastructure. When the Jev model is enabled, the backend sends market state and evaluation questions to TypeSafe AI. The current evaluation request is not designed to include browser language preferences or visitor identification.

Following an external link sends a request to that website, which handles information under its own policy. Provider identities, processing locations and any required international-transfer safeguards must be confirmed for the production deployment; this draft does not promise data residency or provider retention limits.

6. Retention and security

Language preferences remain in the browser until removed. Dashboard history and server-side trading records have separate lifecycles from website access logs. A trading-log rotation setting is not a retention period for visitor data.

Access-log and provider-log retention periods, backup handling and deletion procedures are pending confirmation. Private keys and service API credentials belong on the server and should never be submitted by visitors. No internet service can guarantee absolute security.

7. Your choices and privacy requests

You can clear local browser data, close the page to end its active market connection and choose whether to follow external links. Depending on applicable law, you may have rights to access, correct, delete or obtain your personal data, restrict or object to processing, and complain to a relevant supervisory authority.

Send privacy requests to [email protected]. Applicable processing grounds, any consent requirements and response procedures require confirmation for the operator’s jurisdiction. Do not post personal information or credentials in public issue trackers to make a privacy request.

8. Changes and related terms

This notice should be reviewed when accounts, analytics, new providers or other data collection are introduced. A published revision should state an accurate update date and explain material changes. See also the Terms of Service.

FAQ

  • How to use Jev Score
  • How Jev turns context into decisions

Legal

  • Terms of Service
  • Privacy Policy
GitHub · web3w/jev-traderUpstream · jarrodwatts/jev-trader