MikataPrivacy Policy
Updated
Mikata has no backend. Apart from one redirect to mikata.moex.land when you authorize it (see below), your data only moves between your browser, the servers you add, and Kamaitachi. The developer never receives it.
What Mikata keeps on your device
Mikata stores the following in your browser’s extension storage. None of it leaves your device except as described in the next section.
- The servers you add: each server’s address, its time zone setting, and an optional name.
- Your Kamaitachi access token: it can only be used to submit scores to your Kamaitachi account, the one permission Mikata asks for.
- The result of the last sync: when it ran, each server’s address, how many scores were submitted and imported, and any messages explaining why scores were rejected or a sync failed. These messages come from Mikata, your browser, or Kamaitachi; the ones from Kamaitachi may name the songs or charts involved. Each sync replaces the previous result.
Mikata does not keep your score exports, and it does not read or store your cookies or passwords.
What Mikata sends, and where
To the servers you add. When you sync, Mikata asks each server for its score export. Your browser sends along the login you already have on that site, as it does for any request there; Mikata cannot see it. If that does not return an export, Mikata may send the same request from a tab you have open on that server. It reads only the reply to that request, not the page.
To Kamaitachi. Mikata uploads each export that has scores in it to Kamaitachi with your access token, then checks on the import’s progress for up to three minutes. An export is a record of your plays as the server provides it; Mikata does not look inside it beyond checking its format and counting its scores. If a server’s time zone is set to anything other than UTC, Mikata corrects the play times before uploading; otherwise the export is sent as is. Exports are held in memory only for the duration of a sync. Once your scores are on Kamaitachi, Kamaitachi’s own terms and privacy policy apply.
When you authorize Mikata. Mikata opens Kamaitachi’s authorization page in a new
tab. Once you approve, Kamaitachi sends that tab to
https://mikata.moex.land/callback with an authorization code in the address. Mikata
reads the code from the tab and exchanges it with Kamaitachi for your access token. That page is
static: it runs no analytics, loads nothing from other sites, and has no logging turned on. The page
is hosted by Cloudflare, which processes the request, including your IP address, under its own privacy
policy.
Mikata has no analytics, telemetry, crash reporting, or ads, and sends nothing to the developer.
Permissions
- Storage: to keep the data described above.
- Scripting: only to resend the export request from a server’s tab when the first attempt does not return an export.
- Access to kamai.tachi.ac: to get your access token and upload scores.
- Access to mikata.moex.land: to read the authorization code from the tab’s address after Kamaitachi sends it back.
- Access to each server you add: requested when you add the server, so Mikata can fetch its export.
Sharing
Mikata does not sell your data, and shares it with no one but Kamaitachi, and only to do what you ask of it: sync your scores. Your data is not used for advertising, for determining creditworthiness, or for anything unrelated to syncing. Mikata’s use of information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
Removing your data
- Removing a server in Mikata’s settings deletes it from your browser, along with its entry in the result of the last sync, and gives back Mikata’s access to that site.
- Removing the authorization in Mikata’s settings only deletes the token from your browser. To revoke it on Kamaitachi as well, open Service Integrations in your Kamaitachi profile, then delete Mikata’s key under API Keys.
- Uninstalling Mikata deletes everything it stored.
- Scores already imported to Kamaitachi stay there. You manage them on Kamaitachi.
Changes
If a new version of Mikata handles data differently, this page will be updated before that version is released, and the date at the top will change. Mikata’s source code is public at github.com/moexland/mikata.
Contact
For questions about this policy, email mikata@moex.land or open an issue on GitHub.