bitpool.Back to the market
01 / YOUR INFORMATION

Your space.
Your privacy.

What BitPool uses, why it is needed, and how you can control it.

Last updated · 3 November 2026

Who to contact

BitPool is a publisher-led crypto research and community website. The BitPool operator can be contacted through @litneuron on X for privacy questions, access or correction requests, and complaints. X is a separate service; use a direct message, not a public reply, for an account request. Never send a password, verification link, recovery phrase, or private key.

Information used by BitPool

  • Account information: your sign-in identifier, email, display name, provider, and verification status. Google/email accounts use Firebase Authentication. Existing ChatGPT/Sites sign-ins supply a separate identity.
  • Your workspace: saved post IDs and timestamps. Older accounts may also retain private records from the former journal feature. These are linked to your account and are not published to other members.
  • Community lounge: your chosen public username, messages, replies, timestamps and owner badge are visible to all visitors. Sign-in emails and account names are not included in the public chat feed. Reports are visible to the owner; moderation records and rate-limit counters are used to prevent misuse.
  • Technical information: hosting and authentication providers may process IP addresses, browser information, request logs, and security events to deliver and protect the service.
  • Support messages: information you choose to send to the operator through X, subject also to X’s privacy practices.

Passwords are handled by Firebase Authentication; BitPool’s application database does not store them. BitPool does not request wallet connections, exchange credentials, or seed phrases.

Why it is used and who processes it

We use account information to authenticate members, protect full posts, keep your saved ideas available, respond to requests, and prevent misuse. Authorized operators can access stored records when necessary to operate the service or resolve an account request.

Firebase/Google processes authentication; OpenAI Sites and its Cloudflare infrastructure provide hosting and application storage. The browser also requests fonts from Google Fonts. Market providers receive server requests for public market data; BitPool does not attach member tokens, cookies, or journal notes to those requests.

BitPool does not run advertising trackers or Google Analytics in this release and does not sell member data. Providers may process information outside your country. Firebase Authentication runs in US data centers. See Firebase privacy information, OpenAI’s policy, and Cloudflare’s policy.

Private member activity statistics

For signed-in accounts, BitPool records an account identifier, email address, verification status, the last activity time, and approximate active browsing time summarized by day. This helps the owner understand member engagement. Only the BitPool owner can see email addresses beside member activity in the private dashboard. These emails are not included in public posts, the lounge feed, or responses available to other members. The records remain linked to your account and are not anonymous.

Time is counted while the page is visible and focused, and pauses after 90 seconds without interaction. We do not collect page-by-page history, form contents, session recordings or advertising identifiers for these statistics. Guests are not included. Timing starts when this feature is enabled; it does not reconstruct earlier visits. Activity records are removed when you delete your BitPool account.

Cookies and device storage

Authentication services use browser storage or cookies to maintain your session. You can sign out or clear site storage in your browser; clearing local storage does not erase your server-side saved ideas or account.

Community message retention

Lounge messages become unavailable 24 hours after they are sent. Quoted replies stop showing an original message when that original expires or is removed. Expired messages and their reports are deleted when the lounge refreshes and through scheduled cleanup. Cleanup may run after the expiry time; expired messages remain inaccessible in the meantime. This does not erase screenshots or copies made by visitors, or immediately erase provider backups.

Your lounge username and account link remain until account deletion. Temporary mutes last 24 hours. Reports expire with the reported message. You can remove your own messages earlier; the owner can remove messages and mute accounts for misuse.

Retention and deletion

Account and workspace records are kept while you use BitPool. You can remove individual saved ideas, or use Account & deletion to erase your BitPool account, saved ideas, lounge username, messages, reports you submitted, private activity statistics, and any records from the former journal feature. Google/email members also initiate deletion of their Firebase sign-in account. This does not delete your Google or ChatGPT account.

A minimal record containing the deleted account identifier and deletion-request time remains to prevent old sessions or simultaneous requests from restoring erased data. It contains no name, email, password, or journal text. Provider logs and backups follow the providers’ retention schedules; Firebase states authentication information is removed from live and backup systems within 180 days after deletion is initiated. Deletion is not a promise of immediate erasure from every provider backup.

If an authentication provider is unavailable, the deletion screen explains any incomplete step and allows a retry. Publisher-account closure is handled separately so public posts and member records can be reviewed safely.

Post and browser notifications

Signed-in members have a notification inbox for new publications and important updates selected by BitPool. We store the last notification you marked as read so your read status follows your account across devices.

Browser alerts are optional. If you enable them, we store a browser push endpoint, encryption keys, your account identifier, subscription dates and delivery status. Alerts pass through your browser provider's push service, such as Google, Apple, Mozilla or Microsoft. Alerts include the public post title and category; full analysis still requires sign-in. Your device may show this text on its lock screen.

You can turn alerts off in the notification inbox or your browser settings. Browser subscriptions, associated delivery records and read markers are removed when you delete your BitPool account. Expired subscriptions are removed when their provider rejects delivery. Email alerts are not enabled.

Your choices

Contact @litneuron to request access, correction, export, deletion assistance, or raise a privacy concern. We may need to verify account ownership before acting. Applicable privacy rights depend on your location; nothing here limits rights granted by law. You may also contact the relevant privacy authority. Material changes to this notice will be reflected in its update date.

Ready to leave?

Account deletion is available inside BitPool. You do not need an X account to use it.

Manage your account ↗