2.1 Public On-Chain Data. By design, blockchain transactions are public. We collect and display public data (wallet addresses, transaction hashes, and balances) to provide the Service.

Note: Once broadcast to a blockchain, this data is immutable and cannot be deleted or altered by Forbole.

​

2.2 Automatically Collected Data (RPC & Nodes). When your Wallet interacts with the blockchain, it connects to an Remote Procedure Call (RPC) node. This node inherently receives your IP Address and your Wallet Address to broadcast transactions or fetch balances. While Forbole does not use this data to identify you personally, it is technically processed during your session.

​

2.3 Swap & Bridge Interaction Data. If you use the Swap or Bridge features:

• Transmitted Data: We transmit your wallet address, token types, and amounts to third-party DEX aggregators (e.g., 1inch, Jupiter) or bridge protocols.
• Third-Party Processing: These providers process your IP address and transaction data according to their own policies. Forbole does not control these third parties.

​

2.4 Product Analytics (PostHog). We use PostHog, a product analytics service operated by PostHog Inc., to understand how the Service is used and to improve it. Our PostHog instance is hosted on PostHog's EU Cloud infrastructure.

• Analytics provider: PostHog, hosted on EU infrastructure, operated as our data processor. Analytics is on by default in production and can be turned off at any time (see Your control below).
• Included with every event: a random anonymous identifier generated on first install (never tied to your identity); app version; whether you are using the mobile app or the browser extension; your operating system; and your approximate country, derived from your IP address at the time the event is recorded. Your IP address itself is discarded immediately and never stored.
• Creating or importing a wallet (mobile and extension): we record that a wallet was set up, whether it was created fresh or imported, and a one-way cryptographic fingerprint of the wallet address (see About the address fingerprint below). We also record when an account was added to an existing wallet, and when the onboarding flow was completed — no financial data is included in either of those.
• Opening the app (mobile): we record each time the app is brought to the foreground. No financial or address data is included.
• Unlocking the extension (browser extension): we record each time the extension is unlocked. No financial or address data is included.
• Sending tokens (mobile): we record that a send was started, and separately whether it completed successfully or failed. For completed sends we also record the token type, the network used, the amount sent, the approximate USD value at the time of the send, the fee paid, and a one-way cryptographic fingerprint of the sender's address.
• Sending tokens (browser extension): we record that a send was started and whether it completed successfully or failed, along with the token type and network. Amount, fee, and address fingerprint are not yet captured on the extension and will be added in a future update. For a user's very first send or receive we also record the direction (sent or received), the amount, and the token type — this is a legacy data point that will be removed once the extension is fully updated.
• Bridging tokens (mobile): we record whether a bridge completed successfully or failed, the source and destination networks and assets, the amount bridged, the approximate USD value at the time of the bridge, the fee paid, and a one-way cryptographic fingerprint of the sender's address.
• Swapping tokens (mobile): we record whether a swap completed successfully or failed, the tokens swapped, the network, the swap provider used, the amount swapped, the approximate USD value at the time of the swap, the fee paid, and a one-way cryptographic fingerprint of the sender's address.
• Visiting an app in Explore (mobile): we record which app the user tapped to visit. No financial or address data is included.
• Signing a transaction for a connected dapp (browser extension): we record the website address of the dapp that requested the signature and whether it succeeded or failed. No financial data or address fingerprint is included.
• Participating in a Kastle campaign (server-side, not the wallet app): when our server detects an on-chain transaction that qualifies for an active Kastle campaign, we record the campaign name, the KAS amount of the transaction, the public transaction ID (already visible to anyone on the Kaspa block explorer), the public campaign destination address, and a one-way cryptographic fingerprint of the sender's address. This recording happens on our server, not inside the wallet app, and applies only to transactions that match a campaign.
• About the address fingerprint: instead of storing your wallet address directly, we store a one-way cryptographic hash of it — a fixed-length string derived from your address that cannot be directly read back as an address. We use this fingerprint to count unique active users, link activity across the mobile app and browser extension, and process deletion requests (see section 5.4). Your raw wallet address is never stored in our analytics system.
• What we never collect via analytics: your raw wallet address, private keys, seed phrase, wallet balance, or the destination address of any send you initiate. We do not track you across other apps or websites or use analytics data for advertising.
• Why we collect amounts, fees, and address fingerprints: to measure how the product is used in aggregate, to validate that our fee model is working, and to understand transaction volume across the network — without identifying individual users. The address fingerprint specifically allows us to honour your right to request deletion of your analytics data and to count how many distinct users are active, without ever storing addresses directly.
• Purpose: product analytics only. We do not use this data for advertising, for tracking you across other apps or websites, or for sharing with third parties beyond PostHog acting as our data processor.
• Your control: you can opt out of analytics collection at any time in Settings → Data & Privacy → Share Anonymous Analytics. When opted out, the PostHog SDK stops sending events immediately, and your choice is remembered on your device.
• A full list of analytics events collected by Kastle is available on request via privacy@forbole.com.

4.1 No Sale of Data. We do not sell your personal information.

​

4.2 Third-Party Providers. We share necessary data with:

• DEX Aggregators & Liquidity Providers: To fetch quotes and execute swaps.
• Bridge Operators: To facilitate L1/L2 asset transfers.
• Cloud Infrastructure: For hosting our website and RPC nodes.
• Product Analytics: PostHog Inc., as a data processor, hosting our analytics on PostHog EU Cloud.

5.1 Access and Rectification. You may request access to or correction of any off-chain personal data we hold (e.g., support emails) by contacting privacy@forbole.com.

​

5.2 The Right to Erasure (Important). You may request that we delete your off-chain data. However, we cannot delete, "un-publish," or mask any data stored on a blockchain (such as the Kaspa ledger). Your transaction history is permanent.

​

5.3 Opt-Out. You can opt out of product analytics at any time in Settings → Data & Privacy → Share Anonymous Analytics. To stop all other data processing associated with the Service (including connections to RPC nodes and third-party DEX/bridge providers when transacting), discontinue use of the Wallet and delete the application from your device. Note that on-chain data already broadcast to a blockchain remains public and cannot be removed by Forbole (see section 5.2).

​

5.4 Analytics Data Deletion. You may request deletion of historical analytics data associated with your device by contacting support@kastle.cc. Because the analytics data is keyed to an anonymous device identifier rather than to your identity, we may ask you to provide additional information to help us locate the relevant records. Requests are processed within 30 days. To prevent any future analytics collection, use the in-app opt-out described in section 5.3.

Forbole Technology Limited

7/F, Cheung Hing Industrial Building, 12P Smithfield, Kennedy Town, Hong Kong

​

Email: privacy@forbole.com