Privacy Policy
Last updated October 23, 2026
CollectiveBargaining.io is owned and run by Wade Intelligence Group LLC (“we”, “us”). We run a contract database and research tools for union locals. This page explains what we collect, why, who can see it, and how to get it deleted. Questions go to info@collectivebargaining.io.
The short version: your local's business stays your local's business. We don't sell your information, we don't show ads, and we don't use tracking or advertising cookies.
What we collect
When you ask for access
The Request access form asks for your union, local number, department or employer, name, role, email, and phone. We use it to check that you're with a local and to send your invite. Your local's officers see your request if your local already has an account. To stop spam, we also keep a scrambled, one-way code made from your internet address. It can't be turned back into the address.
Your account
Your name, email, and sign-in details, handled by our sign-in provider, Clerk. If you sign in with Google or Microsoft, we receive your name, email, and profile picture from them. We never see your Google or Microsoft password. We also keep which local you belong to and your role there.
What you and your local put in
Contracts and other documents you upload, the text we read from them, review notes and messages, saved items, your local's comparables list, and feedback you send us. We also keep a record of actions like uploads, approvals, and sharing, with who did them and when.
Problem reports
When you use Report a problem, we keep what you write, the page you were on, your device and browser, and any error code on the screen. If you leave the picture of the page in (or add your own), we keep that too. It can show whatever was on your screen, like contract pages. Only the people who run CollectiveBargaining.io see problem reports.
Questions to the Assistant
When you ask your local's Assistant a question, we send it to our AI provider, along with the contract articles and Data Center numbers it looks up, to get an answer. We save the conversation (your questions, the answers, and the steps it took) in your local's account so you can come back to it. Only you see your conversations, unless you're an officer and hand one to another officer.
Usage and technical information
For each AI request, we record who made it, which feature, when, and how much it cost. We don't keep the question or answer in that record. Our hosting provider keeps standard server logs (internet address, browser type, pages requested) for security and troubleshooting. Sign-in uses cookies to keep you signed in. We don't use analytics or advertising cookies.
Text messages
Members can sign up to get text messages from their local, on their local's sign-up page, in the app, or by texting JOIN to their local's number. Only you can sign yourself up. Your local's officers can't do it for you. Texts are one-way for now: nobody reads replies, except STOP, START, and HELP.
- What we keep. Your name, mobile number, the exact words you agreed to, and when. We also keep a scrambled, one-way code made from your internet address, to stop spam and as proof of the sign-up. If you stop texts, we keep that too, so your local never texts you again by mistake.
- What the texts are. Union business from your local: meeting reminders, contract and grievance updates, vote notices, and urgent notices from officers. Message frequency varies. Message and data rates may apply.
- Stopping. Reply STOP to any text, or turn texts off on My local. Reply HELP for help. Signing up is not a condition of membership.
- Who sees your number. Your local's officers who send messages. We don't sell, rent, or share your mobile number or your agreement to get texts with anyone for their own marketing. Text messaging sign-up information is never shared with third parties or affiliates for marketing purposes.
How we use it
- To run the service: sign you in, store and read your documents, answer questions, and show you results.
- To keep it secure: stop abuse, enforce usage limits, and investigate problems.
- To contact you about your account, your local's requests, and changes to the service.
- To improve the service, using things like which features are used and what they cost.
We don't sell personal information, and we don't use it for advertising.
Who can see what
- Your local. Everything your local uploads is private to your local by default. Your local's officers decide who joins.
- Other locals. Other locals only see a contract if your local chooses to share it. Contracts are generally public records. Shared contracts appear in other locals' search results with your local's name. Your notes, messages, comparables list, and member information are never shared with other locals.
- Us. A small number of people who run CollectiveBargaining.io can see account and usage information to run the service. They can look at a local's content, including its roster, member records, and cases, when needed to fix a problem, answer a support request, check that the service is working for that local, or keep the service safe. Each look is logged.
Companies that help us run the service
These providers store or process data for us, only to provide their service to us. Your data is stored in the United States.
- Clerk: sign-in and accounts.
- Vercel: hosting the website.
- MongoDB Atlas (on Amazon Web Services in Ohio): the database.
- Cloudflare: storing uploaded files, and our domain.
- Inngest: running background jobs, like reading an uploaded contract.
- Anthropic: the AI (Claude) that reads contracts and answers questions. Under Anthropic's commercial terms, it doesn't train its models on data we send it.
- Signal House: sending text messages, once your local's texts start. It gets your mobile number and the text, only to deliver it.
- Google and Microsoft: only if you choose to sign in with them.
When we'd share it otherwise
We may share information if the law requires it, such as a valid subpoena or court order. When we're allowed to, we'll tell the affected local before we respond. We may also share it to protect someone's safety, or as part of a sale or merger of the business. If that happens, this policy keeps applying to your information.
How we protect it
Data is encrypted in transit and stored with providers that encrypt it at rest. The software walls each local's private data off from every other local, and that wall is tested every time the code changes. Admin access is limited to the people who run the service. No system is perfectly secure. If a breach affects your information, we'll tell you and your local promptly.
How long we keep it
We keep account and local data while your local uses the service. We keep access requests, including ones turned down, as a record of who asked and who answered. If you or your local asks us to delete data, we delete it from the live service within 30 days. Copies in backups are erased as those backups expire.
Your choices
- Ask to see the personal information we hold about you, or to correct it.
- Ask us to delete your account. Your local's documents belong to your local, so its officers decide about those.
- Your local's officers can stop sharing a contract at any time.
Email info@collectivebargaining.io for any of these. We'll answer within 30 days.
Children
The service is for working union members and officers. It isn't meant for anyone under 18.
Changes
If we change this policy, we'll update the date at the top. If a change is significant, we'll tell your local's officers before it takes effect.
See also our Terms of Service.