How Nerd fits inside your security boundary

• Authenticated, workspace-scoped accessLive (v1)
  Nerd authenticates its own callers and scopes member, configuration, and audit operations to a workspace. A caller cannot choose a different workspace through a tool argument.
• No customer source-system credentialsLive (v1)
  The assistant host the customer chose keeps the credentials it already uses. Nerd has no path to the customer's CRM, CPQ, ERP, inbox, or other source system.
• Nerd identity and service-secret controlsPartial
  Nerd still processes its own OAuth credentials, member identities, signing material, and service-provider secrets. Code-level controls exist; current production configuration, IAM, access review, and external control effectiveness are not yet fully evidenced.
• SSO / SCIM, formal penetration-test cadenceRoadmap
  Enterprise identity federation and a scheduled external pen-test program are planned.

• Fail closed on missing guidanceLive (v1)
  Nerd serves only the company's published operating guidance. If a required process, rule, or verification contract is unavailable, the connector refuses rather than inventing an answer. The host remains responsible for handling failures in customer systems.
• Status, incident response, backup, and restorePartial
  The public status page is operator-maintained. Incident-response and recovery procedures exist, with local and emulator evidence for parts of the path. Automated public probes, production restore timing, alert ownership, and a contractual recovery commitment are not yet established.

• No customer-system mirrorLive (v1)
  Nerd does not read or warehouse the customer's CRM, CPQ, ERP, inbox, or file store. It keeps the operating configuration a company publishes, Nerd account and access records, audit references, and the blank templates an administrator uploads.
• Metadata and audit minimizationPartial
  The intended architecture keeps customer source content in the customer's host and systems. Nerd still processes request metadata, member identity, configuration, verification input, and audit attribution. A complete production data inventory and field-level disclosure matrix remain unfinished.

• Nerd does not price or author the draftLive (v1)
  The customer's own assistant host reads the approved source and prepares the draft. Nerd is not given the price and has no pricing engine. The customer remains responsible for configuring the host and source permissions correctly.
• No direct write path into customer systemsLive (v1)
  Nerd cannot write a draft, approve a concession, or send to a customer. Those actions, if configured, occur in the customer's host and systems under the caller's permissions.
• Published verification, not independent approval proofPartial
  Nerd can compare a host-reported packet with the company's published verification contract and report what is missing. A host outcome report does not prove that a source was read, a human approved, or a quote was sent. Independent approval evidence is not live.

• Retention, export, and deletionPartial
  Retention and deletion mechanisms exist for parts of Nerd's stored data. Complete production evidence for inventory, export, deletion, scheduled enforcement, backup interaction, and restore remains unfinished.
• Blank files you uploadLive (v1)
  We store uploaded blank templates as files, alongside the company guidance and workspace records needed by the connector. We read inside uploads and refuse files stating a monetary amount; unreadable files are refused too. We do not build a warehouse of your source-system records. Archiving a template preserves its versions and citations. Permanent erasure requires a verified support process. The export route returns current-version files, rather than a list of names; complete historical export and offboarding evidence remain unfinished.
• Data Processing Agreement (DPA), data residency (US/EU)Partial
  A DPA calibrated to our stored guidance, references, and uploaded templates is drafted and pending counsel review (your own systems are not Nerd sub-processors). Regional data residency is North-Star.

On the Team and access page, an Admin can see whether a person has connected their AI, how many questions it answered and blocked, and when that person was last active. Workspace aggregates do not include private chats. Nerd does not show the contents of a person's AI conversation to an Admin.

For the security review pack, sub-processor details, or the draft DPA, email security@asknerd.ai.

Nerd runs no model of its own; the assistant host the customer chooses remains in the customer's environment and does not become a Nerd sub-processor merely by calling the connector. Nerd uses infrastructure providers for authentication, hosting, storage, and email. Nerd runs no model and does no research; your company's assistant researches your company and your customers. Company setup uses information you enter; the assistant your company chose does its own processing. Our cloud provider stores uploaded blank templates. Provider configuration and contractual retention terms require verification. The sub-processor inventory and control map are available on request at security@asknerd.ai.