Skip to content
Coreway
Features Driver app Pricing Demo Support
Español Sign in Start free trial
  • Features
  • Dispatch management
  • Driver app
  • Billing and settlements
  • Pricing
  • Integrations
  • Demo
  • How it works
  • About
  • Support
  • Sign in
  • Start free trial
  • Español

Privacy Policy

Last updated: October 14, 2026 · Coreway home

1. Who we are and what this policy covers

This Privacy Policy explains how personal information is handled in Coreway.

  • “Coreway” is the truck-load dispatch service described on this website. It includes the Portal, the App and this website.
  • “We”, “us”, “our” or “Luxeran” means LUXERAN LLC, a Florida limited liability company based in Tampa, Florida, USA. We operate Coreway and publish this website.
  • “Agency” means the dispatch business that is our customer and uses Coreway to run its loads.
  • “Authorized User” means a member of an Agency’s staff (for example a dispatcher, manager or accounting person) who uses the Portal.
  • “Driver” means a truck driver who uses the App after being invited by an Agency.
  • “Portal” means the dispatcher web application at app.corewaydispatch.com.
  • “App” means the Coreway driver app for Android and iOS (package and bundle ID com.luxeranlabs.coreway).

This policy covers the Portal, the App and corewaydispatch.com. It does not cover the websites or services of third parties, such as load boards, brokers or carriers, even when their names or documents appear inside Coreway.

Coreway is a business service. An Agency decides which people and records it puts into Coreway. For the records an Agency manages, we act on the Agency’s behalf as its service provider. For accounts, security and the operation of Coreway itself, we decide how personal information is used, and this policy describes that use.

2. Personal information we collect

The table below lists the categories of personal information we collect. The category names follow the Google Play Data safety section and the Apple App Store privacy labels. All of it is linked to the person’s account. None of it is used to track people across other companies’ apps or websites.

Category What it includes Who it concerns
Contact info Name, email address, phone number Authorized Users, Drivers, contacts at carriers, owners and brokers
Identifiers Account ID, invite codes, push notification token, device platform and app version Authorized Users, Drivers
Account and sign-in data Password (stored only as a hash) or your Google or Apple sign-in identity, preferred language, role and Agency membership Authorized Users, Drivers
Financial info (earnings) Pay plans, per-load pay, quick-pay requests and pay dates Drivers
Business records Legal names, MC and DOT numbers, EIN, contact details, credit checks, incidents, invoices, payments, receivables and collection events Carriers, owners and brokers, which may include individuals doing business under their own name
User content Rate confirmation PDFs, proof of delivery (POD) and bill of lading (BOL) photos and PDFs, and reasons given when rejecting a load. Chat messages between a Driver and their Agency’s office: the text, photo or PDF attachments of up to 10 MB each, the sender’s name, the time, the load a message refers to, if any, and when each side last read the thread Authorized Users, Drivers
Location Pickup and delivery addresses and stop details for each load. If the Driver allows it: the precise location of the Driver’s phone (latitude, longitude, accuracy and time), up to about every two minutes, including when the App is in the background, only while the Driver has a load they have accepted and not yet delivered, and at each stop arrival and departure. Also, when the Driver’s dispatcher asks where the truck is and the Driver taps Share, one position at that moment Drivers
App activity Loads accepted or rejected, arrival and departure stamps at each stop, times, and an activity log of actions taken in the Portal Authorized Users, Drivers
Technical and security data IP addresses and request logs, used for security and to keep the service running Everyone who uses the Portal or the App
Diagnostics None. We do not use crash analytics or performance analytics SDKs Not applicable

We do not collect contacts, biometric data, advertising IDs, browsing history or SMS messages. The App keeps on your device: your language preference, your sign-in session, whether you have already seen the location explanation, map images kept by the map for faster loading, and any POD or BOL document or chat message (with its attachment) that is waiting to be sent, plus the technical data its components need to work, such as the push notification token. Each document or message is deleted from the device as soon as it is sent. Signing out or deleting your account ends the session and discards any POD or BOL document and any chat message still waiting to be sent: they are deleted from the phone and are not sent to your Agency (one that was already being sent at that moment may still arrive). Before you sign out, the App warns you if any are waiting. Your language preference stays on the phone until you uninstall the App or clear its storage in your phone settings.

Device permissions in the App

The App asks for device permissions only when a feature needs them:

  • Camera and photos: to capture or pick POD, BOL and other load documents, and to take or pick a photo to send in the chat with your Agency’s office. Only the photos you choose are sent.
  • Notifications: to tell you about new assignments and changes to your loads.
  • Location (“while using the app” only): to share your position with your Agency while you have a load you have accepted and not yet delivered. Before asking, the App explains this on a screen titled “Share your location with your office?”. On Android a visible notification stays on screen while location is shared in the background; on iOS the location indicator shows in the status bar. The App never asks for “all the time” access. When your dispatcher asks where you are, and only if you tap Share, the app sends your position once.

