Security and your data
What this covers
For IT and data-protection officers: how the agent connects, what it can and cannot do, what it reads, and where data is kept.
Before you start
Nothing to prepare. This page describes the agent as it ships.
How the agent connects
- Outbound HTTPS only. The agent calls GoRoute. GoRoute never calls the PC, and no port is opened on any network interface. No VPN, fixed IP address or firewall rule is needed beyond outbound HTTPS.
- Its own window is local. The status window and the readiness report are served on
127.0.0.1, which only that PC can reach. - It runs as a Windows user, not as a service. It installs per user with no administrator rights, and starts when that user signs in.
What it can do in Sage
- It only reads. The agent signs in to Sage as a dedicated
GOROUTEuser that you create with read-only rights, and reads through the Sage ODBC driver, which is read-only whoever signs in. Two separate controls stop it writing to Sage. - Nothing is installed inside Sage. No add-in, no Sage Data Objects, no Sage Developer Programme membership, and no Enable 3rd Party Integration. Do not switch that option on for the agent: it does not use it.
- No ODBC data source is created. The agent opens the company by its data path, so nothing is registered on the PC.
- Supplier invoices go in only when a person imports them. The agent writes an import file. A person imports it in Sage with File ▸ Import.
- Only ticked companies are read. A company you did not tick at install is never opened.
What it reads
| From Sage | Why |
|---|---|
| Posted sales invoices and credit notes from the Invoicing module, with their lines and tax codes | To build the e-invoices |
| Customer records: name, address, country, VAT number, e-mail and the Peppol address field | To address each e-invoice |
| Supplier records: name, VAT number and currency | To match supplier invoices |
| Tax codes and currency rates | To map VAT and write foreign-currency invoices |
| The company's own name and VAT number | To check they match your GoRoute account |
| Audit trail entries carrying a GoRoute reference | To find the supplier invoices you imported |
It does not read payroll, bank transactions, stock or any other part of Sage.
Keys and passwords
- Enrolment code. Shown once in the portal, single use, valid for 15 minutes. GoRoute keeps only a fingerprint of it, and repeated attempts are rate-limited.
- The agent's key. At enrolment GoRoute gives the agent a key of its own, for this connection only. It is stored encrypted with Windows Data Protection (DPAPI) for the Windows user, so another user or another PC cannot read it. It is never shown, typed or logged.
- The Sage password for
GOROUTEis stored the same way, and saved only after Sage accepts it. - Rotate key in the portal replaces the key. Remove stops the agent at its next check.
Updates
The agent installs an update only when the file matches the one GoRoute published and carries a valid ClayDesk code signature. A file that fails either check is deleted, not run.
What is stored where
| Where | What | How long |
|---|---|---|
The Sage PC, %APPDATA%\GoRoute\Sage50Agent | Settings, tax-code table, the queue of invoices and their outcome, the log | Until you delete it |
The Sage PC, C:\Users\Public\Documents\GoRoute Sage 50\Supplier invoices | The day's import files and the suppliers' PDFs | Until you delete them |
| GoRoute | Every e-invoice sent and received, with its delivery evidence, as for any GoRoute transaction | Your account's retention |
| GoRoute | The agent's status: computer name, Windows user name, agent, Sage and Windows versions, counts | While the connection exists |
| GoRoute | Diagnostics you request: a log extract and the agent's settings | 30 days |
Logs
The log, agent.log in the agent's data folder, records each check and each send. It never holds
the key or a password. The readiness report carries no invoice amounts and no key, so it is safe to
e-mail. Diagnostics never include the key or a password.
What you should see
On the Sage PC, a per-user program under %LOCALAPPDATA%\GoRoute\Sage50Agent, an entry in the
current user's start-up list, and no new service, port or data source.
If it does not work
If your security tooling flags the agent, check the file's digital signature: ClayDesk LLC. Then contact admin@goroute.ai.
Written for agent 0.2.x and the GoRoute portal release of 31 October 2026.