Skip to policy
← Back to SukimyTerms of Service

Legal

Privacy Policy

Operated by SYMBiEX · Last updated: 2026-10-16

On this page
  • What we collect
  • What we don’t collect
  • Cookies + storage
  • Third parties
  • Retention
  • Your rights
  • Security
  • Changes

What we collect

We use this information to provide requested features, maintain your account, reconcile payments, prevent abuse, and respond to support requests. Accounts and services are for adults 18 or older. Do not submit children's personal information.

  • Wallet address. The Solana public address you sign in with. Used to identify your captain and attribute Stars purchase receipts.
  • Captain identity and display name. The wallet-derived identity (wallet:address) and the display name you choose during onboarding.
  • Account activity. Policy/age confirmation version and time, Stars balance and retained historical quest, story, and crew progress.
  • Chat messages. Public lobby + DM + group messages, retained for the conversation and moderation review.
  • Stars purchase receipts. Solana payment signatures, payer addresses, package identifiers, amounts, and receipt state used to credit Stars and prevent duplicate credits.
  • Suki conversations and Studio requests. Private conversation content, titles and saved memory are stored as ciphertext in Convex and processed in the Phala runtime through the verified confidential inference route described below. Account ownership, request status, approval settings and usage metadata remain outside encrypted chat. Studio prompts/settings, generation jobs, tool requests/results, Stars allowance choices and saved image/video files may be stored outside encrypted chat. Higgsfield or OpenRouter and the selected underlying provider receive the prompts, reference media and generation settings needed for the requested work.
  • Social integration. If you link an X account, we store its X user ID, handle, and link time. The temporary OAuth access token is discarded after identity verification. Public mentions and replies may be processed by the automated Suki account.
  • Operational logs. IP, user-agent, and request metadata are processed by Vercel and Sentry for abuse prevention and error monitoring; we apply filtering to reduce sensitive data in application logs. Do not include passwords, seed phrases, or secrets in prompts or support messages.

What we don’t collect

  • Your private keys, seed phrases, or any custodial access.
  • Off-chain financial information (bank, card).
  • Government IDs (we do not perform KYC at this time).

Confidential Suki chat

Private Suki chat is encrypted in your browser for a pinned Phala runtime key. The hardware-isolated runtime decrypts conversation context, titles, summaries and saved memory, runs verified confidential inference, and encrypts content before saving it in Convex. There is no automatic fallback to ordinary plaintext chat. The website, its key configuration and approved software remain part of the trust boundary; this is not anonymity or protection from every operator or software compromise.

Convex keeps account ownership, timestamps, collection membership, approval settings, request status and model usage alongside ciphertext. Your chosen display name and permitted saved facts can inform Suki’s replies. New facts stay in their conversation unless you choose to share them across a collection or all chats. Turning saved memory off stops its use and extraction. You can search and export decrypted chat text in your browser; account exports contain encrypted chat records. Conversations and saved facts follow the account retention and deletion rules below.

When you ask Suki to use a tool, the runtime selects task-specific inputs from your current request. External tools can send those inputs and results to the relevant research, media or other provider, and work records may be saved outside encrypted chat. Some document and data tasks run privately in the runtime and return encrypted downloads. Your tool approval setting still controls Stars spending, including an auto-approval allowance you explicitly set. Studio quotes share the prompt and selected settings with the generation provider. Public community and X posts are separate actions. We do not intentionally send your entire private transcript to tools.

The runtime verifies the inference gateway and response receipts and requires its approved confidential route. The browser uses the pinned key; it does not independently validate the full hardware certificate chain for every message. Existing chats are encrypted during the rollover and old application and private Agent copies are removed after verification. Pre-rollover encrypted backups and platform execution history expire under their separate retention schedules.

Cookies + storage

We set a host-only, HttpOnly, SameSite=Lax Better Auth session cookie after you sign in (__Secure-better-auth.session_tokenon HTTPS). Its value is HMAC-signed with our Better Auth secret, and the session is stored in Convex with a 30-day expiry. We use local browser storage for interface preferences and temporary session storage for Studio handoffs and pending payment recovery. Pending recovery may include a signed payment authorization or transaction, never a private key or seed phrase. Signing out or closing a tab may remove temporary browser state; authoritative payment and account records remain on our servers. Model-provider and X API credentials are configured by operators as server-side Convex environment secrets; they are not stored in your browser or attached to your wallet session.

