Your space.
Your privacy.

Who to contact

BitPool is a publisher-led crypto research and trade-journaling 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.
• 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.

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.

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 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.

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.