Your data, explained simply.

Your API key, synced WaniKani data, saved study sessions, progress history, goals, settings, and Reader books stay in this browser. Wanascope uses IndexedDB, local storage, and session storage to support these local features and remember your choices.

Pasted Reader text disappears when you reload.

Browser storage is not encrypted, so avoid connecting on a shared device.

With study permissions enabled, Wanascope starts lessons after you pass the quiz and submits completed reviews, including incorrect-answer counts, only through study actions you choose. Saved sessions and unconfirmed results remain in this browser until you finish or end the session, sign out, or clear site data.

Your WaniKani API key goes only to WaniKani's official API over HTTPS for sync, reminder checks, and lesson or review actions you choose. It is not sent to Wanascope servers. Reader text and books are not sent anywhere.

If you connect Bunpro, its separate token and learning data pass through Wanascope's server as described below.

After a connected account syncs successfully, Wanascope privately records its WaniKani user ID, username, current level, first and latest successful sync times, and when its first-connection alert was sent. This account registry recognizes returning accounts and avoids duplicate adoption counts; it is separate from analytics.

Hosting providers also receive normal request data such as your IP address, requested page, browser, and time so they can serve and protect the site.

Production visits use the limited Vercel measurements described below. Reminders and messages send data only when you use those features.

Connecting Bunpro is optional. Its frontend token is saved in this browser.

During a sync, Wanascope's server receives the token, forwards only supported read requests to Bunpro over HTTPS, and returns the learning data to your browser. The server does not store or log the token or learning data and does not cache the responses.

Bunpro receives the requests and applies its own privacy policy.

Your Bunpro identity, vocabulary, grammar progress, and reference data are saved in this browser under your connected WaniKani account.

Disconnecting Bunpro removes its saved token and data; logging out or changing WaniKani accounts also removes the connection.

This beta reads Bunpro only and does not submit reviews or change your Bunpro account.

Bunpro data and credentials are not included in local backup exports.

Vercel Web Analytics receives anonymous page-view data for aggregate traffic reporting, including a normalized allowlisted page, referrer, broad location, browser, operating system, and device type. Query strings, fragments, and unrecognized paths are removed or grouped before sending. It uses no third-party cookies and does not provide Wanascope with a cross-site identity.

Vercel Speed Insights receives real-user Web Vitals, normalized page or route, broad browser, device, network, and country information, and available performance-element attribution.

These measurements run only on production visits and exclude Wanascope's known internal traffic.

The private account registry stores WaniKani user ID, username, current level, first and latest successful sync times, and when its first-connection alert was sent. It never stores your API key or detailed study data.

If you enable reminders, Wanascope stores the browser delivery details, reminder times, language, and summary counts needed to send them.

Your chosen feedback display name is remembered in this browser and can be changed before posting.

The web Feedback board stores your posts, replies, optional display name, selected screenshots, and a random browser identifier used for votes, reports, and blocked authors. Its authentication secret is stored in a first-party cookie that page scripts cannot read; the cookie lasts up to one year and is renewed when you use Feedback. Ordinary learner feedback is separate from your WaniKani account. A private developer roster links an approved developer’s account ID to their feedback browser identity so their posts and replies can show a Dev badge. Posts, replies, and selected screenshots appear publicly when you send them. You can report inappropriate content or block its author.

Web feedback is stored separately from iOS feedback. Public posts show the message and chosen display name. Reply emails, page and device details, and account identifiers are never shown on the board. Privacy requests remain private.

The privacy button opens your email app; this page does not collect the request. If you send it, your email provider and the services used to route and host Wanascope's privacy inbox process your email address, message, and standard email metadata.

Local data remains until you remove the relevant item or clear site data. Logging out removes your API key and synced WaniKani data, but it does not remove Reader books, interface preferences, or the private account-registry row; remove those separately or request registry deletion.

Account-registry rows remain while Wanascope operates the registry unless you request earlier deletion.

Private form submissions are automatically deleted after 180 days. Public web feedback and its replies are retained while useful for support. Clearing site data removes your browser feedback identity; it does not delete submitted posts. For removal requests, contact support@wanascope.com with the feedback number.

Privacy emails remain in Wanascope's privacy inbox according to the routing and inbox services' retention and backup settings.

Reminder records are generally removed after about 1, 7, or 90 days depending on their status.

Vercel and other hosting or security copies follow each provider's settings.

Log out to remove your API key and synced WaniKani data, remove Reader books separately, or clear site data to remove everything stored by Wanascope in this browser; revoke your key in WaniKani as well.

