> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/security/pgp-keys.md).

# Use your own PGP key

Upload your own PGP public key so files are encrypted to a key only you hold, for end-to-end encryption.

Every Pipefile account has a PGP key pair that Pipefile manages for you (see [How your documents are protected](/security/how-documents-are-protected.md)). If you need end-to-end encryption, you can add your own PGP public key instead. Recipients' files are then encrypted to your key, and only your private key, which never touches Pipefile, can open them.

{% hint style="warning" %}
Your own key changes how you work with files. Read [What changes](#what-changes) before you switch.
{% endhint %}

## Add your key

{% stepper %}
{% step %}

### Export your public key

In your PGP tool (for example GnuPG), export your public key in ASCII-armored form. It begins with `-----BEGIN PGP PUBLIC KEY BLOCK-----`.
{% endstep %}

{% step %}

### Paste it into Pipefile

Go to [Settings → Security](https://pipefile.com/dashboard/settings/pgp/new). Paste the whole key into the **New PGP Key** box and click **Add Key**.
{% endstep %}

{% step %}

### Check it's primary

You'll see **New PGP Key Added**. On the [Settings](https://pipefile.com/dashboard/settings) page, the **PGP Keys** card lists your keys by fingerprint; the new key is marked **Primary**.
{% endstep %}
{% endstepper %}

## Which key a request uses

New requests use your **Primary** key. When you have more than one key, the request form shows an **Encryption Key** menu so you can pick one per request. The key is fixed once the request is created; you can't change it on an existing request.

Recipients can see the key's fingerprint on the upload page and compare it with the one you give them.

## What changes

|                      | Pipefile-managed key                    | Your own key                                                                           |
| -------------------- | --------------------------------------- | -------------------------------------------------------------------------------------- |
| Who can decrypt      | Pipefile, for you and your teammates    | Only the holder of your private key                                                    |
| Downloading files    | Files download ready to open            | Files download still encrypted, with a `.gpg` extension; decrypt them on your computer |
| Previews in Pipefile | Available                               | **Preview Unavailable**                                                                |
| Teammates            | Can open files on requests they can see | Can't open the files                                                                   |

Features that need to read a file's contents inside Pipefile don't work for files encrypted to your own key.

{% hint style="danger" %}
Keep your private key and its passphrase backed up. If you lose them, nobody, including Pipefile, can recover the files. If your public key expires, recipients can't upload to requests that use it; renew the key or add a new one.
{% endhint %}

To go back to your Pipefile-managed key for new requests, pick it in the **Encryption Key** menu, or email <support@pipefile.com> to make it primary again.

## Related

* [How your documents are protected](/security/how-documents-are-protected.md)
* [Download and export to PDF](/reviewing-and-exporting/download-and-pdf-export.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.pipefile.com/security/pgp-keys.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.