Understand the boundary between protection and release.
How JikGuard connects during build-time protection, which signing materials stay with your team, and where to find the technical details before release.
Protection requires a server connection.
APK and AAB follow the same protection workflow.
Protection input
APK or AAB.
Build-time connection
A connection to the JikGuard server is required to perform protection.
Signing boundary
Keystores, private signing keys, signing passwords and final signing stay in the customer environment.
Your signing keys stay in your environment.
Keystore and private key
Remain with the customer's team; not uploaded for protection.
Customer environment
Signing password
Remains with the customer; not uploaded for protection.
Customer environment
Google Play App Signing
Uses the App signing key certificate's SHA-256 fingerprint as input; DER / PEM certificate-file import is not part of the current workflow.
SHA-256 fingerprint
Final signing
Performed by your team in your existing release workflow.
Customer-controlled
No JikGuard connection at runtime.
JikGuard protection is applied before release. Once a protected game is running on players' devices, it does not need to connect to JikGuard.
The build-time connection described above is part of preparing a protected release and is separate from how the released game runs.
Ask about data handling →Three stages. Clear ownership.
Prepare APK / AAB
Customer Environment
→
Run JikGuard Protection
Build-time connection required.
JikGuard Cloud
→
Sign & release
Customer Environment