How BucketDesk protects your files.
Last updated November 16, 2026
BucketDesk is a workspace for files that stay in your own Amazon S3 buckets. This page describes how access works and what we do to keep it safe. For questions or a completed security questionnaire, email info@bucketdesk.com.
Your files stay in your bucket
- BucketDesk’s servers do not keep copies of your files. Previews and downloads stream from your bucket when you open them. Copies exist only on your own devices and servers: files synced by BucketDesk Sync, previews cached by the iPhone app, and the offline cache of a self-hosted server. The document server below is the one exception.
- Word, Excel and PowerPoint files open in a document server BucketDesk runs itself. It fetches the file with a short-lived link and keeps it only while the document is open.
- Document AI runs on Amazon Bedrock in your own AWS account, through a separate role you create, and only on what you ask about: the files you question, a folder’s file names when you ask for a bucket summary or Organize, and a call’s transcript for its summary. BucketDesk does not index your bucket. See what a document question costs on Bedrock.
Access to your AWS account
- You connect through an IAM role you create with our CloudFormation template. No access keys are shared, and you can revoke the role at any time.
- Every connection has its own external ID, and BucketDesk only ever holds short-lived credentials that expire within an hour.
- The file role can read and write in the buckets of the AWS account where you create the stack. Your admins choose which buckets join the workspace, your plan decides which features it uses, and member roles decide who can upload, delete or share. See every IAM action the role can use on each plan.
- BucketDesk refuses connections to roles in its own AWS accounts, so one customer cannot point BucketDesk at another’s resources.
Accounts and workspaces
- Sign in with a password, a passkey, or an authenticator app. Workspace owners and admins must set up two-factor authentication before managing connections, members or tokens. New accounts get 14 days to set it up.
- BucketDesk Sync and the iPhone app sign in through the browser with OAuth and PKCE. Access tokens last one hour and refresh tokens 30 days, kept in the device’s keychain. Removing a member signs their devices out on the next request; AWS keys already issued to BucketDesk Sync expire within the hour.
- Workspace roles control who can view, operate, share and administer. Viewers cannot create share links or upload. This is how teams access S3 files without the AWS console.
- Every share link is made for one email address and always expires, after 1 to 30 days. The recipient opens it with a six-digit code sent to that address, and five wrong codes lock it until a new one is sent. The person sharing chooses whether the file can be downloaded or only viewed. BucketDesk stores links as one-way hashes.
- Removing a member immediately revokes their share links, API tokens and AI assistant connections. Changing a password signs out other sessions, API tokens and AI connections.
- API tokens always expire, within a year at most. AI assistant access tokens last one hour. Here is how to connect Claude to Amazon S3.
- Views, shares, deletes and administrative changes are recorded in the workspace activity log.
Encryption
- All traffic uses TLS 1.2 or 1.3; older protocols are refused.
- Our database and backups are encrypted at rest. File names in notifications and activity details, connection secrets and document chats are encrypted again by the application. Sign-in, share and API tokens are stored only as one-way hashes.
Infrastructure and operations
- BucketDesk runs on AWS in the United States (us-east-1). The database is not reachable from the internet. Web traffic arrives through Amazon CloudFront with AWS WAF, and the server refuses requests that don’t come through it. Administrative SSH is limited to our own address and the AWS console.
- Every change goes through code review. Our pre-push hook scans every change and stops pushes that add a known high or critical vulnerability, and the running containers are scanned again every day.
- The app’s scripts run only with a per-request nonce under a Content-Security-Policy. The third-party scripts the app loads are Google Analytics, Google Ads and Google Tag Manager.
- AWS CloudTrail records account activity, GuardDuty watches for threats, and alerts reach us by email.
- Automated scanning checks our code, dependencies, secrets and infrastructure templates, and error monitoring reports production errors. See how we watch each layer.
- Application logs record request paths without query strings, so share tokens and search terms are not logged.
- The database is copied every hour to a separate AWS account, where each copy is kept 35 days and cannot be deleted early, and the server is snapshotted daily.
Service providers
Amazon Web Services (hosting, email, Bedrock), Stripe (payments), Sentry (error monitoring) and Google (analytics and ads, turned off when your browser sends Global Privacy Control). See the privacy notice for details.
Compliance
BucketDesk follows written security procedures for access reviews, change management, incident response, backups and vendor review. We do not yet hold a SOC 2 report or other third-party certification. If your review requires one, tell us; we can answer your questionnaire and share more detail under NDA.
Report a vulnerability
Email info@bucketdesk.com with “Security report” in the subject line. Include the steps to reproduce and what an attacker could gain. Please do not access other customers’ data or disrupt the service while testing. We will not take legal action against anyone who reports a vulnerability in good faith. Our security.txt has the same details.