Privacy notice for purchase activation
This notice explains what information the purchase activation in COOKI STUDIO tools stores and why, where it is processed, and how long it is kept.
- Applies to: Real Sweat System 2.0.0 and later, and other COOKI STUDIO tools that use the same purchase activation
- Effective date: the release date of Real Sweat System 2.0.0
- Document version: 1.0
1. Operator and contact
- Operator: COOKI STUDIO (Cooki). If you ask, we will tell you the author's real name without delay (the same policy as the shop's notice under Japan's Act on Specified Commercial Transactions).
- Questions and deletion requests: send a BOOTH message to the shop (https://cooki.booth.pm), or e-mail [email protected].
2. Summary
- Order numbers, Gumroad license keys, replacement codes and IP addresses are never stored as they are, only as a hash made with a secret key (HMAC-SHA256). The author can match these hashes against the BOOTH seller dashboard and the Gumroad sales records, so we treat them as personal information too.
- We do not store names, e-mail addresses, postal addresses, phone numbers, payment details, BOOTH identification codes (識別コード), the contents of BOOTH messages, Gumroad purchase records, the Windows PC name, hardware information, or anything from your avatars or projects.
- We do not use any of it for ads or marketing, and we do not give it to anyone other than the places in section 6 that process it, except when the law requires it.
- The "device ID" is a random value the tool creates under your Windows account on this PC. It is not made from hardware information, and only its SHA-256 hash (the "device ID hash") is sent to the server.
3. What we store and how long we keep it
| Information | Used for | Kept for |
|---|---|---|
| Orders: hash of the order number or Gumroad license key; store (BOOTH or Gumroad); item, variation, features and number of PCs; payment status; order date (BOOTH only); replacement code (CKR-…) hash (only when handling a leak) | Confirming payment, managing the number of PCs per order, blocking leaked order numbers | While the service runs. Deleted within 1 year after the service ends. |
| Activated PCs: device ID hash; PC name (if you typed one, up to 40 characters); activation, renewal and release times | Issuing and renewing certificates, the PC list and PC release | PCs that are not released: the same as the order. Released PCs: deleted automatically 1 year after release. |
| Wrong-attempt records: device ID hash, IP address hash, number of wrong attempts, lock time (only when a wrong number is entered) | Stopping order numbers from being guessed | Deleted automatically 8 days after the last wrong attempt (if it was locked, 8 days after the lock ends) |
| Action log: type and time of each activation, release and admin action; the first part of the order hash; status changes | Answering questions, recovering from outages | Deleted automatically after 1 year |
| Activation server logs: time, request path, error codes, counts | Checking for problems | Once they pass about 30 MB, the oldest entries are deleted first |
| Cloudflare Worker logs: mail processing results (counts); Gumroad license key check results (outcome code, counts, version name) | Checking that mails and license key checks were processed | 3 days |
| Database backups | Recovering from outages | 30 days on the server, 1 year on the author's NAS |
| Encrypted key backups | Recovering from outages | While the service runs |
- We store only orders for items that use purchase activation. Orders for other items in the shop are not stored, and mails that only report a payment status never create a new record.
- BOOTH orders are registered whether or not you activate. BOOTH orders placed before 2.0.0 are already registered too. A Gumroad purchase is registered only when its license key is first entered in the activation window.
- Logs do not contain order numbers, Gumroad license keys, other keys or IP addresses. The same goes for the author's admin commands.
- When all PCs are in use, the window where that order number (or replacement code) was entered shows the PC names and the activation and renewal times of this order. Do not put your real name or other personal details in the PC name.
- The BOOTH identification code hashes and gift request records stored under the earlier gift request system are deleted from the live database at the next server update. Copies in database backups made before that disappear once the backup periods above have passed (30 days on the server, 1 year on the author's NAS).
4. How we receive information
What the tool sends (HTTPS)
- Activation: order number (or replacement code), product ID, device ID hash, PC name
- Activation with a Gumroad license key: first the license key and product ID to the Gumroad check (
https://api.cookistudio.com/v1/gumroad/claim, a Cloudflare Worker), then the same as activation, with the license key in place of the order number - Automatic renewal (from 7 days after you get a certificate, whenever you are online) and [Release this PC]: only this PC's certificate. The order number is not sent.
- Releasing another PC when all PCs are in use: the order number you just entered, product ID, device ID hash, and the number of the PC to release
- When the server cannot be reached: the tool only downloads an emergency pass document from
cookistudio.com.
We do not store the User-Agent, which contains the tool and Unity versions. Your IP address is used only for the connection, and is kept only as a hash in wrong-attempt records. [Copy report] only copies text to your clipboard and never sends it automatically, and the text does not contain the order number or license key.
What comes from BOOTH
You do not need to do anything.
- Sale notification mails: a Cloudflare Email Worker receives the mails that arrive in the author's Gmail and sends only the order number, item, variation, order date and payment status to the server.
- BOOTH messages: the author reads and answers them on BOOTH. The Email Worker processes only sale notification mails and ignores BOOTH message notification mails, so nothing from a BOOTH message is sent to the server or stored.
- Order CSV: the author sends it to the server over SSH. The server reads it in memory and uses only the order number, item, variation, status and order date. It does not keep the other columns, such as names, addresses and identification codes, or the file itself.
What comes from Gumroad
Only when you enter a Gumroad license key in the activation window.
- A Cloudflare Worker asks Gumroad's license API whether the key is a paid purchase of this product. It does not count this as a use of the key.
- The Worker sends the activation server only the license key (which the server stores only as a hash), the Gumroad product ID, the product name, the version name, and whether the purchase is paid or refunded (including chargebacks and disputes). The server stores this as an order (section 3).
- The Worker sees the key and Gumroad's purchase record only while it answers, and keeps nothing. Your e-mail address and the other purchase details (such as the price and purchase ID) are neither passed on nor logged. The Worker logs keep only the outcome code, counts and the version name.
- Gumroad is the store where you bought the tool. Gumroad's own privacy policy applies to the purchase itself.
5. What is stored on this PC
The %LOCALAPPDATA%\CookiTools\license\ folder holds the device ID (protected by Windows DPAPI; it does not work if copied to another PC), certificates, renewal records, emergency pass documents and unlock files, and the latest time this PC has seen. The COOKI STUDIO tools of the same Windows account share this folder.
The order number and Gumroad license key are not stored. If an older build saved an encrypted order number file, the tool deletes it at the next activation, renewal or release.
To remove this data, click [Release this PC] in every tool you activated, then delete the folder. If you delete it without releasing, this PC still takes up a place on the server.
6. Where information is processed
| Who | What they do | Location |
|---|---|---|
| Activation server | Handles activation, stores the information in section 3 | South Korea. A privately run server that the author entrusts with the service. |
| The author's NAS | Keeps backups | South Korea |
| Cloudflare, Inc. | Relays connections to api.cookistudio.com and protects against DDoS, processes notification mails, checks Gumroad license keys (Cloudflare Worker), hosts cookistudio.com |
The US, and the country of the data center that handled the request |
| Google LLC (Gmail) | Receives BOOTH notification mails | The US and other countries |
| Gumroad, Inc. | Answers the license key check (Gumroad's license API). The store where Gumroad purchases are made | The US |
- Because Cloudflare relays the connection, it processes your IP address, the request contents (including the order number or license key when you activate) and notification mails, and keeps access records under its own policy. Privacy policies: Cloudflare https://www.cloudflare.com/privacypolicy/, Google https://policies.google.com/privacy, Gumroad https://gumroad.com/privacy
- If you do not activate, the tool sends nothing. You then cannot do new installs or add modules, but avatars you already set up, builds and uploads keep working as before.
7. Security measures
- The author's admin work and backups are sent over SSH. The activation server opens no ports to the outside and receives requests only through Cloudflare Tunnel.
- The hash key is kept separate from the database. Database backups do not contain the hash key, and key backups are encrypted with the author's offline key.
- The operator of the activation server can access the information on the server with admin rights.
8. Viewing and deleting your information
- You can ask us to show, correct or delete your information, or to stop processing it, using the contact in section 1. We reply the same way you contacted us (BOOTH message, e-mail or Gumroad).
- The server holds only hashes, so we cannot look you up by name. Please send a BOOTH message from the BOOTH account that placed the order (for a gift, the BOOTH account that received it) and include the order number. On BOOTH, the author uses the 「…」 menu of that BOOTH message conversation → 「このユーザーの注文一覧を見る」 (view this user's orders; for a gift, 「このユーザーが受け取ったギフトを含む注文一覧を見る」) and confirms it is you by checking that the order is among the sending account's orders. These BOOTH messages and order lists are BOOTH's own screens for shop owners, not information this service stores. Even if you write by e-mail, we may ask you to send a BOOTH message so we can confirm it is you. If you bought on Gumroad, e-mail us from the e-mail address of your Gumroad purchase (or contact us through Gumroad) and include the license key. The author confirms it is you by finding that sale in Gumroad.
- After deletion, you can no longer activate or renew with that order. A certificate you already have keeps working until it expires (up to 30 days); after that, only new installs and adding modules are blocked. Copies left in backups are deleted once the periods in section 3 have passed.
- You can use [Release this PC] yourself at any time. From the list shown when all PCs are in use, you can release an old PC once every 7 days per order. If you cannot wait, for example because another PC broke, tell us in a BOOTH message (Gumroad buyers: by e-mail) and the author will release it for you (no 7-day limit).
9. If the service ends
- We will announce it on BOOTH at least 3 months in advance and publish a version that does not need activation on BOOTH.
- A signed permanent unlock file is held by a trusted third party. It contains no personal information.
- Records of orders and activated PCs are deleted within 1 year after the service ends.
10. Changes to this notice
This notice is published at https://cookistudio.com/license/privacy, and you can also open it with [Privacy] at the bottom of the activation window. When it changes, we update the effective date and the change history. For how to activate, see the Activation guide.
Change history
| Version | Effective date | Changes |
|---|---|---|
| 1.0 | Release date of Real Sweat System 2.0.0 | First version |