Privacy Policy

1. Summary (read this first)

• Pop Score-Up is local-first. Your scores stay on your device by default. An optional online platform exists for players who want to share scores and connect with friends, but it is off by default and you must explicitly enable it in Settings.
• Score and profile data stay on your phone in the app's private storage after you choose to sync.
• You log into e-Amusement yourself inside the app. Pop Score-Up never automates KONAMI login and never asks you to type your password into a form we control.
• Network traffic during sync goes to KONAMI (`p.eagate.573.jp`) over HTTPS so the app can read your play data and song jackets—the same kind of pages you would open in a browser while logged in.
• No ads, no analytics SDK, no crash-reporting SDK that phones home to us.
• Uninstalling the app deletes the local archive. You can also export a personal copy via Settings before you leave.

2. Who we are

Pop Score-Up is an unaffiliated fan project for players of KONAMI's pop'n music. It is not developed, endorsed, or sponsored by KONAMI. Jacket art, character art, and related trademarks remain © KONAMI.

In this policy, "we" / "the developer" means the maintainers of this fan project—not KONAMI, and not a separate commercial company. The project's source code is developed in a private repository; this public website serves as the download and information hub for Pop Score-Up.

3. What this policy covers

This policy covers:

• Pop Score-Up for Android & iOS (bundle ID tech.popscoreup), including sideloaded APK builds distributed from this site, any future Play Store / internal-test builds, and TestFlight / App Store builds of the same app.
• This website (the public download splash and related static pages such as this privacy policy), hosted as a static/web front-end for distributing and describing the app.

It does not govern KONAMI's own e-Amusement website, apps, or services. When you log into or use e-Amusement, KONAMI's terms and privacy practices apply to that service.

Separate products that may appear in the same open-source monorepo (for example a desktop scraper or an older Capacitor shell) are only covered here if they are the Pop Score-Up app or this website. Those other tools may have their own behavior; check their documentation if you use them.

4. What we collect (developer collection)

In its default local-only mode, Pop Score-Up does not collect, sell, or share your personal data with the developer.

When online features are enabled (opt-in, off by default), the app uploads your score library to a project-operated server so you can share with friends. That data includes your scores, medals, ranks, play counts, and a device-generated anonymous identifier—but never your e-Amusement username, password, or session cookies. Online upload is covered in more detail below.

In local-only mode, we do not operate a backend that receives:

• Your e-Amusement username, password, or session cookies
• Your song scores, medals, ranks, or play counts
• Your player name, class, portrait, or profile fields
• Advertising identifiers, analytics events, or crash dumps
• Location, contacts, photos (beyond what you choose to export), or microphone/camera data

If a store questionnaire asks whether the app collects or shares user data with the developer or third parties for analytics, advertising, or similar purposes, the intended answer for this app is no—because score handling is on-device and the only intentional network destinations during sync are KONAMI's own hosts (see below).

5. e-Amusement, login, and session cookies

Syncing requires access to your e-Amusement play data. The app does this by:

1. Opening a login WebView where you complete KONAMI's normal login flow.
2. After a successful login, snapshotting the session cookies that KONAMI set into the app's private storage so subsequent requests can load your score pages.
3. Fetching your play-data and related pages over HTTPS and parsing them on the device to build a local library.

We never automate KONAMI login. We never ask you to email credentials. Cookies stay in app-private storage on the device and are used only to talk to KONAMI on your behalf during user-initiated (or user-enabled scheduled) sync.

If your session expires, the app stops and asks you to log in again. Expired or missing sessions are not "fixed" by sending data to us.

6. Where your data lives on the device

After sync, the app may store on-device, for example:

• Song scores, levels, medals, ranks, and related chart statistics
• Profile fields shown by e-Amusement (name, class, counts, etc.)
• Cached jacket images and optional character portrait files
• Sync checkpoints / progress so a long sync can resume
• Preferences (filters, layout, auto-sync toggles, and similar)
• Session cookie snapshot used for e-Amusement requests

This lives in the app's private Android or iOS storage (a local database and app-private files). It is not written to a cloud database unless you enable the optional online features in Settings.

Optional features such as home-screen widgets read a small local snapshot of stats so they can render without contacting a server.

7. Optional online features

Pop Score-Up includes an opt-in online platform for players who want to share scores and connect with friends. It is disabled by default; nothing is uploaded unless you explicitly turn it on in the app's Settings.

What is uploaded when you opt in

• Your score library (song scores, medals, ranks, play counts, and related chart statistics)
• Your e-Amusement profile display fields (player name, class value, character name)
• A device-generated anonymous Ed25519 key pair used to identify your device to the server—this is not linked to your e-Amusement account or personal identity

What is never uploaded

• Your e-Amusement username, password, or KONAMI account credentials
• Your e-Amusement session cookies
• Your device advertising identifier, location, contacts, or photos

Server data

Uploaded scores are stored on a project-operated server. You can request deletion of your server data by contacting us (see §17). The server does not have access to your e-Amusement account and cannot log in as you.

8. Network traffic

