Skip to content

Privacy Policy

Effective date: November 12, 2026 (version 2026-11-12)

At a glance

  • The website collects nothing. brad-os.com has no forms, no sign-up, no cookies of its own, and no analytics. Our host keeps standard request logs.
  • Our tools are invitation-only. There is no public sign-up and no sales process.
  • We collect what the tools need to work: your account details, the 811 ticket and job data your team enters, related addresses and map locations, photos and files you upload, safety and training records (Safety & Fleet Management), and subcontractor tax and bank details (Contractor Onboarding).
  • DigCheck and Forge OS run on CrewNation today. They currently run inside the CrewNation app at thecrewnation.com, on The Crew Nation’s systems and vendor accounts. Accounts are moving to brad-os.com.
  • We do not sell personal information. We do not use it for advertising.
  • We share data with a short list of others: people at your own company (by role), The Crew Nation and the service providers that run the tools, state 811 systems, and your team’s own webhooks — plus where the law requires it. See Section 7.
  • 811 safety. DigCheck is a tracking aid, not the 811 system. Always confirm a ticket’s status in your state’s official 811 portal before digging.
  • Signed safety records are kept for set periods. Safety & Fleet Management training sign-offs, e-sign agreements, and injury and incident statements are kept for B.R.A.D.’s default periods in Section 10, even after a job ends, and are not deleted on request during that time. You can ask for copies (Section 11).
  • You can ask to see, fix, or delete your data. Ask your company’s admin, or contact us at support@brad-os.com. Some records are kept for set periods first; see Section 11.
  • Not for children. The tools are for business use by adults 18 and over.
  • Data is stored and processed in the United States.

1. Who we are

“B.R.A.D.” (Broadband Resources & Administration Dashboard), “we,” “us” and “our” mean B.R.A.D., the business that operates brad-os.com. B.R.A.D. makes software for broadband construction companies. This policy covers the website at brad-os.com (the “Website”) and the B.R.A.D. tools (each a “Tool”): DigCheck, Forge OS, Safety & Fleet Management and Contractor Onboarding.

Our relationship with CrewNation. CrewNation (thecrewnation.com) is a separate business operated by The Crew Nation, which has the same founder as B.R.A.D. Today, DigCheck and Forge OS run inside the CrewNation app, on CrewNation’s servers, database and vendor accounts.

2. Scope: what this policy covers

  • Website (brad-os.com): live, on B.R.A.D.’s own hosting. It collects only standard host request logs (Section 4).
  • DigCheck: live, inside CrewNation today. Collects the data in Section 5.2.
  • Forge OS: in development, inside CrewNation, available to master admin accounts. Collects the data in Section 5.3.
  • Safety & Fleet Management (formerly S.A.F.E.): live, at brad-os.com. Collects the data in Section 5.5.
  • Contractor Onboarding (formerly C.O.R.E.): live, at brad-os.com. Collects the data in Section 5.4.

Please read this plainly. When you use DigCheck or Forge OS today, you are on CrewNation’s website, and your login is a CrewNation login. If you created your account through a DigCheck invitation there, you also agreed to CrewNation’s Terms of Use and Privacy Policy, which continue to govern the CrewNation app itself. This policy describes how the B.R.A.D. Tools handle your information, and it is the policy you accept when your account moves to brad-os.com.

Code names. In some screens, emails and web addresses, DigCheck still appears under its earlier name, “DigSentinel.” They are the same tool.

When we act for your company. Most data in the Tools belongs to the company that uses them — your employer or the contractor that invited you. For that data we generally act on that company’s instructions, so you may need to make some requests through your company. See Section 11.

What this policy does not cover: the state 811 portals, your company’s own systems, or other websites we link to. Their own policies apply.

3. How people get access

  • There is no public sign-up and no sales process. You cannot create a B.R.A.D. account yourself.
  • A B.R.A.D. admin grants a user account permission to each Tool. Invitations come from admin accounts; in DigCheck, a team lead may also invite members to their own team.
  • We do not take payments today, and the Tools do not collect any payment card information.

4. The Website (brad-os.com)

What the public pages collect: nothing directly. The Website’s public pages have no forms, accounts, cookies, local storage, analytics, tag managers or advertising. Fonts are served from our own host, so your browser does not contact a font service when you visit. Signing in to a Tool at brad-os.com sets the sign-in cookies described in Section 8.

Host request logs. Our host, Vercel, automatically keeps standard request logs when you load a page: your IP address, browser type, the page you asked for, and the time. Vercel uses these logs to deliver the site, keep it secure and fix problems.

