1. Who we are and scope
RBCopilot is provided by Ununpentiums Labs ("Ununpentiums Labs", "we", "us"). This policy covers the rbcopilot.com website, the RBCopilot platform, the RBCopilot Field app and related services (the "Service").
RBCopilot is a business product used by highway contractors and their project teams. When a contractor ("Customer") uses the Service, the Customer decides what project information goes into it and who can see it; we process that information on the Customer's behalf under our Terms of Service and the Customer's order form. If you use RBCopilot through your employer or a project you were invited to, contact that organization first with questions about your data — we will help them respond.
2. Information we collect
Information you give us
- Account information: name, work email, password (stored only as a bcrypt hash), company name and type, role, and team membership.
- Company profile: details an administrator enters, such as license numbers, bonding, certifications and contacts.
- Customer content: everything your team puts into the Service — projects, documents, daily reports, photos, quantities, tickets, inspections, test results, bids, pay estimates, change orders, RFIs, claims and notes.
- Field data: reports, photos, voice notes and other entries captured in the RBCopilot Field app, and location or station references when a user chooses to attach them.
- Demo and contact requests: name, company, work email, phone, role and message submitted through our forms.
Information collected automatically
- Activity records: the Service keeps an audit log of changes to project records (who changed what, and when) so your team has a defensible history.
- Technical data: IP address, browser and device information and request logs, as processed by our hosting provider to deliver and protect the Service. We use IP addresses for rate limiting (for example, to stop password guessing); those counters store a one-way hash, not the address itself, and expire with their time window.
- Field devices: a device identifier and connection key for each phone or tablet connected to your company. We store the key only as a one-way hash.
We don't use advertising trackers or third-party analytics on rbcopilot.com.
3. How we use it
- To provide the Service: sign you in, show your company's records to the right people, sync field data, generate reports, charts, pay factors and exports.
- To secure the Service: enforce roles and company isolation, rate-limit sensitive endpoints, keep audit trails and investigate abuse.
- To support you: answer requests, onboard your team and fix problems.
- To respond to demo and contact requests and to communicate about your account.
- To comply with law and enforce our Terms.
We don't sell personal information, and we don't use Customer content to advertise.
4. AI processing
AI features are optional. They run only when AI is enabled for your account and a signed-in user starts an AI feature. In that case, the content needed for the request — for example the question, the bid or document being analyzed, and relevant specification excerpts — is sent to our AI provider, Anthropic, which returns the generated response. When AI is not enabled, nothing is sent to an AI provider. AI output is stored with your project records as part of your Customer content.
5. Service providers
We use these providers to run the Service. They process information on our behalf to provide their services to us.
| Provider | What they do | Information involved |
|---|---|---|
| Vercel | Hosting of the website, application and API; file storage (Vercel Blob) for uploads such as documents and photos | All Service data in transit; uploaded files; request logs |
| Neon | Managed PostgreSQL database | Account information and Customer content stored in the database |
| Anthropic | AI models — only when AI is enabled for your account | The content of each AI request |
Some pages also load content directly from third parties. When your browser requests it, that party receives your IP address and browser information:
| Third party | What loads, and where |
|---|---|
| Google Fonts, rsms.me | Web fonts on the website and in the app |
| YouTube (Google) | The tutorial video on the home page. Its preview image loads from i.ytimg.com with the page; the YouTube player loads only when you press play. |
| Vercel Blob | The home page background video, and uploaded files such as documents and photos (see Vercel above) |
| cdnjs (Cloudflare) | PDF.js, to read PDFs in QC Data Intake and Plan Takeoff |
| jsDelivr | Tesseract.js and its English language data (photo text recognition), heic-to (iPhone HEIC photos) and UTIF (TIFF images), in QC Data Intake |
| unpkg | Leaflet, the map library on the Control Center map |
| Esri (ArcGIS Online) | Map tiles on the Control Center map |
| Photon by Komoot | Address search on the Control Center map; it receives the address text you search for |
Each script library is pinned to an exact version, and our content security policy blocks scripts from any other host. Files you open in QC Data Intake are read in your browser; the libraries above are downloaded, but your files are not sent to those hosts. The Bid History pages are served by a companion RBCopilot service hosted on Vercel.
Our providers may process information in the United States and other countries where they operate.
6. Cookies and local storage
RBCopilot does not use advertising or analytics cookies. The platform uses your browser's local storage and session storage to work:
| Item | Purpose |
|---|---|
rcc_token | Your signed session token, so you stay signed in. It expires on its own; signing out removes it. |
| User and company profile | Your name, role and company name for display, saved at sign-in. |
rcc_lang | Your language choice (English or Español). |
| Active project | The project you last opened, so pages open on it. |
rcc_active (session) | Marks that you signed in during this browser session. |
Signing out clears the platform's local storage in that browser. The RBCopilot Field app also stores reports, photos and queued changes on the device so it can work offline; that data is sent to your company's workspace when the device syncs.
7. When we share information
- Within your company's workspace, according to the roles your administrators assign.
- With service providers listed above, to run the Service.
- With systems you connect, such as the RBCopilot Field service or an asphalt plant system, when your team sets up that connection.
- For legal reasons, when required by law or valid legal process, or to protect the rights, safety and security of our customers, users or the Service.
- In a business transfer, such as a merger or acquisition, subject to this policy.
8. Retention and deletion
We keep Customer content for as long as the Customer's account is active, so the project record stays complete. Some records are protected on purpose — for example, the audit log is kept even if a project is deleted, and projects with submitted, approved or paid pay estimates can't be deleted.
An authorized administrator of a Customer account can ask us to export or delete the company's data. We delete data on request or after the account ends, as described in our Terms, except where we must keep information to comply with law or resolve disputes. Demo and contact requests can be deleted on request.
9. Security
We protect information with company-level isolation, role-based access, bcrypt password hashing, optional two-factor sign-in, HTTPS with HSTS, field-level encryption of sensitive text and an audit trail. Details are on our Security page. No system is perfectly secure; please tell us right away if you believe your account has been compromised.
10. Your rights and choices
Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal information, and to object to or restrict certain processing. To make a request, contact us at the address below. If your information is in the Service because of your employer or a project you were invited to, we may refer your request to that organization, since it controls that data. We won't discriminate against you for exercising your rights. You can avoid AI processing entirely by not enabling AI features.
11. Children
The Service is built for businesses and is not directed to children. We don't knowingly collect personal information from anyone under 16.
12. Changes to this policy
We may update this policy as the Service changes. The "Last updated" date shows the current version. For material changes we will notify account administrators before they take effect.
13. Contact
Privacy questions and requests: support@rbcopilot.com (subject "Privacy request"), or use our contact form. Ununpentiums Labs, South Carolina, USA.