You can refuse or withdraw any permission in your device settings. Some features will not work without it.

3. Where the information comes from

  • From you, when you sign in, complete your profile, stamp a stop, upload a document or send a message.
  • From your Agency, when an Authorized User creates your account or invitation, assigns you to a truck or load, records pay, or enters business records about carriers, owners and brokers.
  • From your device, such as the push token, platform, app version and, if you allow it, location.
  • From sign-in providers, when you choose to sign in with Google or Apple. We receive your name, your email address and an account identifier, and from Google also the link to your Google profile photo, which the App shows as your picture.
  • Automatically, such as IP addresses and request logs when you use the Portal or the App.

4. How we use personal information

We use personal information only to:

  • Provide Coreway: create and assign loads, move them through pickup and delivery, store documents, and keep pay and billing records.
  • Create, secure and sign in to accounts, and send invitations, sign-in links and password recovery emails.
  • Deliver chat messages between a Driver and their Agency’s office.
  • Send push notifications and transactional emails about loads, accounts and the service.
  • Show a Driver’s position to their Agency while the Driver has a load they have accepted and not yet delivered, if the Driver allows location. Show one position to the Agency when its dispatcher asks where the truck is and the Driver taps Share, so the dispatcher can search for loads near the truck. We do not use location for anything else.
  • Bill Agencies for the service.
  • Provide support and answer requests.
  • Keep the service secure, detect and prevent fraud or abuse, and investigate incidents.
  • Keep the service running and fix problems.
  • Comply with the law and enforce our Terms of Service.

We do not use personal information for advertising. We do not build profiles of people to make decisions with legal or similarly significant effects.

5. No sale, no sharing for advertising, no tracking

  • We do not sell personal information.
  • We do not share personal information for cross-context behavioral advertising.
  • We do not use personal information for targeted advertising.
  • The App contains no advertising SDKs and no analytics SDKs.
  • This website sets no cookies and runs no analytics or tracking scripts.

6. Who receives personal information

Your Agency

When an Agency invites you, that Agency receives the information you put into Coreway for its loads, including stops, stamps, documents, earnings, the chat messages you exchange with its office and, if you allow it, location. The Agency decides which of its Authorized Users can see it. The Agency is responsible for its own use of that information.

Service providers

We use the service providers below to run Coreway. They process personal information on our instructions and only to provide their service to us.

Provider Role Location
Hostinger Server hosting for the Coreway database, files and backend Servers in the USA (Hostinger is headquartered in the EU)
Cloudflare DNS, content delivery, network protection, and hosting for this website USA
Grafana Cloud (Grafana Labs) Service logs and metrics used to operate and secure Coreway, when we enable this monitoring (not active today) USA
Resend Sending transactional email from mail.corewaydispatch.com USA
Google Firebase Cloud Messaging Delivering push notifications to Android devices USA
Apple Push Notification service Delivering push notifications to iOS devices USA
Google Sign-In Signing in with a Google account, when you choose it USA
Sign in with Apple Signing in with an Apple account, when you choose it USA
Let’s Encrypt Issuing the TLS certificates that encrypt connections USA
Mapbox Maps in the App and in the Portal. Receives the device’s IP address and the map area on screen when map images load. In the App that area covers the stops of a load and, when the Driver centers the map on himself, his own position. In the Portal that area can include a Driver’s last reported position. Mapbox usage telemetry is turned off in the App, and the Portal loads only map images USA
Komoot (Photon address search, OpenStreetMap data) Address search in the Portal and, when a Driver shares one position on request and the phone did not name the city, a lookup of the nearest city for that position, rounded to about 110 meters (three decimals). Receives the address text a dispatcher types or that rounded position, a fixed hint of the Agency’s region, and the dispatcher’s IP address. Never receives a Driver’s name or account, and never the positions sent while a load is in progress Germany
Stripe Payment processing for Agency billing, once billing starts (not active today) USA

DAT is not connected to Coreway. An Agency’s administrator can connect a carrier’s Truckstop account to search Truckstop’s load board from the Portal for that carrier’s trucks: Coreway then sends Truckstop the searches its dispatchers run (origin and destination city and state, distances, dates, equipment, load type and posting age) and receives the matching postings. Coreway never sends Truckstop a Driver’s name, account or GPS position.

Other disclosures

We may also disclose personal information:

  • When required by law, subpoena or court order, or to respond to lawful requests from public authorities.
  • To protect the rights, property or safety of Luxeran, our customers, users or the public.
  • To a buyer or successor if Luxeran is involved in a merger, acquisition or sale of assets, subject to this policy.