Links out. The sign-in buttons send you to the Tool’s sign-in page. Anything you type there is collected by that app, as described in Section 5.

5. What the Tools collect, and why

5.1 Account information

When you accept an invitation or are granted access, we collect and keep:

  • your email address, first name and last name;
  • your password, stored only in hashed form by our authentication provider — we cannot read it;
  • your account type, which Tools you can use, and your role within each Tool;
  • the invitation record: the invited email, role, who sent it, when it was sent, and when it expires;
  • the time your email was verified and the time you last signed in;
  • a record that you accepted the Terms of Use and this policy, including the document version, the time, your IP address and your browser’s user agent;
  • your language preference.

We also keep an audit log of important actions — for example, who invited whom or who saved or removed a portal login — recording who did it, when, and basic details. Passwords are never written to the audit log.

Why: to create and secure your account, let you sign in, show you only what your role allows, send you account emails, keep a record of consent, and investigate misuse.

5.2 DigCheck

DigCheck tracks 811 locate tickets for crews that dig. It collects:

  • Ticket data: state, ticket number, excavator name, worksite address, city, county, type of work, key dates, utility responses, and DigCheck’s status verdict — plus any link your team makes between a ticket and a project or work order.
  • Filing details: where a filing feature is offered, the excavator, contact and dig-site details needed to file or update a ticket with the state’s one-call system.
  • Location data: we turn worksite addresses into map coordinates and store them so tickets can be shown on a map. For some states we show the ticket’s dig-area outline, read live from the state portal.
  • Notes and attachments: free-text notes your team writes on a ticket, and photos or PDF files you attach.
  • Saved searches (“monitors”): the company name, street number, street, city and county you search on, plus the latest results.
  • Integrations: if your team sets them up, your webhook’s address, its signing secret (stored encrypted), which events to send, and delivery status; and API keys, stored only as a one-way fingerprint plus a short prefix and shown in full once, when created.
  • Team data and alerts: team names, who belongs to each team, and the alerts DigCheck creates when a ticket or search changes.

State 811 portal logins. Some state portals require a login to search. For those states, a B.R.A.D. admin saves B.R.A.D.’s own portal login — customers are not asked for, and do not enter, their own 811 portal passwords. Only admins can save or remove these logins. The password is encrypted (Section 9) and decrypted only on our server at the moment DigCheck signs in to the portal.

Why: to read 811 tickets from state portals, show utility responses and status, file tickets you ask us to file, alert your team when something changes, give your team a shared workspace, produce PDF and spreadsheet reports (generated on request and not kept), and send ticket events to your own systems if your team sets that up.

DigCheck is a tracking aid, not the 811 system. Its information can be late, incomplete or wrong. Always confirm a ticket’s status in your state’s official 811 portal before digging. See Section 7 of the Terms of Use.

5.3 Forge OS (in development)

Forge OS manages fiber and coax construction jobs. It is in development and available only to B.R.A.D. master admin accounts today. It collects: project and job data (projects, work orders and their status history, map shapes, bid items, pricing and subcontractor rates, quantity claims, invoices, purchase orders, price books and customer packets); documents such as construction plans and markups; field photos and documents, including the location and time stored inside a photo file; photos from a field photo app if your company connects one; draft 811 locate requests prepared from project details; AI results pulled from plans and photos; and company settings.

Who in your company sees what: admins and project managers see everything, including internal pricing; subcontractors see only the projects they are assigned to and their own rates; technicians do not see pricing.

5.4 Contractor Onboarding (formerly C.O.R.E.)

Contractor Onboarding helps a contractor company collect paperwork from its subcontractors through one secure link. It collects, from subcontractors: consent to sign electronically (time, IP address, user agent); company and contact details; IRS Form W-9 details including the taxpayer identification number (Social Security Number or Employer Identification Number); certificates of insurance; agreement details and signatures (with time, IP address, user agent and a fingerprint of the signed document); optional direct-deposit and wire details including bank routing and account numbers and a voided-check image; and an audit trail. From company staff it collects email, name, title, role and a saved signature image. Subcontractors do not create an account.

Why: so the contractor company can onboard its subcontractors, collect the tax forms needed for IRS reporting, set up payment, confirm insurance, and keep signed records.

5.5 Safety & Fleet Management (formerly S.A.F.E.)

Safety & Fleet Management holds the safety records a company keeps about its field crews: personnel rosters and contact details, driver’s license and medical card details and images, vehicle and crew records, training topics, assignments and completion records, and, where your company turns it on, injury, illness and incident reports and statements. This information is entered by your company or collected from crew members through personal links your company sends them.

