Privacy Policy

Last updated 9 September 2026.

MenkyoPass is made by Wuyu (wuyuXAI), an independent developer. This page describes what the app collects, why, and where it goes. If anything here does not match how the app behaves, the app is wrong and I want to hear about it: wuyuxai@gmail.com.

There is no account

The app never asks for your name, email address, phone number, date of birth, address, residence card number, or licence number. There is no sign-up and no login. You cannot create an account because no account system exists.

Your answers stay on the phone

Which questions you answered, which ones you got wrong, your streak, your bookmarks, your review schedule, your settings. All of it is stored on the device and nowhere else. None of it is uploaded, and I have no way to read it.

Delete the app and it goes with it. There is no copy on a server to ask me to delete.

What is sent to my server

The app sends anonymous usage counts so I can tell whether a feature is used and whether the app crashed on a phone that is not mine. You can turn this off in Settings, and when it is off nothing is sent at all.

This is the entire contents of one request. There is nothing else in it.

FieldWhat it is
appThe literal string menkyopass.
install_idA random UUID generated the first time the app opens. It is not derived from your Apple Account, your phone number, your device serial number, or your advertising identifier, and it is not shared with any other app.
app_versionThe version of MenkyoPass you are running.
os_versionYour iOS version, for example 18.2.0.
deviceThe hardware model, for example iPhone16,1. Not a serial number.
eventsA list of the events below, each with a Unix timestamp.

The events

EventWhenExtra
first_openThe first time the app is opened.—
app_openThe app comes to the foreground.—
app_backgroundThe app goes to the background.How many seconds the session lasted.
onboarding_doneThe first-run screens are finished.—
core_actionA practice run reaches the last question, or a mock exam is submitted.Which of the two, and which exam mode.
paywall_viewThe purchase screen is opened.—
purchase_startThe purchase button is pressed.—
purchase_resultA purchase finishes, fails, or is cancelled.Whether it succeeded, the App Store product identifier, and on failure one of cancelled, payment_failed, pending, unknown.
restore_resultA restore finishes or fails.Whether it succeeded, and how many purchases were restored.

Individual answers are never reported. Whether you got question 214 right is not an event and there is no field for it. The app knows how far you got in a practice run; my server only learns that a run finished.

Purchases

Purchases go through Apple. Apple takes the payment and tells the app whether you own it. Your card number, your billing address, and your Apple Account never reach me, because Apple does not give them to developers. What I get is a sales report from Apple with country-level totals in it and no customer names.

No advertising, no tracking, no third parties

There are no ads. There is no advertising SDK, no analytics SDK, no crash reporter from a third party, and no social login button. Nothing in the app talks to Google, Meta, or any advertising network. The only server the app ever contacts is mine.

The app does not use the advertising identifier and does not ask for tracking permission, because it does not track you.

Children

The app is for people studying for a Japanese driving licence, so it is written for adults. It does not knowingly collect anything from children, which is an easy promise to keep when it collects identifying information from nobody at all.

Permissions

Notifications, and only if you turn on the daily reminder. The reminder is scheduled by your phone and is not sent from a server; my server never learns that you enabled it. The app asks for nothing else. No camera, no microphone, no location, no contacts, no photo library.

Where it is kept, and for how long

The usage counts go to a server I rent in the United States and stay there.

Individual events are deleted after 30 days. What survives is a daily tally: how many times an event happened, and on how many devices. There is no install ID in that tally, so it can no longer be traced back to a device.

One thing is kept longer. When a purchase succeeds, a row is written with the install ID, the product identifier, and the time, and that row is not deleted on the 30-day schedule, because it is the record of a sale. If you turn usage stats off, no such row is ever written.

Your rights

Because there is no account, there is no name to look you up by under GDPR or the APPI. Turning the setting off in Settings stops anything further from being sent, and after 30 days the events already sent are gone on their own.

To have something removed sooner, email me. I cannot find your rows from your name or your email address, because neither is in the data. Tell me roughly when and on which iOS version you used the app, and I will work out which rows to delete with you.

Changes

If this policy changes the date at the top changes, and the version in the app changes with it. Adding a feature that sends something new means editing this page in the same release, not afterwards.

Contact

wuyuxai@gmail.com. I answer in English, Chinese, and Japanese.