Privacy Policy
Updated：2026-09-24
Campaign measurement
When you arrive through a BTC.LIVE promotion link, we use a first-party random browser identifier cookie lasting up to 30 days to estimate visits and associate the first promotion source with your site account after sign-in. We use site registration records, successful non-hidden chat activity and return visits to report aggregate campaign performance to authorized administrators. We do not send this information to X advertising systems, store chat content in campaign records, or collect wallet addresses for advertising. Short-lived IP-derived hashes limit abuse. Browser Do Not Track and Global Privacy Control signals disable this measurement. Clearing the cookie or switching devices may cause attribution gaps. Campaign records are retained for operational reporting; use the contact below to request access or deletion.
Wallet sign-in
When you connect a wallet, we request its public EVM address and a one-time sign-in signature. We store the verified address, account association, verification time and authentication audit records. Short-lived challenges contain the address and sign-in message; rate limiting uses a short-lived hash derived from your IP address. Signatures are verified during login and are not stored. We never ask for private keys or recovery phrases, hold wallet funds, or request transfers or token spending approvals for login. New wallet accounts receive a random English nickname, which you may change. Connecting a wallet alone does not make you eligible for rewards.
Who we are and how to contact us
This policy describes how BTC.LIVE handles data for its market charts, community chat, free predictions and account features. For privacy questions, access, correction or deletion requests, contact doubleguge@gmail.com.
Google sign-in
With your authorization, Google sends an account identifier, verified email address and basic profile information. We store the Google identifier, email, display name and binding timestamps to create or link your BTC.LIVE account and let you sign in again. The profile permission may include a profile photo; the current implementation does not store or display that Google photo. We do not request Gmail, Drive, contacts or calendar access. Google access and ID tokens are used during authentication and are not stored for later API access; we do not request refresh tokens. New accounts use the Google display name as an initial site nickname, which may be publicly visible. You can change your nickname in your account. Linking an existing account preserves its nickname.
Other account and activity data
Depending on the sign-in method you choose, we receive account identifiers and profile information from X or the existing ChatGPT sign-in service. X connections include a username, display name and follower count used for profile links and community-room eligibility. We store your site profile, membership settings, predictions and results, chat messages, saved rooms, reading preferences, reward records and moderation/authentication audit records to operate those features. Chat anti-spam checks store a daily hash derived from your IP address. Hosting providers also process connection information such as IP addresses as needed to deliver and secure the service.
Public content and service providers
Chat rooms, including creator rooms accessible through shared links, can be read without signing in. Nicknames, selected avatars, messages, membership display information, linked X profiles and public rankings can be visible to others. Google email addresses are not included in public chat profiles. Administrators can access data needed to operate the service and investigate abuse; hiding a message removes it from public display but does not delete its database record. Cloudflare hosts the application, database and stored assets. Google, X and the existing sign-in provider process their own authentication flows. Embedded TradingView charts connect your browser to TradingView, which handles those requests under its own policies. We do not sell Google user data or use it for personalized advertising.
Cookies, security and storage
We use secure, HttpOnly session cookies for sign-in (currently up to eight hours) and short-lived authentication cookies (currently ten minutes). A language cookie remembers your selection for up to one year. Browser storage remembers theme, chart, room and chat display preferences, and may hold temporary drafts. You can clear browser storage or sign out, but this does not delete server-side records. Connections use HTTPS; backend credentials are stored as encrypted secrets. Service providers may process data in countries other than your own.
Retention, deletion and your choices
Account and activity records are retained to support account continuity, historical results, rewards and abuse prevention. The current service does not automatically delete all historical records after a fixed period. To request a copy, correction, account deletion or removal of a sign-in link, email doubleguge@gmail.com; we will verify control of the account before processing the request. Some records may need to be retained for unresolved rewards, security or legal obligations, and backups may retain copies until they are replaced. Revoking Google access in your Google Account stops that authorization but does not itself delete your BTC.LIVE account or previously stored data. Do not send passwords, private keys or login codes with a request.
Changes
We will update this page when our data practices change. If we seek additional Google permissions or use Google data for a new purpose, we will explain that change and request the necessary consent before doing so.