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 data stays in your own browser by default — Taipo has no server for it and no account system of its own. Data only leaves your browser when you connect a service yourself (your own Google Drive, your YouTube channel, GeniusLink, or Amazon's Creators API), and then it goes only to that service, under your own account. The one exception is a minimal, anonymous usage ping, unrelated to your data, described in §6.
§1
What Taipo reads
Taipo reads pages you are already signed into as part of your Amazon Associates, Amazon Influencer, and Creator Connections accounts — earnings reports, click and conversion data, and product and campaign details. It also reads public Amazon product pages (title, price, rankings, product details) and, if you use the Walmart availability feature, public Walmart.com product pages. It reads this data when you 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, notes, and settings are stored locally using your browser's own storage (chrome.storage and IndexedDB). Taipo does not operate a server for this data.
Some small settings (such as your tracking IDs) and, as a fallback, your notes are stored in chrome.storage.sync, which Chrome itself syncs between your own signed-in Chrome browsers. That sync is run by Chrome under your Google account, not by Taipo.
Uninstalling the extension removes all locally stored data along with it, except for whatever you've separately saved to your own Google Drive — see §3.
§3
Optional: Google account connections
Off by default. You can connect Google services from Taipo's Profile page or Settings → Connections. Each one shows Google's own sign-in and consent screen, asks only for the permission listed below, and can be disconnected separately. Nothing in this section happens unless you take that step yourself.
Google permissions Taipo can request
drive.file
Create and update files in a "Taipo Backups" folder in your own Google Drive. By Google's design, this permission only lets Taipo see files it created itself — it cannot browse, read, or change any other file in your Drive.
userinfo.email
Show which Google account is connected (e.g. "Connected as you@gmail.com").
youtube.readonly
Read your own YouTube channel's video list and each video's title, description, publish date, and public statistics (views, likes, comments). Read-only — Taipo cannot upload, edit, delete, or comment on anything.
yt-analytics.readonly
Read daily view counts for videos on your own channel, so you can compare how videos perform over a date range. Read-only — Taipo cannot change anything on YouTube.
With Google Drive connected, Taipo can write these files to the "Taipo Backups" folder, all under your own Google account and never to any server Taipo operates:
- Backups — a snapshot of your settings and fetched data (§1), on the schedule you set, so it can be restored on reinstall or on another device.
- Notes sync files — your Taipo notes, so they sync between your own devices.
- Device coordination files — which of your devices is currently "active," plus a heartbeat timestamp per device. These contain no Amazon data.
- A dashboard snapshot — a lightweight copy of your Dashboard Home summary, so a second device you own can show a read-only mirror.
- Exports you choose to save there, such as a notes export.
YouTube and YouTube Analytics data is stored only in your browser, alongside your other Taipo data, and in any backup you save to your own Drive.
Google API Services — Limited Use. Taipo's use and transfer of information received from Google APIs adheres to the
Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the features described on this page, is never sold, never used for advertising, never transferred to anyone else, and never read by a person.
YouTube. Taipo uses YouTube API Services. By connecting YouTube you also agree to the YouTube Terms of Service, and Google's handling of your data is covered by the Google Privacy Policy.
Disconnecting. You can disconnect any Google service in Settings → Connections, which also revokes Taipo's access at Google. You can also revoke access at any time from your Google Account's third-party access page. Disconnecting stops future access immediately but does not delete files already in your Drive — delete the "Taipo Backups" folder yourself if you'd like them gone.
§4
Optional: other connections
- GeniusLink. If you add a GeniusLink API key and secret, Taipo stores them in your browser and sends them only to GeniusLink (
api.geni.us) to create short links for products you choose. They are included in backups you create, so a restored device keeps working.
- Amazon Creators API. If you add Creators API credentials from your Amazon Associates account, Taipo stores them in your browser and sends them only to Amazon (
api.amazon.com to sign in, creatorsapi.amazon for product lookups) to read product details such as title, price, and sales rank.
Keys and secrets are never sent anywhere else, and never to Taipo.
§5
Deleting your data
- In your browser: uninstall Taipo, or use the delete options in its Settings.
- In your Google Drive: delete the "Taipo Backups" folder.
- Access to your accounts: disconnect in Settings → Connections, or revoke it from your Google Account's third-party access page.
- Usage statistics (§6): they hold only a random install ID and version number, which can't be linked to you. Uninstalling Taipo stops them.
§6
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. It never includes any Amazon, Google, YouTube, or other account data, and is not linked to your name, email, or any account.
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.
- 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.
§7
What we don't do
- No analytics tied to your identity, your accounts, or your browsing — see §6 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 no ability to change anything on your YouTube channel.
- No access to any site or account beyond what's listed in §8.
§8
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 — the mechanism behind most data fetches.
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 tasks, backups, notes sync, and note reminders on schedule without the dashboard tab open — also what triggers the daily anonymous usage ping (§6).
notifications
Show a system notification when a scheduled task finishes, a watcher rule fires, or a note reminder is due.
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 service (§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, and public product pages.
m.media-amazon.com
Load product images.
walmart.com
Check public Walmart product pages for availability, if you use that feature. No Walmart account is used.
youtube.com
Show extra details on YouTube video pages you visit (such as a video's exact publish date), if you turn that on.
googleapis.com
accounts.google.com
Google's own sign-in, Drive, YouTube, and YouTube Analytics APIs, used only for the optional connections in §3.
api.geni.us
GeniusLink's API, used only if you add GeniusLink keys (§4).
api.amazon.com
creatorsapi.amazon
Amazon's Creators API, requested only when you connect it (§4).
raw.githubusercontent.com
Fetch a small, static, public JSON file listing in-app feature announcements. No user data is sent with this request.
taipo-telemetry.mckayjunk.workers.dev
Receives the anonymous usage ping described in §6. No account data is ever sent to this address.
§9
Changes to this policy
If Taipo's data handling changes, this page will be updated first, and the version number above will change accordingly.
§10
Contact
Questions about this policy or how Taipo handles data can be sent to mckayjunk@gmail.com.