Privacy Policy

1. Scope and who we are

This Privacy Policy explains how Ready Mix Connect ("RMC," "Ready Mix Connect," "we," "us," or "our") accesses, collects, uses, shares, retains, and protects information when you use the Ready Mix Connect mobile application, Administration Portal, website, and related services (collectively, the "Services").

RMC is designed for business use by ready-mix fleets, broker fleets, owner-operators, plant organizations, administrators, mechanics, drivers, and other authorized organization members. In many cases, your organization controls the work records entered into RMC and determines who is permitted to access them.

Privacy questions may be sent to support@readymixconnect.com.

2. Information we collect

Account, identity, and organization information

We may collect your name, phone number, email address, authentication identifiers, profile information, organization membership, role, permissions, invitation/onboarding status, and other information needed to create, secure, and administer your RMC access.

Scheduling and work records

RMC may process schedules, plant assignments, schedule groups, call times, truck assignments, driver acknowledgments, shift status, timesheets, haul information, washout information, retained-material records, remarks, and related operational history.

Delivery tickets, documents, and images

Drivers and authorized users may capture or upload delivery-ticket images and other work-related documents. RMC may process document images and recognized text to extract fields such as ticket number, quantity, customer, product or material information, order information, and other load details. Ticket OCR is used to assist the user and the resulting information can be reviewed or corrected before it becomes part of the work record.

DVIRs, inspections, signatures, and fleet records

RMC may collect vehicle inspection reports, inspection answers, defects, maintenance requests and records, truck status, mileage, engine hours, registration and certification information, photos, remarks, and electronic signatures used on driver documents.

Location information

When location features are enabled and permission is granted, RMC may collect precise device location. During an active driver shift, location reporting can continue while the application is in the background or the device is locked so authorized operational users can view the active shift and driver location. RMC uses this information for active-shift operations, dispatch visibility, maps, navigation-related features, plant/jobsite context, and safety/coordination features. Active-shift location reporting is designed to stop when the active shift ends.

Camera, photos, and files

RMC may request camera, photo-library, or file access when you choose to scan or attach delivery tickets, inspection evidence, maintenance photos, or other operational documents. We use that access for the feature you selected.

Microphone and Push-to-Talk

RMC may request microphone permission when you use Push-to-Talk (PTT). Microphone audio is transmitted to authorized participants in the applicable live schedule channel through our real-time communications infrastructure. The current PTT experience is designed for live operational communication rather than as a general-purpose audio recording archive.

Messages, announcements, and notifications

We process direct messages, schedule-chat content, announcements, acknowledgments, notification preferences, push-notification tokens, and related delivery/read status so authorized users can communicate and receive operational updates.

Device, security, and diagnostics information

We may process device and application information such as app version, operating system, device identifiers used by platform services, push tokens, app-integrity/security signals, crash reports, performance diagnostics, error context, and account or organization identifiers associated with a diagnostic event. We use this information to secure, troubleshoot, and improve RMC.

Website and demo-request information

If you request a demo or contact us through readymixconnect.com, we may collect the information you submit, such as your name, company, email, phone number, and message. Our website also uses a hashed representation of a requesting IP address for short-term abuse and rate-limit protection.

3. How we use information

• Provide and administer accounts, organization access, roles, and permissions.
• Create, publish, update, and communicate schedules and assignments.
• Support driver shift workflows, maps, active-shift location, navigation context, and dispatch visibility.
• Create and manage timesheets, haul sheets, delivery-ticket records, DVIRs, inspections, maintenance records, and related documents.
• Provide PTT, messaging, announcements, push notifications, and acknowledgments.
• Prevent unauthorized access, verify application integrity, detect abuse, and protect the Services.
• Diagnose crashes and technical problems, provide customer support, and improve reliability and usability.
• Respond to demo requests, support inquiries, privacy requests, and other communications.
• Comply with applicable legal, regulatory, contractual, and recordkeeping obligations.

4. When information is shared

We do not sell personal information and we do not share personal information for third-party behavioral advertising.

Information may be shared in the following circumstances:

• Your organization and authorized partners. Work records may be visible to authorized owners, administrators, dispatchers, mechanics, drivers, plant contacts, broker/fleet partners, or owner-operators when that access is required by the RMC workflow and the applicable organization relationship or permission.
• Google/Firebase services. We use Firebase and related Google services for authentication, databases, file storage, server functions, push messaging, app integrity, crash diagnostics, hosting, and other infrastructure.
• Maps and navigation providers. Map, geocoding, address, or navigation features may send location or destination information to the map/navigation service used for that feature.
• LiveKit. We use LiveKit infrastructure to provide real-time PTT communications. Channel connection information and live audio are processed as needed to provide that service.
• Email and communications providers. We use service providers to deliver onboarding, support, demo-request, and operational communications.
• Legal and safety reasons. We may disclose information when we reasonably believe disclosure is required by law, legal process, or to protect users, organizations, RMC, or the public from fraud, abuse, security threats, or harm.
• Business transfers. If RMC is involved in a merger, acquisition, financing, reorganization, or sale of assets, information may be transferred subject to appropriate confidentiality and legal protections.

5. Data security

We use technical and organizational safeguards intended to protect personal and operational data. These include authenticated access, organization and role-based authorization, encrypted network transport, managed cloud infrastructure, application-integrity controls, access logging/diagnostics, and restricted administrative access. No method of electronic storage or transmission can be guaranteed to be completely secure, but we work to use safeguards appropriate to the nature of the data and the Services.

6. Data retention

We retain information for as long as reasonably necessary to provide the Services, maintain organization and operational records, meet legal or regulatory obligations, resolve disputes, enforce agreements, prevent abuse, and support legitimate business recordkeeping.

Some records created through RMC—such as timesheets, DVIRs, inspections, maintenance history, schedule history, and other fleet or employment-related records—may be organization business records that must remain available after an individual user's access ends. When appropriate, personal account information can be removed or de-identified while required operational records are retained.

Diagnostic and security records may be retained for shorter periods appropriate to troubleshooting, security, fraud prevention, and service reliability. Backup copies may persist for a limited period after deletion as part of normal backup and disaster-recovery processes.

7. Account and data deletion

You may request deletion of your RMC account and associated personal data through the in-app account/privacy controls or through our external account-deletion page at readymixconnect.com/delete-account.

When we verify and process an account-deletion request, we delete or de-identify personal information associated with the account except information we must retain for legitimate legal, regulatory, security, fraud-prevention, contractual, or business-recordkeeping reasons. Organization-owned operational records may be preserved where required, with account identity removed or minimized when appropriate.

Making a user inactive in an organization is not the same as deleting the user's RMC account. Inactive status preserves the account and applicable records while preventing organization access until an authorized administrator reactivates it.

8. Your choices and controls

Depending on your role and device, you can control certain permissions and preferences through RMC or your device settings, including notification, microphone, camera/photo, and location permissions. Disabling a permission may prevent the related feature from working.

You can also ask us to review, correct, or delete personal information by contacting support@readymixconnect.com. Organization-controlled work records may also need to be handled through your employer, fleet, broker, or other organization administrator.

9. Children

Ready Mix Connect is a business operations product and is not directed to children. The Services are intended for authorized business users who are legally permitted to perform their assigned work and use the applicable organization systems.

10. Changes to this policy

We may update this Privacy Policy as RMC evolves or as legal and platform requirements change. When we make material changes, we will update the effective date and may provide additional notice through the Services when appropriate.

11. Contact

For privacy questions, requests, or concerns:

Ready Mix Connect
Email: support@readymixconnect.com
Website: readymixconnect.com