SECURITY POLICY

Security starts with
a visible boundary.

This overview describes how Northwind scopes customer separation, connections, access, and operations without claiming certifications or controls that depend on a specific engagement.

CUSTOMER-ISOLATED ARCHITECTUREOne business. One defined boundary.
Approved connectionEmail, calendar
or business tools
YOUR BUSINESS BOUNDARYDEDICATED ENVIRONMENT
Your private Northwind systemHosted on Northwind’s local servers or built onsite. Business data and agreed workflows stay separated from other customers.
Post-quantum encryptionWorkflow rulesScoped access
Connected providerOnly the data needed
for the approved task
Northwind support access

Human and administrative access is controlled, scoped, and defined with logs, backups, retention, and support responsibilities for the engagement.

Architecture illustration. Exact equipment, connections, access, and operating controls are documented for each engagement.

01

Customer isolation

Each engagement is designed around a dedicated business environment rather than a shared customer workspace. Customer business records and operating context are separated by business; they are not pooled into a common Northwind customer-data store.

02

Post-quantum encryption

Northwind uses post-quantum encryption end to end and for stored data within its private AI systems. This applies to the Northwind-managed environment; controls for approved external services and their data paths are defined separately.

03

Approved data flows

A connection crosses the customer boundary only when it is explicitly approved for the workflow. We document the connected service, the information needed, the action it may take, and where an external provider will process that information.

04

Access and credentials

Customer, Northwind, support, and administrative access is scoped to the role and task. Authentication, credentials, approval boundaries, remote access, and the people permitted to use them are defined for the implementation.

05

Logs, backups, and retention

The engagement defines which events are logged, what is backed up, how long applicable records are retained, and what recovery expectations apply. These details vary with the selected equipment, services, and business requirements.

06

Private hosted and onsite deployment

The Managed AI Admin Agent runs on Northwind’s own private local servers in Orange County. A dedicated onsite infrastructure buildout at the client’s premises is a separate option. Both are private, Northwind-managed environments; approved external tools may process the information needed for their tasks.

07

Support and change control

Support access is controlled and used for the agreed purpose. Testing, updates, dependency work, monitoring, and incident communication follow the responsibilities and contacts defined for the engagement.

08

Human decisions

Automated actions follow agreed rules. Sensitive, unusual, or out-of-scope decisions can be paused and routed to a person with the context needed to review them.