| Item | Detail |
|---|---|
| Version | 1.0 |
| Product | Umitake BI Tool for Kintone |
| Status | Forms part of our Privacy Policy |
This product performs all aggregation and rendering inside the browser. No business data reaches an Umitake server.
For the CDN and license verification common to every product, see the shared infrastructure document. This document covers only what is specific to this product.
This document describes what is implemented, not what is intended.
1. Our Role
For this product we are not a processor of your business data, because no business data reaches our servers.
The only data we collect as a controller is the license management information described in the shared infrastructure document: the account holder's name, email address, and domain.
2. Data Flow
Your kintone
└──> Your browser (fetched via the kintone REST API)
├──> Aggregation and chart rendering (entirely in the browser)
├──> localStorage (temporary cache — see §4)
└──> Dashboard definitions saved to a kintone app that you own
Our servers appear nowhere in this flow. Fetching records, aggregating them, and exporting the result all happen between your browser and kintone.
3. What We Store
Nothing. We store none of it on our servers.
The only server we operate in this flow handles license verification, which receives three items: your kintone domain, the license key, and the plugin ID (see §3 of the shared infrastructure document).
Everything is stored under your own control:
| What is stored | Where | Contents |
|---|---|---|
| Dashboard and chart definitions | A kintone app that you own | config_type / config_id / config_name / config_json / updated_at |
| Plugin configuration | Your kintone | Only storageAppId, schemaVersion, and licenseKey |
Because dashboard definitions are stored as records in a kintone app, that app's access permissions determine who can view and edit them (see §9).
4. What Transits but Is Not Stored
Nothing transits our servers. However, this product does cache real kintone record data in your browser's localStorage. This is the one place in the product where business data lands in persistent storage, so we state it explicitly:
| Item | Detail |
|---|---|
| Keys | Keys beginning bi_cache_ |
| Contents | Actual record data fetched from kintone — the values behind the charts |
| Retention | 30 minutes by default; removed automatically on the next access after the TTL expires |
| Cap | 4MB total; the oldest entries are discarded automatically when exceeded |
Please note:
- localStorage survives closing the browser. The data stays on the device until its TTL expires.
- On shared or kiosk workstations, logging out does not clear the cache — clearing browser data does.
- This cache is never transmitted to us. It stays on the device.
Exports (CSV / Excel) are generated as a Blob in the browser and downloaded
directly. Nothing is uploaded anywhere.
5. Subprocessors and Locations
This product introduces no subprocessors of its own.
It makes only the two external connections described in the shared document:
| Provider / host | Purpose | Data sent | Data not sent | Location |
|---|---|---|---|---|
| cdn.umitake.com (Cloudflare Pages) | Delivering the plugin itself | IP address, User-Agent, kintone subdomain | Business data | Global (edge) |
| license.umitake.com (Vercel / Neon) | License verification | kintone domain, license key, plugin ID | Business data | United States |
The charting library (ECharts) and the Excel export library are bundled into the plugin and are never loaded from an external CDN.
6. Retention Periods
| Data | Retention | How this is enforced |
|---|---|---|
| Business data on our servers | Not applicable (none is stored) | — |
Record cache in localStorage (bi_cache_) | 30 minutes by default, 4MB cap | TTL expiry and automatic eviction over the cap (implemented) |
License verdict in localStorage (bi_license_) | 24 hours | TTL expiry (implemented) |
| Dashboard definitions | You decide | They are records inside your own kintone app |
| License records and verification logs | Indefinite | As described in §6 of the shared infrastructure document |
7. On Cancellation and Disconnection
There is no business data on our side to delete.
Dashboard definitions are records in your own kintone app and remain after cancellation. Delete them yourself if you no longer want them. We never touch data inside your kintone.
License records are handled as described in §7 of the shared infrastructure document.
8. What We Cannot See
- We cannot see your charts or the records behind them. They never reach us.
- We cannot see what dashboards you have built. The definitions live in your kintone.
- We cannot see your exports. They are generated in the browser and never pass through us.
9. Your Responsibilities
- Permissions on the dashboard storage app. Dashboard and chart definitions are records in this app. Anyone who can open it can view and edit every dashboard definition, including the app IDs and field codes they reference.
- Permissions on the source data. The product calls the kintone REST API using the permissions of the person operating it. Records a user cannot see will not appear in their charts — and conversely, whatever they can see may be surfaced through a chart.
- Shared workstations. As described in §4, real record data remains in the browser for up to 30 minutes.
10. Contact
For questions about this document or help completing a security questionnaire:
Umitake Email: [email protected]
Related: Shared infrastructure · Privacy Policy · Terms of Service