7. How long we keep it

Data How long
Account data (sign-in, profile, role, Agency membership) While the account exists. When you delete your account in the App it is deleted at once; after an email request, within 30 days. What remains is an anonymous, disabled record with an internal identifier and dates, and your Agency membership, marked inactive
Business records: loads, stops, rate confirmations, POD and BOL documents, pay records, invoices and ledgers Kept by the Agency and by us as required by law and for the Agency’s business records, typically up to 7 years
Chat messages and their attachments Kept with the Agency’s business records, like loads and documents. Coreway does not delete them automatically today. When a person deletes their account, the messages they sent stay with the Agency and the sender name saved with them is removed
Push notification tokens While the account exists. Signing out of the App revokes its token, and we stop sending notifications to that device
Driver location reports Deleted automatically 90 days after they are recorded. Deleted at once if the Driver deletes their account. The position saved with a stop arrival or departure stays with the load, like the stamp time
Position shared on request A position you share on request is kept 7 days, then deleted. The record that a request was made and answered (without the position) is kept 30 days. Both are deleted when you delete your account. The city and state of a position you share can stay as the starting point of your dispatcher’s saved load search until your dispatcher changes it or deletes the search, also after you delete your account. That record holds the city, the state and the time you shared it, never coordinates, and is sent to Truckstop only as the origin of that search.
Service logs Kept for at least 15 days, then deleted automatically, within about 5 weeks
Database backups Up to 16 days, then deleted automatically. Data deleted from Coreway can remain in a backup until that backup expires. Backups are stored on our own server, not with a separate backup provider
Security records (sign-in events and administrative actions, which can include IP addresses) As long as needed for security and fraud prevention. The server’s firewall and remote-access logs, which include IP addresses, are deleted automatically within about 5 weeks. When you delete your account, your email and IP address are removed from the sign-in records
Terms acceptance records (account id, document, version, date, Portal or App, language) Kept after the account is deleted, as proof of the agreement. They hold no email or IP address

When a retention period ends, we delete the data or remove its link to the person. See also Delete your account.

8. How we protect it

We use administrative, technical and physical measures suited to the information we hold, including:

  • Encryption in transit with TLS for every connection to the Portal, the App and this website.
  • Stored data and documents live on a server we control. The database and the document storage are not reachable from the public internet except through the service.
  • Row-level access controls in the database, so each Agency and each user sees only the records they are allowed to see.
  • Least-privilege roles for our own services and staff.
  • Private storage for documents such as POD and BOL files and for chat attachments.

No system is perfectly secure. If we learn of a security incident that affects your personal information, we will notify you and your Agency as the law requires.

9. Your US state privacy rights

Depending on the state where you live, you may have some or all of these rights:

  • Know and access: ask what personal information we have about you and get a copy.
  • Correct: ask us to fix inaccurate personal information.
  • Delete: ask us to delete personal information about you.
  • Portability: receive your personal information in a portable format.
  • Opt out: of the sale of personal information, of sharing for cross-context behavioral advertising, of targeted advertising and of profiling. We do none of these, so there is nothing to opt out of, but you may still send the request.
  • Limit the use of sensitive personal information: precise location and account sign-in data are sensitive under some state laws. We collect precise location only with your permission, and we use these data only to provide Coreway and keep it secure. You can withdraw your permission for location at any time.
  • Non-discrimination: we will not treat you differently for using your rights.
  • Appeal: if we decline your request, you can appeal our decision.

Many of these rights depend on your state of residence and on exceptions in the law. Some rights apply differently to information we process for an Agency. In those cases we may refer your request to the Agency or help the Agency respond.

How to use your rights

  • Email [email protected] with the subject “Privacy request” and tell us what you want.
  • Or use the in-app option where available: the Account tab, then Delete account (App version 1.0.5 and later).

Verification. We verify requests by replying to the email address on the account. We may ask for more information if we cannot confirm who you are. We use that information only to verify the request.

Authorized agents. You may use an authorized agent. We may ask the agent for proof that you gave them permission, and we may ask you to confirm your identity with us directly.

Response time. We respond within 45 days. If we need more time, we may extend this once by up to 45 more days and will tell you why.

Appeals. To appeal a decision, reply to our answer or email [email protected] with the subject “Privacy appeal”. We will answer within the time the law of your state requires. If you are not satisfied with the result, you may contact your state attorney general.

Global Privacy Control. We honor Global Privacy Control (GPC) signals as a valid request to opt out of sale and sharing, even though we do not sell or share personal information.

See also Your Privacy Choices.

