Legal & Compliance
JuiceFS Cloud Service subprocessors
The third parties below help us deliver JuiceFS Cloud Service. Each one processes customer data only to run the service, under a written agreement.
Last updated:
What we hold. Your file contents stay in your own object storage bucket — Juicedata does not store them. We run the metadata service, which holds file and directory names, sizes, owners and timestamps, in the cloud region you choose when you create a file system.
Infrastructure
Metadata service hosting. Only the provider of the region you pick processes your metadata.
| Subprocessor | Purpose | Location |
|---|---|---|
| Amazon Web Services, Inc. | Hosts the metadata service | Region chosen by the customer |
| Google LLCGoogle Cloud | Hosts the metadata service | Region chosen by the customer |
Service providers
Third parties that support billing, support and operations of the service.
| Subprocessor | Purpose | Data | Location |
|---|---|---|---|
| Stripe, Inc. | Billing and payments | Billing contact, payment methodcard data stays with Stripe | US |
| Google LLCGoogle Workspace | Email and support correspondence | Contact details, support messages | US |
| Slack Technologies, LLC | Support channels shared with customers | Support messages, logs customers choose to share | US |
| PagerDuty, Inc. | On-call alerting | Service alerts: host and region names | US |
| Functional Software, Inc.Sentry | Error reporting for the web console | Error details, which may include account identifiers | US |
| Mixpanel, or other product analytics | Product usage analyticsif enabled | Usage events |
Changes to this list
How we notify you before a new subprocessor starts.
We will update this page and email the account owner of each paid account at least 30 days before a new subprocessor starts processing customer data.
If you object to a new subprocessor, contact [email protected] within that period, and we will work with you on a solution.
