Privacy Policy

Effective date: 2026-10-29 · Version: 5. Version 5 adds two things we record from today: for each SDK key, the first and last time it checked in from each kind of place (dev machine, live site, store app, server), with the host only; and milestones our servers record about your account and projects (section 2, “Product usage events” and “SDK key check-ins”). Version 4, earlier the same day, lists Langfuse and Browserbase, which we already used but had left out of section 5; neither is new, and we are telling console account holders about the omission by email; says Sentry also receives errors from Mushi Mushi’s own servers; says model providers also receive code snippets for fixes and reviews; describes the request tracker as it is (it records requests, it does not produce a signed export); and corrects the tester ID-check threshold to US$400. (Version 3, 2026-10-28, did not include the version 4 corrections; version 2, 2026-10-10, did not list the free production check or the cookieless visit count; version 1, 2026-09-21, did not list the opt-in known-fix search sent to Firecrawl.)

This policy covers Mushi Mushi Cloud (the hosted service at kensaur.us/mushi-mushi), the admin console, the docs site, the Mushi Mushi Bounties tester marketplace, and the SDKs when they send data to Mushi Mushi Cloud. If you self-host the open-source server, you are the operator and this policy does not apply to your instance.

1. Who is responsible

Mushi Mushi is built and operated by Kensaurus 合同会社, based in Japan (the “controller” for the data described in section 3, and the “processor” for the data described in section 4).

• Contact for anything in this policy: kensaurus@gmail.com
• Subject line that gets the fastest answer: [mushi-privacy]
• Security reports: see SECURITY.md  and the security summary.

There is no separate data-protection officer. The founder answers these requests personally.

2. What data we handle, in one table

We do not sell personal data and we do not run advertising.

3. Data where Mushi Mushi is the controller

This is data about you, the person with the console or tester account: account data, product usage events, docs-site analytics, console error telemetry, support mail, and Bounties tester data.

Legal bases (GDPR art. 6(1))

• (b) contract — creating and running your account, billing, delivering diagnoses, paying tester bounties.
• (f) legitimate interests — keeping the service secure, preventing abuse and quota gaming, keeping the console working (error telemetry), and understanding which onboarding steps fail. We ran a balancing test on the product-usage events: they are scoped to your own account, never shared, and expire (section 7).
• (f) legitimate interests — the docs-site page-view count: an aggregate count per day and page that cannot identify you, with no browser storage. Do Not Track and Global Privacy Control turn it off.
• (a) consent — docs-site analytics. Until you accept the consent bar the docs site loads no analytics code, sends no analytics events, and stores nothing for analytics except your answer; Do Not Track and Global Privacy Control are honoured as a refusal. “No thanks” keeps it that way. The only exception is the page-view count above: it is not the analytics SDK, sends only the path, the ?src= tag and the referring host, and stores nothing in your browser.
• (c) legal obligation — tax records for paid plans and tester payouts.

Free production check (added 2026-10-28). The free production check reads only the public pages of the address you enter (through Firecrawl, section 5) and stores the address, the findings, a one-way hash of your IP address for rate limiting (never the IP itself) and, only if you give it, your email so we can send you the report link once; the email is cleared after that send. Legal basis: (f) legitimate interests (preventing abuse of a free tool); the email is (b) contract — you asked for the report.

4. Data where Mushi Mushi is the processor

End-user report data, fix and repo data, and any voice transcript belong to the project owner — the developer who put the SDK in their app. For that data:

• The project owner is the controller. They decide what the SDK captures, whether to pass end-user identifiers, whether to enable voice intake, and they must tell their own users that screenshots and console output may be captured (this duty is in the Terms).
• Mushi Mushi is the processor and acts only on the owner’s instructions: store the report, run the diagnosis, produce a fix, delete on schedule or on request.
• Data-processing summary (DPA). Mushi Mushi processes this data only to provide the service; applies the security measures on the security summary; uses only the sub-processors in section 5 and gives notice on this page before adding one; assists the owner with data-subject requests through the DSAR tracking in the console; deletes or returns the data at the end of the contract; and makes the SOC 2 readiness evidence available on request. Owners who need a signed DPA on their own paper can email us.