Signing on your phone. Before you sign anything electronically in Safety & Fleet Management, you read your employer’s e-sign notice and agree to it. You can then sign safety training records and safety, injury and incident statements on your phone.

What we record when you agree or sign. What we record depends on what you sign:

  • When you agree to sign electronically: the date and time; your internet (IP) address and the type of device and browser you used; when your PIN was checked (we never record the PIN itself); which personal link and phone session you used; and the exact e-sign notice you agreed to: the words as they were shown to you, their version and language, and a digital fingerprint (a code) of that text.
  • When you sign a training record: the date and time; your IP address and the type of device and browser you used; your typed name; your drawn signature; when your PIN was checked (never the PIN itself); which personal link and phone session signed; your quiz answers; your name, employee code and job title as they were when you signed; and the version and language of the training you saw, with a digital fingerprint of the exact content you signed, so any later change would show. The record also points to the e-sign notice you agreed to.
  • When you sign a safety, injury or incident statement on your phone: the date and time; your IP address and the type of device and browser you used; your typed name; an encrypted copy of exactly what you submitted, which cannot be changed later; and which e-sign agreement was in force for you.

Your drawn signature is not biometric data. Your drawn signature is stored as lines, a list of points on the screen, with no timing for each point. We never turn it into a biometric template, and we never use its shape, speed or pressure to identify you. Drawing with your finger on a touch screen does not capture your fingerprint, and Safety & Fleet Management does not scan faces or fingerprints. Biometric privacy laws such as the Illinois Biometric Information Privacy Act do not treat a written signature as a biometric identifier, so we collect no biometric identifiers when you sign.

Who can see the signing details. Your IP address, your device and browser type, and the personal link and phone session you signed on are shown only to your employer’s Safety & Fleet Management Managers and Admins. You can see your own signed training records and your e-sign agreement.

Why: so your company can track licenses, medical cards, vehicles and training compliance for its crews; keep a reliable record of who signed what, and when; and meet its safety, injury-reporting and record-keeping duties.

5.6 Technical and usage data in the Tools

  • server and request logs (IP address, browser type, page, time) kept by our host;
  • rate-limiting and security data: your IP address is used to limit repeated requests and block bots, and sign-in and password-reset emails are counted per email address and per IP address to prevent abuse;
  • error reports and session replays through Sentry (Section 7);
  • your sign-in time each time you log in.

6. How we use information

We use information only to:

  • provide, run and secure the Tools;
  • create accounts, manage invitations, and control who can see what;
  • send service emails (invitations, sign-in links, password resets) and in-app alerts;
  • read 811 tickets from, send searches to, and file tickets with state 811 systems;
  • send data where your team tells us to, such as your webhook;
  • translate alert text into your language if you use the Tools in a language other than English;
  • find and fix errors and improve reliability;
  • keep records of consent, signatures and important actions;
  • prevent fraud, abuse and security incidents; and
  • meet legal duties and enforce our terms.

We do not sell personal information. We do not share it for cross-context behavioral advertising. We do not use it for advertising of any kind, and we do not use Customer Data to train AI models of our own.

7. Who we share information with

Within your company and to admins. People at your company see data according to their role (Section 5). DigCheck team data is visible to all members of that team, and DigCheck ticket alerts also go to other people at the same company who have DigCheck access, even if they are not on the same team. B.R.A.D. admins can see all DigCheck and Forge OS data.

Service providers. These companies run parts of the Service for us and receive only what they need for that job:

ProviderWhat it doesWhat it receivesTools
The Crew Nation (operator of CrewNation, thecrewnation.com)Hosts DigCheck and Forge OS inside its app and vendor accountsAll DigCheck and Forge OS account and work dataDigCheck, Forge OS
Vercel Inc.Website and app hosting, scheduled jobs, content delivery, request logs, file storage and bot protectionAll web traffic (IP address, browser, page); uploaded files (see Section 9)Website and all Tools
Supabase Inc.Database and sign-inLogin email, hashed password, names, Tool data, alerts, audit logs, consent records (with IP address and user agent)All Tools
ResendSends service emailsYour email address, your name if it appears in the email, and one-time linksAll Tools
PusherReal-time “you have a new alert” signalAn internal user ID in the channel name; alert signals carry no content. Your browser’s connection exposes your IP address and user agent to Pusher.DigCheck, Forge OS
Sentry (Functional Software Inc.)Error monitoring and session replayError details and request information; performance traces from a sample of requests; recordings of a sample of browser sessions (and sessions with an error), with on-screen text and form inputs masked and media blocked. Request bodies are not sent.DigCheck, Forge OS
Mapbox Inc.Maps, address lookup and satellite imagesTicket worksite addresses (to find map coordinates); coordinates (to find addresses and satellite images); map requests from your browser (your IP address and the area you view)DigCheck, Forge OS
Anthropic PBCAI processingPlan and photo images; project and work-order details and addresses (for drafting 811 requests); alert titles and text (for translation only, when you use a language other than English)Forge OS; DigCheck (translation only)
OpenAIBackup translation if Anthropic is unavailableAlert titles and text, for translation onlyDigCheck, Forge OS

