Sub-Processors
Last updated: October 2, 2026
About this list
OpenBoxes Solutions LLC engages the third-party service providers listed below ("Sub-Processors") to process Customer Personal Data in connection with the operation of OpenBoxes Lift. This list is incorporated by reference into our Data Processing Agreement and is referenced in our Privacy Policy.
We commit to providing at least 30 days' advance notice of any new Sub-Processor that processes Customer Personal Data. Notice is provided by updating this page and, for Customers who have subscribed to notifications, by email.
Each Sub-Processor is bound by a written data-processing agreement imposing data-protection obligations substantially equivalent to those in our DPA. We remain accountable for each Sub-Processor's processing of Customer Personal Data.
Current sub-processor list
| Sub-Processor | Purpose | Data categories | Location |
|---|---|---|---|
| Google Cloud Platform | Cloud infrastructure: compute, managed Kubernetes, storage, networking, container registry. Hosts the entire OpenBoxes Lift production environment. | All Customer Personal Data and Customer Tenant Data (encrypted at rest). | United States, us-east1 region |
| Stripe, Inc. | Payment processing: subscription billing, payment method tokenization, invoice generation, dunning. | Account holder name, email, billing address, payment card or bank account details (Stripe stores card numbers in their PCI-DSS Level 1 vault; bank account and routing numbers are entered in Stripe-hosted frames, including the Financial Connections bank-login modal; OpenBoxes only stores tokenized references, the institution name, and last-4 digits), billing history. | United States |
| Sentry (Functional Software, Inc.) | Application error tracking and performance monitoring. Captures unhandled exceptions and selected log events for debugging. | Account holder email and user ID (in error context), browser and OS information, IP address (scrubbed where feasible), stack traces. We configure Sentry to scrub personal data fields where practical. | United States |
| FullStory, Inc. | Session replay and product analytics: records how visitors use the marketing website (consent-gated) and how signed-in customers use the customer portal, so we can find and fix usability problems. | Session recordings (pages viewed, mouse movement, clicks, scrolling, form interactions), device and browser information, IP address, account identifier for portal sessions (never email address). Payment card and bank account fields are entered in Stripe-hosted frames (including the Financial Connections bank-login modal) FullStory cannot see. | United States, na1 data center |
| Twilio SendGrid (Twilio Inc.) | Delivery of transactional email: account verification, billing notifications, password reset, security alerts, lifecycle emails (trial reminders, payment receipts, dunning notices, renewal notices), status page notifications, and the stock alert emails a customer turns on. | Recipient email address, recipient name, message content (typically includes account-related context such as tenant subdomain, invoice amount, trial end date; stock alert emails include product, location and stock level details). | Provider based in the United States |
| Google Workspace (Google LLC) | Our business email. Receives the email customers and prospects send to our support, sales and security addresses, and sends our replies and the personal welcome email a new customer receives from our team. | Sender and recipient names and email addresses, message content and any attachments the sender includes. | Provider based in the United States |
| Anthropic, PBC | AI model provider behind the AI assistant in OpenBoxes, the support assistant in the customer portal, the sales assistant on our website, the automatic sorting of email sent to our support, sales and security addresses, and the AI-assisted column mapping and guidance in data import. | Questions and requests a user types into the AI assistant in OpenBoxes (off unless the customer's account owner turns it on) and the information from that OpenBoxes instance the assistant looks up to answer them, or to prepare a change the user asked for, as that user: product codes, names, descriptions, categories and units of measure; stock quantities and minimum stock levels, lot numbers, expiry dates and bins; location names; stock movement numbers, names, statuses, dates and lines; and the user's name as shown in OpenBoxes (not their username or email address), roles and approver settings, current location, whether an administrator is using OpenBoxes as them, the path and title of the page they are on, and their language setting. On the public demo, the same for the demo's shared sample data. Chat messages and any screenshots attached to a support chat; account details the support assistant looks up to answer (organization name, plan, invoices, a saved payment method's summary such as card brand, last four digits and expiry date, instance status, and instance and access log entries, which can include IP addresses, browser user agents and API key usernames); contact details a website visitor gives the sales assistant (name, email, phone, company); the subject and text of email sent to our support, sales and security addresses (the sender's address is not sent); column headers and up to five sample rows of a file uploaded for import, the field name and value of an import row that needs the customer's attention, and the notes a customer writes about that import. | Provider based in the United States. Requests from the AI assistant in OpenBoxes are processed in the United States; for the other uses we do not select a processing region. |
| Slack Technologies, LLC | Internal notifications to our team: support escalations, new sales enquiries, account and billing events, and operational alerts. | Account holder name, email address and organization name, instance subdomain, contact details a website visitor gives the sales assistant (name, email, phone, company), the sender address of email received at our support, sales and security addresses, and the customer's question or a short summary of the related request. | Provider based in the United States |
| Cloudflare, Inc. (Turnstile) | Bot and abuse protection on the sign-up form, the sales assistant and other public forms. | IP address, browser and device signals collected by the Turnstile challenge. | Provider based in the United States |
| Google Analytics (Google LLC) | Product analytics: how visitors use the marketing website (consent-gated) and how signed-in customers move through the customer portal. | Pages viewed and interactions, device and browser information, IP address, and an account identifier for portal sessions (never email address). | Provider based in the United States |
| GitHub, Inc. | Source code hosting, container registry, CI/CD execution, and the private issue tracker where the support assistant files bug reports and feature requests on a customer's behalf. No production Customer Personal Data is stored in source repositories; build logs may include redacted error excerpts. | Issues filed by the support assistant contain the problem the customer reported and account and instance identifiers. Build logs may incidentally include redacted snippets in case of build-time errors. | United States |
| Keycloak (self-hosted) | Identity provider for customer portal authentication. Hosted on the same Google Cloud infrastructure listed above; included here for transparency about the role and the data it holds. | Account holder name, email, password hash, multi-factor authentication credentials (TOTP secrets), session tokens. | United States, us-east1 region (same as primary infrastructure) |
How we notify of changes
When we engage a new Sub-Processor that processes Customer Personal Data, we update this page with the change at least 30 days before the new Sub-Processor begins processing. The date at the top of this page reflects the most recent update.
Customers may subscribe to notifications about Sub-Processor changes by emailing privacy@openboxes.cloud with the subject line "Subscribe: sub-processor changes".
Customer objections
As described in Section 4.4 of our DPA, Customers may object to a new Sub-Processor on data-protection grounds within 30 days of notice. If we cannot resolve an objection in good faith, the Customer may terminate the affected Service with a pro-rata refund.
Contact
For questions about this list, contact privacy@openboxes.cloud.