How safe is it to give an AI access to the books? Here is how it works.
The service is a server between your AI app and Fortnox. You sign in to Fortnox and choose the company. The assistant reads when you ask, and a change is sent only once you have seen and approved exactly that content. Your books stay in Fortnox — we have no copy and no passwords.
The path a question takes, in five steps.
You ask in your AI app
You write in ChatGPT or Claude as usual — or in Copilot, which has not yet been tested in a live Microsoft environment. The chat takes place at your AI provider and is governed by your agreement with them, just as when you chat without us.
The assistant picks a tool
Every tool is marked as reading or changing, so the app knows the difference before anything runs. A read runs directly. A change is prepared first and shown to you in plain language.
The service calls Fortnox
The call goes to the company you chose, with the access you approved in Fortnox. A company set to read-only cannot be changed, whatever the assistant asks for.
The answer passes straight through
Fortnox answers, and the data goes through the service back to your AI app. We do not store it.
What remains afterwards
In Fortnox the change shows as usual. With us, one line in the change log for each change sent, and one log line without content for each call. Everything we keep is in the list further down.
Does the assistant do things without asking?
No. It is the most common question, and the answer has several layers — and the most important one sits with us, not in the AI app.
Approval lives on our server
A change is prepared, shown to you in plain language, and can only be sent with the approval that belongs to exactly that content. Change a single detail and you approve again. This holds even if the AI app is set to allow everything.
The AI app asks too
ChatGPT and Claude ask before a changing tool runs. In Claude you can also set, tool by tool, whether it is allowed, needs a question first or is blocked. Copilot has not yet been tested in a live Microsoft environment.
Read or change — per company
You choose when connecting whether the assistant may propose changes, and can change it for each company at any time on your connection page.
Guard rails you need not think about
A change is never sent twice, not even if two calls arrive at once — an unclear one is checked with Fortnox instead of re-sent. Files in the inbox and archive can be removed, but at most three per half hour, and each proposal says how many are left. Booked vouchers cannot be deleted by any integration. A warning when something is dated into a closed financial year, and a check of the e-invoice before it is sent.
A warning about changed payment details
If a supplier got a new bankgiro in the register shortly before a payment, or an invoice points to a different account than the register, we warn you — in the chat and at the top of the weekly letter.
Everything we keep, where it is kept, and for how long.
- Your bookkeeping
- Passes through the service while a question is answered and is sent on to your AI app. We do not store it — no copy, no registers, no invoices. So that follow-up questions are quick, what was fetched is kept in working memory for at most three minutes, never on disk, and a change made through the service clears it at once.
- Files you upload
- Go from your browser through the service straight into Fortnox, via a one-time link valid for 30 minutes. They are not stored in between.
- Access to Fortnox
- Encrypted with AES-256-GCM. A connection unused for 30 days lapses by itself.
- Your email address
- Optional. Used only for notices about price and terms, and removed when the connection is removed.
- The weekly letter
- If you have signed up: the address, the weekday and the company. The figures in the letter are fetched when it is written and not stored. If you stop the letter, the address is removed.
- The change log
- Every change sent: what, when, to which company and how it went, with Fortnox's response and the record read back. Encrypted, cannot be altered afterwards, and you can read it yourself.
- An approval in progress
- The content of a proposed change while you decide. Removed automatically after ten minutes.
- Search texts
- What the assistant searches for among the service's functions, so we can see what customers miss. Encrypted and deleted after 90 days.
- Operational logs
- Which kind of call, whether it succeeded and which company it concerned — never the content of an answer or a change. Deleted after 90 days at the latest.
- Backups
- Encrypted copies of the access register and the change log, in the same region as the service.
- Where
- Amazon Web Services in Ireland. We move no data out of the EU; what the assistant fetches becomes part of the chat at your AI provider, under your agreement with them.
- Your AI provider
- OpenAI, Anthropic or Microsoft. They are not our sub-processors, and what they keep of the chat is governed by your agreement and your settings with them.
The formal text is in the privacy information (in Swedish).
The papers your accountant will ask for.
Controller and processor
You are the controller of the data in your bookkeeping. We are the processor for what passes through the service when you ask, and process it only on your instructions. Data processing →
Named sub-processors
One: Amazon Web Services in Ireland, for hosting, email and backups. We tell you before engaging any other. Sub-processors →
If something goes wrong
If a personal data breach touches your data, we get in touch without delay and give you what you need to report it to the Swedish Authority for Privacy Protection yourself. Security questions go to info@amore.cloud.
Certifications, honestly
We are not ourselves certified to ISO 27001 or SOC 2; we are a small company and do not want to sound like anything else. Amazon Web Services, where the service runs, is certified to both.