Your data.

Accounts and phone login

The platform uses your public wallet address, chain identifier and a wallet-linked account identifier to recognise your account. The phone app links to that existing account through a QR request and platform approval. It does not hold your wallet private key or seed phrase.

We store a device name, device identifier, approval time and expiry for each linked phone. The phone session expires seven days after approval. Login credentials use an HttpOnly cookie; the QR secrets used for pairing are temporary. Signing out or revoking a phone ends its access.

Gameplay and reward records

The account service stores your player alias, chosen bird, game inputs, server-verified flight records, scores and related reward records. We use these records to provide saved progress, scoreboards, gameplay verification and reward administration. Your alias, bird and published scoreboard results can be public. Published blockchain transactions and reward records are public and cannot be erased from the blockchain by BELLJACK.

Flight and reward records remain stored to support account history, verification and disputes. Signing out of a phone does not delete those records. Player preferences and some local progress may remain on your device.

Token migration registration

When you register for the JACK migration, we store your Robinhood Chain wallet, its JACK balance at the published snapshot, the Solana destination you provide, and your signed registration messages. We keep previous signed revisions to verify destination changes and resolve disputes. These records are used for migration administration and distribution; they are not shown on public player profiles or leaderboards.

Registration signatures do not transfer tokens. You can download your receipt and update your destination while registration is open. Records remain available after the registration window closes. Any later airdrop transactions will be public on Solana. RPC providers process blockchain queries needed to verify the snapshot. Contact us below for access or data-handling requests.

QR camera

The app requests camera access when you choose to scan a login QR code. It uses the decoded pairing link to connect your phone. BELLJACK does not upload camera photographs or video to the account service for QR login. You can use a pasted pairing link instead.

Optional notifications

In app builds where notifications are configured, enabling them uses Google Firebase Cloud Messaging. Firebase uses an installation identifier and notification registration token to route messages to your phone. BELLJACK stores the registration token, platform and your notification choice against the linked phone session. Apple also uses its push notification service for iPhone delivery. See Firebase privacy and security for provider data handling and retention.

Notification messages contain general BELLJACK updates, rather than wallet addresses, balances or reward amounts. Account-specific delivery requires an active linked-phone session and notification consent. Turning notifications off, signing out or revoking the phone removes its active registration; expiry prevents further account-specific dispatch. A notification already accepted by the delivery provider may still appear.

Use Notifications under Profile in the phone app to change your choice. You can also block notifications in your phone settings. The app does not include Firebase Analytics or advertising SDKs.

Service operation

Requests to the website and account server include network information such as your IP address. The service uses request and security records to operate the platform, limit abuse and investigate failures. Login and gameplay requests use HTTPS. The account server and notification providers process data needed to deliver their services. Links to other websites are subject to those websites' own privacy practices.

Access and deletion requests

To request access to or deletion of your BELLJACK account data, email admin@belljack.world with the public wallet address associated with the account and what you want us to do. Never send a private key, seed phrase or password. Ownership verification may be needed before an account request can be acted on.

Some verification, security or reward records may need to be retained for outstanding disputes or applicable obligations. Public blockchain records remain public. You can end phone access immediately by signing out in the app or revoking that phone on the platform.