Privacy Policy

Last updated:

This notice describes how Nugget handles personal information in connection with its document intelligence API, website, accounts, and support. Nugget is the service operated by the 25madison team. Contact connor.smith@25madison.com for support or privacy requests.

1. Scope and responsibilities

For account administration, service security, and our direct support relationship, Nugget determines the purposes and means of processing. For personal information in documents and other content submitted on a customer's behalf, Nugget acts as a processor or service provider under that customer's instructions and the applicable agreement. The customer determines why that content is submitted and how results are used, and is responsible for appropriate notices and authority to process it.

If your information appears in a customer's document, that customer's privacy notice also applies. The Data Processing Addendum addresses the customer-processing relationship.

2. Information we process and why

Information comes from customers and their authorized users, their submitted content and integrations, authentication and processing providers, and operation of the service. Customers should provide only information needed for their workflow and avoid including credentials or unnecessary personal information in prompts, schemas, or support messages.

Legal bases

Where applicable law requires a legal basis for processing we control, we rely on performance of a contract with the individual for account and service delivery, legitimate interests in operating, securing, and supporting the service subject to applicable balancing requirements, and compliance with legal obligations where processing is legally required. Processing on a customer's behalf follows its lawful instructions; the customer is responsible for its own legal basis.

3. Providers, recipients, and international processing

Nugget uses infrastructure, authentication, storage, document-processing, and model providers as needed for the selected workflow. Google Cloud services, Firebase, and Document AI may process relevant information; selected model providers may receive document content, extracted text, schemas, prompts, and related metadata. See the provider register and the DPA for provider disclosures and processing obligations.

Bring your own key (BYOK) does not avoid processing by Nugget or providers. Nugget uses customer-supplied credentials to make authorized model calls. Document AI processing is separate from LLM-provider keys and may occur as part of a workflow even when a customer supplies its own LLM key. Independent providers’ retention, training use, and processing locations depend on the applicable service, configuration, and contract.

Results and related information may be delivered to callback URLs, integrations, and other recipients selected by the customer. Customers control those destinations and their subsequent use. Authorized personnel and service providers may access information as needed to operate and support the service. Disclosures may also be necessary to comply with applicable law or legal process, or to protect the service and affected people, subject to applicable legal limits.

Processing may involve countries outside the customer's or individual's country. Transfers requiring legal safeguards are subject to the DPA, applicable provider contracts, and applicable law. A selected cloud region does not necessarily cover support, logs, or all provider processing.

Nugget does not sell personal information or use it for targeted advertising. Nugget does not use Customer Content to train general-purpose models under the service agreement.

4. Cookies and browser storage

Authentication and account features may use cookies, tokens, or browser storage to maintain sign-in state and support security. The technologies used depend on the enabled interface and authentication configuration. Browser controls can limit cookies or clear stored data, which may affect sign-in or account features.

5. Retention, deletion, and security

The Retention Policy sets out hosted retention defaults, recovery-copy handling, and deletion boundaries. Document objects have category-specific deletion eligibility periods; asynchronous lifecycle deletion is based on object age and is not a deadline or service-level commitment. Ephemeral processing may remove working data earlier.

Usage records, account-linked aggregates, security records, and deletion-control metadata follow different schedules from document content. Some records have no automatic expiry and require an explicit retention decision on closure or request. Backups and provider-held records do not necessarily disappear when live data is deleted. Log retention varies by deployment and provider.

The service design includes access restrictions and KMS encryption for stored provider keys. Durable purge and deletion-control metadata is restricted and excludes document bodies by design. Security measures reduce risk but cannot guarantee absolute security.

6. Choices and privacy requests

Depending on applicable law and our role, you may have rights to access, correct, delete, or obtain a copy of personal information, restrict or object to processing, or withdraw consent where processing relies on consent. You may also have a right to complain to a relevant supervisory authority. The availability and limits of these rights depend on the circumstances and applicable law.

Contact connor.smith@25madison.com with the nature of your request and enough account or customer context to locate the relevant records. Do not send passwords, API keys, or full documents to establish identity. We verify identity and authority using information proportionate to the request, seek clarification where necessary, and explain the action taken or applicable limits.

For content controlled by a customer, contact that customer where possible. We coordinate with the customer and assist under its instructions and the applicable agreement. Account closure, document purge, authentication-account deletion, and deletion of provider-held records are distinct actions; please identify the scope you seek. The Retention Policy explains the operator-assisted purge process and its limits.

We handle requests under applicable legal requirements and agreed customer obligations. Necessary records may be retained where applicable obligations or justified security needs require it, with the scope and reason assessed in the request process.

7. Updates

We communicate material changes to this notice as required by applicable law and the customer agreement and update the date shown above.