Troubleshooting & support
Resolve the issue with the right context and a private conversation.
Sign-in or access problems#
Check that the email address is correct and look in your spam folder before requesting another code. Use the latest code within its validity period. A successful sign-in does not itself confirm purchased access; contact the team with your payment reference if access is still locked. Never send a sign-in code in a support message.
Keep the release traceable#
Keep the original artifact, protection configuration and build identifier together. A completed protection run is the point at which an output is available; validate that output before publishing. An interrupted connection is not proof of either success or failure. Check the existing operation through the client before resubmitting.
Support with continuity#
Open Support in your Client Area to discuss a project, report an issue or request a configuration review. Accounts without a purchase can use Buy and Support; active customers receive priority. Conversations remain available until you or our team delete them.
Share only the material needed to investigate the issue. Remove credentials and unrelated personal data from logs. Discuss sensitive source material with the team before sending it.