Common questions about trial protection, security, and SDK implementation.
A: The trial continues from server-side tracking. Users cannot restart trials by clearing storage.
A: No. Our browser fingerprinting creates consistent device IDs across sessions and browsers on the same machine.
A: Yes, trial tracking is now available in .NET, JavaScript, Python, and PHP SDKs.
A: Client-side validation is for UX only. Security comes from server-side validation and multiple protection layers.
A: Hardware binding determines how strictly licenses are tied to specific devices.
A: Use the validateLicense() method with the trial token to recover from server records.
A: Yes, but remember obfuscation is not security - it's just making reverse engineering harder.
A: Implement graceful degradation with time-based feature restrictions.
A: Use background scripts for validation and chrome.storage.local for persistence.
A: Use async tracking with error handling that doesn't block the UI.
Looking for security-specific questions?
Security FAQ →