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, the stop's five-digit zip code and the town of its address; 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 town 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 — the complaints customers made about a delivery, each with its package and Amazon's words for it (a positive response leaves the browser only as its day or week, the associate and that it was positive), 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; and each of Amazon's work blocks the company has handed to one of them for those weeks — the day, the block's start and length, Amazon's name for its type (which says the van's size), whether it is a driver's or a helper's seat, and its status. The same page also shows each person's name, contact details and Amazon's own identifiers for the block: none of those leave the browser
Amazon's plan for the company's routes, for the current week and the next three: for each day and each of Amazon's route types, the routes Amazon has assigned the company, Amazon's route target and the capacity the company entered. These are counts about the company's own work — no person is named or identified in them, and the company's Amazon account identifiers stay in the browser
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
Amazon's Book Training class calendars for every Amazon station where the company's delivery associates may be trained — the company's own and any other Amazon station Amazon's Book Training lists for it: each class's dates, times, course and seats, and each such station's code, Amazon's name for it and its time zone. No person is named or identified in them
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 also goes with each request to the company's own portal, so the portal can refuse another company's data as well
The company's own invoices in Amazon's Invoice Portal: each invoice's kind, station, service period, issue date, dispute deadline, amount and status; and, for the company's fleet invoices, each vehicle type's monthly rate and what Amazon paid, each day's registered and paid vehicles by type with Amazon's daily rate and amount, each week's fleet requirement counts, the disputes the company sent (the days, the quantities asked for and the company's own note) and Amazon's adjustments; and, for its weekly invoices, each day's lines as Amazon prints them (what was paid for, how many, the rate and the amount), each kind's total, and the disputes the company sent on them as Amazon's columns name them (the kind of line, the day, the count asked for) with the company's own note — a column that could name a person is not kept. These are the company's business records — no person is named or identified in them — and Amazon's account, tax and draft invoice identifiers stay in the browser. Read only in the browser of a staff member whose job in the portal covers Finance
The link Amazon gives to the company's rate card (Business Administration › Company Documents). The extension sends only that link; the company's portal fetches the card itself. The card holds the company's rates; no person is named in it
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.

When it fills in a form for you

When a staff member presses Copy & open in the company's portal, the portal opens Amazon's own form in a new tab with the words in the page address's fragment — the part after #, which the browser never sends to Amazon — and the extension fills the form in that staff member's browser: Support Central's case form, or the Invoice Portal's re-dispute once the staff member has opened it. It reads the words once and removes them from the address bar. It never presses Next, Submit, Re-dispute or Accept invoice: the staff member checks every field and sends it, or doesn't.

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 submits a form or presses a button that sends anything to Amazon. Copy & open fills Amazon's form; a person sends it.
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 26 October 2026 — the company's weekly invoices are read line by line as well: each day's lines, each kind's total and the disputes the company sent on them (from version 1.0.28; no person is named or identified in them); a positive customer response leaves the browser only as its day or week, the associate and that it was positive, never its package or the customer's words, and a large day of data is sent in several smaller posts (from version 1.0.27; before it the whole response went) (25 October: the company's own invoices in Amazon's Invoice Portal and, for its fleet invoices, their days, weekly counts, disputes and Amazon's adjustments; the link to the company's rate card, which the portal fetches; and Copy & open, which fills Support Central's case form and the Invoice Portal's re-dispute from words in the page address and never sends them (from version 1.0.26; no person is named or identified in an invoice or a card)) (23 October: Fleet Portal's weekly fleet-requirement card for each of the company's stations: Amazon's requirement for the week, its planned, supplemental and allowance counts, the company's Amazon-owned van count and Amazon's count of executed routes (from version 1.0.25; counts only, no person is named or identified in them); and the Book Training class calendars of every Amazon station Amazon's Book Training lists for the company, with each such station's code, Amazon's name for it and its time zone (from version 1.0.24; no person is named or identified in them)) (22 October: Amazon's plan for the company's routes for the current week and the next three, as counts per day and route type (from version 1.0.23; no person in them); the short code of the company the browser's Amazon session belongs to, and the extension's version, sent with each request to the company's own portal (from version 1.0.22; before it the code stayed in the browser); each of Amazon's work blocks the company has handed one of its delivery associates for the current and next week: the day, the block's start, length, type and seat, by staff identifier (from version 1.0.21; never a name, contact details or Amazon's own identifiers)) (19 October: the town of each finished route's stop beside its zip code (from version 1.0.20; never the street, the customer or a telephone number)) (18 October: 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