When support needs a configuration detail or account finding that you prefer not to send as ordinary text, Impreza accepts PGP-encrypted ticket content. Encrypt it on your device before submitting it, then let the authorized support team decrypt it on the support server.
You can separately register your own public key, prove that you control it and require encrypted staff replies. Neither option encrypts every field in a ticket. Keep the subject neutral and send only the details needed to resolve the issue.
Verify the ticket key before encrypting
Open Impreza’s public PGP page. It lists two identities:
- Offline official identity: used for public signatures and certification.
- Ticket identity: used for ticket messages across departments. This is the recipient for your encrypted support message.
Download the ticket public key, compare its full fingerprint with the published value and verify its certification against the offline official identity. A matching display name or email address is not a fingerprint check. Stop if the key or fingerprint differs from the reference you trust.
Use the current key page as the source instead of copying a key from an old tutorial. Import only a public key. Never upload your private key or its passphrase to Impreza or an AI assistant.
Encrypt locally and paste the armored message
Use your PGP application, such as Kleopatra or GnuPG, to encrypt the intended message to the verified ticket key. Export the result as text with its complete BEGIN PGP MESSAGE and END PGP MESSAGE boundaries.
Paste that complete ASCII-armored block into the ticket body. Only the content inside the encrypted block receives this protection. Put no passwords, recovery codes or private configuration in the subject or in surrounding plaintext.
Protected tickets refuse attachments. If support needs a file, encrypt it locally and paste its ASCII armor as instructed on the key page; do not attach the plaintext file. For large material or an unsupported format, ask support for a suitable transfer method first.
After submission, check that the ticket was accepted and follow its status in the portal. The system stores the encrypted block separately and substitutes a notice in the ordinary ticket text and outgoing notifications; it does not automatically encrypt text you submitted outside the block.
Configure encrypted replies with your own key
Sign in as the account owner and open Your PGP key. For an account created without email, use the normal Account ID sign-in and recovery process; a PGP key does not replace the account recovery token.
- Add your public PGP key. Prefer a dedicated key without your real name or personal email in its identity: the public key itself can carry those details.
- Request a verification code. Decrypt the challenge locally with your private key and verify the ticket-key signature.
- Submit the recovered code in the portal. Check that your key is verified and active.
- Choose Require encrypted replies when you want staff replies to require encryption to that verified key. Keep the private key and its recovery material safe.
Adding a key alone is not the same as enabling the requirement. When it is enabled, a plaintext staff reply is refused. The encrypted staff message is signed by the ticket key; verify that signature in your PGP application when decrypting it. Notification emails and ticket subjects remain outside this encrypted body.
Manage or revoke an old public key in the account if you replace it. Revocation changes future use; it does not erase previous tickets or make old ciphertext readable with a new private key.
Understand the protection boundary
Authorized staff can decrypt protected content on the support server. This is client-to-support-server encryption, not end-to-end encryption that excludes Impreza. It does not protect against someone who controls your device or the support server.
The subject, ordinary text outside the encrypted block, notification metadata and unencrypted messages remain visible to the systems handling them. Previous tickets are not retroactively encrypted. Sending through Tor changes the network path; it does not change these PGP content boundaries or prevent support from reading your message.
If an AI assistant helps you draft the ticket, its provider can receive what you paste into that conversation. Encrypt the sensitive final content locally rather than sending it to an assistant for encryption.
Review before sending
- Use the ticket key from the current public key page and check its fingerprint.
- Keep the subject and surrounding text free of sensitive details.
- Paste complete ciphertext; do not upload private keys or plaintext attachments.
- Verify your own key and enable the reply requirement if you need encrypted staff replies.
For an account-data question, start with the privacy report guide and share only the relevant category or finding. Continue through the portal’s support form.