Privacy Policy

01Who we are, and two different roles

This policy is OpsBrio LLC’s, a New Jersey company at 550 Marketplace Blvd, #1002, Hamilton, NJ 08691, telephone (609) 676-4965, email privacy@opsbrio.com. OpsBrio is an operations platform for Amazon Delivery Service Partners — roster, dispatch, fleet, compliance, hiring and a drivers' app — which sends hiring email and text messages to job applicants on behalf of the delivery companies that use it.

Almost everything personal in OpsBrio is somebody else’s employment record. A delivery company decides what to keep about its own drivers, office staff and job applicants, and OpsBrio is the filing cabinet it keeps them in. In data-protection language that company is the controller and we are its processor: we act on its instructions, not on our own account.

For a small amount of data we are the controller ourselves — the account of the person who signs up, our billing records, and anyone who fills in the form on this website. That is section 6. If your company needs a data processing agreement in writing, ask us.

02Job applicants and text messages

A delivery company that hires through OpsBrio collects, on its own application page, an applicant’s name, mobile number, email address, ZIP code, the days they can work, and whether they agree to be texted about the application. OpsBrio holds that for the company and sends the company’s hiring email and text messages on its behalf.

Mobile information and text-message consent are not sold, and are not shared with third parties or affiliates for marketing or promotional purposes. An applicant’s number and consent are used to send messages about that application — interview times, reminders, the steps before a start date — and for nothing else. The only parties that see the number are the company applied to, OpsBrio, and the carrier that delivers the message, which may not use it for anything of its own.

A text is sent only to somebody with a recorded consent: an unchecked box the applicant ticked beside the number they entered, or a yes given to a recruiter and recorded with the date and time. Consent is never a condition of applying or of being hired. Reply STOP to any message to stop them at once, and HELP for help. Message frequency varies and message and data rates may apply. The full terms of the programme are the SMS terms.

03What we hold for a company

Running a delivery station means keeping records about the people who work there. In a portal that can include:

• Who they are: name, the name they prefer to go by, staff identifiers, work email, phone number, home station.
• Their work: schedule, shifts, routes, vans, the day’s board, absences and time off.
• Their hours and pay basis: hours clocked and paid, breaks, and the limits their hours are measured against.
• How the job went: delivery performance scores, rescues, coaching notes, write-ups.
• Vehicles: inspections and their photographs, damage reports, tickets.
• Safety: workplace incident and injury records, which a company is required by federal law to keep. These can include information about a person’s health.
• Employment paperwork: driver’s licence details, signed policies and write-ups, offer letters, and — for the I-9 only — a Social Security number and pictures of the identity documents a new hire gives for it.
• Messages: what people write to each other in the portal’s chat, including pictures, video and documents they attach.
• Applicants: the details in section 2, interview notes, and the messages sent to and received from them.

A driver’s Social Security number is the one field treated differently everywhere: it is encrypted before it is stored, with a key kept outside the database, and only an HR role can reveal it.

04Where it comes from

• The company’s own office staff, typing it in.
• Its drivers, from the phone app — a check-in, a photograph, a message, a signature.
• Amazon’s DSP portal, copied across by the Chrome extension running inside a dispatcher’s own signed-in browser session.
• People who apply for a job through one of the company’s own apply pages, and their replies to its messages.

05What we never do

• We never ask for, store or transmit an Amazon password. The extension cannot sign in to Amazon.
• We never sell personal data, and we never share it with another customer.
• We never use it for advertising, and we run no advertising on this site or in the product.
• We never share a mobile number or a text-message consent with anyone for marketing.
• We never use a customer’s records to train a machine-learning model, ours or anybody else’s.
• We run no analytics, no tracking pixels and no third-party scripts on this website or in the product.

06What we hold for ourselves

• If you ask for a portal: your company name, your name, your email, your phone if you give it, your DSP code and stations, and anything you type in the box. We use it to answer you and to set the portal up. If you do not become a customer, we delete it when you ask us to.
• If you become a customer: the account details of the people we deal with, and our billing records. Billing records are kept for as long as tax law requires.
• Our server logs: the ordinary record of a web request — the address asked for, the time, an IP address, the browser’s description of itself. They exist to keep the service up and to investigate faults and abuse, and our hosting provider keeps them for no more than 30 days.

07Cookies

Three kinds, all of them necessary, none of them advertising:

• A sign-in cookie, so a person stays signed in to their portal.
• A look cookie, remembering whether that person chose the light or the dark theme.
• A layout cookie, remembering which parts of the chat list somebody folded away.

