Privacy — OpsBrio Cortex sync

What the extension does

Amazon provides no data connection for Delivery Service Partners. The extension therefore runs in the browser of an operations staff member who is already signed in to Amazon's DSP operations portal at logistics.amazon.com, takes a copy of the operational data that portal has already shown them, and sends it to their own employer's OpsBrio operations portal — yourcompany.opsbrio.com, or the address their company chose. Each company's portal is its own: its own address, its own database, its own logins.

This is a business tool moving a business's own operational records between two systems that business already uses. It has no connection to Amazon consumer accounts, shopping, or amazon.com.

What it reads

Only pages and data endpoints on logistics.amazon.com that the signed-in staff member is already authorised to see, plus two Amazon file hosts those pages link to for reports and vehicle-inspection photographs. The data covers:

Dispatch routes, delivery itineraries and planned work for the day
Each finished route's own detail: when the van left and how long its drive out took; for every stop, which associate made it (by staff identifier), its place in the route, its status, when it was finished, how many packages were delivered there and the stop's five-digit zip code; and the times the van stopped where no delivery was planned. That page also lists the route's customers — names, telephone numbers and street addresses — and where the van stood: the extension keeps only each stop's zip code and discards the rest before anything leaves the browser
Weekly and daily performance data for the company's own delivery associates, including each associate's customer feedback for the week — how many customers praised a delivery, what they picked and the “Alexa, thank my driver” thanks, as counts by staff identifier, never by name — and the pickups Amazon marks as missed: each stop's route, stop number, time and what went wrong. Amazon's list of those stops also shows the customer's address and map location: the extension discards both before anything leaves the browser
Vehicle inspection records and their photographs
Worked hours and break records for the company's own employees
Roster, fleet and hiring-pipeline records for the company
For the company's own hiring candidates on Amazon's drug test, and for its own delivery associates whose identifier the company does not hold yet: the identifier Amazon gives the company for ordering that person's test from the testing vendor (Amazon's “Drug Test ID”), and the vendor's order as Amazon shows it — its number, the vendor, the status the vendor reports (for example collected, at the lab, or the result) and when it changed. Only those leave the browser, keyed by Amazon's identifier for the person — never the person's name or contact details, and never a test report
The company's own delivery schedule for the current and next week: which of its delivery associates (by staff identifier, never by name) are scheduled on which day, the shift's start and length, and whether the company has published it
For each of the company's own delivery associates: work-anniversary and birthday reminders, recognition milestones, and the preferred name they have asked to be known by. These are read from that person's own staff profile page. That page also shows a date of birth, a home address and a personal telephone number: the extension does not keep, transmit or store any of those — it takes the preferred first and last name and discards the rest before anything leaves the browser
The company's own Work Summary — what Amazon will pay the company for each day: each route's code, type and paid length, the late cancellations Amazon pays, the classroom training days it pays for (the trainee by staff identifier, never by name), and any dispute the company filed with Amazon's answer. No names, check-in times or packages are taken from it
The company's list of its own stations as Amazon holds it — each station's code, Amazon's name for it and its time zone — and, for each, how many of the company's delivery associates, hiring candidates and vans Amazon shows there, so a new company's stations are set up without anybody typing them. Only those counts leave the browser, never a person's name or identifier, and never a van's VIN or name
Which delivery service partner the browser's Amazon session belongs to (its short code), checked against the company's own before anything is sent: a browser signed in to another company's Amazon sends nothing. The code stays in the browser
Workplace incident reports the company itself filed with Amazon — including injury incidents, which the company is required by federal law (OSHA recordkeeping, 29 CFR 1904) to keep its own record of

Some of this is personal information about the company's own employees — names, staff identifiers, worked hours, job performance, and the fact and nature of a workplace injury where one was reported. The extension reads no personal information about anyone outside the company, and reads nothing at all from any other website.

Where it sends it

To one place only: the company's own OpsBrio portal — the one address the staff member typed into the extension, which Chrome asks permission for once — using their existing signed-in session there. The data is sent to no other destination and shared with no third party. It is not sold, rented, or used for advertising, and it is never used to build profiles for any purpose beyond running the company's own delivery operation.

What it stores on your computer

Only what it needs to avoid asking the same question twice: the portal address, station codes, Amazon service-area identifiers that appear in ordinary page URLs, the short code of the company the browser's Amazon session belongs to (kept a minute at a time), timestamps, short non-reversible fingerprints used to skip unchanged data, and the chosen check frequency.

There are no credentials in the extension's storage of any kind. Sessions live in the browser's own cookie store, where they belong. If a laptop is lost, nothing the extension has stored helps anyone.

What it never does

It never asks for, sees, stores or transmits an Amazon password. It cannot sign in to Amazon and has nothing to sign in with.
It never reads any website other than the two Amazon hosts and the company portal listed in its permissions.
It contains no analytics, no tracking, no advertising and no remotely-hosted code.
It never sells or transfers data to third parties, and never uses data for creditworthiness or lending.
It has no access to browsing history, bookmarks, downloads or saved passwords.

Who can see the data

Once received, the data is held in the company's operations portal under that portal's own access rules: operations staff see what their role permits, and delivery associates see only their own records. Access is limited to the employees of the company whose portal it is; no other company on OpsBrio can see it, and OpsBrio's own staff reach a company's records only with that company's agreement, to support it.

How long it is kept

Operational records are retained for as long as the company needs them to run and account for its operation. Photographs are deleted automatically on a retention schedule set by the company. An employee may ask the company to tell them what is held about them, or to correct it.

Uninstalling

Removing the extension from Chrome stops all reading and sending immediately and deletes everything it stored locally.

Contact

This policy covers the Chrome extension. The service it sends data to has its own, alongside the terms it is provided under: opsbrio.com/privacy and opsbrio.com/terms.

Questions about this policy: privacy@opsbrio.com. Questions about what a particular company holds about you go to that company — it is the controller of its own records.

Effective 18 October 2026 — each delivery associate's customer feedback for the week, as counts by staff identifier; each finished route's stops, their finish times, delivered counts and five-digit zip codes, with the route's customers' names, telephone numbers and street addresses, and where the van stood, discarded before anything leaves the browser (versions before 1.0.17 sent that page whole; the portal read only the van's unplanned stops and kept nothing else) (17 October: a hiring candidate's drug test, and a delivery associate's whose identifier the company does not hold yet: the identifier the company orders it with and the testing vendor's status; the pickups Amazon marks as missed, their customers' addresses discarded; 14 October: whose Amazon session the browser is signed in to, checked before anything is sent, and the company's own station list with its counts, its vans among them; 8 October: the Work Summary added to what it reads) (first published 30 August 2026 under the first company's name; the practice is unchanged, the product now has its own). If this policy changes, the effective date above changes with it.

OpsBrio — Cortex sync