Confidentiality

Receiving access details without exposing them

To work on a customer's site, you often need their access details: back office, FTP, database. Receiving them by e-mail or storing them in clear exposes them at the first incident. FreshApp After-Sales encrypts them as soon as they arrive.

  1. You create the key, once

    In the Settings tab, the browser creates a key pair. The shop only keeps the public key; the private key is stored encrypted by your passphrase, which is never sent to the server.

  2. The customer enters their access details

    The field is yours: enabled per request type, mandatory or not, with your label, your help text and a prefilled template. The content is encrypted with the public key as soon as it arrives.

  3. You read them in the request

    Decryption happens in your browser, after you type the passphrase. The content clears from the screen after a minute, and every read is written into the request thread.

  4. They disappear

    Automatic erasure after the period you set (30 days by default, 365 at most) and, if you wish, when the request is closed. The customer can also replace or erase them from their request tracking.

What an attacker sees — the database and the site files only contain ciphertext and the public key. Without your passphrase, the access details stay unreadable.

Loading...
Back to top