Pokecom GO Player Privacy Policy (iOS)
Effective: October 25, 2026
Last updated: October 25, 2026
Developer: digihori (デジホリ工房)
Applies to: Pokecom GO Player for iPhone (Bundle ID: com.digihori.pgp.player.ios)
This policy applies to Pokecom GO Player for iOS provided by digihori. It does not cover Android Player or Pokecom GO Studio.
Data collection and network access by the app
The current app has no account registration, advertising, analytics, tracking, or automatic transmission of ROMs, programs, or input history to the developer. The app itself does not fetch content or data over the network. ROMs, programs, and settings are processed on your device.
For communications by cloud file providers you select, external browsers, GitHub, and other services, or for information you voluntarily post in an inquiry, see the sections below.
Information stored on your device and its purposes
The app stores copies of registered ROMs, machine information, original filenames, ROM component information, and integrity hashes in its private ROM Library. It also stores the selected and running machines, the selected model within each series, the home screen tile/list layout, sound settings, CPU speed, controller input settings, and key mappings locally.
This information is used to validate and restore ROMs, select machines, retain settings, and operate the emulator. Registered ROMs and settings remain until you delete or change them or delete the app. App-private storage is protected by iOS access controls.
Running RAM and CPU state and currently held keys are kept in memory. There is no RAM/CPU save-state feature or restoration across app or process termination. Save programs you want to keep to files.
Reading and saving files
ROMs, BASIC text, and memory dumps are read from files you choose with the standard iOS file picker. Registered ROMs are copied into the app; persistent access permissions to their original URLs are not stored. The app does not request permission to read all files on your device.
You also choose where programs are saved. The app prepares export data in temporary app storage and saves it to your chosen location through the standard iOS file picker. It has no custom upload or sharing feature.
The app supports iOS file sharing for its Documents folder. Files you place or manage there using Finder on a Mac or the Files app are stored separately from the ROM Library.
If you select iCloud Drive, Google Drive, or another provider, that provider may communicate over the network to retrieve, authenticate, save, or synchronize files. This is not a custom cloud synchronization service operated by the app. Consult the provider’s privacy policy. Saving a file does not guarantee that cloud synchronization has completed.
Audio output and external input
The app sends emulator-generated audio to iOS audio output. It respects silent mode and can coexist with audio from other apps. It does not use the microphone, record audio, save audio files, transmit audio externally, or play audio in the background. Interruption and output-change or disconnection notifications are used to control playback.
The app uses information and input from compatible game controllers and external keyboards already connected through iOS to select devices, map keys, and operate the emulator. Connected device names, temporary identifiers, and the selected controller are handled in memory. Device IDs and keystroke history are not stored or transmitted externally. The app does not implement its own Bluetooth communication or pairing.
External links and information displayed in the app
Selecting external links, such as those in the Studio guide or contact information, opens GitHub or another destination in an external browser or other handler. Communications and access information are then governed by the browser’s and destination’s policies and settings.
Guides, licenses, and the privacy policy shown in the app are bundled at build time. Displaying them does not connect to GitHub to retrieve their content. Changes to bundled text are delivered through app updates.
Deletion and backup
Delete registered ROMs through Home → Settings → ROM management (設定 → ROM管理). Deleting the app also deletes app-private data. The iOS Offload App option may retain data and is different from deleting the app.
Deleting a ROM Library entry does not delete its original source ROM or files in Documents or programs exported elsewhere. Delete those files separately in Files or at their saved locations.
The app marks its ROM Library as excluded from iOS backup. This applies to the app’s ROM Library and does not exclude all Documents, other settings, or external storage locations. Not every OS, backup, or device-migration behavior has been verified. Keep your own copies of original ROMs and programs you need.
Contact and revisions
Contact digihori about privacy through the project’s GitHub Issues. Posting requires a GitHub account. This is a public channel. Do not post ROMs, programs, personal information such as email addresses, or confidential information.
We review and use your GitHub username and the message and attachments you choose to post to respond to inquiries and investigate problems. Posts are public and are not automatically deleted when an issue is closed. Storage, deletion, and account information are governed by GitHub’s privacy policy and service features. To remove information, use GitHub’s editing/deletion features or contact GitHub Support.
We revise this policy when data-handling practices change and update its effective/last-updated date and text on this page. Changes to the app’s bundled copy are delivered through app updates.