To access, correct, or delete the private account registry, email a privacy request with only the username or user ID needed to find the row—never your API key.

Vercel's aggregate measurements are not exposed to Wanascope as an identifiable user record.

Wanascope is responsible for the limited server data described here. Contact support@wanascope.com.

Vercel hosts and protects the site and provides privacy-focused aggregate Web Analytics and real-user performance measurements.

Supabase stores the private account registry, feedback, and reminder records in Singapore.

Resend sends a new-account alert without the WaniKani ID, username, or level, plus other operational alerts.

Your email provider and the services used to route and host Wanascope's privacy inbox handle any privacy email you choose to send.

WaniKani receives direct API requests, and the browser's push provider delivers reminders.

Providers may process data across borders.

The account registry is used only to recognize returning accounts, avoid duplicate adoption counts, and operate the service.

Vercel measurements are used to understand aggregate traffic and performance; reminder and message data is used to provide features you request; basic hosting and security data is needed to run and protect Wanascope.

Wanascope does not sell personal data.

Depending on applicable law, you may ask for access, a copy, correction, deletion, restriction, or an explanation; object to processing; withdraw consent; or complain to your local data-protection authority. Contact support@wanascope.com.

Wanascope may ask for enough information to verify the request and will explain if it cannot fulfill it in full.

Wanascope is not designed for children below the age at which they can make their own data choices. A parent or guardian can contact Wanascope if they believe a child submitted information.

Material changes update the effective date and policy version; Wanascope asks again before enabling anything that requires a new choice.

Your WaniKani Personal Access Token is stored in an iOS Keychain item restricted to the current device. Cached learner data, pending study actions, resumable study sessions, and app preferences stay in the app container.

Reader text is processed locally and is not uploaded by Wanascope.

Signing out removes the Keychain token, account-specific local data, saved study session, pending local reminders, and badge; removing the app deletes its local container according to iOS behavior.

Authenticated requests go directly from your device to https://api.wanikani.com/v2.

Dashboard synchronization is read-only.

Only an action you explicitly take in Study uses assignments:start, reviews:create, study_materials:create, or study_materials:update to start an assignment, submit a review, or create or update your own notes and meaning synonyms.

Wanascope does not perform these changes for advertising, analytics, or background profiling.

The iOS app has no developer-operated app account, learner-data sync backend, or analytics backend. The App Store Release build does not operate the internal developer account registry.

Opening, connecting, or refreshing WaniKani does not register your account with Wanascope or automatically send your token, account details, API response bodies, study or Reader content, answers, notes, or synonyms to Wanascope.

Version 1.1 adds optional Feedback collection only when you choose to use it, as described below.

Version 1.1 includes an optional moderated Feedback board in Settings.

We store the text you submit, optional display name, selected JPEG attachment, optional app version/build/locale/system diagnostics, and a random Feedback installation identifier. Reports, votes, and author-block relationships use that identifier. Its authentication secret stays in Keychain.

New posts and replies are held for moderation before other users can see them. Screenshots require separate approval.

Moderators can inspect pending content; approved text and photos are visible to other Feedback users. There is no direct or random chat.

Report inappropriate content or use Block this author to hide it for your installation. Reports are reviewed within 24 hours.

For private support or removal requests, email support@wanascope.com and quote the issue number.

Never submit tokens, private study data, or personal information in posts or screenshots.

Version 1.0 has no Feedback board.

Supabase hosts optional Feedback. Resend may deliver metadata-only issue/report alerts to the operator; alerts do not include your post, image, name, diagnostics, or credentials.

Feedback is not used for advertising or analytics and is not joined to ordinary WaniKani accounts.

Only the private moderator roster associates an operator's verified account UUID with an enrolled Feedback installation.

Email conversations retain the information you choose to provide for answering your request.

Published Feedback is retained while useful for support.

Our retention targets are 30 days for rejected posts and replies, 180 days for unapproved posts and replies, and 90 days for resolved or dismissed reports.

Published open and closed content is not automatically purged.

Image removal includes the stored image, not only its board entry.

Contact support@wanascope.com for removal requests; never send a token or device secret.

No.

Review reminders are scheduled locally with Apple's UserNotifications framework. Wanascope does not register for remote notifications or send an APNs token, reminder schedule, or review count to Wanascope, Supabase, or an analytics provider.

The iOS app has no ads, cross-app tracking, session replay, or third-party analytics SDK.

The app offers four optional one-time tips processed by Apple through StoreKit. Tips do not unlock features.

Wanascope does not receive or store payment-card details, and Apple's handling of purchase information is governed by Apple's policies.