Subprocessors and providers
Last updated:
Nugget is the service operated by the 25madison team. This register describes providers used to deliver the service and the circumstances in which they process customer data.
1. How to read this register
A subprocessor is a provider engaged by Nugget to process Customer Personal Data on Customer’s behalf under the DPA. A provider that Customer contracts with and instructs directly through a BYOK account may instead be Customer’s own processor or another recipient under that provider’s terms. Credentials alone do not decide the legal relationship.
The entries below describe configuration-dependent service paths. A request reaches only the providers used by its workflow. The applicable account relationship determines whether a provider processes data for Nugget or directly for Customer.
2. Providers and processing purposes
| Provider / service | Purpose and potential data | When used and role |
|---|---|---|
| Google Cloud Platform (GCP), including Firebase | Hosting, storage, application infrastructure, and authentication where enabled. May process account identifiers, submitted documents, extracted content, results, operational logs, and usage metadata according to the deployment. | Infrastructure for the hosted service; a Nugget-engaged subprocessor to the extent it processes Customer Personal Data on Nugget’s instructions. Firebase services depend on the deployed configuration. |
| Google Cloud Document AI | OCR and document parsing; may receive documents, images, request metadata, and extracted text or structure. | Only for workflows configured to use Document AI. A Nugget-engaged subprocessor where engaged through Nugget’s cloud account; processing through Customer’s account is governed by the applicable customer-provider arrangement. |
| Google Cloud Vertex AI | Optional model inference; may receive prompts, selected document content, extracted text, request metadata, and generated results. | Only where the selected workflow and deployment enable Vertex AI. Role depends on the account relationship and selected model; not presumed active for every customer. |
| OpenAI | Model inference; may receive prompts, selected document content or images, extracted text, request metadata, and generated results. | Only when Customer selects and configures OpenAI with its BYOK credentials. Customer’s direct provider where Customer contracts with and instructs it directly; the DPA’s subprocessor obligations apply if engaged by Nugget. |
| Anthropic | Model inference; may receive prompts, selected document content or images, extracted text, request metadata, and generated results. | Only when Customer selects and configures Anthropic with its BYOK credentials. Customer’s direct provider where Customer contracts with and instructs it directly; the DPA’s subprocessor obligations apply if engaged by Nugget. |
3. Configuration, locations, and provider data practices
Data sent to a provider depends on the operation, model, input, account, and deployment configuration. Customer should review provider terms and choose settings suitable for the data it submits. BYOK can allocate account control and billing to Customer, but does not by itself prevent provider storage, training use, abuse monitoring, support access, or cross-border processing.
Processing locations, retention, and data-use settings vary by service and account. A selected resource region may not cover logs, support, or all downstream processing. Nugget-engaged subprocessors are subject to the DPA’s purpose limitations and transfer requirements. Independent providers process data under their applicable agreements with Customer. See also the Privacy Policy and Retention Policy.
4. Authorization and change process
Under the DPA, Nugget must maintain a current list of Nugget-engaged subprocessors, impose appropriate written data-protection obligations, and remain responsible for their covered processing. Before adding or replacing such a subprocessor, Nugget will notify Customer through its designated service contact and provide a reasonable opportunity to object on documented data-protection grounds. Urgent changes needed for security or legal reasons are communicated as soon as practicable.
Nugget and Customer will seek a reasonable alternative for a substantiated objection. If no suitable alternative is available, Customer may terminate the affected processing and receive a proportionate refund of unused prepaid fees for that service under the DPA. Customer’s selection of its own BYOK provider is a processing instruction subject to the applicable customer-provider arrangement.
5. Contact and requests
To request configuration-specific information or subprocessor-change notices, report an inaccuracy, raise a data-protection objection, or obtain support, contact connor.smith@25madison.com. Include the relevant service configuration without sending API keys or unnecessary personal data. Related use obligations appear in the Terms and Acceptable Use Policy.