TinyStack · Legal
Privacy Policy
Last updated: 18 November 2026
The short version
- Page content is read in your own browser and stays there. Nothing is uploaded unless you are on Pro and press one of the AI buttons yourself.
- There is no account, no analytics, no crash reporting and no advertising identifier.
- Only two kinds of request leave an extension, and nothing else: a Pro licence check with Creem if you enter a licence key, and the optional AI request behind a button (section 4). Free, and Pro without pressing that button, makes no network request at all.
- An AI request carries only the small sample that one tool needs. We keep no copy of it, and it is not stored on our servers.
- Payments and tax are handled by Creem as the merchant of record. We never see your card details.
1. Who we are and what this policy covers
TinyStack is an independent software project that publishes three Chrome extensions: TableCrate, TubeGlean and StoreCrate. This policy explains what each of them does with information, and what the pages at stackswitch.dev/tinystack do with it. It applies to all three extensions, on every site where you install them.
TinyStack is the data controller for the little that is left to control: support emails you send us, the licence records behind a Pro purchase, and the sample a Pro AI request carries, which we pass to Anthropic for that one request (section 4). You can reach us at zinbklove@gmail.com.
2. What each extension handles
Each extension reads the page you are on only after you click its toolbar icon on that tab. What it reads, and where the result goes, is set out below. Every row is processed inside your browser except the one marked Pro AI, which leaves it once, when you press that button yourself.
TableCrate
| Data | Where it goes | Why |
|---|---|---|
| Tables and repeated lists on the page you are viewing | Stays in that tab and in the extension popup while it is open | Reading the rows you asked to export and building the file |
| The exported file (CSV, XLSX, TSV, JSON or Markdown) | Written by Chrome to your own downloads folder | You keep the result |
| Your settings, saved recipes, licence state and daily export counter | chrome.storage.local on your device | Remembering your choices and applying the free plan limits |
| Pro AI, only when you press the button: the header row, a sample of up to 25 data rows with each cell cut to 80 characters, and the caption | Sent to stackswitch.dev/api/ai/tablecrate, and from there to Anthropic (section 4) | Writing a clean header row and a one-line summary of the table |
TubeGlean
| Data | Where it goes | Why |
|---|---|---|
Titles, descriptions, tags, search results and channel figures that are visible on the youtube.com or studio.youtube.com page you are on | Read in that page, analysed there, shown in the extension's side panel | Scoring the draft, reading tags and comparing results |
| Saved presets, licence state | chrome.storage.local on your device | Remembering your channel settings |
| CSV export of search results (Pro) | Written to your downloads folder | You keep the result |
| Pro AI, only when you press the button: the video's title, up to 4,000 characters of its description, up to 20 of its tags and its channel name | Sent to stackswitch.dev/api/ai/tubeglean, and from there to Anthropic (section 4) | Suggesting alternative titles, tags and description edits |
TubeGlean never asks for a YouTube or Google login, and it never writes to your channel. It reads only what the page already shows you, including the extra detail YouTube renders for the account you happen to be signed in with.
StoreCrate
| Data | Where it goes | Why |
|---|---|---|
| Public storefront data: theme, apps and pixels visible in the page, product catalog and prices | Read and analysed in the tab you pressed Scan on | Showing what the storefront is built with and how its catalog is priced |
| Saved scans for the change history, licence state and export counter | chrome.storage.local on your device | Comparing a store with the last time you looked at it |
| Catalog exports (CSV, JSON, Markdown) | Written to your downloads folder | You keep the result |
| Pro AI, only when you press the button: the store's name, up to 40 product titles with their prices, the price range and the currency | Sent to stackswitch.dev/api/ai/storecrate, and from there to Anthropic (section 4) | Naming the niche, one positioning sentence and three ad angles |
3. What never leaves your browser
- The content of any page you point an extension at, including tables, product catalogs, video metadata and search results — with the one exception you trigger yourself, the AI sample described in section 4.
- The URL or address of any page you visit, and your browsing history — except the site's hostname inside a TableCrate AI request, which names the table's origin and never its path, query or the page itself.
- The files you export, and your downloads folder.
- Your YouTube account, Google account or Shopify login. No extension asks for one.
- Analytics, session recordings, crash reports, advertising identifiers or device fingerprints. None are collected.
No extension loads remote code. All JavaScript is packaged inside the extension and reviewed with each release, which is why nothing can start sending your pages somewhere later.
4. The only network requests
There are exactly two, both to stackswitch.dev, and both made only for something you asked for. No extension contacts any other address.
Pro licence checks. When you enter a licence key, and while a Pro licence is active, the extension asks us to confirm that the key is valid. That request goes to our own licence endpoint atstackswitch.dev/api/license, which forwards it to Creem (creem.io), the payment provider that issued the key. The extension sends your licence key and an instance name such as TableCrate Chrome 138, plus the instance id issued at activation. It contains no page content, no page URLs and no personal information beyond the key itself. The store's Creem API key needed to ask Creem is held only by that endpoint on our server; it is never part of the extension you install, so it cannot be read out of it. The reply says only whether the key is valid. A stored licence is re-checked at most once every few days, and the extension keeps working offline for a grace period.
If you never enter a licence key, the extension makes no network request at all: the AI feature below is authorised by that same key, so it cannot run without one either.
The optional Pro AI features
Each extension has one Pro feature that uses a language model: AI clean-up for a table (TableCrate), AI rewrite for a video's title, tags and description (TubeGlean), and AI positioning for a store (StoreCrate). Each sits behind its own button inside the extension, and each is off until you press that button. Nothing is sent while you are on Free, and nothing is sent in the background: no click, no request.
That click sends one POST to our own endpoint — stackswitch.dev/api/ai/tubeglean, /tablecrate or /storecrate — carrying three things: your licence key, the instance id stored when you activated Pro on this device, and the sample for that one tool:
- TubeGlean: the video's title, up to 4,000 characters of its description, up to 20 of its tags, and the channel name.
- TableCrate: the table's header row and a sample of up to 25 of its data rows, each cell cut to 80 characters, plus the table's caption — which names the table and the site's hostname, such as
example.com. The sample shrinks further when the table is large, and never exceeds 16 KB. - StoreCrate: the store's name, up to 40 product titles with their prices, the price range it read and the currency.
That is the whole payload. Not the rest of the table, not the page, not its address or path, not the rest of the store, not a screenshot, not a saved scan, and nothing about you or your browser.
Our endpoint checks the licence with Creem as described above, then passes the sample to Anthropic (anthropic.com), whose Claude model — claude-haiku-5-5, shown in the extensions as “Haiku 5.5” — writes the answer. One press is one request, with no history attached and nothing chained to an earlier press; the system instruction that shapes the answer is fixed in our code. The Anthropic API key needed to ask is held only by that endpoint on our server, never in the extension you install. Both our endpoint and Anthropic process the request outside Korea, at Cloudflare's edge and in the United States, for the length of that request.
Nothing is stored. The sample, the licence key and the answer exist in memory only while the request runs. We keep no copy of them — not on a server, not in a database, not in an access log — and we keep no record of which video, table or store you asked about. Two short-lived counters keep the endpoint from being abused: a count per IP address for one minute and a count per licence key for one hour, both in the memory of the running worker and gone when it is recycled; a licence that has just been validated may be remembered for up to ten minutes so that a second press does not repeat the Creem call. The request itself reaches Cloudflare, so Cloudflare's delivery logs (section 6) record that a request was made to that path, from which IP address and when, but not what it contained. Anthropic processes the request as our service provider under its API terms, which do not allow it to train models on what it receives; its standard retention deletes API inputs and outputs within 30 days, longer only if a request is flagged for a usage-policy review. Its own handling is described at anthropic.com/legal/privacy.
If you would rather send nothing, do not press the AI button. Every other feature works entirely inside your browser, including the Pro features that lift local limits — unlimited search analysis, CSV and catalog export, saved presets and the change history — and every Free feature too. The AI buttons are the only place where a page's content can leave your browser, and they only work on Pro.
Payment. Pro purchases happen on a checkout hosted by Creem (creem.io), not inside the extension. Pro costs $9 USD per month or $29 USD per year for one extension, and the total including any tax is shown before you pay. Creem is the merchant of record: it collects the payment and your billing details, calculates and remits the applicable sales tax or VAT, and issues the invoice. We receive only the information needed to support your licence, such as the email address on the order and the licence key. We never see or store your card number. Creem's own handling of personal data is described in its privacy notice at creem.io/privacy.
5. Permissions and why each is needed
Chrome shows every permission before you install. Here is what each one is for; none of them is used to read pages in the background.
| Permission | Why the extension needs it |
|---|---|
| activeTab | Read the current tab, and only after you click the extension's icon |
| scripting | Inject the extractor into that tab on demand instead of running on every page |
| storage | Keep settings, saved recipes or presets, licence state and the daily counter on your device |
| downloads | Save the file you exported to your downloads folder |
| host: youtube.com, studio.youtube.com | TubeGlean only: show its panel on YouTube pages. This is the only site permission any of the three extensions asks for. |
| host: stackswitch.dev/api/license/* | Send a licence key to our own licence endpoint to activate, validate or deactivate Pro; that endpoint passes it to Creem. Nothing from any page is included. Off until you enter a licence key. |
| host: stackswitch.dev/api/ai/* | Send the Pro AI sample for the one tool whose button you pressed (section 4). Off until that press, and unavailable on Free. |
| No other hosts | TableCrate and StoreCrate ask for no site at all: they reach the page you are on through activeTab when you click their icon. No extension reads a page in the background, and the two stackswitch.dev paths above are the only addresses any of them can call. |
6. This website
The pages you are reading are served from stackswitch.dev through Cloudflare. Cloudflare keeps the usual delivery and security logs (IP address, user agent, requested page) for a short period; we do not build profiles from them. The pages under /tinystack load no advertising or analytics scripts and set no cookies of their own.
The rest of stackswitch.dev is a separate directory of SaaS pricing comparisons. Those pages may load third-party advertising and are outside the scope of this policy.
7. How long data is kept
Everything an extension stores lives in chrome.storage.local on your device. Uninstalling the extension deletes all of it; you can also clear a saved recipe, preset or scan, or deactivate the licence, from the extension's own settings at any time. Files you exported stay in your downloads folder until you delete them.
On our side there is very little: support emails, which we keep while the question is open and afterwards only as long as needed to handle related requests, and licence records tied to an order. An AI request adds nothing to that — its sample and answer are not stored at all (section 4), and Anthropic deletes its copy of them within 30 days under its standard retention. Purchase and billing records are kept by Creem under its own retention rules, because it is the seller of record and has tax obligations.
8. Your rights
Depending on where you live, you may have the right to access, correct, export or delete personal data held about you, to object to processing, or to complain to a supervisory authority. Since page content is sent only by a Pro AI press and is never stored, and the extensions collect no analytics, most of these requests concern a purchase record, which sits with Creem as the seller. Write to zinbklove@gmail.com and we will either answer it or point you to the right place at Creem. We do not sell personal information, and we do not share it for advertising.
9. Children
The extensions are general-purpose productivity tools, not directed at children under 13, and no extension is designed to collect information from anyone.
10. Changes to this policy
If an extension starts handling data in a new way, this page is updated before that version ships, and the date at the top changes. A change that affects what leaves your browser will also be described in the extension's update notes in the Chrome Web Store.
11. Contact
Questions about this policy, or about anything an extension did on a page: zinbklove@gmail.com. One developer reads that inbox.