| Item | Detail |
|---|---|
| Version | 1.0 |
| Applies to | Every Umitake kintone plugin |
| Status | Forms part of our Privacy Policy |
This document covers the infrastructure shared by all of our kintone plugins — plugin delivery (CDN) and license verification — describing what data goes where, who processes it, and how long it is kept. For product-specific processing, see each product's own data handling document.
This document describes what is implemented, not what is intended. We do not state retention periods or deletion promises that no code enforces.
1. Our Role
When you use our kintone plugins, we act in two capacities:
- As the seller and license administrator — we collect and hold the account holder's name, email address, and kintone domain for our own purposes. In this respect we are the data controller.
- Regarding your business data — the shared infrastructure handles none of it. Products that do handle business data describe this in their own documents; in that respect you are the controller and we are the processor.
2. Data Flow
Your browser (a kintone screen)
├──(1)──> cdn.umitake.com (Cloudflare Pages) … fetches the plugin's JS / CSS
└──(2)──> license.umitake.com (Vercel / Neon) … checks license validity
| # | When | What is sent |
|---|---|---|
| (1) | Every time a kintone page loads | The IP address, User-Agent, and Referer / Origin that accompany the HTTP request — the Origin being your kintone subdomain |
| (2) | On plugin startup (the verdict is cached in the browser for 24 hours, so roughly once per browser per day) | Your kintone domain, the license key, and the plugin ID |
A note on (1): plugin JS and CSS are served with Cache-Control: no-store and are
not cached by the browser, so a request goes to the CDN on every kintone page
load. No business data or record content is involved, but the connection details
above reach the CDN provider (Cloudflare) each time.
3. What We Store
For license management we store the following in our database (Neon / PostgreSQL):
| Table | Contents | Personal data |
|---|---|---|
licenses | License key, kintone domain, plugin ID, plan, expiry, active flag, account holder's name and email address, notes, reseller code | Name, email address, domain (organisation-identifying) |
license_check_logs | One row per verification: license key, domain, plugin ID, result, timestamp | Domain (organisation-identifying) |
Points worth stating plainly:
- The name and email address come from the details registered with our authentication provider (Clerk) at the time of purchase.
license_check_logsrecords every verification, whether it succeeds or fails. This amounts to a record of which domain used which plugin, and when.- License keys are stored in cleartext, not hashed.
- The license administration API carries the license key in the URL path, so license keys appear in the request logs of our hosting provider (Vercel) and CDN provider (Cloudflare).
Separately, the license verdict is cached in your browser's localStorage for 24 hours. It holds only the verdict and region, never business data.
4. What Transits but Is Not Stored
No business data passes through our servers as part of the shared infrastructure. The CDN only serves plugin files, and license verification receives only the three items in §3 (domain, license key, plugin ID).
kintone records, attachments, and field values never travel through it.
5. Subprocessors and Locations
| Provider | Purpose | Data sent | Data not sent | Location |
|---|---|---|---|---|
| Cloudflare | CDN delivery, DNS, TLS termination | IP address, User-Agent, kintone subdomain, and the contents of license verification requests (which pass through in the clear, as TLS is terminated here) | Business data | Global (edge) |
| Vercel | Runtime for the license API, request logs | The verification requests above, IP address | Business data | United States |
| Neon | License database | Everything in §3 | Business data | United States (us-east-1, Virginia) |
| Clerk | Purchaser account authentication | Name, email address, license key | Business data | United States |
| Stripe | Payment and subscription management | Payment details | Business data | United States |
Umitake is a Texas, USA company, and all of the processing above takes place in the United States. See the cross-border transfer section of our Privacy Policy for details.
Note that kintone itself is a service you contract for directly with Cybozu, Inc. and is outside our control.
6. Retention Periods
| Data | Retention | How this is enforced |
|---|---|---|
License records (licenses) | Indefinite | No automatic deletion is implemented |
License verification logs (license_check_logs) | Indefinite | As above |
| License verdict in browser localStorage | 24 hours | TTL expiry (implemented) |
| Vercel / Cloudflare request logs | Each provider's own default | We do not forward or archive them |
We have not implemented any mechanism that automatically deletes license records or verification logs. They persist after a contract ends. We state this as fact; implementing retention is on our roadmap.
To request deletion, contact [email protected] and we will handle it individually.
7. On Cancellation and Disconnection
Cancellation only sets a flag marking the license inactive (is_active = false).
The account holder's name, email address, domain, and license key, along with the
historical verification logs, are not deleted (see §6).
This exists so a license can be reactivated if you return, but the practical effect is that personal data remains. We will action deletion requests individually.
8. What We Cannot See
- We cannot see the contents of your kintone records. No business data reaches the shared infrastructure.
- We cannot see which of your users operated the plugin. License verification happens per domain; no kintone user ID or name is transmitted.
- We cannot see your plugin configuration. kintone plugin settings are stored inside your kintone environment and never reach us.
What we can see is which domain verified which plugin and when, plus the account holder's name and email address.
9. Your Responsibilities
- Managing the license key. It is stored in the kintone plugin configuration and is visible to anyone with kintone app administrator rights, so consider who holds that permission.
- Shared workstations. The license verdict remains in the browser's localStorage for 24 hours — worth noting for shared or kiosk machines.
10. Contact
For questions about this document, help completing a security questionnaire, or data deletion requests:
Umitake Email: [email protected]
Related: Privacy Policy · Terms of Service