That is the whole list. There is nothing to consent to here because there is nothing here that tracks you, and no cookie we set follows anybody to another website.

08Where it lives

Every company’s portal runs on its own database, in the United States (Northern Virginia). Files — inspection photographs, documents, signed letters — sit in that same company’s own storage. We do not operate outside the United States and we do not move customer records abroad.

09Who can see it

Inside a company: whatever its own roles allow. A dispatcher sees the board. HR sees the file. A driver sees only their own records — that is enforced by the database itself, not by the screen, so it holds even when a screen has a bug.

From OpsBrio: every company’s portal has one OpsBrio support login, with an Owner’s access, which stays switched off until the company opens it from its settings and agrees to it. While it is open, our support team uses it to set the portal up, answer the company’s questions and fix a fault; what it changes is recorded under its name, the company can close it at any time, and we do not use it to read records for any other reason. Beyond that, the small number of our staff who run the platform can reach the systems a portal runs on, because applying an update, restoring a backup or fixing a fault requires it. They do that to keep the service running or to answer a request from the company, and not to read records for any other reason.

Nobody else, unless the company tells us to, or unless we are required by law — in which case we will tell the company first, unless we are forbidden to.

10The companies we rely on

We use a short list of American suppliers to run the service. Each holds data only to do its job for us.

Amazon is not on this list. Amazon is where some of the data comes from, not somewhere we send it.

We will tell customers by email at least 30 days before adding a supplier that handles personal data, so there is time to object.

11How it is protected

• One database per company. Not one shared database with a column saying which company a row belongs to. There is no query another customer could write that would reach your records.
• The access rules live in the database. Who may read which row is enforced underneath the application, so a mistake in a screen cannot show somebody a record they are not entitled to.
• Encrypted in transit and at rest. Social Security numbers are encrypted a second time, with a key held outside the database entirely.
• No Amazon credentials anywhere. There is nothing of Amazon’s to steal from us.
• Inspection photographs expire on a schedule the company sets — longer, or never, for one that shows damage or belongs to an accident or injury record — and when they expire the files are deleted, not merely hidden.
• Sign-in is by password or an emailed link, and an emailed link is good for 24 hours and one use.

No system is perfect. If personal data is exposed we will tell the affected company without undue delay and, in any case, within 72 hours of establishing what happened, with what we know and what we are doing about it.

12How long it is kept

• Operational records are kept for as long as the company needs them. It is their decision; we do not delete a customer’s records on our own initiative.
• Applications: when a company declines an applicant, their résumé and the files they sent are deleted on the company’s schedule — 180 days after the decision unless it sets another. The rest of the application — the details in section 2, notes and messages — stays with the company’s records.
• Inspection photographs follow the retention the company sets in its own settings; a photograph that belongs to a damage, accident or injury record is kept with that record.
• Chat messages follow the retention the company sets, by kind of conversation — four years unless it chooses less, and never more than five.
• I-9 files: the Social Security number is removed a set time after the company marks the hire entered in its payroll system (30 days unless it sets another). Pictures of identity documents are kept while the person works there, then until the later of three years after hire or one year after their last day, as federal law requires; for an applicant who was never hired, they are deleted a set time after the company declines them (30 days unless it sets another).
• When a company leaves, its database is kept for 30 days so it can take a copy, then the whole project is deleted, backups included, within a further 30 days.

13If you are a driver, an employee or an applicant

If you drive for, work at or applied to a company that uses OpsBrio and you want to know what is held about you, to correct it, or to have it deleted, ask that company. The records are theirs, the decision is theirs, and they can see and correct everything from inside their own portal. Where a record has to be deleted, we delete it on the company’s instruction — unless the law requires it to be kept.

You can write to us at privacy@opsbrio.com and we will pass it on to them and help them answer it, but we will not change or hand over a company’s records on the strength of a request being forwarded.

Some states give you rights directly, including the right to know, to correct, to delete and not to be discriminated against for asking. Where those apply, they apply to the company as the controller, and we help it answer.

14Changes, and how to reach us

If this policy changes in a way that matters, we will email the companies using OpsBrio at least 30 days beforehand, and the date at the top of this page will change with it.

Privacy questions, and requests from a customer about their own records: OpsBrio LLC, 550 Marketplace Blvd, #1002, Hamilton, NJ 08691; telephone (609) 676-4965; email privacy@opsbrio.com.

The Chrome extension has its own policy, written for the same facts from the extension’s side: the Cortex sync privacy policy. Our terms of service and SMS terms sit alongside this one.