Atwood, LLC d/b/a Nunc

Privacy Policy

Simple rules across our product surfaces: Nunc Data Studio (web analytics & workspace), Nunc Console (tenant administration), Nunc Sidecar (workstation device bridge), and Nunc MCP & SDK. Your organization owns the tenant. We run the governed control layer.

Effective November 12, 2026

The standards we actually run

These are product controls, not marketing badges. We do not claim HIPAA, PCI-DSS, or a completed SOC 2. ISO/IEC 42001 is the AI management system we built the product around; certification is each organization's own program.

  • ISO/IEC 42001-aligned

    AIMS spine: human oversight, model registry, panic switch, evidence trail. Trust & AIMS

  • Guardian on every AI turn

    Six stages: sanitize / PII, secrets, content, injection, egress, DLP. Security

  • Per-tenant isolation

    Your org gets its own dedicated store, memory index, and audit ledger. We do not mix tenants.

  • Default-deny local tools

    Sidecar shell is allow-listed. Writes wait for a person. API keys are stored as cryptographic hashes.

Who we are

This policy is issued by Atwood, LLC, doing business as Nunc (“Nunc,” “we”). Sign-in is authenticated through enterprise identity and SSO providers configured by your organization.

We process data as a processor for the organization that holds the tenant. That organization is the controller of member, staff, and work data inside Nunc.

What each product sees

Nunc Data Studio, MCP & SDK

Conversations, analytical queries, work runs, and files you submit go directly to your tenant's governed gateway — never to a shared consumer model pool. Connected warehouses are queried zero-copy, and external writes pause for explicit human approval according to your organization's policy.

Nunc Console

Tenant administration. We store the identity attributes provided by your identity provider (name, email, organization membership, role), plus the policies you configure: integrations, tool grants, fleet settings, and billing contacts. Administrators see audit and usage strictly for their own organization; there is no cross-tenant access path.

Nunc Sidecar

A lightweight workstation service for managed laptops. It authenticates the device to Nunc with a dedicated machine key, federates allowlisted on-device tools that your tenant's governance gateway authorizes, and writes Claude's enterprise MCP lock (URL only — staff authenticate with company SSO inside their client).

  • The disk stays on the machine. We receive tool results only when a governed call requests a file read, directory listing, or allowlisted command.
  • Local shell execution is deny-by-default. Only commands explicitly allowlisted by your administrator can run — no destructive commands, credential dumpers, or unrestricted shell access.
  • Compute inventory records device ID, sidecar version, and whether the enterprise MCP lock is active — never the contents of local files.

What we collect

  • Account. Identity attributes from your organization's SSO or identity provider. We do not store your SSO password.
  • Work in Nunc. Prompts, tool traces, workflow runs, knowledge you ingest, and audit records — strictly isolated within your tenant.
  • Device (sidecar). Device ID, version, lock/policy state, and connection health.
  • Operations. Logs needed to operate and secure the service (authentication failures, rate limits, Guardian blocks) and content-hashed audit entries where the platform records a governance decision.

What we do not do

  • We do not sell your data.
  • We do not train public foundation models on your tenant's content.
  • Default inference runs on managed, in-network open-weight models with zero prompt retention. We do not route prompts to external third-party model providers unless your tenant explicitly enables or connects one.
  • The sidecar does not continuously sync workstation drives. Local files leave the machine only as the result of a governed tool invocation authorized by your tenant policy.
  • Cardholder data and PHI are out of scope for standard workspaces. Subscription billing is handled directly by a PCI-DSS Level 1 payment processor — never inside Nunc prompts.

Subprocessors and connected systems

We rely on vetted infrastructure subprocessors across four categories: cloud edge compute & isolated storage, managed zero-retention model inference, enterprise authentication & SSO, and PCI-DSS Level 1 subscription billing. Customer-installed integrations (such as Salesforce, Snowflake, or Slack) receive only the requests authorized by your organization's connector grants. We never share tenant content across customers. Current subprocessor details and Data Processing Addenda (DPA) are available upon request at support@nunc.cloud.

Retention and your rights

Audit and usage records are kept so the organization can prove what happened. Your tenant admin can disable surfaces, revoke keys, and disconnect devices. For a copy or deletion of personal data, ask your organization's Nunc admin, or write to us — we will work with the controller. Self-serve export and deletion endpoints are on the AIMS roadmap.

Contact

Atwood, LLC d/b/a Nunc
support@nunc.cloud

Product controls: Security · AIMS · Sidecar install