GoBags Dashboard Privacy Policy

This policy governs GoBags Dashboard (the “Application”), an Amazon Selling Partner API application built and operated by entrpy, LLC (“entrpy”, “we”), a South Carolina limited liability company. It describes what the Application collects from a seller’s Amazon account, how that data is used, stored, protected, retained, and deleted, and how a seller revokes access.

It is written to comply with the Amazon Services API Data Protection Policy and the Acceptable Use Policy. Where this policy and those policies conflict, Amazon’s policies control.

1. What the Application collects

The Application reads data from a seller’s Amazon account only after the seller authorizes it through Amazon OAuth, and only within the seven Selling Partner API roles entrpy holds, all of which are Normal roles:

• Selling Partner Insights: marketplace participation.
• Inventory and Order Tracking: order headers and order line items (SKU, ASIN, quantity, item price, status, purchase date).
• Amazon Fulfillment: FBA inventory summaries and inbound shipment contents.
• Amazon Warehousing and Distribution: AWD inventory levels and inbound shipments.
• Finance and Accounting: financial events and event groups, including fees, refunds, reimbursements, and settlement totals.
• Product Listing: catalog attributes for the seller’s own listings.
• Pricing: the seller’s current and competitive prices for their own listings.

2. What the Application does not collect

entrpy holds no Personally Identifiable Information roles and no Restricted roles. The Application does not collect, request, receive, store, or process buyer names, buyer shipping or billing addresses, buyer email addresses, buyer phone numbers, gift messages, or tax and regulated information. It does not request Restricted Data Tokens.

This is enforced in the Application’s code, not only by Amazon’s permission model. Selling Partner API paths that expose buyer information are on an explicit denylist and are refused before any request is sent, even though the roles entrpy holds would not return that data in the first place.

3. Read-only access

The Application performs read operations only. It makes no write call to Amazon of any kind: no listing creation, edit, or deletion, no price change, no inventory or feed submission, no report creation, no order action, and no buyer or solicitation messaging.

This is enforced in code. The Application has a single function through which all Selling Partner API traffic passes. That function issues an HTTP GET with the method as a hardcoded literal, constructs no request body, and matches every path against a fixed allowlist of read operations before opening a connection. A path that is not on the allowlist is refused. An automated test asserts this invariant on every change.

4. How the data is used

Seller data is used for one purpose: to render the seller’s own analytics inside the seller’s own dashboard, so that the seller can see inventory position, sell-through rate, reorder timing, and landed margin. It is used for no other purpose.

Seller data is not used to train machine learning models. It is not sent to a large language model. It is not aggregated across sellers, used for benchmarking, used for advertising, or used for entrpy’s own commercial analysis.

5. Sharing

entrpy does not sell, rent, resell, license, or share seller data with any third party. There is no advertising network, no analytics provider, no data broker, and no model provider in the path of seller data.

The Application runs on infrastructure operated by three providers, who process data solely as infrastructure for entrpy and have no independent right to use it:

• Vercel, which hosts the Application.
• Supabase, which hosts the Application’s Postgres database.
• Cloudflare, which enforces the login perimeter in front of the Application.

entrpy will disclose seller data to a government or law enforcement body only where legally compelled, and, unless legally prohibited, will notify the seller and Amazon before doing so.

6. Storage and encryption

In transit. All communication with Amazon uses HTTPS with TLS. The Application calls only sellingpartnerapi-na.amazon.com for data and api.amazon.com for token exchange. The Application makes no plaintext HTTP call. The dashboard itself is served over HTTPS.

Credentials. The Login with Amazon client ID, client secret, and the seller’s long-lived refresh token are stored as server-side environment variables on Vercel, which encrypts them at rest. They are never committed to source control, never included in the browser bundle, never exposed to any client-side code, and never written to a log.

Refresh token handoff.A refresh token is issued to the Application at the moment the seller completes Amazon’s consent screen. Between that moment and the moment it is placed into the Vercel environment, it is held in a single database row encrypted with AES-256-GCM. The encryption key exists only as an environment variable and never in the database, so a copy of the database alone does not yield a usable Amazon credential. That row is deleted once the token is in place. It is a courier, not a credential store, and runtime calls never read from it.

Seller business data. The non-PII business records the Application derives from Amazon data (per-SKU units, revenue, inventory counts, fees) are stored in the Application’s managed Postgres database, which encrypts data at rest at the storage layer.

7. Access control

The dashboard sits behind Cloudflare Access. Reaching it requires authenticating against an identity provider and appearing on an explicit email allowlist; every request carries a signed assertion that the Application verifies before serving a byte. Database credentials are held server-side only and are never sent to the browser. The table that holds the encrypted token has row-level security enabled with no policy, so no browser client can read it under any circumstance.

Access to seller data inside entrpy is limited to the personnel who operate the Application and need it to do so.

8. Retention and deletion

The Application stores no Amazon buyer Personally Identifiable Information, so the Data Protection Policy’s 30-day PII retention limit has nothing to act on. The records it does retain are the seller’s own non-PII business data, kept for as long as the seller is engaged with entrpy, because deleting them would delete the seller’s own history.

A seller may request deletion at any time. On request:

• entrpy deletes the seller’s data from the Application’s database and destroys the stored refresh token within 30 days.
• The same happens automatically at the end of the engagement, without the seller having to ask.

Amazon data is fetched from Amazon on demand rather than mirrored wholesale, so the source of truth for a seller’s Amazon records remains Amazon, and it is governed by Amazon’s own policies.

9. Revoking access

A seller may revoke the Application’s access at any time, without contacting entrpy, from Seller Central: Apps and Services → Manage Your Apps → Revoke access next to GoBags Dashboard. Revocation invalidates the refresh token immediately, and the Application loses the ability to read anything from the seller’s Amazon account from that moment.

10. Security incidents

If entrpy becomes aware of a security incident affecting Amazon Information, entrpy will notify Amazon at security@amazon.com within 24 hours of discovery, notify the affected seller, investigate, and preserve the relevant records for use in the investigation, in accordance with the Data Protection Policy.

11. Changes to this policy

entrpy may update this policy as the Application changes. The “Last updated” date above reflects the most recent change. A change that broadens what the Application reads or how it uses seller data will not be applied to an existing seller without notice.

12. Contact

Privacy questions, data access requests, and deletion requests: andrew@entrpy.co.

entrpy, LLC, a South Carolina limited liability company. Company website: entrpy.co.

Amazon, Amazon Seller Central, Fulfillment by Amazon, Amazon Warehousing and Distribution, and the Amazon Selling Partner API are trademarks of Amazon.com, Inc. or its affiliates. entrpy, LLC is an independent software developer. It is not affiliated with, sponsored by, or endorsed by Amazon.