Privacy Policy

Effective date: November 5, 2026 · Last updated: November 5, 2026

This policy explains how the SynapseAI Wallet browser extension handles information when you manage accounts, connect to decentralized applications, interact with blockchains or request support. Local processing is included. It also explains the technical information received when you visit this policy page.

1. Scope and wallet custody

SynapseAI Wallet is published under the SynapseAI brand. This policy covers the browser extension; it does not replace the terms or privacy policies of independently operated websites, blockchain networks, exchanges or hardware-wallet services.

Software-wallet recovery phrases and private keys are handled locally, with persistent secrets stored in a password-encrypted vault. They are available to the wallet in memory when required for authorized operations. Hardware-wallet signing is performed through the selected device and its integration. Wallet passwords and recovery phrases are not required by our RPC or market-data services. Do not include them in support messages or screenshots.

2. Information the extension handles

Account identifiers and contact information: Public wallet addresses, account names, address-book labels and addresses are used to identify accounts and recipients. Names, email addresses or other contact details may also be provided voluntarily in support correspondence. Creating a local wallet does not require a name, phone number or email address.
Financial and transaction information: The wallet processes balances, token holdings, transaction history, recipients, amounts, fees, approvals, signatures and smart-contract requests. RPC and wallet-data services receive public addresses and request details to return balances, prepare or simulate operations and submit transactions.
Authentication information: The extension processes the local unlock password, encrypted key material, and authentication or pairing information used by selected integrations. Local password and key handling is distinct from publishing a signed transaction or sharing a signed authentication message with a service you use.
Connected websites and browsing-related information: Site origins, names, icons, connection permissions and wallet request context are used to show the active website, maintain connections and check requests. Relevant website identifiers can be sent to wallet-data and risk-checking services. This is website information associated with wallet features, rather than a requirement to upload your complete browser history.
Usage and diagnostic information: Depending on the Data Analysis setting, the extension can report feature events, toolbar pin status, generated installation/session identifiers, extension and browser versions, and error diagnostics. Error reporting applies filtering to reduce sensitive information. This filtering is not a reason to include secrets in reports.
Network information and approximate location: Services contacted by the extension and this website receive connection information such as an IP address, request time and browser information. An IP address can indicate an approximate region. The extension does not request GPS or precise device-location access.
Support communications and screenshot content: When you submit feedback, the message and screenshot you choose to send are uploaded with diagnostic context. This can include public wallet addresses, account counts, the current wallet screen, extension version, language, platform and browser information. Screenshots can contain visible text, images, balances or addresses. Review them before submitting.

Health information is not requested for wallet features. Please do not send health data or unrelated sensitive information in feedback.

3. Why information is used

Information is used to operate and secure the wallet, display assets and networks, handle website connections, prepare and submit user-authorized blockchain operations, provide market information, diagnose failures and answer support requests. Usage reporting, when enabled, helps assess the operation and reliability of these features.

Access to websites allows the extension to make its packaged wallet provider available to compatible applications. Website access alone does not authorize a transaction. Account access and signing requests are handled through the wallet's permission and confirmation flows.

4. External services and sharing

The current extension uses third-party infrastructure. Depending on the feature and your settings, recipients include:

Rabby/DeBank services: wallet and portfolio information, transaction parsing and simulation, risk information and related wallet features. The built-in screenshot-feedback flow currently sends reports and attachments to api.rabby.io, not exclusively to a SynapseAI-operated support server.
Blockchain RPC providers: default, public fallback and user-configured endpoints receive requested account or contract data and submitted signed transactions. BSC read requests may be retried with another public provider if an endpoint fails.
DexScreener and asset-content services: token quotes, price changes, icons and other requested resources.
Google Analytics and Sentry: usage and error diagnostics when reporting is permitted by the Data Analysis setting.
Selected integrations: WalletConnect/Reown, swap services, and hardware-wallet providers such as Trezor, OneKey and GridPlus receive the information necessary for the integration you use.
Connected applications and public blockchains: applications receive the accounts or responses you authorize; blockchain networks receive transactions you submit.

These services may process information under their own policies, in countries different from yours. A third-party service can receive your IP address even when a request contains only public blockchain information. Disabling usage reporting does not stop requests needed for wallet features.

5. Your choices

Usage reporting: turn off Data Analysis in wallet settings to disable the reporting controlled by that preference. The setting can differ between new installations and upgraded profiles; check your installed wallet. It does not disable user-submitted feedback or required RPC and service requests.
Website connections: review and disconnect connected sites in the wallet. Disconnecting a website does not revoke on-chain token approvals; those require a separate blockchain operation.
Support: sending feedback is optional. Review the message and screenshot and avoid including secrets or unrelated personal information.
Local information: use wallet controls to remove accounts or clear local extension storage by removing the extension. Back up recovery information first. Removing local information does not erase public blockchain records or copies already received by external services.
RPC selection: custom network endpoints are configurable. The BSC fallback mechanism can contact other public RPC providers after an error, even when a custom BSC endpoint is configured.

6. Retention and security

Local wallet information remains in the browser profile until removed, replaced or cleared by the wallet's storage controls. Some cached records have their own limits. Support and diagnostic information is retained by the receiving service under its retention practices; the extension cannot erase third-party records by clearing its local history.

Public blockchain records are generally permanent and cannot be deleted by SynapseAI. Wallet actions can make public addresses, amounts and contract interactions visible to anyone.

Built-in public services use encrypted network connections. The security of a user-configured RPC endpoint depends on its configuration. Vault encryption, browser isolation and diagnostic filtering reduce risk, but cannot guarantee protection against a compromised device, malicious website or incorrectly shared recovery information.

7. Data-use commitments

SynapseAI does not sell wallet user data. We use and transfer information for the disclosed wallet functions and related support, security and operational purposes, not for unrelated advertising or data monetization. We do not use or transfer it to determine creditworthiness or for lending decisions.

Our use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. Service-provider transfers described above support wallet functionality and are not a sale of data.

8. This privacy page

This page has no analytics scripts, advertising pixels, forms or wallet-connect functionality. Our web server receives standard request information, including IP address, requested path, time and browser information, for website delivery, troubleshooting and security. Server logs are subject to operational rotation and retention limits.

9. Contact and changes

For privacy questions or requests concerning information held by SynapseAI, email synapseaivip@gmail.com. Do not send your recovery phrase, private key or wallet password.

For information held by an independent provider, you may also need to contact that provider directly. We cannot remove data from public blockchains. We may update this policy when features or data practices change; the date above identifies the latest revision. Material changes will be disclosed through appropriate product or listing notices.