1. The short version
- Hostler is software for carriers that haul Amazon Relay freight. Carriers (our customers) use it to schedule drivers, track safety and compliance, keep driver files, check timecards against the ELD and correct them in ADP, recruit drivers and message drivers.
- Most of the personal information in Hostler is about a customer’s own drivers, staff and job applicants. The customer is in charge of that information. We hold it and use it for the customer, under our contract, only to run Hostler for it.
- We do not sell personal information. We do not share it for advertising. We do not use it to train AI models.
- Our website sets no cookies and runs no analytics.
- The driver app does not use your location, camera, photos, contacts or microphone. (Your employer’s ELD does report the truck’s location to Hostler, section 5.4.) You can delete your login inside the app.
- Some Hostler features use AI from Anthropic. What drivers write in the driver app does not go to it. Messages in a carrier’s Slack channels can. Our AI coding tools can see customer data when we fix or build Hostler (section 9).
- Questions or requests: info@gethostler.com.
2. Who we are
Hostler (“we”) is a small business based in California. One person owns and runs it, as a sole proprietorship, under the name Hostler.
The owner’s legal name is Samer Dimes, doing business as Hostler.
Hostler was built at United Interstate Group LLC (“UIG”), an Amazon Freight Partner based in California, which still uses it every day. UIG is a customer, our first, and the rest of this policy calls it our first customer. Some features work only for it today. Some of UIG’s records are also kept on a computer in its office (section 14).
Hostler’s owner also works at UIG. UIG never sees another customer’s data, and we never use another customer’s data for UIG, including for hiring, pay or bidding for freight (section 8 has the general rule).
You can reach us at the contact details in section 20.
3. What this policy covers
This policy covers personal information we handle through:
- gethostler.com, our public website;
- the Hostler office app, which a carrier’s office staff use in a web browser;
- Hostler Assistant, our Chrome extension, which works inside the office user’s own browser;
- the Hostler driver app for iPhone and Android;
- email and demo calls with us.
It does not cover:
- The other systems a carrier connects to Hostler, such as Amazon Relay, Netradyne, J.J. Keller, Geotab, ADP, Fountain and Slack. Each of those companies has its own privacy policy, and the carrier’s own agreement with each of them applies.
- How a carrier, as an employer, handles its workers’ information outside Hostler. If you drive or work for a carrier, your employer’s own privacy notice tells you what it collects about you and why.
4. Who is in charge of what
Privacy laws treat two roles differently, so we explain both.
The carrier is in charge of information about its drivers, employees and job applicants, and of everything its staff put into Hostler or connect to it. We call this Customer Data. The carrier decides what goes in, which of its staff can see it, and how long it is kept. We are the carrier’s service provider (in some laws, its processor). We use Customer Data only to provide Hostler to that carrier, as our Terms of Service and any data processing addendum we sign with the carrier say.
If you are a driver or an employee and you want to see, fix or delete information about you, ask your employer first (section 16.6).
We are in charge of information about:
- people who visit our website, email us or book a demo;
- office users’ account details (name, work email, role and company), as far as we need them to run accounts, keep the service secure and bill;
- billing contacts;
- people who send us copyright notices or counter-notices, and the users a notice names, in our record of each notice and what we did (Copyright Policy).
5. What we collect
5.1 Website visitors
- Nothing in your browser. gethostler.com sets no cookies. It runs no analytics, no advertising trackers and no forms, and it loads nothing from other websites.
- Server logs. Vercel, which hosts the website, keeps short-lived logs of each request: your IP address, browser type, the page you asked for and the time. We use them only to keep the site running and safe, and we do not combine them with anything else.
5.2 People who book a demo or email us
- Book a demo opens a Google Calendar booking page. What you type there (your name, your email and any answers the page asks for) goes to Google, and then to us as a calendar booking. Google’s privacy policy covers what Google does with it.
- Email. Our email runs on Google Workspace. If you email us, we receive your email address, what you write and anything in your signature, such as your company and phone number.
- Why. We use this to answer you, hold the demo, set up your account and follow up about Hostler.
- Marketing email. We do not send marketing email today. If we start:
- we will send it only to people at businesses who have dealt with us or asked for it, and never to bought lists;
- every message will say honestly who it is from and what it is about, and will include our mailing address;
- every message will have an unsubscribe link that keeps working for at least 30 days, and we will honor an unsubscribe within 10 business days;
- we will keep the list of people who unsubscribed only to make sure they get nothing more, and we will never sell or share it;
- we will not send marketing text messages without your written consent.
Emails about your account, billing, security, or changes to our terms or this policy are not marketing. They still reach you after you unsubscribe from marketing.
5.3 Office users (a carrier’s staff)
- Your account: your name, work email, role (Owner, Operations Manager or Driver Team Lead) and company. Your password is stored only in scrambled form (a hash) by our sign-in provider, Supabase. Nobody at Hostler can read it.
- Sign-in records: when you sign in, from which IP address and which browser. Supabase keeps these for security.
- Invites. If someone at your company invites you, Hostler keeps the invite: your email, the name and role they gave you, who invited you and when. The invite email names your company and the role, and shows who invited you and their email address. It reaches you through our email provider (section 10.1), and its link works for 24 hours.
- Last active. Hostler records when you last used the app. Anyone with an office seat at your company can read it, and Owners and Operations Managers see it on the Team page.
- Activity record. Hostler records important actions, with who did each one and when. Owners and Operations Managers can read it, and also see who answered each driver’s request and who last changed the office phone number. Ordinary edits to a person’s record are stamped with who made them and when. The activity record covers:
- revealing or setting a Social Security number, or copying one from ADP;
- importing or exporting people, and saving or clearing the roster or the schedule;
- sharing a week with drivers;
- updates to J.J. Keller driver files;
- every step of a timecard correction, and answering a driver’s request;
- setting the office phone number drivers see;
- inviting, removing or changing the role of an office user, and turning modules on or off;
- in Messages, claiming, handing on, closing or reopening a driver’s conversation, and changing the Messages settings.
- Messages. Hostler records who in the office claims, hands on, closes or reopens each driver’s conversation in Messages, and when, and when each office user last had one open. Every office seat at your company can see this.
- What you type into Hostler: notes, schedules, messages to drivers, questions to the dispatch desk, your answers and notes on drivers’ time-off requests and timecard questions, and the office phone number drivers can call from the app. A driver sees a note you add to an answer, but never your name.
- Your Slack messages. If your company connects Slack, your own messages in the channels Hostler copies are copied too. They can be sent to our AI provider with the rest of the channel (section 9).
- On-call details. If your company lists you as on-call staff, Hostler stores your name and your Slack member ID, so it can page you in Slack when a driver needs a person.
- Desk messages through your account. If your company connects your Slack account for the dispatch desk, the desk’s messages post through that account, under your name. Every message the desk sends to a driver on its own ends with a line saying the dispatch desk sent it automatically (section 9).
- Billing details, if you start a subscription (section 5.5).
- Your browser also keeps some things on your computer (section 11).
5.4 Drivers, employees and job applicants (Customer Data)
Hostler holds only what the carrier puts in or connects, so what applies depends on the modules and connections it uses (some work only for our first customer today, section 2).
| Kind of information | Examples | Where it comes from |
|---|---|---|
| Identity and contact | Name, phone, email, home address, date of birth, employee code, payroll ID | The carrier’s own records (for example, an employee spreadsheet it imports) and its staff; ADP (name, badge and file number, when the office adds a worker from ADP or Hostler ties a People record to one); Relay’s driver list; Fountain (when the office adds a new hire to People or invites them to the driver app) |
| Government ID numbers | Social Security number; driver’s license and commercial driver’s license (CDL) number and state | The carrier’s records; ADP (the full Social Security number, for our first customer only: see “How Social Security numbers are protected” below); the Relay driver profile (license number); J.J. Keller (last four digits of the Social Security number) |
| Employment | Status, position, hire and rehire dates, termination reason, job title, review and training dates and notes, handbook receipt, I-9 and E-Verify status, benefits flag, access to other systems, supervisor, badge and file numbers | The carrier’s records and staff; ADP |
| Pay and time | Hourly pay rate; timecard punches and hours by pay code; timecard corrections, the driver’s answers and the office’s approvals; the office’s notes on a driver’s timecard days, which drivers do not see | ADP; the carrier’s staff; the driver app |
| Requests from drivers | Time-off requests (the days, any reason the driver picks: vacation, family, medical or other, and any note), questions about a timecard day, whether the driver took a request back, and the office’s answer and note, with who answered and when | The driver app; the carrier’s Owners and Operations Managers |
| Qualification and compliance | CDL class and endorsements, medical card expiry date, Relay compliance forms and their status, driver qualification file status, motor vehicle record (MVR) dates, results and documents, and drug and alcohol testing (below) | The carrier’s records; Amazon Relay; J.J. Keller |
| Schedule and dispatch | Shifts, start times, domicile, truck number, Relay blocks and trips assigned, stops and times, load notes, call-outs and their reasons, outcomes of calls with Amazon’s operations center | The carrier’s staff; Amazon Relay |
| Location and driving | Live truck location (GPS), speed, ignition and fuel level; hours-of-service and duty-status logs, including personal conveyance and yard moves, which Payroll compares with ADP timecards | The carrier’s electronic logging device (ELD) system, Geotab |
| Safety | Netradyne driver scores and safety alerts; links to alert videos; each driver’s safety standing on Relay; the carrier’s Relay scorecard; vehicle inspection (DVIR) results | Netradyne; Amazon Relay |
| Messages | Messages between drivers and the office in the driver app. If the carrier connects Slack, the messages and photos in the channels Hostler copies (below) | Drivers and office staff; Slack |
| Job applicants | Name, email, phone, hiring step, the job applied for, labels, notes and messages, interview times, and documents the office uploads or creates (for example a road-test certificate) | Fountain, and the carrier’s staff |
| Driver app login | See section 6 | The office’s invite; the driver app |
Drug and alcohol testing, and medical details. We receive nothing from drug-testing laboratories. Hostler does not save medical records: it keeps the date a medical card expires, and the word Medical when a driver picks it as the reason for time off. But a Slack photo, a note or a message can hold medical details if someone puts them there, and Hostler keeps it as written. We do hold the drug and alcohol test history that the carrier’s records and its J.J. Keller account show:
- each test’s date, type, reason (for example random or post-accident), collection method and result (negative, non-negative or pending);
- random-pool membership;
- the dates queries of the federal Drug and Alcohol Clearinghouse were run, but not their results.
MVR documents come from the carrier’s own records and its J.J. Keller files (section 7).
What is not saved, or is kept only for a while. Section 13 says how long.
- Live Geotab data. Hostler’s servers do not save truck locations or hours-of-service clocks. The dispatch desk sends some to our AI provider (section 9), and the driver app keeps a driver’s own hours on their phone (section 6.1). For Messages, the servers keep a note of whether a driver is driving (section 6.1).
- Payroll’s working copy. So the payroll screens open quickly, Hostler keeps a copy of what it reads from ADP and Geotab: each worker’s ADP ID, badge and file number, employment status and dates, termination reason, job title, pay cycle, supervisor, hourly rate and timecard punches by pay code, and each driver’s ELD duty-status logs (times, statuses and truck). It holds no names (only a fingerprint made from them, called a hash), Social Security numbers, dates of birth or home addresses. Only Owners and Operations Managers can see it. The one exception is the driver app’s Timecard tab, which shows each driver their own days from it, as clock times and hours, never pay (section 6). For a day the office corrects, the punches before and after, the correction and ADP’s answer are also saved with the correction record.
- Fountain applicants are held only in the open office app and are not saved, with two exceptions the office chooses: when it adds a new hire to People, their name, phone and email from Fountain are saved in People; and when it invites them to the driver app, their name and email are saved with the invite.
- The recruiting change log records what your staff did through Hostler, who did it and when, without the applicant’s name, phone, email or message text. For a document the office uploads, it records the type, size and a fingerprint, never the document or its name. For a Relay invite, it records the domicile and the length and fingerprint of the email address, never the address. A road-test form Hostler made is never recorded by a fingerprint.
- Netradyne video links expire about 30 minutes after Netradyne issues them. The extension keeps up to 8 in memory and never saves them. Videos play in your browser straight from Netradyne.
Sensitive information. Several of these are “sensitive personal information” under California law: Social Security numbers, driver’s license numbers, citizenship or immigration status (I-9 and E-Verify records), precise location, drug and alcohol testing information, a time-off request marked Medical, and what people write in messages, time-off requests and timecard questions. We use them only to provide Hostler to the carrier. We never use them to work out other things about people, and never for advertising. Hostler collects no biometric information, such as face or fingerprint data.
How Social Security numbers are protected.
- The full number cannot be read through the app’s normal data access. Everyone except Owners and Operations Managers sees only the last four digits.
- An Owner or Operations Manager can reveal it, one person at a time. Each reveal goes in the activity record, and the page hides the number again after 15 seconds.
- Copied from ADP. For our first customer only, if its ADP account releases full numbers to Hostler, Hostler can copy a driver’s number from ADP into their People record while an Owner or Operations Manager is using Hostler. It does this only when all of these hold: the record has no number; nobody has ever set or cleared that record’s number by hand; the record is tied to that ADP worker by its badge number and the names agree; and no other record holds the same number. The activity record keeps the last four digits and the badge number, never the full number.
- Road-test certificates. When an Owner or Operations Manager fills one in, Hostler reads the driver’s number from People through the same logged reveal. It puts the number only into the form in their browser and does not save it again. It uses the number only when the People record is plainly the driver being tested: the same name as their application, no one else in People with that name, and the same email, phone or J.J. Keller employee code. Whoever fills in the form can always say it isn’t theirs, and changing the driver’s name on the form stops it being used. Otherwise (the driver is not in People, their record has no number, or the record isn’t plainly theirs), the Owner or Operations Manager can type the number from the driver’s card. It stays in that browser window, goes only into the form, and is never sent to Hostler’s servers or saved.
- We can also reach the database directly, but only for the reasons in section 14.
Who at the carrier sees what. The carrier decides who gets an office seat and which role. Every office seat, Driver Team Leads included, can see people’s records, including dates of birth, home addresses, license numbers, medical card dates, drug and alcohol test results and MVRs. Only Owners and Operations Managers see pay rates, payroll, full Social Security numbers, billing, and drivers’ time-off requests and timecard questions. A driver sees only their own information (section 6), and their employer’s name and office phone number.
Slack. If a carrier connects Slack, Hostler copies every message and photo in every public and private channel the connected Slack account belongs to (up to 100 channels), about every 2 minutes, and keeps the copy for the carrier. Hostler skips its own report channel (the office channel in the carrier’s Slack where the desk posts and takes instructions, section 9) and does not read direct messages. The copying runs on Hostler’s servers, whether or not anyone has Hostler open. Photos are kept as resized copies with our storage provider (section 10.1). Hostler also reads the workspace’s member list, to show people’s names. The dispatch desk uses these messages to understand what drivers need, and recent messages and photos may go to our AI provider (section 9). A carrier should connect a Slack account that belongs only to the channels it wants Hostler to read. It must tell its drivers and staff about this copying, and about the ELD reads and Payroll’s comparisons above, as our Terms of Service require.
Hostler is not a background-check company. Hostler does not run background checks or prepare reports about people for others to use in decisions about them (what the law calls consumer reports). It shows the carrier records the carrier already has, or gets from its own providers.
5.5 Billing contacts
- Stripe runs our payment page. Card details go straight to Stripe. We never see or store card numbers.
- We send Stripe the company name, the email of the person who starts checkout and an internal company ID.
- Stripe collects the card, the billing address and, if you give one, a tax ID.
- We keep the Stripe customer ID, the subscription’s status and dates, a record of billing events, and a record of who accepted our Terms at checkout, with the name and email given there.
6. The Hostler driver app
This section is the privacy policy for the Hostler driver app on the App Store and Google Play. It applies whether the app is published in the stores by Hostler or by your employer. The rest of this policy also applies. Our Driver app terms say how you may use the app.
Who it is for. Your employer gives you the app to see your schedule, your hours and your timecard, to ask the office for time off or about a timecard day, to answer timecard corrections, and to see when your licence, medical card and annual review are due. If your employer uses Hostler’s Messages, you can also message the office. The app shows only what your employer has turned on.
How you get in. There is no sign-up and no password. The office invites you from Hostler, and the invite creates your login with the email address the office has for you. Each time you sign in, we email a one-time code to that address, and you type it in the app. Each code works once, for 24 hours, and a newer code replaces it. Nobody at Hostler will ask you for it, so don’t give it to anyone. The app shows your own information only after the office links your login to your record. Until then it shows only that it is waiting for the office, and you can still delete the login (section 6.6).
The demo company. App store reviewers sign in to a demo company with a code we give them. Its drivers, schedules, timecards and requests are invented, and they are put back as they were every night. The nightly reset does not clear the real records kept in it:
- each sign-in, wrong code and lockout at the review login, with the time, the IP address and the app or phone details it came from, so nobody can guess the code;
- what a reviewer does in the app, in the activity record.
The review login’s last-active time and, if the reviewer’s phone allows notifications, its notification token are kept as section 6.1 describes. Section 13 says how long all of these are kept.
6.1 What the app collects
| Data | What it is | Why | App Store label | Google Play label |
|---|---|---|---|---|
| Name | Your name as your employer’s records have it, attached when the office invites you | To show you your own schedule, timecard and requests, and to tell the office who sent a request | Name | Personal info: Name |
| Email address | The email you sign in with | To sign you in, to link you to your employer’s record, and to email you if we must tell you something about your login, such as a copyright notice or a suspension | Email Address | Personal info: Email address |
| User ID | The ID our sign-in provider gives your login | To keep your account and your records together | User ID | Personal info: User IDs |
| Device ID | The notification token Apple or Google gives your phone; whether it is an iPhone or Android; which of the two store versions of the app it is (Hostler’s or your employer’s); which notifications you turned on; when the phone was first registered after you signed in; and when it was last registered again (each time the app starts with notifications allowed, and when you change your notifications) | To send you the notifications you chose, and messages from the office if your employer uses Hostler’s Messages | Device ID | Device or other IDs |
| Time-off requests and timecard questions | The days you ask for, the reason you pick (vacation, family, medical or other), any note you type, the timecard day you ask about and your question, when you sent each, and when you took one back | So the office can answer you | Other User Content | App activity: Other user-generated content |
| Your timecard answers | Whether you accept or decline a correction, when, and any reason you type, or the office’s note if it recorded your answer for you (section 6.4) | To correct your timecard | Other User Content | App activity: Other user-generated content |
| Messages | If your employer uses Hostler’s Messages: what you write to the office, and when you sent it. If your employer also uses Slack, your Slack messages are not shown in the app. If it connects Slack to Hostler, Hostler copies the messages and photos in the Slack channels it is set to read (section 5.4) | Your conversation with the office | Emails or Text Messages | Messages: Other in-app messages |
| Timecard information | The punches, corrections and paid-time changes shown on the Timecard tab, in hours and minutes (never dollar amounts) | To show and correct your timecard | Other Financial Info | Financial info: Other financial info |
All of this is linked to you. It is used only to run the app and Hostler for your employer. It is not used for tracking, advertising or analytics. The app contains no analytics, advertising or crash-reporting code.
- Medical as a reason. If you pick Medical, the office sees that one word as your reason. You never have to say more: the reason and the note are both optional. If you type a note, the office reads all of it.
- Sign-in records (when you signed in, from which IP address, and the app or phone details it came from) are kept by our sign-in provider for security.
- Last active. Once the office has linked your login, Hostler notes when you last used the app. Your employer’s office staff can read it. It is deleted with your account.
- Activity record. When you send or take back a request, or answer a timecard correction, Hostler’s activity record notes what you did, the days it covered, when, and your email address. It never records your reason or your note. When you send the office a message, it notes that you did, when, and your email address, never what you wrote. Owners and Operations Managers can read it.
- What the app does not use: location, camera, photos, contacts, microphone or browsing history. The iPhone app carries a note about the photo library because Apple requires one: a file component built into the app could read photos if the app told it to. The app never does, so it never asks for your photos. On Android, the only permission the app ever asks for is to show notifications (section 6.2).
What stays on your phone. The app keeps these on your phone:
- your sign-in session, until you sign out;
- the email address you last signed in with, so the app can fill it in next time;
- while you are signing in, which address the code went to, and when;
- the last copy of your Today, Schedule, Timecard, My documents and Sent to the office screens, so you can read them with no signal;
- a request you send, until it reaches the office or you choose not to send it (with no signal, it waits on your phone and goes when the app is open and has signal);
- a waiting request that Hostler then turns down, with the reason, until you clear it;
- which notifications you turned on;
- the “your block starts in 2 hours” reminders, which the phone sets itself;
- the time of the newest office message you have seen, so the app can mark new ones;
- any reason you started typing to decline a correction but have not sent yet.
Signing out removes all of this except that email address and an unsent decline reason. Deleting your account in the app removes those too. If your login ends another way (for example, deleted by email, section 6.7, or from another phone), the app on this phone keeps what it saved, and block reminders it already set still go off, until you delete the app. Notifications already on your phone stay until you clear them.
What the app shows. The Schedule, Timecard and My documents screens show what your employer holds in Hostler: the weeks the office shares with you, your timecard, and the dates in its driver files. The Today tab shows how many hours you have left to drive, on your shift and in your cycle. For that, and to hold some notifications while you drive, Hostler reads the last 36 hours of your duty-status log, and the hours you have left, from your employer’s electronic logging system. If your employer uses Hostler’s Messages, Hostler also reads that log, and whether the truck you are logged into is moving, when you send the office a message. If they show you driving, the message may not be sent. It uses only your own account there, and only when it is sure the account is yours. Hostler’s servers save nothing from these reads but short notes for Messages: whether you are driving, what showed it (your duty status or the truck), and when. Your employer’s office staff see these notes in Messages. The notes are kept as your employer’s records (section 13). If your employer uses Hostler’s Payroll, your ADP punches and duty-status logs are kept in Payroll’s working copy (section 5.4).
6.2 Notifications
On an iPhone, or on Android 13 or later, the app asks before it sends notifications. On older Android phones they are on from the start. In Me, under Notifications, you choose which of these you get:
- your schedule is out or changes;
- your block is about to start (set on your phone itself, 2 hours before);
- the office answers a request;
- a timecard correction needs your answer, or the office corrected your timecard directly;
- your CDL or medical card is about to run out or has run out, or your annual review is due (60, 30 and 7 days before, and on the day). Hostler does not send these yet. When it does, they will come only if your employer keeps its driver files in Hostler.
These never show pay, other drivers’ names or who in the office answered. A new week’s schedule or a card notice due between midnight and 7 am Pacific time waits until 7 am. Some notices also wait, for up to an hour, while your ELD shows you driving.
If your employer uses Hostler’s Messages, a message from the office also sends a notification. It can show the first words of the message (up to about 120 characters) and carries a label made from your name, so your phone keeps the conversation together. A timecard notice about one day also carries a label made from your name and that day, so a newer notice about the same day replaces the older one.
Notifications pass through Apple or Google to reach your phone, and they can show on your lock screen. You can turn them off at any time in your phone’s Settings. The app keeps working without them.
6.3 AI and the driver app
- Your messages, requests, questions and answers in the driver app are not sent to any AI service to answer or sort them. Your employer’s staff read them. Our AI coding tools can see them only in the cases section 9 describes.
- If we ever want to change that, we will update this policy first, and the app will ask you before anything you write in it goes to an AI service. If you say no, it won’t.
- If your employer also uses Slack, Hostler’s AI desk (section 9) may help answer messages drivers send in Slack, and those Slack messages can go to the AI.
- Today the desk’s replies to drivers do not reach them; they go to Hostler’s report channel, an office channel. If live sending is switched on, they appear in Slack under an office person’s name, with a line saying they were sent automatically. The desk does not write to you in the driver app.
6.4 Time off, timecard questions and corrections
What you send the office. A time-off request or a timecard question goes to the office (its Owners and Operations Managers). They can approve or decline time off, or mark a question seen, and they can add a note. Approving time off does not change your schedule by itself: the office does that. You can take a request back until the office answers it. Taking it back does not delete it: the office still sees it, marked taken back.
Timecard corrections. The corrected clock times are written to your timecard in your employer’s payroll system (ADP) when you accept a correction and the office approves it, or when the office corrects your timecard directly. A direct correction shows under Recent on the Timecard tab. If you answer another way, such as by phone or in person, the office can record your answer, with a note saying how you gave it. The app shows it as recorded by the office, and an accepted correction then goes ahead the same way. A correction can also take a wrong pair of punches off. Hostler changes only clock times. It never sends ADP a pay rate or a dollar amount, but changed times can change the hours you are paid for. Hostler keeps a record of each correction, with the times before and after.
6.5 Encryption
The App Store and Google Play versions of the app talk to Hostler’s hosted service and to our sign-in provider only over encrypted connections (HTTPS).
6.6 Delete your account in the app
- Tap Me.
- Tap Delete my account.
- Confirm.
If the app says your login isn’t linked yet, there is no Me tab: tap Delete my account at the bottom of that screen, then confirm.
This takes effect straight away. It deletes your login, your profile and every phone registered for notifications, and it signs you out. The office’s list of app invites shows that your login was deleted. Your email address stays in some of the records your employer keeps, listed below.
What your employer keeps. These are your employer’s work and payroll records, which the law often requires employers to keep:
- your messages with the office, and the driving notes in section 6.1;
- your time-off requests and timecard questions, and the office’s answers;
- your timecard corrections, your answers and the office’s notes on your timecard days;
- the activity record of what you did in the app (section 6.1), with your email address;
- notes of some notifications Hostler lined up for you, whether or not they were sent: what each was about and when;
- your record in your employer’s driver files, roster and schedules, including the weeks the office shared with you;
- the office’s app invite, with your email address and your name as your employer’s records have it.
Hostler does not delete these on a schedule. Your employer cannot delete most of them in Hostler itself, so they stay until it asks us to delete them or stops using Hostler, and then section 13 applies. Deleting your login does not change your job, your ADP timecards or your pay. To see, correct or delete your employer’s records about you, ask your employer.
Coming back. Your login stays deleted unless the office invites you again, including when it invites all its drivers at once. Hostler then makes a new login with the same email. It does not email you when this happens. If you don’t want a new login, tell the office.
6.7 Delete your login without the app
You can also ask us to delete your Hostler driver app login without using the app. Email info@gethostler.com from the email address you sign in with, with the subject “Delete my Hostler login”. Or ask the office to send your request to us; the office cannot delete your login itself. app.gethostler.com/delete-account explains both ways.
We may ask you to confirm from that address that the request is yours. We then:
- delete your login, your profile and every phone registered for notifications within 7 days;
- tell your employer.
The records your employer keeps (section 6.6) stay with your employer.
7. The Hostler Assistant Chrome extension
Who uses it. A carrier’s office staff, in their own Chrome browser, signed in to their own accounts. It works for one company: the one whose Hostler office page connected it, with a press there. Another company’s office page in the same Chrome gets nothing from it.
Which sites it works on. It works only on these sites:
- Amazon Relay (relay.amazon.com);
- Netradyne (idms.netradyne.com);
- J.J. Keller’s client center (external.jjkellerclientcenter.com and preview.jjkellerclientcenter.com);
- Fountain (the carrier’s own Fountain account, for example app.amazon-us.fountain.com, and the Fountain address it loads its data from);
- the carrier’s own office app, at app.gethostler.com, and a test copy of Hostler on the same computer, which only we run.
It does not read any other website, and it does not collect your browsing history.
What it reads. On those sites it reads the information the site already shows you or loads for you. It keeps a copy of the answers the site sends to your own browser, and it reads the page. On Relay, J.J. Keller and Fountain it can also ask the site, as you and in your signed-in tab, for more of the same information, such as a trip’s notes, a proof-of-delivery document or a driver’s testing page.
- Amazon Relay: trips, including each trip’s pay as Relay lists it, and a truck’s last reported position on a trip in transit; load notes, the scorecard, Relay’s driver list, each driver’s profile and compliance file, and inspection results. The profile includes the license number and Relay’s safety standing, but not Relay’s list of open safety incidents or its “Policy” line. It shows documents such as proof of delivery, but does not save them. For Recruiting, it looks up an applicant’s email address in Relay’s driver list, including invites not yet used. It does this for an applicant at the Relay step, or at the DQF (driver qualification file) or Hired step when Relay’s driver list has no one of that name, when their record is opened and when someone presses the invite. It hands the page only that email’s status and domicile, and each domicile’s name and number of drivers. When Hostler keeps your company’s trip-board history (section 13), it also reads Relay’s History page once a day, normally overnight, for the trips finished in the past week, and earlier weeks, at most one a night, back up to 90 days. If a read does not work, it tries again a few hours later, at most three times a day. It does this in a background tab of its own, which it closes when it is done.
- Netradyne: driver scores and safety alerts. It never makes requests of its own to Netradyne; it keeps what the Netradyne console already loaded. To refresh, it can open the console in a background tab of its own, and to get an alert’s video link it can open the alert there, the same as clicking it. Video links are kept in memory only, as section 5.4 describes.
- J.J. Keller: driver qualification files, drug and alcohol testing pools and test results, and MVR documents. It opens each driver’s testing page using your existing sign-in. Before pressing anything on a driver’s file, it reads the name J.J. Keller shows, to check it is the person the office chose. On J.J. Keller’s upload page, for up to 30 minutes after Hostler adds files, it reads: whether a file has been added and not yet submitted; the driver the page names; the document type each added file shows; which of the files Hostler added are still on the page; and J.J. Keller’s own on-screen messages there (its warnings while files go in, such as a probable duplicate, and its answer when the office presses Submit).
- Fountain: the carrier’s openings, each opening’s steps, and the applicants in each step with their contact details, labels, notes, messages, documents and step history. It also reads the interview calendar (upcoming times, where they are, who holds them, and which applicants are booked), the open interview times Fountain offers an applicant, the file types each opening accepts, and the names and email addresses of the people on the carrier’s Fountain account who can hold interviews. Those email addresses are used only to add a time in Fountain under the signed-in user, and are not shown or saved. It never marks a message as read.
What it never handles. It never handles your passwords for those sites. It works inside the session you are already signed in to. It never answers security checks such as CAPTCHAs.
What it writes. It makes changes in Relay, Fountain and J.J. Keller when someone presses a button in Hostler:
- assigning drivers to blocks and trip legs (you can watch it fill them in);
- filing delay reports;
- adding trip notes;
- sending a question about a load to Amazon’s Relay Assistant, including a callback phone number the user enters (normally the office’s line), so Amazon’s operations center can call back;
- in Fountain: moving an applicant to a step, putting them on hold or rejecting them with a reason, booking or cancelling an interview, adding interview times, adding a note, sending the applicant a text, sending Fountain’s own reminder for the step they are on (Fountain texts and emails it), sending Fountain’s own booking link for the interview step, asking them to upload a document again, uploading a document the office chose, and resending a document to sign. When Hostler moves an applicant, Fountain sends whatever that step is set up to send (a text, an email or a document to sign), exactly as if the office had moved them in Fountain, unless the office ticks the box to skip it;
- in J.J. Keller, when someone presses one of Recruiting’s J.J. Keller buttons:
- it opens that driver’s file or J.J. Keller’s upload page and presses J.J. Keller’s own Upload button for that driver. It uses your J.J. Keller tab, or a new one if none is open or if yours holds an upload you haven’t submitted (that tab is left as it is). It clears J.J. Keller’s own note of which driver the upload page should pick, and reloads the page;
- for someone with no current J.J. Keller file (none, or only a former driver’s terminated one), it presses “Driver/Employee not yet in the system” and types their first and last name from Fountain. If the upload page comes up with someone else picked, it clears that and goes back to the driver’s file;
- it adds the files the office chose in Hostler, or the road-test forms Hostler made in their browser, to that driver’s upload page, and picks each one’s document type where J.J. Keller’s list has one. J.J. Keller starts receiving a file as soon as it has a type;
- it checks that the page names that driver before the first file and again before each file goes in, and stops if it names anyone else. Road-test forms go only into the file of the driver the forms name;
- it never presses Submit, Upload Anyway, Clear or Export. The office checks the page, picks any type left to it and submits;
- in Relay, when someone presses Recruiting’s Relay invite: it invites one new driver by email to the carrier’s Relay account, with the domicile the office chose (the same invite as Relay’s own Add driver), or asks Relay to resend an unused invite. First it checks Relay’s driver list for that email, and sends nothing if the email is already there. Afterwards it reads the list again to confirm Relay shows them as invited. It counts a resend as sent only when Relay itself says it went. Hostler marks anything it can’t confirm as unconfirmed, and sends nothing more to that email for a few minutes. It never cancels an invite. It never cancels an invite, and it does not keep the invited email in the extension’s storage.
Two features act on their own, without a click for each action:
- Automatic delay filing. It is off unless the carrier switches it on. It follows strict rules: it never files a reason that blames the carrier, and it remembers each stop it has filed on that computer and does not file it again.
- The dispatch desk, for a carrier with the Dispatch module. Its automatic cycle starts paused, runs only after an office user switches it on, and can be paused again at any time (section 9). While it runs, it can send a question about a load to Amazon’s Relay Assistant (up to 6 a day) and assign an open bobtail leg to a named office user (up to 6 a day), with no person clicking first. It posts each action in the carrier’s Slack before and after.
Where the data goes. Copies stay in the extension’s storage on your computer and are handed to your company’s office app. From there, some of it goes to Hostler’s servers to be saved for your company: J.J. Keller driver files, drug and alcohol pool records, and the raw pages J.J. Keller sent to the browser (kept as section 13 says); the trip board’s history, finished trips from Relay’s History page, and load notes; and a log of the changes Hostler made in Relay, Fountain and J.J. Keller. Road-test forms Hostler fills are made in your browser and are not saved on Hostler’s servers or in the extension’s storage; they go only where the office sends them: a download, or that driver’s J.J. Keller upload page through the extension. If your company uses the dispatch desk, what the office app holds from Relay and Netradyne also goes with each desk question to our AI provider (section 9), and summaries go to your company’s Slack. Nothing goes to anyone else.
Why it asks for each permission.
- storage and unlimitedStorage: to keep its copies on your computer, beyond Chrome’s usual size limit for an extension.
- tabs and scripting: to find and work in the Relay, Netradyne, J.J. Keller and Fountain tabs you have open, and in the ones it opens itself.
- alarms: to refresh on a timer.
- debugger: to make clicks that Relay accepts as real clicks, on Relay tabs only. Chrome shows a bar at the top of the window while this is in use. (Hostler’s own development copy, which only we run, also uses it to take screenshots of the Hostler office page, kept on that computer.)
The companion program. Hostler can also use an optional companion program on a carrier’s own computer. It uses a Relay sign-in saved on that computer to assign drivers in Relay without taking over the screen. The saved sign-in stays on that computer. No customer uses it today, though a Relay sign-in saved for it is still on our first customer’s computer (section 14).
Chrome Web Store Limited Use. Hostler’s use of information received through the extension follows the Chrome Web Store User Data Policy, including its Limited Use requirements:
- We use it only to provide the extension’s features to the carrier.
- We do not sell it, and we do not use it for advertising, credit or lending.
- We pass it to others only as section 10 describes, to provide those features.
- People at Hostler do not read it unless one of these applies: the carrier asks us to (for example, for support), it is needed for security, the law requires it, or it has been combined and made anonymous for our internal operations.
- Someone who works on Hostler and is also on a carrier’s own staff sees that carrier’s data as that carrier’s staff, not as Hostler.
- When we fix a problem a carrier asked us to fix, our AI coding tools can see that carrier’s data. For our first customer, they also see its data while we build and test the features it asked for (section 9).
8. How we use information
Customer Data. We use it only on the carrier’s behalf, to:
- run the Hostler features the carrier uses, and show the information to the carrier’s staff by role;
- connect to the systems the carrier links, and make the changes its staff make, approve or switch on;
- send notifications to drivers and staff;
- run the dispatch desk, if the carrier uses it (section 9);
- give support when the carrier asks;
- keep Hostler secure, prevent misuse and fix problems;
- handle a copyright notice or other legal complaint about specific material (Copyright Policy);
- meet our legal obligations.
Information we are in charge of. We use it to:
- answer questions, hold demos and set up accounts;
- run accounts and billing, and keep tax records;
- keep the service secure;
- tell customers about changes to Hostler or to this policy;
- improve Hostler, based on how the service works and fails, not by going through customer records;
- meet legal obligations and enforce our Terms of Service.
What we never do:
- sell personal information;
- share it for advertising that follows people across websites and apps, or use it for any advertising;
- train AI models on it;
- use one customer’s data for another customer;
- compare carriers against each other, or build benchmarks across carriers;
- build profiles of drivers for anyone except their own employer.
Suggestions, not decisions. Hostler suggests things: who is eligible for a block, which timecard looks wrong, what a reply to a driver might say. The carrier’s people make the decisions about hiring, firing, discipline, pay and who gets work. If you want a person to review a decision about you, ask your employer. In dispatch, the desk can take a few routine actions on its own (sections 7 and 9), and the carrier can pause it.
Information that cannot identify anyone. If we ever use information that has been changed so it cannot identify a person or a customer, we will keep it that way, and we will not try to work out who it is about.
9. AI
Some Hostler features use Claude, an AI model made by Anthropic, PBC. The main one is the dispatch desk, part of the Dispatch module, which is still in development and is used today only by our first customer. Under Anthropic’s Commercial Terms of Service, Anthropic may not train its models on the content we send it, and we keep our rights to what we send and what comes back.
When information goes to Anthropic:
- An office user asks the dispatch desk a question.
- The desk checks new messages in the carrier’s Slack channels about every 20 minutes, to answer drivers. This runs only while the carrier has the Dispatch module, the desk’s automatic cycle is switched on (section 7), and the office app is open in a tab in an office user’s browser.
- The desk writes its daily report and review of the day, in the evening or when an office user asks. This happens even while the desk is paused.
- An office user gives the desk an instruction in Hostler’s report channel.
- An office user asks Hostler to redraft the carrier’s dispatch playbook, or to grade the desk against the carrier’s past conversations.
What is sent:
- the question, the instruction, or the driver’s Slack message;
- the last 12 hours of messages in the Slack channels Hostler copies (up to 60 messages), from drivers and office staff alike;
- driver names, phone numbers, domicile, notes and eligibility from Relay’s driver list;
- driver-file problems, such as “medical card expiring”, and problems in drivers’ Relay compliance files;
- trips and the schedule;
- live truck positions and hours-of-service standing;
- safety alerts and the scorecard tier;
- load notes;
- similar past Slack conversations and how they were resolved, and the office’s notes on closed cases;
- the carrier’s dispatch playbook, which includes notes on past cases that can name drivers;
- up to 3 photos posted in any copied Slack channel in the last 2 hours.
To redraft the playbook or grade the desk, Hostler sends Slack conversations, joined with Relay trip, load-note and Hostler-action history.
What is not sent. Hostler does not add Social Security numbers, dates of birth, home addresses or pay rates. But anything a driver or staff member types or photographs in a copied Slack channel is sent as written. Messages drivers write in the Hostler driver app are not sent.
Where, and for how long. Anthropic stores what we send in the United States, but may run the model on servers in other countries. It deletes what we send and what it returns within 30 days, with two exceptions. If Anthropic’s systems flag content under its Usage Policy, it may keep that content for up to 2 years and its safety scores for up to 7 years. It may also keep content longer where the law requires. We have no agreement with Anthropic for it to keep nothing.
People stay in charge.
- Messages the desk writes to drivers go to Hostler’s report channel until live sending is switched on. With live sending on, the desk can reply to drivers in Slack on its own, within fixed daily limits.
- The desk’s actions in Relay (section 7) do not wait for live sending.
- In Slack, the desk’s messages to drivers appear under the name of the office person whose account is connected. Each one the desk sends on its own ends with a line saying the dispatch desk sent it automatically. The desk does not write in the driver app.
- Hostler checks each message the desk or the office sends through Hostler, and refuses one that matches its list of words that pressure a driver over hours of service or about disabling safety devices. The check can miss.
- When the desk is running, a Slack message that matches its emergency words goes to a person. The list can miss, and messages in the driver app are not watched this way. In an emergency, call 911.
- When a driver needs a person, Hostler pages the carrier’s on-call staff in the carrier’s Slack, quoting the driver’s message. It pages again, up to a limit, until someone takes it. Pages run on Hostler’s servers, and pages already under way keep going while the desk is paused. While it is paused, no new page starts.
- An office user can pause the desk at any time.
AI tools we use to build Hostler. We use AI coding tools from Anthropic to write and fix Hostler. When we fix a problem a customer asked us to fix, these tools can see that customer’s data. For our first customer, whose own staff direct how Hostler is built, these tools also see that customer’s data while we build and test the features it asked for. Copies of data these tools make while they work, and their working notes, stay on the computer we build Hostler on (section 13 says how long). We use them only under terms that do not let Anthropic train its models on that data.
10. Who we share information with
We share personal information only as this section describes. We do not sell it, and we do not share it for advertising.
10.1 Our service providers (subprocessors)
These companies run parts of Hostler for us. Each one may use the data only to provide its service to us, under its contract or data-processing terms with us, and must protect it at least as well as this policy does.
| Company | What it does for Hostler | What it receives |
|---|---|---|
| Supabase, Inc. (on Amazon Web Services, in the U.S.) | Database, file storage (Slack photos and archived trip-board history) and sign-in | Everything Hostler saves: accounts, Customer Data, sign-in records |
| Vercel Inc. | Hosts our website and Hostler’s hosted service, and runs its scheduled jobs (Slack copying, on-call pages, the payroll copy, driver app notifications, the demo company’s nightly reset and nightly clean-up) | Every request to the website and the hosted service passes through Vercel; it keeps request logs (IP address, page, time) |
| Resend | Delivers Hostler’s automatic emails | The recipient’s email address and the email’s contents (for an invite, what section 5.3 lists) |
| Anthropic, PBC | AI for the dispatch desk (section 9), and the AI coding tools we use to build and support Hostler | What section 9 lists; for support, what a fix needs to see; for our first customer, what building and testing the features it asked for needs to see |
| Stripe, Inc. | Payments, invoices and sales tax | Company name, buyer’s email, card, billing address, tax ID |
| Apple Inc. (Apple Push Notification service) | Delivers notifications to iPhones | Notification token, notification text and the labels described in section 6.2 |
| Google LLC (Firebase Cloud Messaging) | Delivers notifications to Android phones | Notification token, notification text and the labels described in section 6.2 |
| Google LLC (Google Workspace and Google Calendar) | Our email and demo bookings | Emails to and from us; demo bookings |
We send notifications to phones directly through Apple and Google. No other notification service is used. The driver app is built with Expo, an open-source framework, and Expo receives no Customer Data from us.
Public map services. For the map in the office app, our server also asks Esri and OpenStreetMap for map images and the U.S. National Weather Service for weather alerts. They receive the map area being viewed and truck coordinates, without driver names. Road closures come from the California Department of Transportation’s public feeds, which our server asks for without sending anything about trucks or drivers. Because our server makes these requests, your IP address is not sent. These are public services, not our service providers.
Before a new service provider receives Customer Data, we will update this list and email customers at least 30 days ahead, unless we must act faster for security or to keep the service running, as our Terms of Service say.
10.2 Systems the carrier connects
When a carrier connects one of its own systems, Hostler reads from it, and in some cases writes to it, on the carrier’s behalf. It uses the carrier’s credentials or the carrier’s signed-in browser. These companies are the carrier’s providers, not ours, and the carrier’s agreements with them apply.
| System | What Hostler does with it |
|---|---|
| Amazon Relay | Reads (section 7). Writes driver assignments, delay reports, trip notes, and questions to Amazon’s Relay Assistant with a callback number, normally the office’s line. Sends or resends Recruiting’s driver invites when someone presses a button in Hostler (section 7). The dispatch desk can do some of this on its own (section 7) |
| Netradyne | Reads only |
| J.J. Keller | Reads (section 7). When someone presses a Recruiting button in Hostler, adds the files the office chose, or the road-test forms Hostler made, to that driver’s upload page (section 7). It never submits; the office does |
| Geotab | Reads only |
| ADP Workforce Now | Reads workers (names, badge and file numbers, employment status and dates, job title, supervisor, pay rate and, for our first customer only, the Social Security number if ADP releases it) and timecards. Fills an empty badge number in People when exactly one active ADP worker has that name and the start dates fit, an empty hire date from the worker its badge number points to when the names agree, and an empty Social Security number under the rules in section 5.4. It never refills a number or date someone removed. Writes corrected clock times, and takes a wrong pair of punches off, only after an Owner or Operations Manager approved or entered the change. Never writes pay rates or pay amounts |
| Fountain | Reads applicants and their steps; makes the changes listed in section 7 (moves, holds, rejections, interview bookings, notes, texts, reminders, document requests and uploads) only when someone presses a button in Hostler |
| Slack | Copies channels as section 5.4 describes, and reads the office’s instructions and replies in Hostler’s report channel. Posts the desk’s messages to drivers, a daily report to the carrier’s channel, and pages to the carrier’s on-call staff |
10.3 Inside the carrier’s own company
The carrier’s office staff see Customer Data according to their role, and drivers see only their own information, as section 5.4 describes.
10.4 The law and safety
We disclose information if the law, a subpoena or a court order requires it, or if we need to in order to protect someone’s safety, or to protect Hostler and our customers from fraud or abuse. If a request is for Customer Data, we will tell the customer first, unless the law forbids it.
If you send us a copyright notice or counter-notice, we send a copy, with your name and contact details, to the other side, as our Copyright Policy explains.
10.5 If Hostler changes hands
If Hostler is sold, merged or transferred, the information may pass to the new owner. The new owner must keep the promises in this policy, or tell you about any change first. Before any such change, customers will be able to export their data (section 15).
10.6 With your permission
We share information in other ways only if you ask us to or agree to it.
11. Cookies and storage on your device
Website. gethostler.com puts nothing on your device (section 5.1).
Office app cookies. The office app uses two kinds of cookies. Both are needed for the app to work:
- Sign-in cookies keep you signed in.
hostler-orgremembers which company you are working in, so your browser keeps each company’s stored data apart.
There are no analytics, advertising or third-party cookies.
Office app browser storage. To load quickly, the office app keeps copies of what it read from Relay, Netradyne and J.J. Keller in your browser. Most of it is deleted when you sign out. Some of it stays on that computer on purpose:
- the roster, with its backups and any copy not yet saved;
- the scheduler’s current week, with its backups;
- earlier People edits;
- Relay load notes for the last 200 trips, including notes on calls with Amazon’s operations center;
- color and layout settings, and Relay’s list of domiciles;
- dispatch-desk bookkeeping.
The dispatch desk’s chat is kept only until you close the tab.
Use Hostler on computers your company controls. On a shared computer, sign out and clear the site’s data when you finish.
Extension storage. The extension keeps its copies on your computer (section 13 says for how long).
Driver app. The app keeps on your phone what section 6.1 lists, and signing out or deleting your account removes it as section 6.1 says.
12. Do Not Track and Global Privacy Control
- Do Not Track. Some browsers send a “Do Not Track” signal. There is no common standard for answering it. Hostler does not track you across other websites or apps, and lets no one else do so through our website or apps, so the signal has nothing to switch off and we change nothing when we get it.
- Global Privacy Control. We do not sell or share personal information, so a Global Privacy Control signal has nothing to turn off. If your browser sends one, we treat it as a valid request to opt out of sale and sharing anyway.
13. How long we keep information
Hostler keeps most records until the customer deletes them or leaves. A few working copies expire on their own. This table says what happens to each.
| Information | How long |
|---|---|
| Customer Data (people records, roster, schedules, messages and the driving notes in section 6.1, drivers’ time-off requests and timecard questions, timecard records, compliance files, notes of notifications lined up for drivers, the dispatch desk’s messages, the activity record) | While the customer’s account is open. Archiving a person keeps their record. If a customer wants records deleted, it asks us, and we delete them unless the law requires us to keep them. After a customer leaves, it has 30 days to ask us for a copy (section 15). We then delete its data within 30 more days. Copies in backups expire within 7 days after that |
| Slack copies, Relay trip-board history (finished trips from Relay’s History page included), load notes and the log of Relay changes | The same as Customer Data. Trip-board history moves out of the database into a compressed archive with our storage provider 90 days after Hostler saves it, and is kept the same way |
| Raw J.J. Keller reads (the pages J.J. Keller sent to the office’s browser) | 90 days, then deleted. The driver files, testing pools and test results Hostler takes from them are kept as Customer Data |
| Recruiting change log (what your staff did through Hostler, who did it and when; no applicant name, phone, email or message text) | The same as Customer Data |
| Payroll’s working copy of ADP and Geotab (section 5.4) | Refreshed about every 10 minutes. Any part not refreshed for 2 days is deleted |
| Live Geotab truck locations and hours-of-service clocks | Not saved on Hostler’s servers (section 5.4) |
| The dispatch desk’s duplicate check (keys that stop it sending the same thing twice) | 60 days, except its record of trailer numbers already announced, which is kept as Customer Data |
| Office user accounts | While the customer’s account is open. Removing a person on the Team page ends their access at once but keeps their login, which can be given access again. To delete it, the customer asks us |
| Driver app login and profile | Until you delete it (section 6) |
| The demo company’s real records (the review login’s sign-in records and the activity record of what reviewers do, section 6) | Kept. Nothing deletes them |
| Notification tokens | Until you delete your account, someone else signs in to the app on that phone with notifications allowed, or Apple or Google says the token no longer works. Signing out also deletes it, but only if the app can reach Hostler and has registered the phone since it last started. If not (for example, with no signal, or if notifications have been off since the app started), the token stays until one of the other things happens, and the phone may still get your notifications until then |
| What Anthropic receives | Up to 30 days, with the exceptions in section 9 |
| Copies and notes our AI coding tools make (section 9) | Copies are deleted when the work is done. Notes are kept only while useful, and name people as little as possible |
| Office app storage | Most of it is deleted at sign-out. Section 11 lists what stays |
| Extension storage | Until the extension is removed or its storage is cleared. Signing out of Hostler does not clear it |
| Website logs and sign-in records | As long as Vercel (website logs) or Supabase (sign-in records) keeps them |
| Copyright notices and counter-notices, and our record of each one and what we did | 3 years after the last step in each case, then deleted |
| Emails and demo bookings | As long as the conversation is useful, and no longer than 2 years after our last contact, unless you become a customer |
| Billing records | As long as tax law requires, generally 7 years |
14. Security
What we do:
- Each customer is walled off in the database. Every row of data belongs to one company, and the database itself refuses to show it to anyone signed in to another company. Hostler’s scheduled jobs and a few server tasks use a key that can see every company; their code acts for one company at a time.
- Every page and request in the app needs a signed-in user with the right role. Your identity comes from your sign-in, never from what a request claims. The exceptions include:
- the sign-in, password-reset and email-confirmation pages;
- the public privacy, help and account-deletion pages;
- the map library’s files;
- a page that says which version of Hostler is running (it holds no data);
- Stripe’s notification address, which checks Stripe’s signature first;
- the App Review sign-in address, which opens only for one fictional review account, and only with its code;
- the addresses our scheduled jobs use, which check a secret key first.
- The most sensitive fields are locked down further. Full Social Security numbers and pay rates are restricted as section 5.4 describes.
- Our own access. We can reach the database directly. We do that only to run, repair and update the service, for support the carrier asked for, for our first customer while we build and test what it asked for (section 9), for security, to handle a copyright notice or other legal complaint about specific material (Copyright Policy), or when the law requires it. Our AI coding tools work under the same rule.
- Important actions are kept in an activity record that no one can change or delete through Hostler.
- Limits on repeated tries. Our sign-in provider limits repeated sign-in attempts, and Hostler limits how fast its own pages and requests can be used.
- Encryption. Our website and Hostler’s hosted service use encrypted connections (HTTPS), and so does the driver app (section 6.5). Our database provider encrypts stored data and files (AES-256).
- Card numbers never reach us. Stripe handles them.
- Secret keys are never sent to a browser or a phone.
What we do not have yet.
- Office users sign in with an email and a password. Hostler does not offer two-step sign-in yet. Drivers have no password (section 6).
- Hostler has not had an independent security audit, such as SOC 2.
Our first customer. Hostler used to run on a computer in our first customer’s office. It now runs on our hosted service, but that computer still keeps some of that customer’s records as files. It keeps these files, as that customer’s backup, until 9 November 2026, when they are deleted:
- copies of Slack channels and their photos;
- trip-board and load-note history;
- a log of the changes Hostler made in Relay;
- the desk’s sends, escalations and on-call pages;
- case notes and the dispatch playbook;
- raw J.J. Keller reads, including those more than 90 days old;
- a copy of the driver roster.
A saved Relay sign-in for the companion program is kept on that computer too. No other customer’s data has ever been kept on that computer.
What you can do:
- Use a strong password that you use nowhere else.
- Give office seats only to people who need them, at the lowest role that works.
- Remove a person’s access on the Team page as soon as they leave.
- Sign out on shared computers.
If something goes wrong. No system is perfectly secure. If a security incident affects Customer Data, we will tell the affected customer as soon as we can, and within 72 hours of finding it. We will help them notify the people affected, as the law requires. If an incident exposes sign-in details (an email address with a password) or other information we are in charge of, we will also tell the people affected directly, as the law requires.
15. Getting your data out
- People. A customer can export the main fields of its people records as a spreadsheet at any time (People, then Export CSV). The export shows only the last four digits of Social Security numbers, and it includes pay rates only for Owners and Operations Managers. Drug-test entries, notes and J.J. Keller files are not included; ask us for those.
- Trips. A customer can export Relay trips (upcoming, in transit and history) as spreadsheets.
- Everything else. Ask us, and we will provide a copy in a common format (CSV or JSON) within 30 days, at no charge. We are building a fuller self-serve export.
- If Hostler shuts down or is sold, customers will be able to get their data out first.
16. Your privacy rights
16.1 Everyone
Whatever the law where you live, you can ask us:
- what personal information we hold about you;
- to correct it;
- to delete it.
Email info@gethostler.com. For Customer Data, section 16.6 says what we do.
16.2 California
California’s privacy law (the CCPA, as amended by the CPRA) gives California residents rights over their personal information. Hostler is a small business and may not meet the size thresholds that make the CCPA apply to it. We honor these rights anyway.
Information we are in charge of, in the last 12 months. We keep each kind as section 13 says.
| CCPA category | Examples | Source | Why we use it | Who receives it |
|---|---|---|---|---|
| Identifiers | Name, email, IP address, account ID | You; your company; your browser | Accounts, demos, support, security | Supabase, Vercel, Resend, Google, Stripe, Anthropic |
| Customer records | Name, billing address, phone | You | Billing and support | Stripe, Google |
| Commercial information | Subscriptions and purchases | You; Stripe | Billing | Stripe |
| Internet or network activity | Website and app request logs, sign-in records, last-active times, activity record | Your browser; Hostler | Security and running the service | Supabase, Vercel, Anthropic |
| Professional information | Your company and job title | You | Demos, accounts, support | Google, Supabase, Anthropic |
| Sensitive: account sign-in | Email with password (stored scrambled) for office users; for drivers, email with a one-time code | You | Signing you in, only | Supabase, Resend |
- We have not sold or shared personal information in the last 12 months.
- We do not sell or share the personal information of anyone under 16.
- We use sensitive information only for purposes the CCPA allows, such as providing the service you asked for and keeping it secure. So the right to limit its use does not change anything we do. You can still ask.
Your rights:
- Know and access: what we collect, where it comes from, why, who receives it, and a copy of the specific information.
- Delete it, unless the law lets or requires us to keep it.
- Correct it.
- Opt out of sale or sharing. We do neither.
- Limit the use of sensitive information. See above.
- No retaliation or discrimination for using these rights. That includes employees and job applicants.
16.3 How to make a request
- Email: info@gethostler.com, with the subject “Privacy request”.
- Mail: the address in section 20.
Checking it is you. We check that the request comes from you, by matching it with information we already hold. If you have an account, we will reply to its email address. A request for specific pieces of information needs a closer match.
Someone acting for you. You can have someone else (an authorized agent) make a request for you. They need your signed permission, and we may check with you directly.
Timing. We confirm we got your request within 10 business days. We answer within 45 days. If we need more time, we will tell you why, and we may take up to 45 more days. Requests are free. We may refuse requests that are clearly unfounded or excessive, and we will tell you why.
16.4 California “Shine the Light”
We do not disclose personal information to other companies for their own direct marketing.
16.5 Other U.S. states
If you live in another state with a privacy law, you may have similar rights. We will honor them as that law requires.
If we turn down your request, you can appeal. Reply to our answer with the word “Appeal”. We will answer within the time your state’s law sets, usually 45 to 60 days. If we still say no, you can contact your state’s attorney general.
16.6 Drivers, employees and job applicants
For Customer Data, your employer is in charge. Send your request to your employer. If you send it to us, we will:
- pass it to your employer within 5 business days and tell you we did;
- help your employer answer it.
If your employer stops using Hostler, it can still answer you from the export it took (section 15).
17. Children
Hostler is a business tool. It is not meant for anyone under 18, and we do not knowingly collect information from anyone under 18. If we learn that we have, we will delete it, or, for Customer Data, ask the carrier to. If you think a child’s information has reached us, email info@gethostler.com.
18. Where information is kept
Hostler is for carriers in the United States. Hostler’s database and servers are in the United States. Our AI provider stores what we send in the United States, but may run the model on servers in other countries (section 9). Some service providers, such as Apple and Google, which deliver notifications worldwide, and Google Workspace and Stripe, may handle information in other countries under their own safeguards.
Hostler is not offered to people in the European Union, the United Kingdom or elsewhere outside the U.S.
19. Changes to this policy
When we change this policy, we change the “Last updated” date at the top.
Bigger changes. If a change is material, for example a new kind of data or a new use, we will tell customers’ Owners and Operations Managers by email at least 30 days before it takes effect.
Driver app changes. If the driver app starts collecting something new, we will:
- update its App Store and Google Play privacy labels first;
- ask you in the app, where the law or the app stores require it.
20. Contact us
Hostler
Legal name: Samer Dimes, doing business as Hostler
Email: info@gethostler.com
Mail: 7726 N First St PMB 523, Fresno, CA 93720
Privacy questions and requests go to the same email address. We read every message.