Signed permission
The server signs a short-lived permission for the specific app and registered device. The app verifies it; it never holds the server’s signing secret.
PROTECTION, WITH CLEAR BOUNDARIES
Secure access.
Respect for your work.
Security is a set of tested controls—not a promise that software can never be copied, modified or attacked.
Device proof
A connected device proves possession of its private key before renewal. A copied serial number alone is not enough.
A visible expiry
A permission lasts no more than 24 hours or the paid period, whichever ends first. Internet outages need a clear, approved policy.
Records are separate
Expiry must not erase customer records, alter balances or interrupt a file save. Normal PIN authentication still applies.
PRACTICAL PROTECTION
Seven protection groups.
One fair promise.
Make copying harder without punishing genuine customers. No desktop app can honestly promise impossible-to-break protection.
Seven groups organise eight technical controls. Each status below describes its actual stage, not a piracy-proof claim.
- 01
Account ownership
Private account actions require sign-in. Owner actions are checked separately.
Implemented in preview - 02
Subscription authority
Only verified provider evidence or an explicit owner test grant can create access. Browser success text is not payment proof.
Test mode only - 03
Registered computer
A random installation key identifies the device. Customer photos, phone numbers and hardware serials are not used as an activation key.
Implemented in preview - 04
Signed permission
The server signs a short-lived, device-bound permission. The app has a public verification key, never the signing secret.
Test mode only - 05
Protected offline cache
A valid cached permission can be checked without internet. Windows account protection is not a hardware dongle or a guarantee against same-user malware.
Desktop source tested - 06
Renewal, revocation and recovery
Explicit online refresh checks the registered device. A network failure does not erase an existing cached permission or studio records.
Test connectionRevocation blocks future permission renewal. Already-issued offline permission lasts until expiry; replacement needs account ownership checks.
Recovery policy pending - 07
Signed distribution
A publisher-signed installer, verified updates and staged rollout are required before protected commercial distribution. A checksum alone is not publisher trust.
Launch requirement
A licence expiry must never delete customer history, photos or backups. Existing authenticated record access and safe completion of running jobs are protected.
What is actually ready?
The existing owner candidate has tested access and file-integrity protections but is deliberately unlicensed and unsigned. This website’s test protocol does not silently convert it into a commercial protected release.
What still requires approval?
Production signing keys, public customer authentication, payment-provider onboarding, recurring collection, refund policy, a publisher certificate, final protected-package testing and physical-device compatibility.
Honest limitations
An offline installation cannot learn about revocation immediately. Windows-protected keys are not an absolute defence against an administrator controlling the machine. The current desktop PIN does not encrypt its SQLite database or backups. Open-source engine licences still apply.
Account security
Administrative actions require explicit server-side authorization. Device linking is account-scoped. Payment evidence is verified server-side. Test keys and entitlements are separate from production. Private studio data is not needed for licence checks.