HCE Test Tool
Privacy Policy
Effective date: October 1, 2026
HCEImage provides HCE Test Tool as a development and testing utility for controlled contactless payment integration environments.
Data collection and sharing
HCE Test Tool does not automatically send personal data, emulation-session data or diagnostics to HCEImage or third-party services. The application does not include advertising, analytics, crash reporting, tracking or other network services. User-initiated copying, report exports and support contact are described below.
Data stored on the device
The application stores emulation-session history, settings, APDU exchanges, validation results and optional notes locally on the user's device. Bundled card profiles contain synthetic test data only. Users may also import native synthetic card-profile definitions or create copies of existing profiles within the app. An imported or created profile, including any profile-default synthetic test security data it contains, is stored in private no-backup app storage until the user deletes it or clears application data. Imported and created profiles are not included in Android backup. This information provides the application's testing and diagnostic features.
Users can delete individual history records, clear all stored history and delete imported or created profiles from within the application. Clearing history does not delete profiles. Uninstalling removes local application data, subject to the operating system's backup and restore behavior. Android backup is enabled; backup and restoration depend on the device, operating system and user settings. Deleting history does not delete separately exported reports, clipboard copies or system diagnostic logs.
Test security data
For supported card profiles, users can optionally enter synthetic application-cryptogram keys, offline-authentication keys or legacy verification card keys/results in the Emulator. These temporary overrides are masked, validated and held only in application memory. By default, they are cleared after the next emulation with that profile starts. Users can instead choose to keep them until the application process closes; they can also remove them earlier. While present, they survive tab changes and device rotation. They are not saved to card profiles, settings, history, reports, logs, clipboard output or Android backups. They are distinct from synthetic default test security data supplied in an imported profile or retained by a local profile copy, which persists with the private profile file. Copying a profile does not include temporary Emulator overrides.
The application may use these values to generate synthetic card responses. Those generated APDU responses and their decoded results are handled like other emulation-session data and may appear in history, diagnostic logs, clipboard copies or user-exported reports as described in this policy. Production issuer keys, real payment credentials and other live secrets must never be entered.
Copying and diagnostic logs
Users can explicitly copy raw APDUs and decoded values to the system clipboard. The application marks clipboard content as sensitive to suppress supported system previews; other clipboard access and retention follow the operating system's behavior.
The selected diagnostic level controls local Android logs. Detailed APDU logging can include complete synthetic test card data. Logs are not sent to HCEImage automatically; device debugging tools and user-created diagnostic captures may include them.
Exporting and sharing reports
Users may explicitly save or share diagnostic reports in Markdown, HTML or PDF format. Full-evidence reports may include emulation-session data, raw APDUs, decoded values and saved notes. Users can instead choose a redacted report, which retains diagnostic structure, status words and timing but omits card-derived values and free-form notes. Export and sharing occur only after a user action and use the destination or application selected by the user. A selected destination may store or transmit the report under its own policies. HCEImage does not receive reports unless the user chooses to send them to us.
NFC and contactless card emulation
HCE Test Tool uses Android NFC host card emulation to exchange test APDU commands and responses with a nearby compatible reader. This processing occurs between the Android device and the reader; the reader receives the emulated test responses.
The application is intended only for authorized development, integration testing and controlled test environments. It must not be used with production payment data or for real payment transactions.
Children's privacy
HCE Test Tool is a specialized developer utility and is not directed to children.
Website hosting
This public policy page and the developer guide linked from in-app guidance are hosted by GitHub Pages. Opening the guide is an explicit user action in an external browser. GitHub logs visitor IP addresses for security purposes under the GitHub Privacy Statement. This website hosting is separate from the application data practices described above.
Changes to this policy
This policy may be updated when the application's functionality or data practices change. The effective date above identifies when this policy took effect.
Contact
For privacy or support questions, contact HCEImage at hceimage@gmail.com. If you email us, we receive your email address, message and any attachments you choose to send, and use them to respond to your request. Do not include real payment card data or other sensitive information in support messages.