Frequently Asked Questions
Answers to the questions that matter before you protect, sign, and release an Android game.
Protection & signing.
Do I need to provide my keystore or private signing key?
No. Your keystore, private signing key, and signing password remain in your environment.
You sign and verify the protected APK or AAB within your own release workflow. JikGuard does not require you to hand over your private signing credentials.
How does Google Play App Signing work with the protection workflow?
If you use Google Play App Signing, JikGuard uses the SHA-256 fingerprint of the App signing key certificate where required by the protection workflow.
You copy the fingerprint from Google Play Console and provide the SHA-256 value to JikGuard. You do not need to upload the App signing certificate as a DER or PEM file.
Does the build-time protection process require an internet connection?
Yes. The protection process requires a connection to JikGuard during build-time protection.
The Protection Tool runs as part of your Android protection workflow, while the required protection processing uses the JikGuard service.
Does client-side protection replace server-side anti-cheat?
No. Client-side protection addresses risks such as repackaging, reverse engineering, runtime tampering, memory manipulation, and other attacks against the game client.
Games that rely on server-authoritative validation, behavioral analysis, account-risk systems, or continuous real-time anti-cheat operations may still require those additional security layers.
Build workflow.
Which platforms is JikGuard currently available for?
Currently available for Android. The current standard product protects Android game clients; the operating systems used to run the Protection Tool are a separate consideration.
Can I protect both APK and AAB builds?
Yes. The Protection Tool supports both APK and AAB as protection inputs.
The protection flow is the same for both formats, so you can continue with the format used by your existing Android release workflow.
Which game engines are supported?
JikGuard supports Android games built with Unity, Cocos, and Unreal Engine.
Which operating systems can I run the Protection Tool on?
The Protection Tool supports Windows, Linux, and macOS.
You can use the Tool from the development or build environment that fits your existing workflow.
How does protection fit into my existing build and release workflow?
Start with the APK or AAB produced by your existing Android build process.
Run the build through the Protection Tool, complete the required build-time protection processing, and then continue with the protected output in your own signing, verification, testing, and release workflow.
Your signing keys and final signing process remain on your side.
Licensing & support.
How does a JikGuard license relate to my package name?
Each standard JikGuard license is assigned to one package name.
You can use that license for the same package name during its active term. If you need to protect a different package name, a separate license is required.
Can I protect new builds of the same package name during my license term?
Yes. While your license is active, you can create new protected builds for the licensed package name.
You do not need a separate license each time you release a new build of the same package name.
What happens to released protected builds when my JikGuard license expires?
Protected builds that have already been released continue to run after the license expires.
JikGuard standard licenses are prepaid for a fixed term and do not renew automatically. An active license is required when you need to create new protected builds.
Does JikGuard offer a public free trial or protected demo?
No. JikGuard does not offer a public free trial, and the current product does not provide a Protected Demo.
The first-month price, where shown on the Pricing page, is a paid license offer rather than a free trial.