Privacy policy

Scope and contact

This policy covers the MoonShip Chrome extension, website and configured MoonShip services operated by the MoonShip project. Contact the project operator at zfy3712z@gmail.com for privacy requests, corrections or support. Public blockchains and independently operated wallet/provider services also have their own policies.

X page access

The store distribution asks for explicit agreement and optional access to x.com and twitter.com before injecting its page features. It recognizes cashtags and reads public post/author/profile IDs, handles, display names and avatars from selected public timeline, search, post and profile responses already loaded by X. It does not request new X API traffic or read X direct messages, passwords or cookies. It excludes messaging/settings response operations and does not parse the page’s general initial-state object in the store distribution.

Cashtags and numeric post/profile IDs are sent to the configured MoonShip API for asset candidates and public capital statistics. Display observations for IDs already in the protocol directory may be sent for name/avatar refresh; page observations are not authentication. The selected post’s preview and permalink are held in trusted extension session storage to display your entry. Wallet handoffs carry selected public IDs and display hints. We do not collect your full browser history or unrelated websites.

Accounts, wallets and transactions

When you choose login, Privy and X authenticate your X account. MoonShip receives the verified numeric account identity and authenticated wallet/session information needed for control checks. Embedded-wallet keys are handled by Privy’s wallet infrastructure; external-wallet keys remain with your wallet. MoonShip’s extension does not ask for your seed phrase or export an external wallet’s private key. Authentication/session tokens are sensitive and are used for the requested service, not advertising.

Wallet addresses, asset selections, balances, signed authorizations, quotes, payment/delivery hashes, claim/upgrade records and receipt evidence are processed for the actions you request, recovery and capital relationships. Local transaction journals prevent accidental duplicate payments and remain after page access is disabled. Subject claims publish the X ID-to-subject/controller relationship; settled actions, tokens and transfers are public onchain. Public records cannot be erased by MoonShip.

X following discovery

On the website, after X login and wallet preparation, onboarding automatically uses TwitterAPI.io to match your public following with existing MoonShip subjects, including unclaimed subjects. The configured backend sends only your X username to that provider to read public profile and following metadata. X passwords, cookies, OAuth tokens and wallet credentials are never forwarded. Before login, the website links to this disclosure. You can skip the step; skipping stops subsequent batches, though an in-flight batch may finish. No subject is created or claimed and no economic relationship or permission is granted by a match.

Following observations and matches are private to the authenticated account, scoped to the selected network, and are not identity proofs. Batches read at most 200 accounts; an import window reads at most 1,000. Incomplete or limited results are marked. Results are cached for 24 hours; cache records older than seven days are removed on the next cache access. Settings can clear the list. A minimal account/network onboarding completion marker and abuse-prevention counters are retained separately, so clearing or reopening does not restart imports. Existing manual import in extension Settings still requires a separate request. Provider failures keep prior results and allow normal browsing. Protected accounts are unavailable. TwitterAPI.io has its own retention policies.

Conversations and preferences

If you use token-gated conversations, the service processes participants, messages, room membership, blocks and access policies. The configured server stores messages; end-to-end encryption is not currently provided. A configured Stream Chat deployment also processes this information. You choose whether to use conversations and send messages. Language, theme, onboarding completion, network choice and page-access consent are stored locally; authenticated profile/preferences and policies may also be stored by the service.

Service providers and disclosure

Necessary information is shared with the configured MoonShip backend, Privy/X for authentication, your selected wallet, blockchain RPC providers, public DEX market-data services and the selected execution/funding providers. Ethereum execution uses Uniswap; CCTP/Circle, Aurora Intents and Relay receive the route/asset/address information needed when their configured routes are used. Availability depends on the deployment; discovery alone does not activate a route. Cloudflare hosts the website and may process ordinary access/network logs. These providers may process data in other countries under their own policies.

We do not sell user data, use it for advertising or unrelated profiling, or provide a general browsing-history feed. Access is limited to providing the requested features, operational security, legally required disclosure and user-authorized support. Human access is limited to those purposes; do not include secrets when requesting support. MoonShip’s use and transfer of information received through Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Public onchain posts

When available on the selected network, publishing sends the entire text, author wallet, timestamp and optional subject snapshot to a public Monad contract. The author confirms a network fee in the wallet. Text can be read by anyone independently of MoonShip; deleting local data or an account cannot remove it. The first version has no edit or delete function. Do not post secrets or private information. A subject snapshot is not proof of X authorship, a trade or endorsement.

Retention, security and your choices

Local settings/caches remain until cleared or the extension is removed; selected post session data is cleared when page access is disabled or the browser session ends. Financial journals remain available for reconciliation. Server-side public profiles, account/preferences, chat and settlement archives are retained to operate these features and recover unresolved operations; no automatic deletion interval is currently promised. Request offchain deletion/correction at zfy3712z@gmail.com. The operator verifies the requester and explains any records retained for unresolved operations, security or legal obligations. Public chain records and independently retained third-party data are outside our deletion control.

Store services use HTTPS. Extension code is bundled, X data is treated as unverified, and wallet signatures and exact settlement evidence remain separate checks. Turning off “Page access & privacy” stops future page reading/transmission, removes page modules and clears the selected post; it does not cancel an already submitted transaction, erase chain records or discard recovery journals. You can revoke X site access in Chrome or uninstall. Review material privacy changes before enabling newly disclosed processing.