Encrypt it before it reaches us. Our PGP public key.

When you'd use this

PGP is optional. We already move your file through encrypted transfer channels and keep it encrypted at rest, so you don't need PGP to send us data safely. But if PGP is part of how your organization handles sensitive files, we're glad to work that way — encrypt your file to the key below and send it however we've arranged, and only our processing team can open it.

Not sure whether you need it, or how your tool handles encryption? That's exactly the kind of thing we'll set up with you before anything is sent — just ask.

Verify the key

Before you trust any public key, check that its fingerprint matches what the owner publishes. Here are ours. If the key you downloaded doesn't show this exact fingerprint, don't use it — call us instead.

Using it with GnuPG

If you work from the command line, importing and encrypting takes two steps. Most desktop PGP tools do the same thing through their own interface.

# 1. Import the key, then confirm the fingerprint matches above
gpg --import peachtree-data-public-key.asc
gpg --fingerprint dp@peachtreedata.com

# 2. Encrypt your file to us
gpg --encrypt --recipient dp@peachtreedata.com yourfile.csv

Want your return file encrypted too?

The key above lets you encrypt the file you send to us. If you'd like us to encrypt your processed file on the way back, we'll need a copy of your public key. You can include it in the file you send us, or email it to your account manager — either works.

Once we have it, we keep it on our keychain, so you only need to send it again if you rotate your key or it expires. If either happens, just send the new one the same way.