State 811 one-call centers and the portal software they use. DigCheck sends them ticket numbers and search details automatically, on a schedule, and — where you use a filing feature — the ticket details you ask us to file. These centers are independent, not our service providers; their own terms and policies apply, and a filed ticket becomes part of the state’s official record.

Your company’s webhooks and API clients. If your team sets them up, DigCheck sends ticket and monitor events to the address your team chooses, and returns data to API keys your team creates.

De-identified information. We may share technical or usage information that has been de-identified or combined so that it no longer identifies you or your company.

Legal and safety reasons. We may share information if the law requires it, to respond to valid legal process, to protect the rights, safety or property of users or others, or to investigate fraud or security issues.

Business changes. If B.R.A.D. is involved in a merger, sale or similar transaction, information may transfer as part of it, subject to this policy.

8. Cookies and browser storage

Website (brad-os.com): none. See Section 4.

In the Tools, cookies and browser storage are limited to what sign-in and preferences need:

  • a sign-in session cookie that keeps you signed in, and a short-lived verification cookie used during sign-in;
  • a language cookie that remembers your language;
  • bot protection on the sign-in, forgot-password and invitation forms;
  • a deployment cookie our host may set to keep your session on one version of the app during updates;
  • preferences stored only in your browser, such as your color theme or a dismissed prompt;
  • error-monitoring session state (Sentry), so a session replay can be linked to an error;
  • map requests: the map library loads tiles from Mapbox and sends Mapbox usage telemetry.

We use no advertising cookies and no third-party tracking cookies. You can block or delete cookies in your browser settings; if you block the sign-in cookies, you cannot use the Tools. Because we do not sell or share personal information for advertising, Do Not Track and Global Privacy Control signals do not change how the Tools work.

9. How we protect information

We use reasonable safeguards. No system is perfectly secure, and we cannot promise that information will never be accessed without permission. What we do today:

  • Encryption in transit. All traffic to the Website and Tools uses HTTPS.
  • Encryption of stored secrets. Saved 811 portal passwords and webhook signing secrets are encrypted with AES-256-GCM before they are stored, decrypted only on our server when needed, never shown on screen and never written to logs.
  • One-way fingerprints. Invitation links and API keys are stored only as hashes, not in readable form.
  • Access controls. Access is invitation-only, each person sees only what their role allows, and the database refuses direct public access.
  • Bot and abuse protection on sign-in and invitation forms, request rate limits, and limits on sign-in and reset emails.
  • Audit logs of important actions.

Files you upload. DigCheck attachments and Forge OS documents and photos are stored at long, random, hard-to-guess web addresses. Anyone who has the exact address can open the file without signing in, so do not share file links outside your team.

Contractor Onboarding is built so that taxpayer ID numbers, bank routing and account numbers, wire routing numbers and SWIFT codes are encrypted with AES-256-GCM, with only the last four digits kept in readable form; full numbers can be revealed only by authorized admins, with each reveal logged; generated tax and payment documents are kept in private storage opened through short-lived links; subcontractor links use long random tokens that expire and can be revoked; and the activity log is append-only.

If something goes wrong. If we learn of a security breach that affects your personal information, we will notify you and others as the law requires.

10. How long we keep information

DataHow long we keep it today
Website request logsPer our host’s standard retention.
Account informationUntil the account is deleted. Removing someone’s access to a Tool does not delete their account.
DigCheck tickets, notes, searches, alertsUntil an authorized user deletes them. Nothing is deleted automatically today. A ticket stops refreshing after it expires, but it is not deleted.
Forge OS projects, documents, photos, financial recordsUntil deleted by an authorized user. Nothing is deleted automatically today.
DigCheck PDF and spreadsheet reportsNot kept. They are created when you ask and sent straight to you.
Expired invitationsKept as part of the account record.
Consent records and audit logsKept to show what was agreed and done.
Error reports and session replays (Sentry)Per Sentry’s retention settings.
Contractor Onboarding W-9s and signed documentsAt least 4 years, to meet IRS record rules.
Safety & Fleet Management rosters, license and medical card records, vehicle recordsUntil an authorized user deletes them, as your company’s compliance record.
Safety & Fleet Management signed training records (including quiz answers)At least 7 years after the employee’s employment ends, or 10 years after signing, whichever is later.
Safety & Fleet Management e-sign agreementsAs long as any record signed under them is kept.
Safety & Fleet Management injury and incident statementsAt least the latest of: 7 years after the employee’s employment ends, 5 years after the end of the calendar year of the incident, or 3 years after a related workers’ compensation claim closes. 30 years if the record is an exposure record or a medical record.
Any Safety & Fleet Management record under a legal holdUntil the hold is cleared, even if its period above has ended.