10. Notice for Drivers

  • Your Agency invited you. Your App account exists because an Agency invited you with an invite code. That Agency is the one you work with in Coreway.
  • What your Agency sees. Your Agency sees the loads assigned to you, your stops and the arrival and departure stamps you mark, the documents you upload, your earnings records and, if you allow it, your location while you have a load you have accepted and not yet delivered. Inside the Agency, only its administrators, managers and the dispatchers assigned to your carrier can see your location. Accounting staff, brokers, other Drivers and other Agencies cannot.
  • Location is limited. Location is sent only while you have a load you have accepted and not yet delivered: from the moment you accept it, through pickup and transit, until delivery. It stops when the load is delivered, canceled, reassigned to another driver or removed from you by the office, when you sign out, and when you close the App by swiping it away. Using other apps or locking the phone does not stop it. A load you have only been offered never sends location. Nothing is shared when you have no load in progress. The one exception is a location request: when your dispatcher asks where you are, and only if you tap Share, the app sends your position once. If you tap Not now, or you do not answer within the time shown, no position is sent. On Android a visible notification is shown while it is shared in the background; on iOS the location indicator shows in the status bar.
  • Turning location off. There is no separate switch in the App or in your Agency’s settings: the location permission is the only control. You can turn location off at any time by removing the permission in your device settings (on Android: Settings, Apps, Coreway, Permissions; on iOS: Settings, Coreway, Location). The “My location” row on the App’s Home screen shows whether your location is being shared, and tapping it helps you turn the permission on. Without the permission the App keeps working normally; your Agency sees that no live location is available and may call you instead.
  • How long location is kept. Location reports are deleted automatically 90 days after they are recorded, and can remain in database backups for up to 16 more days. The position recorded with a stop arrival or departure is part of that stop’s record and is kept with the load, like the stamp time. If you delete your account, your location reports are deleted at once. A position you share on request is kept 7 days, then deleted. The record that a request was made and answered (without the position) is kept 30 days. Both are deleted when you delete your account. The city and state of a position you share can stay as the starting point of your dispatcher’s saved load search until your dispatcher changes it or deletes the search, also after you delete your account. That record holds the city, the state and the time you shared it, never coordinates, and is sent to Truckstop only as the origin of that search.
  • Chat with your office. Messages and attachments you exchange with your Agency’s office are stored on the server that runs Coreway (see section 6), in its database and in private file storage. Inside the Agency, only its administrators, managers and the dispatchers assigned to your carrier can read them. Accounting staff, brokers, other Drivers and other Agencies cannot. The messages are part of the Agency’s records: if the Agency removes you as a Driver, you can no longer open the conversation, and its administrators and managers can still read its history. If you delete your account, your messages stay with the Agency. The sender name saved with each message you sent is removed, but the conversation stays linked to the driver record the Agency keeps for you, which shows the name the Agency entered.
  • Safe driving. Never use the App while driving. See our Terms of Service.

11. Children

Coreway is for adults 18 years of age or older. We do not knowingly collect personal information from anyone under 18. If you believe a person under 18 has given us personal information, email [email protected] and we will delete it.

12. Push notifications

The App sends push notifications about assignments, load changes, new chat messages from your office and your account. A chat notification shows the sender’s name. It never contains the message text or its attachments. You can turn them off at any time in your device settings. If you do, you may not learn about new assignments until you open the App. Signing out of the App revokes its push token, so we stop sending notifications to that device. The revoked token is deleted together with your account.

13. Email

We send transactional emails only, such as invitations, sign-in links, password recovery and messages about your account or loads. We do not keep marketing lists at this time. If we ever send marketing email, it will comply with the CAN-SPAM Act, identify LUXERAN LLC as the sender with our location in Tampa, Florida, USA, and include a way to unsubscribe. For any question about our emails, contact [email protected].

14. Text messages

We do not send SMS text messages.

15. Where the service is offered

Coreway is intended for use in the United States. If you use it from another country, your information will be processed where we and our service providers operate, as described in section 6.

16. Changes to this policy

We may update this policy. We will post the new version on this page with a new “Last updated” date. If a change is material, we will also give notice in the Portal, in the App or by email before it takes effect.

17. Contact

LUXERAN LLC
Tampa, Florida, USA
Email: [email protected]

Coreway

Dispatch software for US agencies.

LUXERAN LLC · Tampa, Florida, USA

Product

  • Features
  • Dispatch management
  • Driver app
  • Billing and settlements
  • Pricing
  • Integrations
  • Demo
  • How it works
  • Sign in
  • Start free trial

Company

  • About Coreway
  • Support
  • [email protected]
  • Support: Monday to Friday, 9:00 to 17:00 US Eastern

Legal

  • Privacy Policy
  • Terms of Service
  • Your Privacy Choices
  • Delete your account
  • Accessibility
  • Support

© 2026 LUXERAN LLC · Tampa, Florida · [email protected]

English is the controlling version of the legal pages. Español