LEGAL // PRIVACY POLICY
Privacy Policy
This policy explains what information Blue Collar Crypto collects, why, how we use and share it, and the choices and rights you have. Blue Collar Labs LLC is the controller responsible for your information.
Effective 1 July 2026 · Blue Collar Crypto is operated by Blue Collar Labs LLC.
01 · SCOPE
This policy applies to information we process when you use Blue Collar Crypto (the "Service"). It should be read together with our Cookie Policy and Terms of Service.
02 · INFORMATION WE COLLECT
We collect the following categories of information:
- Account information — email address, chosen handle, display name, and a securely hashed password (we never store passwords in plain text).
- Wallet and on-chain information — blockchain wallet addresses you link (verified by a signature), and the public on-chain holdings, tokens, NFT, and validator activity associated with them. This data is public on the blockchain; we index and display it.
- Profile and activity — content you create (posts, comments, media), reactions, attestations, reviews, disputes, group memberships, and trust/reputation signals derived from your activity.
- Device and technical information — IP address (stored only in hashed form for security), browser and device characteristics, and a device fingerprint used for fraud and multiple-account detection (see section 4).
- Usage information — pages viewed, actions taken, timestamps, and request metadata, used to operate and secure the Service.
- Communications — messages you send us and, where applicable, notification and email preferences.
- Authentication data from single sign-on — if you sign in with Google or X, we receive basic profile information (such as your email and identifier) from that provider.
03 · HOW WE USE INFORMATION
We use information to:
- provide, maintain, and improve the Service and your account;
- compute and display trust, reputation, and on-chain gating features;
- detect, prevent, and respond to fraud, abuse, multiple accounts, automation, and security incidents;
- communicate with you about your account, security, and Service updates;
- comply with legal obligations and enforce our terms.
04 · DEVICE FINGERPRINTING AND FRAUD PREVENTION
To protect the integrity of trust and reputation and to prevent sybil / multiple-account abuse, we generate a device fingerprint from server-side signals (such as network and request characteristics) and from limited browser-reported signals (such as an automation flag and screen characteristics). We use it to detect when one device or actor controls multiple accounts and to score automation. IP addresses used in this process are stored only as keyed hashes, not in raw form.
Consent. When you create an account, you consent to these fraud-prevention device checks. Admin-provisioned accounts and visitors who do not complete signup are not fingerprinted in this way. The legal basis is your consent and our legitimate interest in securing the Service.
05 · PUBLIC BLOCKCHAIN DATA
Blockchain networks are public and, by design, permanent and outside our control. Wallet addresses you link and their associated on-chain activity are publicly visible on the relevant network regardless of our Service. When you link a wallet, you acknowledge that this information is public and may be displayed and associated with your profile.
06 · LEGAL BASES (EEA/UK USERS)
Where the GDPR or UK GDPR applies, we rely on the following legal bases: performance of a contract (to provide the Service you request); legitimate interests (to secure the Service, prevent fraud, and operate trust features, balanced against your rights); consent (for fraud-prevention device checks at signup, for optional product analytics, and where otherwise indicated, which you may withdraw); and legal obligation (to comply with applicable law).
07 · HOW WE SHARE INFORMATION
We do not sell your personal information. We share it only with:
- Service providers / processors that help us run the Service, including cloud hosting and deployment, error and performance monitoring, blockchain RPC and data providers (used to read public on-chain data), single sign-on providers, media providers, email delivery, and product analytics (PostHog, only if you allow analytics — see section 14). These providers process data on our behalf under contractual safeguards.
- Legal and safety — where required by law, legal process, or to protect the rights, safety, and integrity of the Service and its users.
- Business transfers — in connection with a merger, acquisition, financing, or sale of assets, subject to this policy.
08 · INTERNATIONAL TRANSFERS
We and our providers may process information in countries other than yours, including the United States and the European Union. Where required, we use appropriate safeguards (such as standard contractual clauses) for cross-border transfers.
09 · RETENTION
We keep personal information for as long as your account is active and as needed to provide the Service, then for a reasonable period to meet legal, security, fraud-prevention, and dispute-resolution needs, after which we delete or anonymize it. Security records such as fingerprint data are retained only for the period necessary for fraud prevention. Note that public on-chain data cannot be deleted from the blockchain by us.
10 · SECURITY
We use technical and organizational measures to protect information, including password hashing, hashed IP storage, signed authentication tokens, access controls, rate limiting, and audit logging. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. You are responsible for safeguarding your credentials and wallet keys.
11 · YOUR RIGHTS AND CHOICES
Depending on where you live, you may have rights to access, correct, delete, port, or restrict processing of your personal information, to object to certain processing, and to withdraw consent. Where the CCPA applies, you have rights to know, delete, correct, and to not be discriminated against for exercising them; we do not sell or share personal information for cross-context behavioral advertising.
To exercise your rights, contact privacy@bluecollarcrypto.io. We may need to verify your identity. You may also have the right to complain to your local data-protection authority.
12 · CHILDREN
The Service is not directed to children under 18, and we do not knowingly collect their information. If you believe a child has provided us information, contact us and we will delete it.
13 · COOKIES AND LOCAL STORAGE
We use a small number of cookies and browser-storage entries that are strictly necessary or functional. If you allow product analytics (section 14), PostHog also stores an analytics identifier and session state on this browser; it stores nothing until you allow it. See our Cookie Policy for details and choices.
14 · PRODUCT ANALYTICS
If you allow it, we use PostHog, a product-analytics provider, to understand how the Service is used. Analytics is off until you allow it on this browser, and you can turn it off again at any time. Your choice is stored on this browser and is kept when you sign out.
When analytics is on, we record:
- Pages you open — the page address only, without its query string or fragment. Addresses that name a person, a post or a dispute are recorded as their page type (for example a member profile is recorded as “/u/[handle]”), never the handle or id itself.
- Link tags — if you arrived through a tagged link, only its source, medium and campaign tags (utm_source, utm_medium, utm_campaign), shortened to 100 characters. Other link tags and advertising click identifiers are discarded.
- A small set of actions — publishing a post, publishing a comment, joining a community, following or unfollowing a member, sending a message, completing onboarding, and linking or unlinking a wallet. These carry only basic details such as the kind of post, the community type, or the chain; never the text you write, message contents, or wallet addresses.
- Sign-up and setup steps — starting and finishing sign-up, viewing and finishing each onboarding step, and starting and finishing a validator claim. These carry only the sign-up method (password, Google, X or wallet), the onboarding step name, or the chain. Every event also carries whether you are signed in (member or anonymous).
- Errors the site runs into, with any page addresses stripped of query strings.
- Standard technical details PostHog attaches to each event, such as browser type and version (including your browser’s user-agent string), screen size, and your country, derived from your IP address. Location is recorded at country level only.
If you are signed in, these events are linked to a pseudonymous identifier: a keyed hash of your account number, computed on our servers with a secret key, so it cannot be traced back to your account without that key. It is never your name, handle, or email. We do not record anything on sign-in, sign-up completion, password-reset, email-verification, or messaging pages (on the sign-up page itself we record only the page view and which sign-up method you started), and we do not use session recording, heatmaps, or automatic click tracking. Analytics is not used for advertising.
Your choice. Turning analytics off stops collection from this browser straight away. To ask us to delete analytics data already collected, contact privacy@bluecollarcrypto.io.
Vercel Web Analytics. Separately, our host Vercel counts page views in aggregate. It uses no cookies and stores nothing on your device, so it does not need your consent. Page addresses are sent without their query string or fragment, with person identifiers replaced as above, and nothing is sent from sign-in, sign-up completion, password-reset, email-verification or messaging pages. Along with the page address, Vercel records the referring site, and derives your country, browser, operating system and device type from the request. Visitors are counted with an identifier that resets every day; Vercel does not store your IP address.
15 · CHANGES TO THIS POLICY
We may update this policy from time to time. We will change the effective date and, for material changes, provide notice where appropriate. Your continued use after changes take effect constitutes acceptance.