> 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/how-documents-are-protected.md).

# How your documents are protected

How Pipefile encrypts and stores the documents your recipients upload, and the account controls that protect access to them.

## Encryption from the recipient's browser

Files uploaded through Pipefile are encrypted in the recipient's browser with [OpenPGP](https://en.wikipedia.org/wiki/Pretty_Good_Privacy) before they leave the device, then sent over a TLS connection. Upload areas that encrypt this way are marked with a lock icon.

* When you create your Pipefile account, we generate a 4096-bit PGP key pair for it. Recipients' files are encrypted with your public key.
* Key pairs are stored in an encrypted database on a private network. Private keys are password protected, and that password is kept in a separate secrets manager.
* Encrypted files are stored in private storage buckets with strict access controls.
* A file is decrypted temporarily when someone on your team works with it, for example to preview or download it, and is served over TLS.

For full end-to-end encryption, you can upload your own PGP public key and keep the private key offline. Pipefile then can't decrypt those files at all. See [Use your own PGP key](/security/pgp-keys.md).

## Hosting and testing

Pipefile's servers are hosted on Amazon Web Services. We run regular penetration tests with security researchers. The vendors that process data for Pipefile are listed on the [subprocessors page](https://pipefile.com/subprocessors), and more detail is on the [security page](https://pipefile.com/security).

## Who on your team can see a document

Documents belong to the request they were uploaded to. Who can open a request depends on your team settings:

* Team admins can see every request on the team.
* With **Shared inbox** on, members see each other's requests; with it off, they see only their own and the ones assigned to them.
* With [user groups](/team-and-account/user-groups.md), sharing stays inside each group.

See [Team members and admins](/team-and-account/team-members-and-admins.md#team-wide-settings).

## Protecting your account

Passwords are stored as PBKDF2 hashes with SHA256, a method recommended by NIST. On top of your password, Pipefile offers:

| Control                                                                                                    | What it does                                                                                                                          |
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| [New device verification](/team-and-account/two-factor-and-device-verification.md#new-device-verification) | Emails you a confirmation link when you log in with a password from a new browser, device or network. On by default.                  |
| [Two-factor authentication](/team-and-account/two-factor-and-device-verification.md)                       | An authenticator app or hardware security key as a second step at login, with backup codes. Admins can require it for the whole team. |
| [Single sign-on](/team-and-account/single-sign-on.md)                                                      | Your team logs in through your company's identity provider (**Enterprise**).                                                          |

Use a strong, unique password for Pipefile, and don't reuse it on other sites.

## Sending documents to recipients

{% hint style="warning" %}
Pipefile is built for collecting documents. Files you attach to a request for your recipients (sample documents, blank forms, instructions) are not PGP encrypted the way uploads are. They are sent over TLS, but don't attach sensitive information. If you must, send a password-protected PDF and share the password another way.
{% endhint %}

## Related

* [Use your own PGP key](/security/pgp-keys.md)
* [Recipient FAQ](/for-your-clients/recipient-faq.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/how-documents-are-protected.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.