the Service

Privacy Policy

Effective September 20, 2026

1. Who we are and what this policy covers

the Service is a recruiting and applicant-tracking service for trucking and transportation companies ("carriers"), operated by [operator name not configured] ("we", "us"). Carriers use it to receive job applications from drivers, communicate with applicants, order background reports the law requires, and manage hiring.

This policy explains what information the service handles, where it comes from, how it is used and shared, and the choices you have. It covers:

  • Carrier users — recruiters and other staff who sign in to the service;
  • Applicants — drivers who apply to a carrier, contact a carrier, or are contacted by one;
  • People who message a carrier on Facebook Messenger or Instagram, where the carrier has connected those channels.

For an applicant's information, the carrier you applied to decides why and how it is used; we process it on that carrier's behalf, as its service provider. Questions about a particular application are best sent to that carrier, and we will help the carrier answer them.

2. Information we handle

Carrier users

  • Name, e-mail address, job title and phone number, and the company and role of each account.
  • A password, stored only as a salted one-way hash — we cannot read it.
  • Sign-in sessions: a random session identifier (stored only as a hash), when it was created and last used, and the browser's user-agent string.
  • The internet address of a sign-in attempt, held briefly in memory to limit repeated attempts. It is not stored.
  • A record of actions taken in the service, such as who changed an applicant's status, placed a call or sent a message.

Applicants

  • Contact details: name, phone number, e-mail address, and mailing address and address history.
  • What a driver application requires under U.S. Department of Transportation rules: date of birth, Social Security number, driver's license details and endorsements, driving experience, employment history, accidents and traffic violations, and answers to the carrier's questions.
  • Consents and signatures: which disclosure was accepted and its version, when, and the internet address and browser it was accepted from.
  • The job applied for, where the application came from (for example a website form or a Facebook lead form), and the carrier's notes and hiring decisions.
  • Reports a carrier orders with the applicant's authorization — motor vehicle records and FMCSA Pre-Employment Screening Program (PSP) reports — and the status of those orders.
  • Communications: records of phone calls between the carrier and the applicant (numbers, time, duration, outcome) and, where the carrier's phone system records and transcribes calls, the transcript and an automated summary; and messages exchanged with the carrier on connected channels.

Information from Facebook and Instagram (Meta)

When a carrier connects its Facebook account to the service, and only with the permissions that carrier grants, we receive from Meta:

  • The name and Facebook user ID of the person who connected, the list of permissions granted, and access tokens for that person and for the Facebook Pages they choose to connect.
  • The names and IDs of those Pages, the lead forms on them, and the Instagram professional account linked to a Page.
  • Lead form submissions: the answers a person gave on the carrier's Facebook or Instagram lead form (such as name, phone number, e-mail, location and experience), which become an application with that carrier.
  • Messages: where the carrier has switched on Messenger or Instagram messaging, the messages people send to the carrier's Page or Instagram account and the carrier's replies, the sender's Page-scoped or Instagram-scoped ID, the type of any attachment, and the sender's name when Meta provides it.

We use this information only to provide the service to that carrier: to show its leads and conversations to its own staff, to let them reply, and to keep the connection working. We do not use information from Meta for advertising, do not sell it, do not combine it across carriers, and do not use it to build profiles of people for any other purpose.

Cookies

The service uses one essential cookie, which keeps a signed-in user signed in; it holds a random identifier and nothing about you, and is not readable by scripts. Your light or dark theme choice is remembered in your browser. We do not use advertising or analytics cookies or third-party trackers.

3. Where the information comes from

  • Directly from you — when you fill in an application, sign a consent, or use the service as a carrier user.
  • From the carrier — for example a recruiter entering or correcting an applicant's details.
  • From Meta — lead form submissions and messages, as described above.
  • From report providers — the results of reports a carrier orders with the applicant's authorization.
  • From the carrier's phone system — call records, transcripts and summaries, where the carrier has connected it.

4. How the information is used

  • To receive, review and process job applications, and to let carriers meet their driver-qualification obligations under federal regulations.
  • To let carriers and applicants communicate — by phone and on the channels the carrier has connected.
  • To order and deliver the reports a carrier requests with the applicant's authorization.
  • To sign users in, keep accounts secure, prevent abuse, and keep a record of who did what.
  • To operate, maintain and fix the service, and to comply with the law.

We do not sell personal information, and we do not use it to make automated hiring decisions: hiring decisions are made by the carrier's people.

5. Who the information is shared with

  • The carrier you applied to or contacted. Each carrier sees only its own applicants, leads and conversations; carriers are kept separate from one another.
  • Report providers, at the carrier's request and with the applicant's authorization — the FMCSA Pre-Employment Screening Program, and a motor vehicle record provider. They receive what the report requires, such as name, date of birth and driver's license number. A Social Security number is not sent to order these reports.
  • Meta — when a carrier replies to a person on Messenger or Instagram, the reply is delivered through Meta. Use of Facebook and Instagram is also subject to Meta's own privacy policy.
  • The carrier's own phone system — when a recruiter places a call from the service, the applicant's phone number is passed to the phone system the carrier connected.
  • Service providers that host and run the service for us, under obligations to protect the information and use it only for that purpose.
  • Authorities and others where the law requires it, or to protect the rights, safety and security of people and of the service; and a successor, if the business is reorganized or sold, under this policy's commitments.

6. How the information is protected

  • Connections to the service are encrypted in transit (HTTPS).
  • Sensitive items are additionally encrypted within the database: Social Security numbers, access tokens and keys for connected services, report contents, call transcripts and summaries, and the content of messages. A Social Security number is shown to carrier users only as its last four digits.
  • Passwords are stored as salted one-way hashes; sign-in attempts are rate-limited; sessions end when a user signs out or an account is deactivated.
  • Each carrier's data is separated from every other carrier's at the database level, and access within a carrier depends on the user's role.
  • Sensitive values such as Social Security numbers, passwords, tokens and message contents are kept out of system logs.

No system is perfectly secure. If we learn of a breach affecting your information, we will notify the affected carrier and, where the law requires, you.

7. How long the information is kept

Applicant information is kept for as long as the carrier keeps its account and needs the information — including the periods for which federal regulations require carriers to keep driver qualification and application records — and is then deleted or de-identified. Access tokens for a connected service are deleted when the carrier disconnects it. Sign-in sessions expire after fourteen days. Information is deleted earlier on a valid request, as described below, unless the law requires it to be kept.

8. Your choices and rights

  • Applicants may ask to see, correct or delete their information. Because the carrier you applied to controls it, please contact that carrier; you may also contact us and we will pass your request to the carrier and help carry it out.
  • People who messaged a carrier on Facebook or Instagram, or submitted a lead form, may ask for that information to be deleted — see the Data Deletion Instructions.
  • Carrier users may ask their company's administrator, or us, to correct or deactivate their account. A carrier can disconnect Facebook, Instagram, or any other connected service at any time in Settings, which stops new information from arriving and deletes the stored access tokens.
  • Depending on where you live, you may have further rights under local law — for example to know what is held about you, to have it corrected or deleted, to object to or limit certain uses, and not to be treated unfairly for using these rights. We honour such requests as the law requires and will confirm your identity before acting on one.

9. Children

The service is for employment in commercial driving and is not directed to anyone under 18. We do not knowingly collect information from children.

10. Changes to this policy

We may update this policy as the service changes. The date at the top shows when it last changed; if a change is significant we will tell carriers before it takes effect.

11. Contact

Questions about this policy, or a request about your information:

[operator name not configured]
[contact e-mail not configured]