This Privacy Policy explains exactly what data the Obserway Assistant Chrome extension ("Extension") collects, how it is used, processed, retained, and with whom it is shared. Please read it carefully.
1. Who We Are
The Extension is developed and operated by Obserway. For questions, contact us at [email protected].
2. What Data We Collect
2.1 Amazon Order Data (from Seller Central)
| Data Field | Purpose |
|---|---|
| Amazon Order ID | Unique identifier to track each order |
| Order status (Unshipped, Shipped, etc.) | Determine which orders need processing |
| Order date, latest ship date, latest delivery date | Scheduling and deadline tracking |
| Sales channel (e.g., Amazon.com.mx) | Route orders to the correct workflow |
| Total order amount and currency | Financial record keeping |
| Product title, ASIN, seller SKU, quantity, unit price | Identify ordered products |
| Buyer full name | Address shipment |
| Shipping address (line 1, line 2, city, state, postal code, country) | Fulfil the shipment |
| Buyer phone number (where available) | Carrier delivery requirement |
| Buyer email address | Order association and account matching |
| Tracking number | Upload shipping confirmation to Amazon |
| Shipping service and fulfilment method | Carrier identification |
2.2 Amazon Account Health / Performance Notifications
On Amazon Seller Central (sellercentral.amazon.com.mx and sellercentral.amazon.ca), the Extension reads your store's performance notifications and policy-compliance messages. From these it extracts product identifiers (ASINs) and the notification subject/reason, which are sent to the Obserway backend so your account-health issues can be surfaced and tracked. No buyer personal data is collected from these notifications.
2.3 Authentication Data
- Obserway account access token – A short-lived JWT issued by Obserway upon login. Stored locally in Chrome's storage.local. Used exclusively to authenticate requests to the Obserway backend.
- Obserway account refresh token – A long-lived JWT issued by Obserway. Stored locally and on the Obserway backend (obserway.quicklycommerce.com) to obtain new access tokens automatically when the previous one expires. Used exclusively for authentication with Obserway servers.
- Obserway account username (email) – Stored locally in Chrome's storage.local and on the Obserway backend to associate order data with your account.
- Obserway account password – Submitted only at the moment of login. Transmitted over HTTPS to the Obserway backend (obserway.quicklycommerce.com) where it is stored encrypted at rest. It is used exclusively to refresh expired authentication tokens server-side on your behalf when the Extension is not actively running, ensuring uninterrupted order syncing. The password is never shared with any third party and is never sent to Amazon, Telegram, or any other service.
2.4 Browser Tabs and Amazon Page Content
- Tab metadata (read-only): The Extension queries open tabs solely to detect whether an Amazon Seller Central tab is already open, which determines whether to open a background tab for order fetching. Tab URLs are not stored or transmitted.
- Amazon page content: Content scripts injected into amazon.com, sellercentral.amazon.com, sellercentral.amazon.com.mx and sellercentral.amazon.ca pages read the order, buyer, address, tracking and account-health information shown on those pages. This is the source of the data described in Sections 2.1 and 2.2. No keystrokes, passwords, or unrelated page content are read.
2.5 Browsing History
The Extension uses the Chrome history permission to perform a single, local presence check: it queries your browser history for a recent visit to sellercentral.amazon in order to determine whether you operate as a seller or a buyer, which controls which features run. Only a yes/no result is used. No browsing-history URLs, titles, timestamps, or counts are stored, logged, or transmitted off your device.
2.6 Affiliate / Partner-Site Activity
On a defined list of Obserway partner and affiliate websites (product-review blogs and link pages listed in the Extension's manifest), the Extension displays a brief loading overlay and reads the page's outbound links to identify the Amazon product (ASIN) you are navigating to. That ASIN is sent to affiliate-api.quicklycommerce.com to generate the correct Amazon affiliate redirect link. No personal data is collected on these sites — only the product identifier (ASIN) and the fact that a product link was clicked. These scripts run only on the partner domains explicitly listed in the Extension and on amazon.com; they do not run on arbitrary websites.
2.7 Operational Telemetry
For reliability monitoring, the Extension sends the following information — relayed through the Obserway backend (obserway.quicklycommerce.com), not directly from the Extension — to a private Telegram bot operated solely by Obserway staff:
- Your Obserway username
- Error messages and diagnostic events (e.g., failed token refresh, scraping errors, stale fetch alarms, shipping-upload failures)
- Counts of orders processed
No buyer personal information, no passwords, and no order contents are ever sent to Telegram. The Telegram bot credentials are held only on the Obserway backend and are never included in the Extension. This channel is used exclusively for internal operational monitoring by Obserway staff.
2.8 Connection / Network Data
When the Extension submits order data to the Obserway backend, our server records the IP address from which the request originated, stored alongside the associated order record. This IP address is collected server-side (it is not read or stored by the Extension on your device) and is used only for security, fraud prevention, and abuse/duplicate-account detection. It is not shared with any third party.
3. How We Use This Data
- Sync Amazon order details to the Obserway platform for centralised order management.
- Forward order and address data to the Obserway fulfilment service so shipments can be dispatched.
- Automate shipping confirmation uploads (tracking numbers) back to Amazon Seller Central on your behalf.
- Surface Amazon account-health / policy notifications affecting your products.
- Determine seller-vs-buyer role so the correct features run.
- Generate correct Amazon affiliate redirect links on partner sites.
- Display order status and operational summaries inside the Extension popup.
- Detect and alert on orders that are delayed or missing data.
- Maintain uninterrupted authentication so that order syncing continues even when your browser is closed.
- Protect the service through security monitoring, fraud prevention, and abuse/duplicate-account detection.
4. How Data Is Processed
- The Extension scrapes order data from Amazon Seller Central pages you have open in your browser, via a content script injected on those pages.
- Scraped data is sent over HTTPS to the Obserway backend API at obserway.quicklycommerce.com, where it is stored in a secured MySQL database associated with your account. When order data is received, our server also records the originating IP address with the order (see Section 2.8).
- The backend then forwards order data to the Obserway fulfilment platform at obserway.com to generate shipment records.
- When tracking numbers are available, the Extension uploads them to Amazon Seller Central on your behalf using your existing authenticated Amazon session.
- Account-health notifications read from Seller Central are sent to the Obserway backend for tracking.
- On partner sites, product identifiers (ASINs) are sent to affiliate-api.quicklycommerce.com to build affiliate redirect links.
- If your access token expires while the Extension is not running, the Obserway backend uses your stored credentials to obtain a new token automatically.
5. Third Parties We Share Data With
| Party | Data Shared | Purpose | Relationship |
|---|---|---|---|
| Amazon / Amazon Seller Central (amazon.com, sellercentral.amazon.com, sellercentral.amazon.com.mx, sellercentral.amazon.ca) | Tracking numbers | Uploading shipping confirmations on your behalf | Your existing Amazon seller account; data is read from and written to Amazon only under your authenticated session |
| Obserway Backend (obserway.quicklycommerce.com) | All order data listed in Section 2.1, account-health notifications (2.2), your username, your encrypted password, refresh tokens, and the originating IP address (2.8) | Order storage, processing, management, security monitoring, and server-side token refresh | Operated by Obserway (first party) |
| Obserway Fulfilment Platform (obserway.com) | Order details, shipping address, buyer name, phone, products | Generate shipment records and assign tracking numbers | Operated by Obserway (first party) |
| Quickly Commerce Affiliate API (affiliate-api.quicklycommerce.com) | Your Obserway username and product/ASIN identifiers | Internal Obserway analytics and affiliate-link processing | Operated by Obserway (first party) |
| Telegram Bot API (api.telegram.org) | Your Obserway username and operational diagnostics (see Section 2.7), relayed via the Obserway backend | Transport for internal operational alerts to a private Obserway-owned bot | Telegram is used solely as a message-transport service; messages are received only by Obserway staff |
We do not sell, rent, or share your data with any other third parties, advertising networks, or analytics providers. Your browsing history is never shared with anyone (see Section 2.5).
6. Data Storage
- On your device (Chrome storage.local): Authentication tokens (access + refresh), username, fetched order list, detected role, extension logs. Cleared automatically when you uninstall the Extension or log out.
- On Obserway servers (obserway.quicklycommerce.com):
- Order records, shipping addresses, product details, tracking numbers, buyer name/phone/email — stored in a secured MySQL database.
- Account-health notification records (ASINs and reasons).
- The originating IP address recorded with each order (see Section 2.8).
- Encrypted Obserway account credentials (username + password) used exclusively for server-side token refresh.
- Refresh tokens used exclusively for Obserway authentication.
7. Data Retention
- Active order data – retained while your Obserway account is active and for up to 90 days after an order is fully shipped and closed. The IP address recorded with an order is retained for the same period as that order record.
- Authentication tokens – retained locally until you log out or uninstall the Extension. Server-side tokens expire automatically.
- Stored credentials (password) – retained only while your Obserway account is active. Deleted within 30 days of account deletion or when you log out from all devices.
- Deleted accounts – upon account deletion request, all stored data associated with your account (orders, addresses, credentials, tokens, recorded IP addresses) is permanently deleted within 30 days.
8. Security
All communication between the Extension and our servers is encrypted using HTTPS/TLS. Sensitive credentials are stored only in Chrome's storage.local (not storage.sync) and are never exposed to web pages. Server-side credentials are encrypted at rest. We follow industry-standard security practices including access controls, encrypted connections, and regular security reviews.
9. Your Rights
You have the right to:
- Access the data we hold about you.
- Correct inaccurate data.
- Delete your data by requesting account deletion.
- Export a copy of your order data.
To exercise any of these rights, contact us at [email protected].
10. Children's Privacy
The Extension is intended for use by business operators aged 18 and above. We do not knowingly collect data from children under 13.
11. Changes to This Policy
We may update this Privacy Policy periodically. The "Last updated" date at the top of this page will reflect any changes. Continued use of the Extension after changes constitutes acceptance of the updated policy.
12. Contact
For privacy questions or data requests:
📧 [email protected]
🌐 obserway.com