AfterShip Carrier Claims — Chrome Extension Privacy Notice
Last updated: 24 September 2026
Last updated: 24 September 2026
1. Scope
This notice describes how the AfterShip Carrier Claims Chrome extension handles data. It supplements the AfterShip Privacy Policy, which covers AfterShip's own practices, and the Data Processing Addendum, which governs data we process on behalf of our customers.
2. What the extension is for
The extension has a single purpose: to fill a merchant's own AfterShip shipment data into the claim forms on usps.com and ups.com. The merchant reviews every field and submits the claim themselves.
3. What the extension reads
From the merchant's AfterShip account — only for the shipment the merchant chose to claim: shipment details (tracking number, carrier, service, ship date, weight, package count, ship-from and delivery addresses), recipient details (name, address, and phone where the carrier's form asks for it), order and item details (item name and description, quantity, item value, purchase date, order value, shipping fee), the insurance fee where one is recorded, and the claim reason. The exact set depends on which fields the carrier's form actually has.
From the carrier's claim page — only what filling the form requires: which step of the form is open; the tracking number the form is bound to, so one shipment's data is never written into another shipment's claim; for the fields the extension itself filled, whether the value was accepted and whether the portal flagged it; the labels of the options it has to choose between; and the portal's own notice when it refuses a claim, so the panel can stop and tell the merchant. That notice stays inside the extension — only our own status code reaches AfterShip. The extension reads nothing else on the page: no unrelated page text, no keystrokes, no mouse activity, and no browsing history.
From the browser — a truncated hash of the AfterShip session cookie on accounts.aftership.com, used only to tell a real sign-out from an ordinary cookie refresh. The cookie value itself is never stored or transmitted.
4. What the extension writes
The extension writes only into the input fields of the carrier's claim form, and only the values described in section 3. The extension also stores one value in the carrier site's own session storage: the tracking number the claim form is currently bound to, so the panel can still tell which shipment a confirmation page belongs to after the portal reloads the page. That value is cleared when the browser closes, and nothing else is written to any site. The extension never submits a claim. Today it does not upload any files; if we add that — for example attaching damage photos already held in the merchant's account — we will disclose it inside the extension and update this notice before the change takes effect.
5. What is sent to AfterShip
Two requests, both to AfterShip's own backend:
- when the merchant clicks "Fill carrier form" and at least one field is filled: the shipment and claim identifiers, so the claim record shows the merchant started filing;
- when the carrier accepts the claim: the shipment and claim identifiers, the carrier, and the tracking number read from the carrier's page, used to confirm the claim matches the shipment before the record is marked as submitted. This read-back is used only to close out the claim's status; it is not used for analytics.
No content from the carrier's page is sent beyond that tracking number, and the extension does not send data to any other destination.
6. What is stored on the device
Five small values in extension storage, and nothing else: the AfterShip organization the panel should load; the shipment the merchant clicked "File a claim" on (its ID, tracking number and carrier), removed once the panel has opened it; the session-cookie hash described in section 3; the URL patterns the panel sends down for recognizing the carrier's claim pages, which are plain text used for matching, not code; and a note that the merchant has seen the in-extension data disclosure, together with its version, so the notice is shown once and shown again only if our data handling changes. Session-scoped values are cleared when the browser closes. Separately, the extension keeps in the carrier site's own session storage the single value described in section 4. The panel also keeps claim-acceptance records in browser storage until they reach our backend, so closing the panel does not lose them.
7. Service providers
The extension package itself contains no third-party code and sends data to no third party. The panel displayed inside it is part of the AfterShip web application, and like the rest of that application it uses a third-party product analytics provider. That provider receives usage events — for example that the data disclosure was acknowledged, that a claim was opened, that a form was filled, and how many fields were filled — together with the signed-in user's email address and id and the organization's id and name, the same identity we use across the AfterShip web application, plus the browser and IP telemetry its script collects. It never receives content from carrier pages, recipient details, or order data. No other provider receives data from the panel.
8. Limited Use
Our use of data collected through this extension adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only for the single purpose described in section 2, is not sold or transferred to third parties except as needed to provide that functionality, is never used for advertising or to build advertising profiles, and is not used to determine creditworthiness or for lending.
9. Roles
Merchant and recipient data handled by the extension is processed by AfterShip as a processor under the customer's Data Processing Addendum; the AfterShip Privacy Policy covers AfterShip's own controller-side practices.
10. Retention
The extension does not retain the data it fills into carrier forms. Records created in the merchant's AfterShip account follow that account's retention. Data stored on the device is retained as described in section 6.
11. Changes
Before any change to the extension's data handling takes effect, we disclose it inside the extension. The first-run disclosure carries a version number; raising that version shows the notice again to merchants who have already accepted the previous one. This notice is updated at the same time.