Privacy policy.

What you provide.

A free Amazon check request includes your brand, Amazon link or ASIN, marketplace and work email. The request may also include the ad source from the link you followed. A product question includes the product details and contact information you enter. A call booking includes the information you give Cal.com.

Requests are kept as correspondence in the info@baregold.ca inbox, in internal alerts, and in our application’s database, where we prepare your free Amazon check from them. To prepare it we read public information about your brand’s Amazon listings and Health Canada’s licence databases. Server logs use request identifiers without contact details. Email info@baregold.ca to have your request deleted.

We may follow up about your request. Every email identifies BareGold and our mailing address. Reply “no” or email info@baregold.ca to stop further emails.

Your tracking choice.

Google Analytics, Google Ads and Microsoft Clarity stay off until you accept optional tracking. You can reject it and still request a free Amazon check, ask a question or open the booking calendar. Your choice is stored in your browser. Brief request-confirmation records in your browser contain only timestamps.

Use the Tracking preferences button to change your choice. Rejecting after accepting stops future tracking; it does not erase information already collected by those providers.

Amazon seller data (clients only).

We receive Amazon account data only from clients, after they accept and pay the starter terms, and only through the connections they grant.

What we collect.

• SP-API connection, by invitation only, to our app Baregold-Production-API. We store the seller’s selling partner ID, the marketplace (Amazon.com or Amazon.ca), a label with the client’s name, the refresh token Amazon issues, the connection date and any revocation date. When the connection is made, we read one page of that seller’s listings to confirm the token belongs to that seller. We do not store the result.
• DataDoe connection, which the client authorizes. DataDoe collects account data from Seller Central and Amazon Ads: sales, fees and settlements, inventory, listings, account health and ads performance.
• Cost sheet: the landed cost per product that the client sends us.

Why we use it.

Only to do the work the client engages us for, such as the account check-up, listing fixes, cases and ads, and to confirm that the right seller connected. A client’s data serves only that client. We do not sell it.

Where it is stored and how it is protected.

• The connection record is kept in our application’s Neon Postgres database. The refresh token is encrypted with AES-256-GCM and bound to the seller ID.
• Our code does not write the token or Amazon’s one-time authorization code to its logs, and does not put either into a page or a link. Vercel’s request logs can record the one-time code, which expires after 5 minutes.
• The connection pages use HTTPS, are not cached and send no referrer. Each connection attempt is checked with a signed, secure, HTTP-only cookie that expires after 10 minutes.
• DataDoe stores the account data it collects. Our app reads it from a Google BigQuery dataset provided through DataDoe’s BigQuery integration, using a read-only service account.
• Access to our app is limited to named people, by password.

Who it is shared with.

• Amazon, for the token exchange and SP-API calls.
• DataDoe, which stores and processes the account data. We use DataDoe’s Actions to make changes the client has approved.
• Our infrastructure providers: Vercel (hosting), Neon (database) and Google (BigQuery, and Google Workspace email).

Client data and deletion.

Nothing is connected to your Amazon account until you accept and pay the starter terms. A client’s data serves only that client. Its name or results go elsewhere only with its written OK.

We delete a client’s data within 30 days of the earliest of: you revoking access, the end of our service (including a starter with no monthly work after it), or any other loss of access. This is our commitment, and a person carries out each deletion.

When our service ends, we disconnect everything that same day, delete the stored SP-API token and start deletion here and at DataDoe. Today this is done by hand: we record the revocation date, delete the connection record, remove the seller from DataDoe and ask DataDoe to delete its data.

We keep request correspondence while handling and following up on the request. Contact us about access, correction or deletion of your information, including client data.