Announcing BYOB (Bring Your Own Bucket)

Starting today, all SendSafely Enterprise and Business customers have the option of going BYOB, short for Bring Your Own Bucket (probably not what you were thinking). With BYOB, all encrypted files and messages are stored in an Amazon S3 bucket that you own and manage instead of using our S3 storage facilities. This means is that you have full access to your data files store at all times, and can even control the policy we use to delete items. Want to keep deleted items forever? No problem! With BYOB, you call the shots.

If you are an Admin in your organization’s SendSafely portal and are interested in going BYOB, contact support@sendsafely.com to enroll. Once enrolled, you will need to configure an API Key and API Secret that has read and write permissions to your S3 bucket. We will even walk you through the process of getting that set up and configured if you haven’t done it before.

Frequently asked questions

What is SendSafely BYOB (Bring Your Own Bucket)?

BYOB was an option announced in 2014 that let SendSafely Enterprise and Business customers store all encrypted files and messages in an Amazon S3 bucket they own and manage, instead of SendSafely’s own S3 storage.

Can I use my own AWS S3 bucket with SendSafely?

Yes. Business and Enterprise customers can configure SendSafely to use their own AWS S3 buckets in the region of their choice, as described in the SendSafely FAQ. This option was first introduced in 2014 under the name BYOB.

Are files stored in a customer-owned bucket still encrypted?

Yes. The BYOB announcement describes the files and messages placed in the customer’s S3 bucket as encrypted; the bucket replaces SendSafely’s storage location, not the encryption. SendSafely encrypts content on the sender’s device with OpenPGP, as described on the Secure File Transfer page.