Privacy Policy

This policy describes what information Uller collects when you visit the simulator or hold a simulated account, why we collect it, and the choices you have. Uller is a public sandbox; we collect only what we need to authenticate you, scope your simulated state to your account, and keep the service running.

• Privy authentication identifier. When you sign in through Privy we receive an identifier for your account so we can attach simulated state to it.
• Optional self-selected username. If you set a display name in the onboarding flow we store it with your account.
• Simulated trading state. Your simulated balance, positions, open orders, order history, trade history, and funding events are stored against your account so they persist between sessions.
• Request metadata for rate limiting. The rate limiter sees the IP address and user-agent of each request and the x-sim-user header (your account id) so it can enforce per-user buckets.
• Browser storage.A small number of keys are written to your browser's localStorage to keep the interface usable across reloads. These are enumerated below.

• Government-issued identification, passport details, or other KYC documents.
• The contents of any real wallet, including balances, transaction history, or private keys.
• Real fiat banking information, card numbers, or payment credentials.
• Biometric data.
• External on-chain transaction histories beyond what Privy needs to verify a connected wallet.

Uller does not set advertising or analytics cookies. The following keys may be written to localStorage in your browser:

• uller_guest_id — anonymous identifier used to scope simulated state for guests who have not connected a wallet.
• uller_seen_how_it_works— flag indicating you have already dismissed the "How it works" modal, so we don't show it again on the next visit.
• uller_onboarding_skipped — flag indicating you have dismissed the onboarding modal.

You can clear these at any time through your browser's storage controls. Clearing them will reset the related UI state and, for a guest, start a new simulated account.

We use a small number of external services to run the simulator:

• Privy— authentication. Privy handles the wallet-connection or login flow and shares an account identifier with us so we can attach state to your account. Privy's own privacy policy governs the data it collects.
• Public market-data APIs — Coinbase for SOL-USD and GeckoTerminal for token pools. We fetch market snapshots from public endpoints; we do not send your information to those providers to do so.
• Analytics — none currently. If we add an analytics provider in the future, this policy will be updated to describe it.

Simulated state may be reset, recalculated, or deleted at any time, including on routine redeploys, when we migrate persistence backends, or when we determine that an account is abusing the service. We do not guarantee that any simulated balance, position, or history will persist.

When the server runs without a configured database the engine keeps state in process memory, which is cleared on each restart.

Uller is intended for users aged 18 and over and is not directed at children. We do not knowingly collect information from children. If you believe a child has used Uller, please contact us so we can remove the associated account.

• You can clear browser storage at any time to reset local preferences and, for guests, start a new account.
• You can disconnect your wallet or sign out through Privy to end your authenticated session.
• You can request deletion of your simulated account history by emailing the support address below. We will confirm and complete the deletion within a reasonable period.

We take reasonable measures to protect the service and the information it stores, including transport encryption, scoped database access, and per-account rate limiting. No internet service is perfectly secure, and we cannot guarantee that the simulator will be free of vulnerabilities or unauthorized access.

Uller may be hosted, processed, or backed up in regions where our infrastructure providers operate, which may differ from the region you access the service from. By using Uller you understand that information may be transferred to and processed in those regions.

We may update this policy from time to time. Updates take effect when posted to this page, and the "Last updated" date at the top reflects the most recent revision.

Questions about this policy, or requests to delete a simulated account, can be sent to team@uller.example.