Privacy Policy
In short
- What we collect: what you type into our forms, your IP address, access and error records, and records of product button presses. We also send contact form and sign-up entries to our Slack workspace. We do not send button presses to Slack. We save them only in our database at Cloudflare. The forms use Cloudflare Turnstile to block automated sending. (Section 2)
- Short-term records: a count of submissions and button presses (at most 2 hours) and, for 30 days, a copy of a record (contact form, sign-up or product button press) only if saving fails. For a contact form or sign-up, the copy is also made when sending to Slack fails. (Section 2)
- Companies that help us run the site: Cloudflare, Slack and Google (all in the United States). (Section 5)
- We do not sell personal data. (Section 4)
- Questions, requests and complaints: write to us by email. (Section 10)
Koukitsuko Ltd. (好橘子株式会社, "we", "us") publishes this policy on how we handle personal information on our website (https://www.koukitsuko.com/). We follow the Act on the Protection of Personal Information of Japan (the "APPI") and related laws. The Japanese version of this policy is the original. If the two differ, the Japanese version applies.
This policy covers www.koukitsuko.com only. Laiza (shop.laiza.jp) and FractalBox have their own policies.
1. Who we are
- Name: Koukitsuko Ltd. (好橘子株式会社)
- Representative Director: Justin Lau (劉 梓澄)
- Location: Kizugawa, Kyoto, Japan (京都府木津川市). We give the street address on request.
We will tell you our address without delay if you ask at the contact point in section 10. We do not ask why you want it. You do not need an identity document to learn the address.
2. Information we collect
We collect the following information on this site. We save form entries in our database ("D1", run by Cloudflare) and send them to our Slack workspace. Cloudflare also runs a short-term store ("KV"). We use KV only for the two records named below.
- Contact form: your name, email address, message, display language, IP address, and the time you send it.
- Sign-up form that opens from the "Tell me more" button of a product: your email address, the product you are interested in, an optional note, display language, IP address, and the time you sign up. If you sign up without a product, we record interest in all products. If you sign up again with the same email address, we merge the interests, and we update the date and time and the display language. We replace the note only if you enter a new one. The database keeps the IP address of your first sign-up. The Slack message for the new sign-up holds the new IP address.
- Record of a product button press: the product name, display language, IP address, and the time of the press. This record does not include your email address. We save this record only in D1. We do not send it to Slack.
- Slack message: each contact form and sign-up also goes as a message to our workspace at Slack (United States). The message holds the name, email address, message, product, display language, IP address and time, as far as that form has them. A product button press does not go to Slack. For how long Slack keeps the message, see section 7.
- Access records: Cloudflare, which delivers the pages, records the IP address, the time of access, the page viewed, the type of browser, and similar data. Our own program also records what went wrong when an error happens. That record does not include your name, email address or message.
- Bot check (Cloudflare Turnstile): the contact form and the sign-up form use Cloudflare Turnstile to block automated sending. Your browser loads the Turnstile script and a small frame from challenges.cloudflare.com when you start to use a form (when you move into the contact form (click or tab) or open a sign-up window), not when a page opens. Cloudflare receives your IP address, technical details of your connection (a TLS fingerprint), your browser type (user agent), and signals from your browser, such as which web functions it supports and how it behaves on the page. It receives them together with our site key and the name of our site. Cloudflare uses them to tell people from automated programs. Cloudflare also uses them for its own purpose of improving its bot detection (section 5). Cloudflare states that Turnstile does not read what you type into the form. Turnstile gives your browser a token, and we send the token and your IP address to Cloudflare to confirm it. We do not receive these signals and we do not store the token. For the details, see the Turnstile Privacy Addendum.
- Records to stop abusive submissions: we keep a count of submissions and button presses for each IP address in KV for a short time. This record deletes itself after at most 2 hours.
- Copy of a record (contact form, sign-up or product button press): we make this copy when saving to D1 fails. For a contact form or sign-up, we also make it when sending to Slack fails. We keep it in KV for 30 days, then delete it automatically.
We keep the IP address with its record, for as long as we keep that record (section 7). The limit of "at most 2 hours" applies only to the count of submissions and button presses.
3. Why we use it
We use personal information that we collect only for these purposes.
- To reply to your enquiry, and to the note you add when you sign up, and to deal with them.
- To send product news to people who signed up (for now, the representative sends it by email, one person at a time). You can stop the news at any time by contacting us at section 10.
- To count product button presses, so that we know which products people are interested in.
- To stop abusive submissions and to keep the site safe and working. We keep the IP address so that we can look into abusive submissions.
- To deal with requests about your data, and to check who you are.
- To comply with law.
If we want to use information for a purpose outside this list, we first ask for your consent.
4. When we share data
We do not sell personal data. We do not give it to a third party, except in these cases.
- When you agree.
- When required by law.
- When it is needed to protect a life, body or property, and it is hard to get your consent.
- When it is especially needed for public health or for the healthy growth of children, and it is hard to get your consent.
- When a national or local government body needs our help to carry out work set by law, and getting your consent could impede that work.
- When the data passes to a successor in a merger, company split, business transfer or similar event.
The companies in section 5 are not "third parties" under the APPI. We let them handle data only to the extent needed for our purposes. The exception is the data that Cloudflare receives directly from your browser: the connection data that it uses for its own network security, and the Turnstile signals (section 2) that it also uses to improve its bot detection (section 5). For entrusting companies in other countries, see section 6.
5. Companies that help us run the site
To run this site, we entrust the handling of personal data to the companies below.
- Cloudflare, Inc. (United States): delivers the website; hosts the database (D1) that stores form content and the short-term store (KV); runs Turnstile, the check against automated sending (section 2).
- Slack (United States): it receives the message that we send to our Slack workspace for each contact form and sign-up (section 2).
- Google (United States): Google Workspace email. It now handles only the email that people send to support@koukitsuko.com (requests and enquiries) and our replies.
Cloudflare receives connection data directly from your browser, for the security of its network. For Turnstile, it also receives the signals named in section 2 directly from your browser, and it uses them for its own purpose of improving its bot detection. Cloudflare handles this data on its own responsibility, not only on our instructions. We do not hand data to Cloudflare for these purposes. For Turnstile, however, we send Cloudflare the token and your IP address to confirm the check (section 2). For details, see the Cloudflare Privacy Policy.
6. Handling in other countries
The companies in section 5 are United States companies. Requests to this site are handled on Cloudflare servers around the world. The data we store is with United States companies (Cloudflare, Slack and Google). The region where data is handled is not fixed.
- The country of the companies: the United States of America (Cloudflare, Slack and Google).
- The system for protecting personal information in that country: at federal level there is no comprehensive law like the APPI. Some states have laws on the protection of personal information.
- How we make sure the data is protected: we use Cloudflare, Slack and Google under their service terms. These service terms include standard data processing terms. Those terms limit the use of the data to the provision of the service to us, and they say that the company must keep the data secure. We rely on these terms as the system that meets the standard of the Rules of the Personal Information Protection Commission (Article 28(1) of the APPI).
We check each company's measures, and the system of the United States, about once a year. If you want the details of these measures, or want to know more about the United States system or about these companies, contact us at section 10. We then give you the information that Article 28(3) of the APPI requires.
7. Storage and security measures
We keep the records in D1, the messages in Slack and the emails in Google until you ask us to delete them or we decide we no longer need them. Our Slack workspace is on the free plan of Slack. On this plan, Slack hides messages older than 90 days. It does not delete them at that point. Slack may delete data older than one year. On the current plan, we cannot view or delete messages older than 90 days ourselves. We still delete the D1 record when you ask, and we ask Slack to delete the message where possible (section 9). A deleted record may stay in Cloudflare's automatic D1 backups for a limited time. Except for the count of submissions (at most 2 hours) and the copies of submissions in KV (30 days), both in section 2, we have no automatic deletion of our own.
To prevent leaks, loss and damage of personal data, we take these measures.
- We limit access to personal data to the people who need it for the work (for now, only the representative; this does not count the companies in section 5).
- Communication between your browser and the site is encrypted with TLS (HTTPS).
- The accounts that hold personal data (Cloudflare, Slack, Google Workspace) use two-factor authentication.
For the United States system, see section 6.
8. Cookies, browser storage and what your browser sends elsewhere
- Cookie: to remember your display language, we set a cookie named "lang". It lasts one year from the last time you visit a page other than this policy. It does not identify you. We do not set it on the pages of this policy.
- Browser local storage: we store your light or dark display setting (key name: theme) inside your own browser. We also store the email address you typed in a form in your browser, so that you do not have to type it again (key name: kk_email). It is sent to us only when you press the send button. You can delete both in your browser settings.
- External transmission: this site uses no analytics tool, no advertising tag, no external font, and no embedded map or video. Your browser sends data to our site. There are two exceptions, and both go to Cloudflare. First, when a page fails to load, your browser may send a connection-error report to Cloudflare. The report holds the IP address, the URL of the page, the type of browser (user agent) and the type of error. Second, when you start to use the contact form or a sign-up window, your browser loads the Cloudflare Turnstile script and frame from challenges.cloudflare.com and sends Cloudflare the data named in section 2. We do not use the pre-clearance mode of Turnstile, which sets a cookie. What Cloudflare itself stores in your browser through Turnstile follows the Turnstile Privacy Addendum and the Cloudflare Cookie Policy. What happens after you follow a link to another site follows that site's own policy.
9. Requests about your data
For personal data about you that we hold (retained personal data), you can ask for the following.
- Notice of the purpose of use
- Disclosure (including a copy as an electronic record)
- Correction, addition or deletion of the content
- Stopping use, erasure, or stopping the giving of the data to third parties
- Disclosure of the record of giving data to third parties
The steps are these.
- How to ask: send your request by email to the contact point in section 10.
- How we check who you are: we send our answer to the email address you used to contact us. Only if we cannot send it to that address, we ask you to show an identity document. We destroy a document we received for this check without delay after the check. For a request only for our address, we ask for no document.
- Records with only an IP address: a record of a product button press holds no name and no email address. We disclose such a record only after the connection details of your request match the details in the record.
- Deletion and stopping use: before we delete data or stop using it, we ask you to confirm by a reply from that same email address.
- Slack messages: on the current free plan, we cannot view or delete Slack messages older than 90 days ourselves. When you ask us to delete data, we delete the D1 record and the Slack messages that we can still see. For older messages, we ask Slack to delete them where possible. We cannot promise that Slack will do it.
- Timing and fee: we respond to your request without delay. There is no fee.
- If we cannot grant a request: we tell you why.
10. Contact point and complaints
Send questions, requests and complaints about personal information to this contact point.
- Koukitsuko Ltd., personal information contact point (Representative Director)
- Email: support@koukitsuko.com
We do not belong to any accredited personal information protection organization. If you are not satisfied with our response, you can also consult the Personal Information Protection Commission of Japan.
11. Changes to this policy
We review this policy when the law or our operation changes. When we change it, we publish the change on this page and update the date of the last revision.