Privacy notice

1. Who we are and what this notice covers

ByteEco Inc operates this company website. This notice explains how information is handled when you browse our pages or submit freight, vehicle inspection, driver interest, government or other business inquiries. It covers the website as currently implemented, including its DEV preview.

The DEV site is for testing and asks visitors to use synthetic details. If you enter real personal information, it can still be transmitted and stored by the system. This notice does not cover a future mobile app, employee payroll, live vehicle tracking or trip paperwork uploads, which are not available on this website.

2. Information you provide

Contact details: name, email address, telephone number and, where requested, company name. Freight inquiries also include customer type, pickup and delivery ZIP codes, preferred pickup date, commodity, weight and optional notes.

Inspection requests include vehicle model/year, preferred service location and date. Driver interest forms include city, license class and driving experience or availability you choose to describe. General, government and Rigxy inquiries include a topic and your message.

We also store your chosen language, the privacy acknowledgment submitted with a form, request reference, submission and update times, and processing status. Authorized staff may add follow-up notes, assignments and a history of changes. Required fields are marked with an asterisk; without them the relevant form cannot be submitted.

Do not enter Social Security numbers, payment card or bank details, medical information, passwords, full driver-license numbers or restricted procurement information. Recruiting applicants may separately upload the front and back of their own CDL after submitting an application and providing specific insurance-verification authorization. These images contain license and identity details. Other forms do not accept attachments. Provide only information necessary for your request.

3. Technical information and browser storage

Driver applicants and contact-form visitors must verify their email with a code delivered through AWS email services before an application is saved. We keep a hashed email identifier, verification state and submission timestamps to enforce at most six driver applications and, separately, twelve contact inquiries in a rolling 365 days. Contact topics share the same limit. Codes expire after ten minutes; verification and quota records are scheduled for deletion 366 days after the latest send or application. Database deletion can occur later. This does not delete the application itself.

Your browser sends technical information needed to load the site and communicate with our hosting and API providers, such as IP address, requested URL and browser/network information. Infrastructure providers may process technical and security logs to operate the service. Our API uses a hash derived from IP address and a time window to limit excessive submissions; hashing is not a guarantee of anonymity.

A browser local-storage entry named byteeco-locale remembers English or Chinese on that browser. It is not an advertising identifier. You can change language in the page header or remove this preference by clearing site data in your browser.

The current public website does not integrate advertising pixels, third-party audience analytics or cross-site behavioral advertising. Its application code does not set advertising cookies. Infrastructure or separate staff sign-in services may use technologies necessary for delivery, security or authentication.

The public site has no separate Do Not Track or Global Privacy Control processing logic. There is no advertising-sale or cross-context behavioral-sharing feature in the current site. This describes the present implementation, not a statement that these browser signals are irrelevant under applicable law.

4. Why information is used

Information is used to review and respond to your inquiry, clarify shipment or inspection requirements, consider driver interest, coordinate business discussions, and keep a record of follow-up. It is also used to prevent duplicate or abusive submissions, investigate technical problems and control staff access.

Submitting an inquiry is not a booking, inspection confirmation or employment offer. The privacy acknowledgment records your acknowledgment of this handling of your request; it does not enroll you in marketing or waive any privacy rights. This DEV release does not send automated inquiry emails.

5. Access, service providers and disclosures

CDL images are accessible only to recruiting personnel and administrators. With the authorization recorded at upload, recruiting staff may download the images and provide them to the insurance company or authorized insurance agent handling the application for insurance verification. The website does not automatically email these images; copies provided to an insurer are handled under that recipient’s practices. Request data is handled by authorized ByteEco staff according to their role. The current backend restricts recruiting inquiries to recruiting personnel and administrators, and other business inquiries to operations personnel and administrators.

Amazon Web Services (AWS) provides website hosting, API execution, data storage and operational logging. AWS Cognito supports the separate staff sign-in system. These providers process information as part of delivering the service; hosting on AWS does not mean the information is made publicly accessible.

Information may also need to be disclosed when required by applicable law or valid legal process, or when necessary to investigate misuse and protect legal rights or system security. This site has no feature for selling inquiry data, advertising audience sharing or publishing submissions as testimonials.

6. Processing location and security

The current DEV application database and API run in AWS US East (Ohio). Website content is delivered through AWS hosting infrastructure, which can serve visitors across regions. Accessing the site from another country may involve transfer of information to the United States.

The deployment uses HTTPS, restricted backend access, role-based permissions and staff authentication configured to require multi-factor authentication. No internet transmission or storage method is completely secure. Please avoid entering sensitive information into free-text fields.

7. How long information is kept

CDL images are stored in a separate private, encrypted bucket. Application access is blocked 30 days after upload, and storage lifecycle cleanup removes expired images asynchronously. The upload authorization expires after at most 24 hours; successful uploads cannot be overwritten through that session. Upload and staff-download audit events record the application, side, actor/action and time, with a 90-day expiry. A downloaded local or insurer copy is not removed by website cleanup. Current inquiry records and staff follow-up records do not have an automatic deletion deadline. They remain in the database until an authorized manual cleanup occurs. A routine retention and deletion schedule has not yet been implemented. Please do not assume that closing an inquiry deletes its contents.

Duplicate-submission and rate-limit records are configured to expire after about 24 hours; database expiry cleanup can take longer. This expiry does not delete the underlying inquiry. Application function logs are configured for one-month retention. Database recovery backups may retain earlier data for their recovery window; these settings do not establish a single retention period for all provider logs or backups.

The language preference remains in your browser until you change it or clear the site data. Contact our team with questions about retention or to request deletion. These requests require staff review; the website does not provide automatic deletion.

8. Your choices and privacy requests

You may browse informational pages without submitting a form. You may ask ByteEco about information you previously submitted or request access, correction or deletion. Use the Contact ByteEco link below, select General business inquiry and begin your message with “Privacy request”. Include the earlier request reference, if available, and enough context to locate the record. Do not send identity documents in the form.

A request may require proportionate verification before information can be disclosed or changed. Legal recordkeeping requirements or other applicable exceptions may limit deletion. There is no self-service account export or deletion feature in the current site; requests require manual handling.

Depending on your location and whether a privacy law applies to ByteEco and the relevant processing, you may have additional rights, such as knowing what information is collected, receiving a copy, correction, deletion, or opting out of sale or certain sharing. California law provides such rights for covered businesses and circumstances. This notice does not claim that every provision of the CCPA applies to ByteEco, and does not limit rights you have under applicable law.

9. Children

The site is intended for business contacts and people seeking driving work, not children under 13. Do not submit a child’s information. If you believe a child’s information has been submitted, contact ByteEco using the privacy-request route above.

10. Other services and changes to this notice

Links to external services, including government resources or a separate product website, may lead to services with their own privacy notices. This notice covers ByteEco’s current company website and is not a privacy policy for those separate services.

When website practices change, this notice should be updated along with them. The date above identifies the latest revision. Material changes and any additional notice or consent required by applicable law must be addressed before the relevant new processing begins.

Contact ByteEco

For privacy questions or requests, use our contact form and identify your message as a privacy request. The DEV form remains a test channel; do not include sensitive identifiers.