When you log in or sync, the app makes HTTPS requests primarily to KONAMI's e-Amusement hosts (for example p.eagate.573.jp) to:

• Complete login in the WebView
• Load your play-data / score / profile pages
• Fetch publicly available music-list metadata and jacket images

Those requests include the session cookie KONAMI issued to you, sent back to KONAMI on KONAMI's domain—the normal way a logged-in browser works. That traffic is between your device and KONAMI, not a Pop Score-Up API.

The app is designed to use HTTPS for this traffic and not to make plaintext HTTP requests for sync/login content.

Background or scheduled sync (if you enable it) uses the same on-device session and the same KONAMI destinations. It does not introduce a second, developer-operated endpoint for your scores.

9. Platform permissions (why they exist)

Android

Exact permission labels can vary slightly by Android version, but the Android app may request permissions such as:

These permissions are not used for advertising, tracking, or contacting the developer with your score archive.

iOS

The iOS app uses the platform's native equivalents for the same purposes: URLSession background tasks for sync work, ActivityKit for Live Activity progress display, and local notifications. It does not request location, contacts, photos, camera, microphone, or any other privacy-sensitive iOS permission, and it does not use the advertising identifier (IDFA).

10. Exporting and deleting your data

Export

In Settings you can export a scores.json (or equivalent) copy of your local library. That file is written where you choose on the device so you can back it up or move it yourself. Export is optional and user-initiated.

Import

You may also import a compatible scores file (for example from another device or an older build). Import only runs when you pick a file; it does not pull data from a developer server.

Deletion

Because there is no server-side copy maintained by us:

• Uninstalling Pop Score-Up removes the app-private storage for that install (scores, cache, cookies, preferences), subject to normal Android uninstall behavior.
• Clearing the app's storage from system settings has a similar local effect without necessarily removing the APK.
• There is no separate "delete my cloud account" request to file with us, because we do not host your account or archive.

If you previously exported a file, that copy remains under your control until you delete it.

11. This website

The public site is a download and information page for Pop Score-Up. It does not host a live personal score dashboard and does not require an account.

• APK download: the Android package is served as a static file from the site (or its CDN/host). Your browser performs a normal file download.
• No site login: we do not provide user accounts on this domain for the app.
• Hosting logs: like almost all websites, the hosting provider (for example Vercel or its infrastructure partners) may process standard technical request data—IP address, user agent, timestamps, requested URLs—to deliver the site, protect against abuse, and keep the service running. That is infrastructure logging, not Pop Score-Up reading your e-Amusement scores.
• No intentional marketing pixels are part of the app's design for this splash. If a host enables optional web analytics later, this policy should be updated; as of the last updated date above, the product intent is a simple static marketing/download surface without an app-developer analytics pipeline for score data.
• A service worker may be registered by the web app shell for caching static assets. That cache lives in your browser; it is not a score database and is not uploaded to us.

12. Children

Pop Score-Up is a tool for tracking arcade scores from an e-Amusement account. It is not directed at children under 13, and we do not knowingly collect personal information from children. Because we do not operate a collection backend, we also do not maintain child profiles. If you believe a minor has been encouraged to share KONAMI credentials insecurely, stop and use KONAMI's official account recovery/security paths as appropriate.

13. Security

We take practical steps consistent with a small open-source fan project:

• Local storage of scores and cookies in app-private areas
• HTTPS for e-Amusement traffic
• No design that sends your password or score archive to a developer server

No independent third-party security audit of the app has been claimed or completed. Device security also depends on your phone's OS, screen lock, and who has physical access. Sideloading an APK requires trusting the source of the file—prefer downloads from this site or other channels the project officially documents.

14. Third parties

• KONAMI / e-Amusement: your login and play data are governed by KONAMI when you use their service. We only help you view a local copy of data you can already access while logged in.
• Google / Android / device OEM: the operating system and store (if you install via Play later) have their own policies for app distribution, notifications, and background work.
• Hosting / CDN for this website: delivers static pages and the APK; see §11.
• No ad networks, no score-sharing social backend, no developer analytics SDK are part of the current Android app design described here.

An optional online platform is available for players who choose to enable score sharing and friend features. It is off by default. When enabled, your score data is uploaded to a project-operated server; see §4 and §6 for what is and is not sent. This policy will be updated if the online feature set expands materially.

15. KONAMI disclaimer

Pop Score-Up is an unaffiliated fan project. pop'n music, e-Amusement, jacket artwork, character artwork, and related names and assets are © KONAMI. This app is provided for personal score tracking of data from your own account and is not an official KONAMI product.

16. Changes to this policy

We may update this page when the app or site behavior changes (for example new permissions, a new distribution channel, or optional online features). The "Last updated" date at the top will change when we do. Continued use of the app or site after an update means you should re-read the policy when that date moves.

17. Contact

For questions about this policy or the project, contact the developer at:

aneeshpradhan@acm.org

Please do not include e-Amusement passwords, full cookie dumps, or other secrets in email. Describe problems in general terms or redact sensitive values.