How safe is it?
Here is how it works when an AI gets access to your books.
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 checks, as you see them.
| Account | Debit | Credit |
|---|---|---|
| 6110 Office supplies | 1,000.00 | |
| 2641 Input VAT | 250.00 | |
| 1930 Business account | 1,250.00 | |
| Total | 1,250.00 | 1,250.00 |
Example. Nothing is sent until you press Approve.
| Company | Access |
|---|---|
| Norrsken Bygg AB | Read and propose changes |
| Norrsken Fastigheter AB | Read only |
| Norrsken Holding AB | Read only |
Changed whenever you like on your connection page. Example.
Different bankgiro on the invoice than in the register. Nordvik Kontorsservice, SEK 3,000, due Friday.
New supplier with a large invoice. Sandhamn Ventilation, SEK 35,750, no earlier invoice.
Call the supplier on a number you already have before you pay.
Example.
Connected. Ask about your books.
The path a question takes, in five steps.
You ask in your AI app
You write in ChatGPT, Claude, Gemini or Grok as usual — or in Copilot. 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?
Not unless you chose it. 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 is bound to the content
A change is shown in plain language and can only be sent with the approval for exactly that content. Change a detail and it must be approved again. It is the AI app that asks you, so keep it asking before changes; ChatGPT and Claude do so from the start. Deletions, sending, credits and changed payment details you also approve on a page of our own.
Automatic attachments, if you want them
Whoever connected the company can, under Advanced settings, let documents be attached to existing records without a yes each time. An attachment changes no amounts and can be removed. Off from the start.
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.
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. 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 email.
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 an upload link valid for 30 minutes. They are not stored with us. |
| Access to Fortnox | Encrypted. A connection unused for 30 days lapses by itself. |
| Your email address | Optional. Used for notices about the terms, when a company is added to your connection, when someone asks for access and when an invitation is used. When a company is added, the address is shown in the email to that company. Removed when the connection is removed. |
| The weekly email | 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, you can read it yourself, and deleted after 90 days. |
| 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. Not saved at all when the company uses protection mode. |
| Operational logs | Which kind of call, whether it succeeded and which company it concerned, and for visits the IP address and browser — never the content of an answer or a change. Deleted after 90 days at the latest. |
| Backups | Encrypted copies of what the service stores, in the EU. Kept for 90 days; what has been deleted leaves the backups within the same time. |
| Where | In the EU. We move no data out of it; what the assistant fetches becomes part of the chat at your AI provider, under your agreement with them. |
| Your AI provider | OpenAI, Anthropic, Google, Microsoft or xAI. 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 (English summary of the binding Swedish text).
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, for hosting, email and backups, in the EU. We tell you at least 30 days before engaging any other. Sub-processors →
If something goes wrong
If a personal data breach touches your data, we get in touch without undue 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. Our hosting provider in the EU is certified to both.
Protection mode
Turn off bank transactions, the customer register, payroll and employees or documents and files for the connection, company by company. What is turned off never reaches the assistant. It is under Advanced settings on the connection page.
Your AI provider’s terms
What the assistant fetches becomes part of the chat with your AI provider, under your agreement with them. Which plans have a data processing agreement and do not train on your content: AI providers’ terms →