Security and trust
How the Companion protects you
This page explains, in plain words, how your data is handled, who holds which keys, what stopping an agent guarantees, what we have tested, and how to report a security issue.
Your data
| Who | What they can see |
|---|---|
| The AI company | Only what your rules let an agent read, with names, accounts, addresses and other protected details replaced by tokens such as SUPPLIER-1. Never your limits, approved lists or sealed instructions. |
| Your own tools | Real details, and only for actions your rules allow or a person approved. |
| DynaGuard's servers | Your organisation's records, with protected details and names stored encrypted. With your own key turned on and locked, our servers cannot read protected details. |
| Your bank | Only the payment order file your team chooses to submit. |
The boundary: the Companion protects what goes through it. Anything typed, pasted or uploaded directly into an AI chat has already reached that AI company. Use Protect (text or files) before you paste or upload.
Each organisation is kept completely separate. The owner can export all data, or delete the organisation for everyone, at any time. The service runs on DigitalOcean cloud servers, and every connection is encrypted (HTTPS).
Who holds which keys
- Your passkey stays on your device and is unlocked by your face, fingerprint or device PIN. DynaGuard keeps only its public part.
- Your signing keys are created by your Companion. The rules you give agents and the approvals you make are signed with post-quantum cryptography.
- Files you protect (Word, Excel, CSV and PDF) are processed in memory and never stored. Only their tokens are kept, as for text. Pictures removed from Word and Excel files are kept sealed with your organisation's key for 30 days, so that a restored copy gets its logos, stamps and signatures back; then they are deleted automatically. Pictures in PDFs are not kept. Every protected file is checked again for every original detail before it is released.
- Your own protected words are sealed like every other protected detail. Activity records that words were added, approved or removed, never the words themselves. In a team, words a member asks to protect for everyone wait for an owner or approver.
- Paragraphs you choose in a file are listed only on your own screen; the file is read in memory to build the list and is not stored. Each chosen paragraph is replaced by one code, and comes back only when you restore the AI's file on your device.
- Pairing your own agents uses a short code that works once, for 10 minutes; only a keyed hash of it is stored. The agent receives its credentials only after you approve on your phone with your passkey, once, directly; they are then deleted from our server and are never shown on a screen.
- Your own key (optional) is held by your organisation, protected by your passkeys and an organisation passphrase. While it is locked, DynaGuard cannot read protected details. While you unlock it for a work session, the service can use them for that session only. If every passkey and every copy of the passphrase is lost, nobody can recover the protected details, including DynaGuard.
What stopping an agent guarantees
- At once: the agent's sign-in and authority end, so it cannot start any new action. Its helper agents stop too.
- Cancelled: every request still waiting for approval, and every approved request that has not started yet.
- Already running: an action that was already being carried out is not interrupted. It finishes and is recorded, or is shown as outcome unknown if the tool does not confirm. Check Activity and the tool before trying again.
Compatibility
| Client | Status (October 2026) |
|---|---|
| Claude (claude.ai and the Claude desktop app) | Tested by DynaGuard with the custom connector and sign-in. |
| Your own agents through REST | Tested by our automated tests, following the quickstart on our home page. |
| Your own agents through MCP (Streamable HTTP) | Tested by our automated tests. |
| ChatGPT, Copilot, Gemini and other apps | Designed to work where the app and your plan support remote MCP connectors with sign-in. Not yet tested by us: tell us if you try one. |
Testing and reviews
- Every release: automated end-to-end tests of approvals, refusals, limits, helper agents, detail protection, file protection, payment orders, export and deletion, plus journeys in real browsers; and a check that every third-party component has a licence that does not oblige publishing our code.
- Internal security review, October 2026 (release 3.0): a review with attack tests covering sign-in and approvals, agent authority and helper limits, detail protection, payment orders, outbound connections to your tools, and data deletion. All findings were fixed before release 3.0.1, each with a test that keeps it fixed.
- External assessment: planned during the pilot. We will publish a summary of its scope and date here.
How payments work
- Bank-ready payment orders. An approved payment becomes a signed ISO 20022 payment order, with a PDF and a proof, that your own bank or finance team executes. Money only moves through your bank's own controls.
- Any time of day, in your currency. Payment orders can be issued around the clock, in your organisation's own currency, up to its highest limit.
- Signed by your organisation. These payment settings are signed by your organisation's own top-level authority and checked by your Companion in every payment authority. Raising a limit needs a second device, a second person and a 24-hour wait.
Report a security issue
Email md@dynaguardtechnologies.com with the subject Security report. Include what you found, how to reproduce it and the time it happened. Please do not access other people's data, and give us reasonable time to fix the issue before sharing it. Never send passphrases, agent secrets or passkey details.
Privacy
Pilot organisations receive our Privacy Notice with their invitation. It explains what we collect, why, how long we keep it and your rights. To read it before joining, email md@dynaguardtechnologies.com.
Terms
Use of the Companion during the pilot is governed by the Pilot Terms agreed with each pilot organisation. To request a copy, email md@dynaguardtechnologies.com. DCT-A is patent pending.