1. Program information and the parties' roles
Business customers may provide driver or employee contacts, vehicle details, pickup and delivery information, storage instructions and other program records. Processing may include receipt, storage, routing, operational coordination, reporting and related business administration.
Legal roles depend on the activity and applicable law. CLR may follow a customer's instructions for an agreed program while separately determining the use of records needed for its own billing, security, insurance or legal obligations. These roles must not be assumed to be identical for every record or jurisdiction.
2. Authorized instructions and confidential information
Customers should provide information they are authorized to disclose, identify material restrictions and use agreed channels for confidential records. Send only information needed for the work. Tell CLR if a contact, authorization, handoff instruction or access permission changes.
Any existing nondisclosure agreement remains effective for the information it covers. Submitting an inquiry does not make private program information public or authorize its use as a testimonial, reference or marketing example. Contact CLR before sending restricted records through an unsuitable public form.
3. Providers, individual rights and retention
Relevant providers and service participants may need appropriate information to perform their roles. Applicable contracts and law determine permitted onward disclosure, safeguards and assistance. A request concerning a business customer's information may require coordination with that customer, while CLR remains responsible for its own obligations.
Return, export, retention and deletion depend on the records, applicable agreement and lawful preservation duties. A customer instruction does not override another person's protected rights or require unlawful deletion of records.
4. Requesting a program-specific agreement
Ask CLR to address any required data-processing addendum, security schedule, international-transfer terms or customer-specific privacy requirements before the relevant processing begins. Identify the program, data categories, people involved, purpose, locations, duration and applicable requirements so the parties can evaluate them.
This notice explains the process; it is not a pre-signed DPA, a blanket GDPR or other compliance certification, an automatic authorization of every subprocessor or a new audit commitment. Agreed terms must reflect the actual service and legal relationship.
5. Questions, requests and document updates
Contact CLR Auto Transport Corp., 8450 Whitcomb Street, Merrillville, IN 46410, at info@clrautotransport.com, 888-257-2677, or our Contact Us form. Identify the policy or issue so we can route the request.
This document supplements CLR's Privacy Policy and Terms of Use. Applicable law and accepted service agreements continue to govern their respective subjects. Updates are identified by the date shown on the page and do not retroactively change accepted service arrangements. Other policies are available in the Legal Center.