Privacy Policy
Taipo automates Amazon Associates and Creator Connections reporting inside your own browser. This page explains, plainly, what the extension can access and — just as important — what it never does with it.
In short: Your Amazon data stays local by default — Taipo has no server for it, and nothing about your sales, earnings, or account is sent anywhere unless you explicitly turn on Google Drive Backup yourself. Even then, it only ever goes to a folder in your own Google Drive, never to a server Taipo operates. The other exception is a minimal, anonymous usage ping, unrelated to your Amazon data, described in §4.
§1
What Taipo reads
Taipo reads pages you are already logged into and viewing as part of your Amazon Associates, Amazon Influencer, and Creator Connections accounts — earnings reports, click and conversion data, product and campaign details, and (if you configure it) your own YouTube channel's video list. It reads this data either when you manually run a task, or on a schedule you set yourself.
Taipo does not access any Amazon account other than the one you are signed into in your browser, and does not access any page or account you haven't directed it toward.
§2
Where it goes
By default, nowhere but your own machine. Fetched data and your settings are stored locally using your browser's own storage (chrome.storage and IndexedDB). Taipo does not operate a server for this data, and has no account system of its own to upload it to.
Uninstalling the extension removes all of this data along with it, except for whatever you've separately chosen to back up to your own Google Drive — see §3.
§3
Optional: Google Drive Backup & multi-device sync
Off by default. If you choose to connect a Google account from the Profile page, Taipo gains the ability to write to a folder it creates in your own Google Drive, named "Taipo Backups." Nothing in this section happens unless you take that explicit step.
Once connected, three kinds of files can be written there, all under your own Google account, never to any server Taipo operates:
- Full backups — a snapshot of your local settings and fetched data (the same data described in §1), written on the schedule you configure, so it can be restored if you reinstall or switch devices.
- Device coordination files — small control files used only if you run Taipo on more than one device: which device is currently "active," and a periodic heartbeat timestamp from each device you've connected. These contain no Amazon data.
- A small dashboard snapshot — a lightweight copy of what your Dashboard Home page currently shows (the same summary cards you'd see on screen), refreshed periodically, so a second device you own can display a read-only mirror of your main device's dashboard without needing a full backup transfer.
This uses Google's drive.file permission scope specifically — by Google's own design, that means Taipo can only ever see or manage files it creates itself. It cannot browse, read, or touch any other file or folder already in your Drive.
You can disconnect at any time from the Profile page. Disconnecting stops future backups immediately but does not delete files already written — you're free to delete the "Taipo Backups" folder yourself directly in Google Drive whenever you'd like.
§4
Anonymous usage statistics
Taipo sends a daily ping to our own analytics endpoint so we can track real install and usage counts, separately from the Chrome Web Store's own count. This is unrelated to §1–§3 — it never includes any Amazon, Associates, Influencer, or Creator Connections data, and is not linked to your Amazon account, name, or email.
Two tiers:
- Always on: a randomly generated install identifier and Taipo's version number. Your approximate US state may be inferred by our server from your network connection at the moment of the ping — Taipo itself never reads or transmits any location or IP data; that inference, if any, happens entirely on the receiving end.
- Opt-in (Settings → "Share anonymous usage stats," off by default): additionally includes how many tasks you have configured and which built-in task types they are. Task names, schedules, and any data those tasks fetch are never included.
This data is not sold, shared with third parties, or used for anything beyond understanding Taipo's own usage.
§5
What we don't do
- No analytics tied to your identity, your Amazon account, or your browsing — see §4 for the one minimal, anonymous exception.
- No advertising, and no data shared with advertisers.
- No selling, renting, or otherwise sharing your data with third parties.
- No access to your Google Drive beyond files Taipo itself creates, and only if you explicitly connect it — see §3.
- No access to any site or account beyond what's listed in §6.
§6
Permissions, and why each exists
Chrome extensions must declare everything they might touch up front. Here is every permission Taipo requests and the specific job it does:
Browser permissions
tabs
Find, open, and switch between the Amazon tabs a task needs to run in.
tabGroups
Group the tabs a running task opens, so a multi-step fetch doesn't scatter loose tabs across your window.
scripting
Read data out of an open Amazon or YouTube page you're already viewing — the mechanism behind every data fetch.
storage / unlimitedStorage
Save your settings and fetched data locally. Sales and collection history can grow past Chrome's default storage limit, hence the unlimited grant.
alarms
Run a task on the schedule you set, without needing the dashboard tab open — also what triggers the daily anonymous usage ping (§4) and, if connected, Google Drive Backup (§3).
notifications
Show a system notification when a scheduled task finishes or a watcher rule you configured fires.
webRequest
Observe (never modify) requests to Amazon's own domains, to capture the request details needed to call the same internal endpoints the Amazon page itself already uses.
contextMenus
Adds a right-click shortcut for looking up a product ASIN.
identity
Shows Google's own sign-in screen when you choose to connect a Google account for Drive Backup (§3) — only used if you take that step yourself.
Site access
amazon.com
amazon.ca / .co.uk / .com.au
affiliate-program.amazon.com
Read your own Associates, Influencer, and Creator Connections data for each marketplace you use.
m.media-amazon.com
Load product images already shown on pages you're viewing.
youtube.com
Match your uploaded Amazon videos against your own YouTube channel, if you've configured one.
raw.githubusercontent.com
Fetch a small, static, public JSON file listing in-app feature announcements. No user data is sent with this request.
googleapis.com
accounts.google.com
Google's own sign-in and Drive API, used only for the optional Drive Backup feature described in §3 — nothing here is contacted unless you connect your Google account yourself.
taipo-telemetry.mckayjunk.workers.dev
Receives the anonymous usage ping described in §4. No Amazon, Associates, Influencer, or Creator Connections data is ever sent to this address.
§7
Changes to this policy
If Taipo's data handling changes, this page will be updated first, and the version number above will change accordingly.
§8
Contact
Questions about this policy or how Taipo handles data can be sent to mckayjunk@gmail.com.