// privacy policy
Last updated: October 1, 2026
1. Diagnostic data we collect (all extensions)
Every S-Hub extension sends a small amount of anonymous diagnostic data so we can fix bugs and see which features are used. This is:
- Anonymous usage events via Google Analytics 4 — installs, updates, feature-usage counts, and paywall interactions.
- Error reports — the extension's name and version, the error type and stack trace, the domain where the error happened, and your browser/user-agent string.
These reports contain metadata only. They do not include the content you work with — no page text, no cookie values, no form input, no email content, no screenshots, and no information that identifies you personally.
2. What stays on your device
Your settings, saved items, and the content each extension works with — for example saved prompts, reading positions, captured screenshots, or edited cookies — are stored locally in your browser using Chrome's storage API.
Some of this data is saved with Chrome's sync storage. In some extensions, that includes a few settings (for example, your display language or reading preferences). In extensions with Premium features, it also includes the record kept by ExtensionPay: an ID for your installation and your purchase or trial status; the email address you used at checkout may be included. If Chrome sync is on, Chrome copies this data to every Chrome browser you are signed in to; if it is off, the data stays in this browser only. The copying is done by Chrome, not by us.
Apart from that, this data stays on your device, except when you explicitly export it, or when an extension sends it to a third-party service to do its job (see sections 3 and 4).
3. No account required
Our extensions don't require sign-up or login. Premium features are handled by ExtensionPay, which processes payments separately — we don't receive or store your payment details.
4. Extensions that use external services
A few extensions send data outside your browser because their core feature depends on it. Some send it to a named third-party service, and one — Rakuten Sellers Analytics — is routed through a relay server we operate. Here's exactly what goes where:
| Extension | What it sends | Where it goes | Why |
|---|---|---|---|
| 請求書よみとり (Invoice Reader) | The invoice page image and text — only when you enable AI extraction | OpenAI, using your own OpenAI API key; and Japan's National Tax Agency invoice lookup | Read invoice fields (OpenAI Vision); verify registration numbers |
| DataPick | The table data you choose to export | Your own Google Sheets (via your Google sign-in) | Export extracted data to your spreadsheet |
| Rakuten Sellers Analytics | The search keywords and category IDs you enter in the extension | A relay server operated by S-Hub (s-hub-dashboard-beta.vercel.app), which forwards the request to Rakuten Web Service | Look up Rakuten marketplace data without shipping API credentials in the extension |
Invoice Reader — When a PDF has no embedded text layer, the extension sends the page image to an OCR server operated by S-Hub (seikyu.dev-tools-hub.xyz) so the text can be recognized. This happens by default and requires no setup on your part. Separately, optional AI extraction runs only if you turn it on and supply your own OpenAI API key; when enabled, the invoice image and text are sent to OpenAI with your key.
Rakuten Sellers Analytics — Your search keywords are sent to a relay server we operate, which forwards them to Rakuten Web Service. We don't store them in our database, but the relay server's access logs record the request URLs, which include those keywords.
If you don't use these specific features, no such data is sent.
5. Early-access sign-ups and this website
Some pages on this website (for example /procshot/signup/ and /snapreply/signup/) let you leave your email address to hear about a feature that is not ready yet. Signing up is optional and is not needed to use any extension.
- What we store: the email address you enter, which extension the page is about, the page address, the referring page, and campaign tags in the link (utm_source, utm_medium, utm_content, utm_campaign).
- Where it goes: a database operated by S-Hub (hosted on Supabase).
- What we use it for: only to tell you about that extension's feature. We don't sell or share it.
- Some extensions (for example Procshot) also link to an early-access form on Google Forms. Anything you enter there is sent to Google Forms and used the same way.
- This website itself uses Google Analytics to count page views and button clicks (including a sign-up having been sent — not the email address).
- To have your sign-up deleted, email us at the address in section 8.
6. Data sharing
We don't sell, rent, or trade your data. The anonymous diagnostics in section 1 are used only to maintain and improve the extensions.
7. Changes
We may update this policy from time to time. The "last updated" date above reflects the current version.
8. Contact
Questions about this Privacy Policy? Contact us at ktg.shota@gmail.com