End users of a project owner’s app should contact that owner first. If you cannot reach them, email us and we will forward the request.

5. Sub-processors

6. International transfers and residency

Mushi Mushi is operated from Japan, and production data is stored in Tokyo. The EU recognises Japan as providing adequate protection, and Japan recognises the EEA and the UK in the same way, so EEA/UK ↔ Japan transfers need no extra safeguard.

Transfers to the US sub-processors above rely on the provider’s EU-US Data Privacy Framework certification where it exists, and otherwise on Standard Contractual Clauses in the provider’s data-processing terms.

You can pick a residency region at project creation; see Data residency for what is live today and what is reserved.

7. Retention

8. Your rights and how to use them

If you are in the EEA, the UK, or another place with similar law, you can ask us to access, correct, delete, restrict, or export your data, object to processing based on legitimate interests, and withdraw consent (the docs consent bar can be reset by clearing site data). You can also complain to your local supervisory authority.

• Console accounts: most of this is self-service in Settings. For a full export or deletion, email kensaurus@gmail.com from the address on the account.
• Project owners handling requests from their end users: the console has a DSAR tracker (Compliance → DSARs) that records each request and who completed it, and a host backend can erase one end user’s reports through POST /v1/sdk/erase-subject; see SOC 2 readiness → DSAR.
• End users of someone else’s app: contact the app’s owner. If you cannot, email us with the app name and we will route the request.

We answer within 30 days. We will ask you to prove you own the account or the reporter identity before releasing anything.

9. Japan — Act on the Protection of Personal Information (APPI)

This section applies to personal information handled by Mushi Mushi as a business operator under the APPI (個人情報の保護に関する法律).

• Business operator (個人情報取扱事業者): Kensaurus 合同会社, Japan. Contact: kensaurus@gmail.com.
• Purpose of use (利用目的): to provide and improve the Mushi Mushi service, bill for paid plans, answer support requests, keep the service secure, pay Bounties testers, and comply with law. We do not use personal information beyond these purposes without your consent.
• Provision to third parties (第三者提供): we do not provide personal information to third parties except (a) to the sub-processors in section 5, who act on our instructions under a contract (委託), (b) where required by law, or (c) with your consent. Some sub-processors are outside Japan (mainly the US); we have confirmed their data-protection systems and the measures they take, as required for cross-border provision.
• Retained personal data (保有個人データ): you may request disclosure, correction, addition, deletion, suspension of use, or suspension of third-party provision. Email us with [mushi-privacy] in the subject. We will verify identity and respond without undue delay. We do not charge a fee.
• Security measures (安全管理措置): row-level security on the database tables, encryption at rest and in transit, least-privilege access with an append-only audit log, and the controls listed on the security summary.
• Complaints (苦情): use the same address. If we cannot resolve it, you may contact the Personal Information Protection Commission (個人情報保護委員会).

10. Children

Mushi Mushi is not directed at anyone under 16, and we do not knowingly collect their data. Project owners must not point the SDK at apps built for children without their own compliance review. If you think a child has given us data, email us and we will delete it.

11. Cookies and browser storage

We use no advertising or cross-site cookies. The docs-site page-view count (section 2) stores nothing in your browser. What each surface stores in your browser:

The SDK sets no cookies and reads no third-party cookies.

12. Changes

We will post changes on this page and bump the version number. For changes that reduce your rights or add a sub-processor, we also email console account holders at least 14 days before the change takes effect. Continued use after the effective date means the new version applies.

13. Contact

Kensaurus 合同会社 · Japan · kensaurus@gmail.com · subject [mushi-privacy]

Related: Terms of Service · Security summary · Data residency · SOC 2 readiness