Third parties

  • Vercel — hosts the web app, processes request logs, and provides page-usage analytics when deployed.
  • Convex — application database and agent runtime; stores captain rows, chat messages, account activity, and durable Suki conversation threads.
  • Solana RPC providers, Jupiter, and x402 facilitators — RPC providers receive public addresses and transactions for reads, simulation, and broadcast; Jupiter provides token pricing; x402 facilitators verify and settle supported USDC payments. Blockchain payment details are public.
  • Sentry — error monitoring (with PII scrubbing wired in). Optional; only active when DSN is set.
  • Configured model provider — an OpenAI-compatible text-generation service selected by the operator receives Suki prompts and recent chat context. Private Suki chat requires the verified confidential inference route described above; it does not automatically fall back to an ordinary provider.
  • Higgsfield and OpenRouter — receive image/video generation prompts and settings for the creative studios. The selected model may route requests to an underlying provider. Generated media links may remain available on provider infrastructure before files are copied to our account library.
  • X — provides OAuth and social API services for account linking, mention polling, and Suki posts.

Retention

Private conversations and saved memory are retained to support continuing chats. Archiving a chat hides it; archiving is not erasure. You can export an individual conversation and manage saved memories from Suki. Settings lets you turn saved memory off: this stops automatic fact extraction and use of saved facts, while preserving history within the current conversation. New accounts start with saved memory off; existing accounts retain their previous behavior until changed. Turning it off does not delete existing facts.

Generated media, prompts, and job records are kept to provide your library and support billing. Removing an item hides it from the library; it does not currently erase the stored file, job record, provider copies, or backups. Settings provides a permanent account-deletion control that disables access and starts removal of account-owned chats, saved memory and stored media. Active paid jobs or unsettled payments must finish first; failed cleanup steps require review. Contact us for individual deletion requests or help with a blocked cleanup.

We retain the minimum payment and ledger records needed to reconcile purchases, prevent duplicate credits, investigate fraud, and resolve disputes, including after chat content or an account is deleted. When handling a deletion request, we explain records that must remain and the applicable reason. Public Solana transactions cannot be erased. Service-provider logs and backups follow their own retention schedules; deletion from our active database is not a promise of immediate deletion from every backup.

We do not automatically purge existing private conversations on an inactivity timer. You can download application data or start permanent account deletion in Settings. Contact symbiex@symbaiex.com to request export or deletion; we verify control of the account using a wallet signature or an equivalent authenticated request, review the request, and confirm what was removed or retained and why. We never need your private key.

Your rights

Email symbiex@symbaiex.com to request your data, request correction, or request account deletion. We aim to respond within 30 days; timing and available rights can depend on your location and the request. Account deletion does not unwind on-chain transactions or reward credits already attributed to your wallet.

Security

Private Suki chat content is encrypted in your browser for the pinned Phala runtime key and stored encrypted. The runtime decrypts the inputs needed for a reply and uses verified confidential inference. This does not encrypt account metadata, payment records, public messages or external tool work, and it does not protect against every compromise of the website or approved software. See the confidential chat details above.

See our SECURITY.md for vulnerability disclosure and our operational threat model. To report a security issue privately, email symbiex@symbaiex.com.

Stars and cross-chain payments

Cross-chain Stars top-ups use NEAR Intents 1Click with confidential execution requested on supported routes. Source-chain deposits and Solana withdrawals remain public. Confidential execution reduces public linkage within the provider’s execution layer; it is not a guarantee of anonymity or protection against timing and amount correlation.

Sukimy and its payment provider process your source asset, network, refund address, deposit address, order identifiers, quote and settlement details. Sukimy associates the order with your authenticated captain account to credit Stars and handle support. The provider also applies its own security and compliance controls. This payment feature does not conceal prompts or encrypt ordinary chat history.

Stars are credited from verified net USDC settlement at 100 Stars per USDC. Provider, bridge, network and refund fees may apply. Financial order records are retained with our payment records for reconciliation and legal obligations; account deletion does not erase public-chain transactions. An unresolved payment must be reconciled before account erasure proceeds.

NEAR Intents confidential execution documentation ↗

Changes

The published version is shown above. Material changes are reflected in the app's policy acceptance flow. Contact us if you need clarification before continuing.

Terms of ServiceBack to Sukimy