The source remains identifiable.
Email, document store, CRM or another system inside the agreed account and scope.
Customer-controlled sourceSecurity & Trust
Intelligence moves where it is authorised. Confidential information remains within agreed boundaries.
Arthur works through defined organisational context, deliberate connections and accountable authority. The boundary comes before the capability.
Organisation 01OperationsBoundary closed
Organisation 02Authorised contextPermission gate open
Organisation 03KnowledgeBoundary closed
Arthurpermission-aware intelligenceEvidence trail
Our position
Your business stays your business.
DELTAGUARD will tell you what information a workflow needs, where it may go, what may remain and who controls the next action. Security begins before access is granted.
The permission boundary
Access is granted. Access is bounded. Access can be withdrawn.
Move through the model to see the working relationship between the organisation, its permissions and Arthur.
What Arthur can see
Disconnected until you decide otherwise.
Choose systems in the model. Only authorised routes illuminate; the rest remain outside Arthur’s working context.
Arthur2 authorisedIllustrative permission stateDocuments · Projects
Becoming a DELTAGUARD client does not itself connect these systems. Each route needs an agreed purpose, suitable credentials and the permissions required for the work.
Try the controls — this visual changes locally and does not connect to any real system.Security before access
Five decisions define the working boundary.
Nothing needs to be connected until these questions have clear answers.
- 01
What Arthur may access
The named systems, accounts, information and purpose of the connection.
- 02
What Arthur may retain
Where information is transient and where operational records, memory or evidence may remain.
- 03
What Arthur may do
The difference between reading, preparing, recommending and changing something.
- 04
What requires human authority
Approval points, accountable roles, escalation and stopped states.
- 05
What happens when access ends
Connection withdrawal, credentials, export, retention and deletion arrangements.
The information journey
One flow. Five places to stay precise.
The route varies by service and connection. Retention and access are established around the work being delivered.
The route has a purpose.
The connection and capability are made available for the agreed work.
Permission boundaryOnly useful context should travel.
Arthur or an external intelligence service may process the context required by the workflow.
Transient or operationalThe result has a defined state.
Working context, durable memory, prepared work and approval are treated differently.
Retention by designImportant activity remains explainable.
Relevant outputs, sources and approvals can remain connected to the result.
Evidence and outcomeTransient processing
Context used for a particular operation.
Operational storage
Records needed to deliver and govern the service.
Arthur memory
Working and durable knowledge states.
Logs & evidence
Relevant action, approval and incident history.
Backups
Recovery copies with their own treatment.
Trust principles
Control should remain understandable to the people accountable for it.
Useful intelligence does not require vague access or invisible authority.
Access is not ownership
Your organisation remains the owner of its information. DELTAGUARD treats access as permission granted for an agreed purpose.
Organisational boundaries matter
Arthur works inside named organisational context. Each commissioned information path is considered against that boundary.
Connections are deliberate
Sources, accounts and capabilities are connected for a defined reason, using the access needed for the work.
People retain authority
Sensitive or state-changing work can be placed behind approval according to the capability and the organisation’s rules.
Important activity should be explainable
Evidence, approvals and relevant execution records help people understand what happened and why.
Information handling is specific
Processing, operational storage, memory, audit evidence, backups and retention are different matters and are addressed as such.
Third-party intelligence providers
External capability. Organisational continuity remains with Arthur.
Arthur can use external intelligence services where a workflow benefits from them. DELTAGUARD treats those providers as replaceable capabilities—not as the owner or sole home of the organisation’s operating knowledge.
Where provider processing matters, the provider, necessary context and applicable handling terms can be discussed before the connection is commissioned.
Organisation knowledgeScoped context
Operational records
EvidenceArthur’s continuity layer
Operational records
EvidenceArthur’s continuity layer
Arthurpurpose · context · providerProvider AExternal processing
Provider BExternal processing
Replaceable capabilityCONFIDENTIAL / FIRST
Confidentiality & NDA
Confidential before anything connects.
DELTAGUARD is prepared to agree appropriate confidentiality and NDA protections before sensitive operational detail is shared. Controlled disclosure begins with knowing who needs the information and why.
Direct answers
The questions a responsible director should ask.
Specific answers create more confidence than generic claims.
01What can Arthur see?
Only the systems and information made available for the authorised work. Becoming a DELTAGUARD client does not automatically connect email, documents, finance, CRM or any other system.
02Can another organisation see our information?
Arthur’s client-facing memory and projections are scoped to the organisation. Every additional commissioned data path is assessed against that organisational boundary before it is used.
03Can DELTAGUARD personnel see everything?
No unrestricted staff access is implied by a client relationship. Where delivery or support requires DELTAGUARD access, who needs it, why and for how long should be established before sensitive information is shared.
04Where does information go?
That depends on the authorised workflow. Information may stay in a connected client system, pass through controlled processing, or be retained as an operational record, Arthur memory, evidence or recovery copy. Arthur distinguishes short-lived working context from durable organisational memory. The route and retention are discussed before connection.
05Are external intelligence providers involved?
They may be used for some workflows. Where they are relevant, DELTAGUARD can explain the provider, the context needed for the work and the applicable handling terms before that workflow is commissioned.
06What happens when our relationship ends?
The exit arrangement should address connection withdrawal, credential revocation, export where applicable, operational retention, backups and deletion. These are agreed for the service rather than hidden behind one blanket promise.
Security before sales.
Talk about the boundary before connecting a single system.
You do not need to send sensitive information to discuss confidentiality, architecture, permissions or information handling with DELTAGUARD.