sorro

Privacy policy

Effective 7 October 2026

Sorro is developed and operated by Enclave HK Limited, incorporated in Hong Kong. This policy explains the information used by our website and mobile application. For privacy questions or requests, contact sumer@enclave.money.

Information we process

Feed and older app builds

The first App Store release has a read-only Feed for viewing third-party trader calls, source information and linked markets, without likes or comments. Likes and comments have been removed from Sorro’s backend, and older TestFlight builds have been expired. Those older builds previously supported these interactions.

Historical records from those older builds include like records linked to your account and the relevant post, comment text, account/post associations, timestamps and related technical or audit records. Previously collected records can remain in Sorro’s database until deleted under the retention and deletion process described below. Removing the controls in a new release does not itself delete older records.

In-app content reports record your account, the call and the selected concern. Reported posts are immediately hidden pending review. Source-block preferences are linked to your account and can be changed in Settings. Reporting and blocking do not change your trades. These personal records are removed when you delete your account.

Trade-content concerns sent to sumer@enclave.money are support correspondence. We process the message, the contact details you provide, attachments and any relevant call identifiers to investigate and respond. This is separate from Feed likes or comments.

Why we use it

We use this information to authenticate you, connect your wallet, display your account and markets, submit instructions you authorize, deliver requested alerts and new-call notifications from traders you follow, maintain security, diagnose failures, and respond to support or privacy requests. We may also preserve records where required by applicable law.

Wallets and device authentication

Privy provides embedded-wallet infrastructure. External-wallet users sign through their connected wallet. Sorro’s backend holds an encrypted, approved Hyperliquid delegated signing key, distinct from your main-wallet private key. Google Cloud KMS protects its encryption key outside local development; the executor decrypts the delegated key in memory to sign supported trading and account actions. These flows do not send your main-wallet private key or seed phrase to Sorro’s backend.

The main wallet signs initial delegated-key and builder-fee approvals, key revocation and supported fund movements. Ordinary trade confirmation authorizes the backend to use the delegated key; it is not a separate main-wallet signature for every trade.

Biometric confirmation is performed by iOS on your device. Sorro does not receive or store your biometric templates. You can manage Face ID and notification permissions in iOS Settings.

Service providers and public networks

Providers include Privy for authentication and embedded wallets; Apple and Google for supported sign-in; Google Cloud for backend infrastructure and key protection; Google Firebase Hosting for this website; Apple Push Notification service for notifications; Hyperliquid and relevant blockchain networks for account information and transaction processing; and Unit for supported deposit routes.

Market information and logos can be obtained from third-party sources, including CoinGecko, Logo.dev, public issuer sources and issuer websites. Requests to third-party services may expose request information to that provider. Each independent provider handles information under its own terms and privacy policy.

Research-text processing through OpenRouter is currently disabled. This optional processing is also disabled by default and requires explicit server configuration. If enabled, it processes third-party trade-call text together with the market ticker, direction and reference market price to extract explicitly stated price levels and time frames. That flow does not send wallet private keys, delegated signing keys or your personal account balances to the model, and it does not authorize or submit trades.

Blockchain and protocol records may be public and are not controlled by Enclave HK Limited. Transactions and public wallet activity can remain available after an app account is removed.

Sharing and tracking

We share information as needed with providers that support the functions described above, when you authorize a transaction, or where disclosure is required by applicable law. Sorro does not sell personal information or use it for cross-app advertising tracking. This website has no advertising analytics or marketing cookies.

Retention and security

We retain account and service records while needed to provide the service, resolve disputes, protect accounts or meet applicable recordkeeping obligations. This includes authentication and wallet records, trading instructions, activity and diagnostic records, support correspondence, and any older-build likes or comments still held. Removing a feature does not automatically purge records previously collected through it. We use access controls, encrypted network connections and protected key storage. No service can guarantee absolute security. Data may be processed outside your country, including where our infrastructure and providers operate.

Your choices and deletion requests

You can change app permissions through iOS Settings. Sorro’s Settings lists signing keys and supports removal with your main-wallet signature, using Privy or the external-wallet connection. Hyperliquid also provides account controls. Signing out ends your local app session; it does not revoke the delegated key or separate builder-fee approval. Key revocation is not account deletion.

Initiate account deletion in Settings → Delete account. Confirm ownership and review what is deleted and what remains. Sorro removes its account, personal preferences, device registrations, private trading history and stored delegated trading key, and invalidates Sorro sessions; temporary cache-cleanup failures are retried. Privy identity, linked sign-in methods and wallet/recovery records are intentionally retained to preserve access to your self-custodial wallet. Signing in with the same Apple, Google or email account restores that wallet to a fresh Sorro account. Optional wallet backup is available in Settings and the deletion flow. Sorro account deletion does not automatically revoke the Apple sign-in connection. If you used Apple, you can also stop using Sign in with Apple for Sorro in your Apple Account settings. For help, access or correction of your associated personal information, email sumer@enclave.money. We may need to verify your identity without asking for wallet secrets. We will explain any records that must be retained and why. Do not send private keys, seed phrases or authentication codes.

An app-account deletion request is not an instruction to withdraw funds, cancel orders or close positions on Hyperliquid. Public blockchain records cannot be erased by Sorro. Before requesting deletion, ensure you can access your wallet and funds independently; contact support if you need help understanding access to an embedded wallet.

Age and policy changes

Sorro’s trading services are intended for adults who can lawfully use the relevant products. We do not knowingly seek personal information from children. We may update this policy as the service changes; the effective date above identifies the latest version.

← Back to Sorro