Safety & Fleet Management safety records. The periods above for signed training records, e-sign agreements, and injury and incident statements are B.R.A.D.’s defaults. We chose them to meet legal record-keeping duties and so the records are there to defend or respond to injury, workers’ compensation and contract claims and to inspections. They apply even after the employee’s employment ends, and even after the employer stops using Safety & Fleet Management or its account ends. When there is a claim, lawsuit, inspection or dispute, a company Admin or B.R.A.D. can place a person’s or a company’s records under a legal hold. A record under a legal hold may be kept longer than its period, and is not deleted until the hold is cleared.

When a user is removed from a DigCheck team, their access ends and their API keys are revoked; tickets they created stay with the team. We may keep information longer if the law requires it, to resolve disputes, or to enforce our agreements.

11. Your choices and rights

Your company’s admin. Because accounts are granted by admins, the fastest way to update or remove your access is often to ask your company’s admin or a B.R.A.D. admin.

Requests to us. You can ask us to tell you what personal information we have about you and give you a copy, correct information that is wrong, delete your information, and tell you who we share it with. Send requests to support@brad-os.com. We will verify your identity before acting, usually by confirming the request came from the email address on your account, and we will respond within 30 days. If your company controls the data (Section 2), we may refer your request to your company or act on its instructions.

Limits on deletion. We may need to keep some records — for example tax forms, signed documents, consent records and financial records — where the law requires or allows it. If you delete an account, some shared work records, such as team tickets, may stay with your company.

Safety & Fleet Management safety records are not deleted on request. Signed training records, e-sign agreements, and injury and incident statements are kept for the full periods in Section 10. During those periods they are exempt from deletion requests, because we need them to meet legal obligations and to establish or defend legal claims, such as injury, workers’ compensation and contract claims. You can still ask to see them and get copies.

Your copies of Safety & Fleet Management records. While you work for a company that uses Safety & Fleet Management, you can download your signed training records and your e-sign agreement at any time from “My records” on your phone. Your injury and incident statements and your other Safety & Fleet Management records are available on request through your employer. Your employer has agreed to provide a free paper copy within 7 working days of your request; ask your employer’s training contact. If you no longer work there, ask your former employer for copies.

Withdrawing your e-sign agreement. You can stop signing electronically at any time: tap “Stop signing electronically” in “My records,” or tell your employer’s training contact. Your employer then switches you to paper or in-person signing. Records you already signed stay valid.

US state privacy rights. Depending on where you live, state law may give you rights to know, access, correct, delete, or get a portable copy of your personal information, to limit use of sensitive information, and to opt out of the sale or sharing of personal information or certain profiling. We do not sell or share personal information for advertising and do not use it for profiling that has legal or similar effects. You may use an authorized agent where state law allows, and we will not treat you differently for using your rights. If we deny your request, you may appeal by replying to our decision.

Emails. The emails the Tools send are service emails — invitations, sign-in links, password resets and alerts. We do not send marketing email.

Users outside the United States. The Tools are built for US companies and intended for use in the United States. If a law such as the EU or UK GDPR nonetheless applies to you, we rely on: performing our contract with you or your company; our legitimate interests (security, fraud prevention, error monitoring and reliability); legal obligation (tax and record-keeping); and your consent where we ask for it.

12. Where data is stored

We store and process information in the United States.

13. Children

The Website and Tools are for business use by adults. They are not meant for anyone under 18, and we do not knowingly collect information from anyone under 18. If you believe a child has given us information, contact us and we will delete it.

14. Changes to this policy

We may update this policy as the Tools change — for example, when DigCheck and Forge OS move to brad-os.com, or when Contractor Onboarding or Safety & Fleet Management launch. We will change the effective date at the top, and if a change is significant we will tell users before it takes effect, in the product or by email. The current version always lives at brad-os.com/privacy.

15. Contact us

B.R.A.D. — privacy questions and requests: support@brad-os.com. The Terms of Use describe the agreement that governs the Service.